Hey gang So my current Netmaker setup seem to be working fin GRAVITL #client

Hey gang! So my current Netmaker setup seem to be ...

few-airline-95046

06/12/2022, 8:41 PM

Hey gang! So my current Netmaker setup seem to be working fine, I have a bunch of nodes that seem healthy and they can all speak to each other... but then I stumbled upon some errors in the MQ logs.

Copy code

655066103: New connection from 172.19.0.3:47836 on port 8883.
1655066103: OpenSSL Error[0]: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate
1655066103: Client <unknown> disconnected: Protocol error.

This doesn't seem to be a result from any of my nodes, as I occasionally see them in the MQ logs without errors. I also validated the certs with both openssl and mosquitto_pub from each node, and got good results... So what are there error messages coming from? They appear quite often, probably every ~2-3 seconds.

bored-island-21407

06/12/2022, 8:54 PM

Based on the IP address in the it would appear to be a container. Must be either netmaker or trafik. netmaker should be connecting via 1883 not 8883 so it must be trafik. Don't think the default logging on trafik provides enough info on what is being proxies. Something is trying to connect to sssl://broker.yourdomain.com

few-airline-95046

06/12/2022, 9:00 PM

Hmm, yes, traefik seem to be 172.19.0.3

bored-island-21407

06/12/2022, 9:02 PM

Do you have an old node that you previously set up that is not part of your current network(s)

few-airline-95046

06/12/2022, 9:05 PM

I had that thought too but couldn't figure out which machine that would be...but come to think of it, it could be a RPI. gonna check that one 😄

few-airline-95046

06/12/2022, 9:15 PM

hmm, the RPI had an outdated netclient running, but uninstalling didn't stop the mq logs from continuing with the

alert bad certificate

few-airline-95046

06/12/2022, 9:39 PM

I think I found the culprit. My two Unraid nodes which is running netclient daemon. Looking at htop with the tree view, I could see two different netclient daemon running. Killing off the processes on both unraid machines and the error logs in MQ stopped.

few-airline-95046

06/12/2022, 9:40 PM

Not sure what's wrong though... both those nodes did show up in the mq logs without errors as well.

Copy code

2022-06-12T21:32:54.369045156Z 1655069574: New connection from 172.19.0.3:52294 on port 8883.
2022-06-12T21:32:54.377486791Z 1655069574: New client connected from 172.19.0.3:52294 as us5t0DQkg9fC7CxFVLrJSXg (p2, c1, k30, u'Cradle').
2022-06-12T21:32:54.382531348Z 1655069574: Client us5t0DQkg9fC7CxFVLrJSXg disconnected.

bored-island-21407

06/12/2022, 9:42 PM

if you had two netclient processes running (probably different versions), one of them could be connecting correctly and the other generating errors

few-airline-95046

06/12/2022, 9:45 PM

Sounds plausible. Restarted the daemon on both machines now and all looks good so far 🙂

2 Views

Previous Next