5037 is not occupied and the error message is reply fd for adb server to client communication not specified. The version of adb is 1.0.39. I want to share port for STF Provider. Appreciate for any help.
As Moon said in his comment: the solution is to run
adb -a -P 5037 daemon
and then
stf provider --adb-host ip -port 5037
Related
I am attempting to create a Docker container from a SQL Server image using the following Docker command:
docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=p#$$w0rd!" -p 1433:1433 --name sql2 -d microsoft/mssql-server-linux:2017-latest
However, the running the command tells me that port 1433 is already in use:
docker: Error response from daemon: driver failed programming external
connectivity on endpoint sql2
(6cfcd552054d9e9d62d1e9ec1c11a6c5051e6912cc6658e12b0bc5e992c30cfd): Error
starting userland proxy: Bind for 0.0.0.0:1433 failed: port is already allocated.
There are no other existing containers, and running the docker container ps -a command displays the container, but without a specified port.
Can anyone tell me why I am getting this error message and what can be done to fix it?
(Windows 10 -- Docker for Linux)
You probably have SQL Server installed that is using port 1433. You can
1) Use a different port
2) Shut down SQL Server service (using services.msc)
Please see the command below:
docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=Password1" -p 1433:1433 -d microsoft/mssql-server-linux:2017-latest
After I run this command I can connect to the database using SQL Studio manager as shown below:
I can also connect using: 192.168.99.100,1433.
Next I remove the container and execute the following command:
docker run -e "ACCEPT_EULA=Y" -e "SA_PASSWORD=Password1" -p 600:600 -d microsoft/mssql-server-linux:2017-latest
I have made up the port here. Now, please see the screenshot below:
1) Why is the tcp port 1433?
2) Why can I not connect to the database on port 500?
I realise the documentation tells you to use port 1433 as shown here: https://hub.docker.com/r/microsoft/mssql-server-linux/. However, it does not tell me why.
(1) The image Dockerfile presumably says EXPOSE 1433 because that's the port the server listens on; the bare 1433/tcp output in docker ps means that port isn't published to the host.
(2) When you docker run -p 600:600, you tell Docker to forward port 600 on the host to port 600 in the container. Nothing's listening on that port, so you can't connect.
(3) If you docker run -p 600:1433, you'd tell Docker to forward port 600 on the host to port 1433 in the container, where the server is listening, and I would expect this to work.
I'm trying to setup SQLserver on my mac using Docker.
When I start it, it seems to be working, but when I try to connect with mssql, it crashes.
I have tried with localhost instead of 0.0.0.0, same result.
iMac benoitd$ **docker run** -e 'ACCEPT_EULA=Y' -e 'SA_PASSWORD=DB22017' -p
1433:1433 -d microsoft/mssql-server-linux
ee2f1a94410dfb6e5f39ba009ffee20b906270e9602d831ff2344e93d2ec5d14
iMac benoitd$ **docker ps**
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
ee2f1a94410d microsoft/mssql-server-linux "/bin/sh -c /opt/mssq" 4 seconds ago Up 2 seconds 0.0.0.0:1433->1433/tcp awesome_mahavira
iMac benoitd$ **mssql -s 0.0.0.0:1433 -u sa -p 'DB22017'**
Connecting to 0.0.0.0:1433...
Error: Failed to connect to 0.0.0.0:1433:1433 - getaddrinfo ENOTFOUND 0.0.0.0:1433 0.0.0.0:1433:1433
iMac benoitd$ **docker ps**
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
d'oh.... the problem was with the password for sql server. It need to be a strong pw.
thanks for your help! and happy new year :)
i have got a new Linux Server (Debian 6.0) with a Database (MySQL) which is accessed by Port 3306 like as usual.
Now I'd like to access the database due port problems of some users (because port 3306 is often blocked by network firewalls) by port 80 or 443. So the transfer must be redirected from Port 80 to 3306 to keep the Database working.
I have tried following command:
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT --to-port 3306
but I got following error:
iptables: No chain/target/match by that name.
Does anyone can help me solve this problem? The NAT table is empty (PREROUTING,POSTROUTING,OUTPUT have no entries) (checked with iptables -t nat -n -L)
In iptables Kernel modules required for NAT functionality:
Run following command to load modules in kernel:
# modprobe iptable_nat
# modprobe ipt_REDIRECT
Make sure you have above modules compiled in kernel:
[root#instructor tmp]# grep REDIRECT /boot/config-$( uname -r )
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_BRIDGE_EBT_REDIRECT=m
In VPS Server:
Enable modules on host server using modprobe command
Execute following command from the host server to enable all the modules for the VPS
vzctl set VEID --iptables iptable_nat --iptables ipt_REDIRECT
Add rules in file /etc/vz/conf/veid.conf
IPTABLES="iptable_nat ipt_REDIRECT"
I have started the pgpool using the command
sudo pgpool -n &
it started giving the following message on the terminal:
2012-05-04 10:54:29 LOG: pid 4109: pgpool-II successfully started. version 2.3.2.1 (tomiteboshi)
But when I try to run the following command:
createdb -p 9999 bench_replication
I get the following error message:
createdb: could not connect to database postgres: could not connect to server: No such file or directory.
Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.9999"?
When I change the port from 9999 to 5432, a database bench_replication is created on the local node only, not on slave nodes. But, tutorial say to mention port 9999 in this command in order to create database bench_replication on all slave nodes through pgpool.
To confirm whether pgpool is really running or not, I stop the pgpool using command
2012-05-04 10:58:50 LOG: pid 4109: received smart shutdown request
stop request sent to pgpool. waiting for termination...done.
[1]+ Done sudo -A pgpool -n
which confirms the pgpool was actually running. What am I doing wrong? I have changed all my pgpool configuration file as mentioned in the standard tutorials on net.
Try this command :
createdb -p 9999 -h 127.0.0.1 bench_replication
By default PostgreSQL try to use the socket.
Late response but useful for future generations:
When you run
createdb -p 9999 bench_replication
under root, this generates the following error in log:
no pg_hba.conf entry for host "12.34.56.78", user "root", database
"postgres", SSL off
This means you should explicit mention username just like this:
createdb -U postgres -p 9999 bench_replication
Then you will get another error:
no pg_hba.conf entry for host "12.34.56.78", user "postgres", database
"postgres", SSL off
So you were blocked by second node on HBA level.
In this case either you should allow on second node access from first (in pg_hba.conf):
host all postgres 12.34.56.77 trust
or you should set password:
createdb -U postgres -p 9999 bench_replication -W SoMeP4Ssw0rD
If this is not clear enough - just check for your logs.