meteohub.de

Hello,
Since last reboot my MB Nano SD restart's the logger every round hour with new error-logs on system-protocol:

logger (14.10.2020 09:01:03): databases connected. Update interval 3600 seconds.
logger (14.10.2020 09:01:03): data logger (version 5.1d, build 3475) started.
logger (14.10.2020 09:01:03): error (22) while doing bind (port 22222): Invalid argument
logger (14.10.2020 09:01:03): killed process "17682/sh" listening to port 5553.
logger (14.10.2020 09:01:03): killed process "17683/sh" listening to port 5551.
logger (14.10.2020 09:01:03): killed process "17684/sh" listening to port 5552.
logger (14.10.2020 09:01:03): killed process "17686/meteosys" listening to port 5554.
logger (14.10.2020 09:01:03): killed process "22608/sleep" listening to port 5556.
logger (14.10.2020 09:01:04): data logger stopped.
logger (14.10.2020 09:01:04): databases disconnected.
logger (14.10.2020 09:01:04): parent process to be terminated.
logger (14.10.2020 09:01:33): databases connected. Update interval 3600 seconds.
logger (14.10.2020 09:01:33): data logger (version 5.1d, build 3475) started.
logger (14.10.2020 09:01:33): connect station 0 (Vantage via serial).
logger (14.10.2020 09:01:33): connect station 1 (User-defined via Plug-in).
logger (14.10.2020 09:01:33): connect station 9 (System Data via Plug-in).
logger (14.10.2020 09:01:34): station 0 (Vantage), wakeup sent.
logger (14.10.2020 09:01:37): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (14.10.2020 09:01:37): services paused.
logger (14.10.2020 09:01:37): station 0 (Vantage), no need to update console date/time.
logger (14.10.2020 09:01:37): station 0 (Vantage), setup script executed.
logger (14.10.2020 09:01:38): station 0 (Vantage), internal logger activated.
logger (14.10.2020 09:01:38): station 0 (Vantage), syncing.
logger (14.10.2020 09:01:48): station 0 (Vantage), gettime request sent.
logger (14.10.2020 09:01:48): station 0 (Vantage), no Vantage time offset.
logger (14.10.2020 09:01:48): station 0 (Vantage), eeprom request sent.
logger (14.10.2020 09:01:48): station 0 (Vantage), rain collector size 0.2 mm per tick.
logger (14.10.2020 09:01:48): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (14.10.2020 09:01:48): station 0 (Vantage), transmitter 8 active as station type #7 "Soil".
logger (14.10.2020 09:01:48): station 0 (Vantage), firmware version request sent.
logger (14.10.2020 09:01:48): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (14.10.2020 09:01:48): station 0 (Vantage), no reading of Vantage's internal logger.
logger (14.10.2020 09:01:53): sensors are now providing data.
logger (14.10.2020 09:01:53): services started.

Whats going on there? Do I have to worry that the MB Nano SD will die or is it a negligible problem? In the previous SW/FW-versions (4.3) such an error never appeared. In the settings I disabled the restart of the logger in case of data loss, but this did not change anything. It seems as if the logger tries to establish a connection via port 22222, but I have no remote request from an external program to the station. (as IP logger).
Question: what means "Internen Konsolenverbindung verwenden"?
regards
Michael

Hello,
I think I (don't) have found the cause:
My script for Station #1 air quality sensor had probably set a too short sleeptime for polling the sensor (who has a internal IP-Adress which would explain the binding-error port 22222), it runs at a 5-minute measuring interval instead of the usual 2.5 minutes. Will see what happens in the next full hour...
This is the modified script (300 sec's interval) running to integrate the Air-Quality-Data from my local sensor:

#!/bin/sh
#
while true;
do
data=$(wget --timeout=2 -qO- http://192.xxx.x.x/data.json)
status=$?
if [ $status -ne 0 ] || [ -z "$data" ]; then
>&2 echo "Error retrieving data -> sleeping"
sleep 60
else
age=$(echo $data | tr '{' '\n' | grep age | awk -F '"' '{print $8}')
if [ $age -gt 300 ]; then
>&2 echo "Data too old ($age secs.) -> sleeping"
sleep 30
else
aqi100=$(echo $data | tr '{' '\n' | grep SDS_P1 | awk -F '"' '{printf "%.1f\n", ($8*10.0)}')
if [ ! -z "$aqi100" ]; then
echo "air0 $aqi100"
else
>&2 echo "PM10 not available"
fi
aqi25=$(echo $data | tr '{' '\n' | grep SDS_P2 | awk -F '"' '{printf "%.1f\n", ($8*10.0)}')
if [ ! -z "$aqi25" ]; then
echo "air1 $aqi25"
else
>&2 echo "PM2.5 not available"
fi
# sensor sleeps for 300 secs, 30+ secs for new measurement
sleeptime=$((330-age))
sleep $sleeptime
fi
fi
done

Edit: Unfortunately The error 22 (logger) persists.. Have anyone an idea how to resolve it?
logger (14.10.2020 16:00:31): databases connected. Update interval 3600 seconds.
logger (14.10.2020 16:00:31): data logger (version 5.1d, build 3475) started.
logger (14.10.2020 16:00:31): error (22) while doing bind (port 22222): Invalid argument
logger (14.10.2020 16:00:31): killed process "21664/sh" listening to port 5553.
logger (14.10.2020 16:00:31): killed process "21665/sh" listening to port 5551.
logger (14.10.2020 16:00:32): killed process "21666/sh" listening to port 5552.
logger (14.10.2020 16:00:32): killed process "21667/meteosys" listening to port 5554.
logger (14.10.2020 16:00:32): killed process "26163/sleep" listening to port 5556.
logger (14.10.2020 16:00:32): data logger stopped.
logger (14.10.2020 16:00:32): databases disconnected.
logger (14.10.2020 16:00:32): parent process to be terminated.

Edit2: The error is gone! Today the log from the MeteoBridge is clean since yersterday evenig, i do nothing..
Can't explain it to me, but it's a good one. regards
Michael

xray77 wrote: Wed Oct 14, 2020 9:28 am Question: what means "Internen Konsolenverbindung verwenden"?

Having set this option tells the NANO it should use the connection to the console it is plugged into for getting data.
When you deselect it you can make any weatherstation that can be connected to via TCP/IP your primary weather station.
I your case I would select it, which also reduces follow on options to select from.