meteohub.de

I'm on Rpi 3B and This is happening every 4 or 5 days where whatever happens knocks out all sensor reporting, everything just fails no sensors from any of the stations at all. The gw1000 is station 2, I have a 8 xmiter Davis as 0 and a purple air as 1.

Messages
logger (17.04.2021 19:46:56): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (17.04.2021 19:46:56): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:47:04): message above repeats 27366 times.
logger (17.04.2021 19:47:05): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (17.04.2021 19:47:05): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:47:24): message above repeats 72029 times.
logger (17.04.2021 19:47:25): station 2 (GW1000), error make socket 10.24.1.103: port 45000: Invalid argument
logger (17.04.2021 19:47:25): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:47:35): message above repeats 39696 times.
logger (17.04.2021 19:47:35): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (17.04.2021 19:47:35): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:47:54): message above repeats 86753 times.
logger (17.04.2021 19:47:55): station 2 (GW1000), error make socket 10.24.1.103: port 45000: Invalid argument
logger (17.04.2021 19:47:55): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:48:05): message above repeats 38073 times.
logger (17.04.2021 19:48:05): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (17.04.2021 19:48:05): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:48:24): message above repeats 65104 times.
logger (17.04.2021 19:48:25): station 2 (GW1000), error make socket 10.24.1.103: port 45000: Invalid argument
logger (17.04.2021 19:48:25): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:48:35): message above repeats 40373 times.
logger (17.04.2021 19:48:35): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (17.04.2021 19:48:35): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:48:54): message above repeats 81354 times.
logger (17.04.2021 19:48:55): station 2 (GW1000), error make socket 10.24.1.103: port 45000: Invalid argument
logger (17.04.2021 19:48:55): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:48:57): message above repeats 9680 times.
logger (17.04.2021 19:48:57): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (17.04.2021 19:48:57): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:49:05): message above repeats 21028 times.
logger (17.04.2021 19:49:05): open named pipe "/dev/meteobridge" failed: Invalid argument
logger (17.04.2021 19:49:05): error while doing accept on socket 5557: Invalid argument
logger (17.04.2021 19:49:24): message above repeats 65672 times

and on...

As written by mail, here is my analysis:

1) logger (17.04.2021 19:46:56): error while doing accept on socket 5557: Invalid argument
This is a message from the logger where the logging process is requested to reply the current data in terms of a XML report.
So there must be some device in your network that tries to poll data from Meteobridge. What exactly is that good for?
When you fire that request too often, connections stack up and can make the process stall. Reporting all sensors in a setup with tons of sensors should not be done more often than once a minute. How fast do you poll here?
When filled up the ECONNREFUSED1 status is reported back to the requesting process, but this does not seem to interest your requesting program and it fires the next request immediately. This is why numbers like "logger (17.04.2021 19:47:04): message above repeats 27366 times." show up.

2) logger (17.04.2021 19:46:56): open named pipe "/dev/meteobridge" failed: Invalid argument
When all connections are consumed by 1) elementary functions like sending data to the wnet process are also blocked.

Sorry Boris I didn’t see your email.
The only thing I have running that is polling MeteoBridge is Weather Display, and even that is only for the Davis sensors (Station 0) not the other 2 stations. I don’t think you can adjust how often it polls, and from watching it only polls every few seconds.

What I don’t understand is this never happened before I put the GW1000 onto the MeteoBridge, and why every 4 or 5 days it just suddenly happens?

So this issue occurred again, same error messages after 7 days.
I have removed the the GW1000 from MeteoBridge because reliability is key, and the issue has not reoccurred. I don’t have any programs communicating with the gw1000.

So this is some issue with Meteobridge and it’s interaction with the GW1000 or with large multi sensor setups.

https://www.ecowitt.net/home/share?authorize=JU2JFS
GW 1000 and my MB is resetting !!
reading the last message I don't think we should link this hardware problem to a loss of power and / or something else