NanoSD Continually Reboots

[wilkerjnc]

My NanoSD continually reboots for no apparent reason that I can see.

Some configuration details:

Code: Select all

WiFi Client
Wireless LAN
SSID:	 <SSID Name>
Known SSIDs
WLAN Region:	00 - World
Encryption:	WPA2-PSK
Mode:	auto (2.4 GHz)
Passphrase:	******

Code: Select all

System
Platform:	Meteobridge NANO SD   (ambientweather Version)
RAM:	125 MB total, 48 MB free (61% used)
Storage:	swissbit SLC, 1.8 GB total, 1.8 GB free (3% used, 621.4 yrs)
SW Version:	Meteobridge 5.2 (Aug 16 2021, build 3986), FW 1.4
Uptime:	2 hours, 14 minutes    Buffer: 1 items (0%)

Messages:

Code: Select all

database (01.09.2021 18:01:43): process started.
database (01.09.2021 18:01:43): Content of RAM database restored.
wnetd  (01.09.2021 18:01:48): process started.
system (01.09.2021 18:01:48): start of logging process initiated.
wnetd  (01.09.2021 18:01:48): send data thread started (pid:1961 tid:1963)
logger (01.09.2021 18:01:49): databases connected. Update interval 3600 seconds.
logger (01.09.2021 18:01:49): data logger (version 5.2, build 3986) started.
logger (01.09.2021 18:01:51): connect station 0 (Vantage via serial).
logger (01.09.2021 18:01:51): connect station 9 (System Data via Plug-in).
logger (01.09.2021 18:01:51): station 0 (Vantage), wakeup sent.
logger (01.09.2021 18:01:54): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (01.09.2021 18:01:54): services paused.
logger (01.09.2021 18:01:54): station 0 (Vantage), no need to update console date/time.
logger (01.09.2021 18:01:54): station 0 (Vantage), setup script executed.
logger (01.09.2021 18:01:55): station 0 (Vantage), internal logger activated.
logger (01.09.2021 18:01:55): station 0 (Vantage), syncing.
database (01.09.2021 18:02:04): database sync done (31 tables, 54/2420 writes).
logger (01.09.2021 18:02:05): station 0 (Vantage), gettime request sent.
logger (01.09.2021 18:02:15): message above repeats 1 time.
logger (01.09.2021 18:02:15): station 0 (Vantage), no Vantage time offset.
logger (01.09.2021 18:02:15): station 0 (Vantage), eeprom request sent.
logger (01.09.2021 18:02:15): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (01.09.2021 18:02:15): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (01.09.2021 18:02:15): station 0 (Vantage), firmware version request sent.
logger (01.09.2021 18:02:15): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (01.09.2021 18:02:15): station 0 (Vantage), no reading of Vantage's internal logger.
logger (01.09.2021 18:02:15): station 0 (Vantage), 10.243.1.149's request on port 22222 accepted.
logger (01.09.2021 18:02:23): sensors are now providing data.
logger (01.09.2021 18:02:23): services started.
system (01.09.2021 18:15:28): Access point operation disabled 923 secs after boot.
logger (01.09.2021 19:28:46): station 0 (Vantage), connection on port 22222 closed.
logger (01.09.2021 19:29:46): station 0 (Vantage), 10.243.1.149's request on port 22222 accepted.
system (01.09.2021 20:05:54): Access point operation disabled 7548 secs after boot.
logger (01.09.2021 20:10:14): station 0 (Vantage), connection on port 22222 closed.
logger (01.09.2021 20:11:00): station 0 (Vantage), 10.243.1.149's request on port 22222 accepted.

Code: Select all

Live Data
#	Sensor	Signal	Metric Data	Imperial Data	
0	Outdoor	11 sec	26.8°C 77% (dew 22.4°C, heat 29.1°C)	80.2°F 77% (dew 72.3°F, heat 84.3°F)	
0	Indoor	5 sec	24.3°C 41% 1004.0hPa (992.3hPa)	75.7°F 41% 29.65inHg (29.30inHg)	
0	UV	5 sec	0.0uvindex	0.0uvindex	
0	Solar	25 sec	0W/m²	0W/m²	
0	Wind	3 sec	0.4m/s (avg 1.3m/s) 305° NW	0.9mph (avg 2.9mph) 305° NW	
0	Rain	5 sec	rate 0.0mm/h	rate 0.00in/h	
9	Data #10	29 sec	145% system load	145% system load	
9	Data #11	29 sec	2.3h uptime	2.3h uptime	
9	Data #12	29 sec	3% data store usage	3% data store usage	
9	Data #13	29 sec	60% RAM usage	60% RAM usage	
9	Data #15	29 sec	59 processes	59 processes	
9	Data #16	29 sec	2sec since last data	2sec since last data
It will reboot anywhere from an hour to almost 3 days of uptime.

