I'm trying to setup the group replication plugin I specified all settings in /etc/mysql/my.cnf and did the appropriate firewall rules: However I cannot connect to the remote server. There are two different public IP address servers and not a local machine.
The ufw output settings on the target server: Iptables is not installed.
To Action From
-- ------ ----
33061 ALLOW IN Anywhere
3306 ALLOW IN Anywhere
22 ALLOW IN Anywhere
80 ALLOW IN Anywhere
443 ALLOW IN Anywhere
80,443/tcp ALLOW IN Anywhere
33061/tcp ALLOW IN Anywhere
33061 (v6) ALLOW IN Anywhere (v6)
3306 (v6) ALLOW IN Anywhere (v6)
22 (v6) ALLOW IN Anywhere (v6)
80 (v6) ALLOW IN Anywhere (v6)
443 (v6) ALLOW IN Anywhere (v6)
80,443/tcp (v6) ALLOW IN Anywhere (v6)
33061/tcp (v6) ALLOW IN Anywhere (v6)
Error Log output
2018-05-25T17:36:41.825416Z 0 [Note] Plugin group_replication reported: 'XCom protocol version: 3'
2018-05-25T17:36:41.825460Z 0 [Note] Plugin group_replication reported: 'XCom initialized and ready to accept incoming connections on port 33061'
2018-05-25T17:36:41.912783Z 0 [ERROR] Plugin group_replication reported: '[GCS] Error on opening a connection to {remote IP}:33061 on local port: 33061.'
If i check the remote port I get:
root#li111-4:/etc/nginx/sites-available# nc -zv {remote IP} 33061
nc: connect to {remote IP} port 33061 (tcp) failed: Connection refused
Related
while doing oc port forward:
oc port-forward container_name 5679 5679
getting this error:
Unable to listen on port 5679: Listeners failed to create with the following errors: [unable to create listener: Error listen tcp4 127.0.0.1:5679: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted. unable to create listener: Error listen tcp6 [::1]:5679: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.]
tried different ports but still getting same error
I recently ran into a problem that mysqld service wasn't running.
I checked the MySQL's wamp log and got the following messages:
[ERROR] Can't start server: Bind on TCP/IP port: No such file or directory
[ERROR] Do you already have another mysqld server running on port: 3306 ?
So I ran it and realized that my TCP port 3306 was already running with another mysqld.exe process
netstat -ano|find "3306"
TCP 0.0.0.0:3306 0.0.0.0:0 LISTENING 4576
TCP 0.0.0.0:33060 0.0.0.0:0 LISTENING 4576
TCP [::]:3306 [::]:0 LISTENING 4576
TCP [::]:33060 [::]:0 LISTENING 4576
after that I went to Task Manager and found the 4576 PID which was the other mysqld.exe running. So I finished the task and restarted my WAMP server, and all services went smoothly.
The problem probably occurred because I've got two wamp servers installed, don't ask me why... Hope I can help someone with this same problem.
I installed a Cloud Datalab notebook on a Cloud Dataproc cluster following the instructions listed in the official documentation
After creating the cluster, I then created a SSH tunnel to the master node in the Cloud Shell and connected to the cluster interface using the Cloud Shell. Instructions. I could access the Jupyter notebooks after this. I used the -v verbose option to see the SSH connection logs:
gcloud compute ssh cluster-datalab-m --project=abcxyz-123 --zone us-west1-a \
-- -v -4 -N -L 8080:cluster-datalab-m:8080
But after some time, I got a popup saying "A connection to the notebook server could not be established. The notebook will continue trying to reconnect. Check your network connection or notebook server configuration." and my cluster stopped responding to any commands.
When I looked at the SSH output on the Cloud Shell, I saw that multiple channels were being requested at this point.
A preview of SSH logs just during the break point:
debug1: channel 1: new [direct-tcpip]
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 2: new [direct-tcpip]
debug1: channel 1: free: direct-tcpip: listening port 8080 for cluster-datalab-m port 8080, connect from 127.0.0.1 port 52832 to 127.0.0.1 port 8080, nchannels 3
debug1: channel 2: free: direct-tcpip: listening port 8080 for cluster-datalab-m port 8080, connect from 127.0.0.1 port 52833 to 127.0.0.1 port 8080, nchannels 2
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 1: new [direct-tcpip]
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 2: new [direct-tcpip]
debug1: channel 2: free: direct-tcpip: listening port 8080 for cluster-datalab-m port 8080, connect from 127.0.0.1 port 52837 to 127.0.0.1 port 8080, nchannels 3
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 2: new [direct-tcpip]
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 3: new [direct-tcpip]
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 4: new [direct-tcpip]
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 5: new [direct-tcpip]
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
debug1: channel 6: new [direct-tcpip]
debug1: Connection to port 8080 forwarding to cluster-datalab-m port 8080 requested.
I closed this SSH connection manually and then tried to SSH into the master node by clicking the SSH button on the Compute Engine console but even that was taking lot of time and didn't complete successfully.
I looked at this stackoverflow question but I couldn't find any /etc/sshguard folder in the master node so I don't think that is the issue for my case. The master node was running Debian 8.10.
Is there any way to ensure that the SSH connection (and the Jupyter notebook) works continuously?
We've updated the documentation at cluster web interfaces. Using cloud shell works for Datalab, but not Jupyter. Cloud Shell Preview only supports HTTP, but Jupyter uses websockets.
Instead, you should follow the instructions for setting up a SOCKS proxy and pointing Chrome at it. There's a handy bash script called launch-jupyter-interface.sh that does that for you. You'll just need to modify it to point to your Chrome installation.
The Jupyter tutorial also mentions using that script.
I'm trying to connect to MySQL remotely with pymysql and I'm getting the error message:
(2003, "Can't connect to MySQL server on 'ip address' ([WinError 10061]
No connection could be made because the target machine actively refused it)")
In my my.cnf file I've got bind-address set to 0.0.0.0 and skip-networking isn't there.
Running "sudo netstat -atn" shows port 3306 is only listening on localhost:
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN
My firewall allowing traffic from 3306:
To Action From
-- ------ ----
22/tcp ALLOW Anywhere
22/udp ALLOW Anywhere
80/udp ALLOW Anywhere
80/tcp ALLOW Anywhere
443/tcp ALLOW Anywhere
443/udp ALLOW Anywhere
3306/tcp ALLOW Anywhere
3306/udp ALLOW Anywhere
22/tcp (v6) ALLOW Anywhere (v6)
22/udp (v6) ALLOW Anywhere (v6)
80/udp (v6) ALLOW Anywhere (v6)
80/tcp (v6) ALLOW Anywhere (v6)
443/tcp (v6) ALLOW Anywhere (v6)
443/udp (v6) ALLOW Anywhere (v6)
3306/tcp (v6) ALLOW Anywhere (v6)
3306/udp (v6) ALLOW Anywhere (v6)
I've restarted everything multiple times. I don't think its a MySQL authentication issue. I've got my users host set to '%'. How do I set the server to listen to any address on 3306, not just 127.0.0.1?
Edit:
Here's the output from 'ps auxf | grep mysqld
':
root 15493 0.0 0.4 11988 2072 pts/0 S+ 12:25 0:00 \_
grep --color=auto mysqld
root 25057 0.0 0.3 4448 1540 tty1 S Jun13 0:00 \_
/bin/sh /usr/bin/mysqld_safe --skip-grant-tables
mysql 25415 0.1 8.8 821124 44224 tty1 Sl Jun13 8:04 \_
/usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-
dir=/usr/lib/mysql/plugin --user=mysql --skip-grant-tables --log-
error=/var/log/mysql/error.log --pid-file=/var/run/mysqld/mysqld.pid --
socket=/var/run/mysqld/mysqld.sock --port=3306
mysql 15361 0.2 7.4 380788 37416 ? Ssl 12:24 0:00
/usr/sbin/mysqld
15042 0.0 7.4 380788 37164 ? Ssl 12:21 0:00 /usr/sbin/mysql
d
10061 is WSAECONNREFUSED, 'connection refused', which means either a firewall (unlikely) or more probably nothing listening at the IP:port you tried to connect to.
Background: I've been connecting to MySql from Windows to an Ubuntu VM through putty's ssh tunnel for years now, and it's worked great.
2 weeks ago I started up a new Ubuntu 16.06 amd64 VM, put the latest MariaDb on it, and everything worked as before. Workbench worked, and my code was able to connect through the tunnel as well.
Last week, the connection somehow became unstable. It would not connect anymore, and timeouts would occur 100% of the time until it mysteriously started working again. Even now, at the beginning of writing this question, it was not working. Now it is. It has sometimes not worked when ufw was disabled completely. Does anyone know what is going on? Are there timeouts or cooldowns on the various pieces that I'm not aware of? I've restarted the service countless times, and the VM many times as well.
Configuration:
my.cnf:
bind-address = 127.0.0.1
ufw:
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip
To Action From
-- ------ ----
80/tcp ALLOW IN Anywhere
443/tcp ALLOW IN Anywhere
22/tcp ALLOW IN Anywhere
3306 on lo ALLOW IN Anywhere
127.0.0.1 3306/tcp ALLOW IN Anywhere
80/tcp (v6) ALLOW IN Anywhere (v6)
443/tcp (v6) ALLOW IN Anywhere (v6)
22/tcp (v6) ALLOW IN Anywhere (v6)
3306 (v6) on lo ALLOW IN Anywhere (v6)