It does not matter whether I have a DHCP or fixed IP address to the local WIFI.

The unit is in the same room as the router as well.

[wilkerjnc]

The most reboot was a few hours past 3 days.

Also, and this happens about avert 2nd or 3rd reboot; it asks again to accept thee license:

Code: Select all

Acceptance of license terms is a prerequisite for using this application
License
License Key: activated (mbnano-01046)
License Agreement
USER LICENSE AGREEMENT
====================================================================
YOUR INSTALLATION AND/OR USE OF THIS SOFTWARE INDICATES YOUR 
ACCEPTANCE OF THIS LICENSE AGREEMENT AND WARRANTY.

This product consists of a (1) HARDWARE vocore2 manufactured and sold by 
TAIYUAN VONGER ELECTRONICS AND TECHNOLOGY CO. LTD and (2) OPENWRT linux 
distribution (www.openwrt.org) and (3) METEOBRIDGE non Open Source 
application components owned by smartbedded GmbH, a limited liability 
c.
.
.
This License shall be governed by the laws of Germany. 
Court of jurisdiction is Hamburg.

Contact

Email: info(at)smartbedded.com
Web Site: http://www.smartbedded.com/ 

 I have read and accepted the license agreement above

[admin]

Looks like a too weak power supply.

[wilkerjnc]

My power supply is the original Davis one as seen in the pic:

Switching Adapter 6625
Model: DSC-3PFB-05 FUS
Output: +5v 0.3A

Is the an indicators in any log on the NanoSD itself that could help verify this?

What is the recommended power output for an external power supply?

[admin]

Please try an 1A option.

Please read here: viewtopic.php?f=56&t=13795

[wilkerjnc]

OK I installed 1 of these today:

https://www.amazon.com/dp/B015PXUHYA?ps ... ct_details

Universal AC Adapter, ZOZO 12W 3V 4.5V 5V 6V 7.5V 9V 12V Regulated Multi Voltage Switching Replacement Power Supply for Household Electronics Routers Speakers CCTV Cameras Smart Phone USB

2A on the 5V line.

Lets see how that goes...

[wilkerjnc]

6 days, 15 hours, 22 minutes since the last actual reboot, but the networking dropped and restarted:

Code: Select all

system (15.09.2021 09:26:20): Disconnected from WLAN or Internet, reconnect issued.
system (15.09.2021 09:26:27): Access point operation temporarily enabled.
logger (15.09.2021 09:26:56): station 0 (Vantage), 10.243.1.149's request on port 22222 accepted.
system (15.09.2021 09:31:09): Access point operation disabled 559256 secs after boot.
logger (15.09.2021 10:24:01): child process received timeout signal (14).
logger (15.09.2021 10:24:01): disconnect station 0 (Vantage): exit
logger (15.09.2021 10:24:01): disconnect station 9 (System Data): exit
logger (15.09.2021 10:24:02): data logger stopped.
logger (15.09.2021 10:24:02): databases disconnected.
logger (15.09.2021 10:24:02): parent process to be terminated.
logger (15.09.2021 10:24:03): databases connected. Update interval 3600 seconds.
logger (15.09.2021 10:24:03): data logger (version 5.2, build 4020) started.
logger (15.09.2021 10:24:03): connect station 0 (Vantage via serial).
logger (15.09.2021 10:24:03): connect station 9 (System Data via Plug-in).
logger (15.09.2021 10:24:03): station 0 (Vantage), wakeup sent.
logger (15.09.2021 10:24:06): waiting for sensors (wind0, rain0, th0, thb0) to provide data.
logger (15.09.2021 10:24:06): services paused.
logger (15.09.2021 10:24:07): station 0 (Vantage), no need to update console date/time.
logger (15.09.2021 10:24:07): station 0 (Vantage), setup script executed.
logger (15.09.2021 10:24:07): station 0 (Vantage), internal logger activated.
logger (15.09.2021 10:24:08): station 0 (Vantage), syncing.
logger (15.09.2021 10:24:18): station 0 (Vantage), gettime request sent.
logger (15.09.2021 10:24:18): station 0 (Vantage), no Vantage time offset.
logger (15.09.2021 10:24:18): station 0 (Vantage), eeprom request sent.
logger (15.09.2021 10:24:18): station 0 (Vantage), rain collector size 0.01 inch per tick.
logger (15.09.2021 10:24:18): station 0 (Vantage), transmitter 1 active as station type #0 "ISS".
logger (15.09.2021 10:24:18): station 0 (Vantage), firmware version request sent.
logger (15.09.2021 10:24:18): station 0 (Vantage), firmware version 3.80 (supports LOOP2)
logger (15.09.2021 10:24:18): station 0 (Vantage), no reading of Vantage's internal logger.
logger (15.09.2021 10:24:23): sensors are now providing data.
logger (15.09.2021 10:24:23): services started.

Should this be another thread?

FYI, the NanoSD is about 2.5 (7 feet) from the WiFi router.

[Mattk]

FYI, the NanoSD is about 2.5 (7 feet) from the WiFi router.

Probably of more interest is the distance from the NanoSD to the ISS?

[wilkerjnc]

The NanoSD is of course in the Vantage Pro2 logger socket, the VP2 is about 10 m (~33 feet) from the actual ISS.

The outside wall is just regular wood type composite siding, no brick.

[wilkerjnc]

From the OpenWrt system log I see

Code: Select all

<many instances of this>
Wed Sep 15 21:31:26 2021 daemon.warn dnsmasq-dhcp[1184]: no address range available for DHCP request via apcli0
Wed Sep 15 21:31:26 2021 daemon.warn dnsmasq-dhcp[1184]: no address range available for DHCP request via apcli0
Wed Sep 15 21:35:30 2021 daemon.notice netifd: Network device 'ra0' link is up
Wed Sep 15 21:35:30 2021 daemon.notice netifd: Interface 'wwan' has link connectivity
Wed Sep 15 21:35:30 2021 kern.info kernel: [602716.704360] IPv6: ADDRCONF(NETDEV_UP): ra0: link is not ready
Wed Sep 15 21:35:30 2021 kern.info kernel: [602716.710402] IPv6: ADDRCONF(NETDEV_CHANGE): ra0: link becomes ready
Wed Sep 15 21:35:36 2021 daemon.err uhttpd[954]: ls: /sys/bus/usb/drivers/cdc_ether/: No such file or directory
Wed Sep 15 21:36:17 2021 daemon.warn dnsmasq-dhcp[1184]: no address range available for DHCP request via apcli0
Wed Sep 15 21:36:17 2021 daemon.warn dnsmasq-dhcp[1184]: no address range available for DHCP request via apcli0
Wed Sep 15 21:36:26 2021 daemon.notice netifd: Network device 'ra0' link is down
Wed Sep 15 21:36:26 2021 daemon.notice netifd: Interface 'wwan' has link connectivity loss

[admin]

When you have another program poking to the NANO via port 22222 operation depends on what the other program is doing.
Please cut off that and see if the NANO operates fine and stable without that.

[wilkerjnc]

The program in question was weewx version 4.5.1 running on Linux.

I shut it down about 3 hours ago, so I will monitor to see how this goes.

I have not seen any more of the port 22222 requests from my Linux system, but I do see this

Code: Select all

Thu Sep 16 22:03:56 2021 daemon.warn dnsmasq-dhcp[1184]: no address range available for DHCP request via apcli0

continually in the system log.

[admin]

I understand this message in a way that the DHCP server (probably your router) cannot give an IP address to the NANO because its pool of IP addresses is exhausted. May be there are too many devices for the defined pool size in your LAN?

Reason: After the defined DHCP lease time has passed, a LAN client asks for its IP address at the DHCP server, so that it can adapt to a new address if demanded by the DHCP server. This seems to fail because of the reason mentioned above.

[admin]

Thinking more about this, it can also be a configuration issue with the dnsmasq daemon running the Meteobridge. Did you apply any tweaks to the networking by the OPENWRT interface? I ask because others don't have this message.

[Mattk]

This may be totally irrelevant but will add the following comments based on an observation of an Envoy/NanoSD which had been consistently but irregularly rebooting for no apparent reason especially considering there is another Envoy/Nano right beside it that wasn't rebooting.

Scenario is a single ISS about 40 metres away and a single clay block wall. Envoy/WLIP's have no problem at that distance but there are two (2) MBPro's that struggle for signal hence these receive signal from a Davis Repeater on the same TX ID, repeater ID is irrelevant in this case. All good so far.

The two Envoys/Nano's were originally configured similar to the MBPro's, same TX ID (ISS) and Direct (no repeater) yet one rebooted when it felt like it and the other never rebooted. One Envoy is FW 1.90, the other 3.80 but who would know what the FW has to do with it?

Finally set the rebooting Envoy/Nano combo to "via repeater A" (because the Nano config supports the repeater config) .... and the rebooting stopped, well for the last 8 days anyway.

Haven't determined the logic (if there is any) with this as yet, or if this is signal related? Just mentioning this similar sounding reboot type issue, any relevance? I have no idea.