On Tuesday, February 6, 2018 at 12:35:10 AM UTC-8, Rod in Edm wrote: > > I've been running Weewx since last November on a RPi3 with an RTC > installed, and an mSATA-USB interface board plugged into one of the RPi3's > ports carrying a Samsung 850 EVO 250GB SSD. Power to the SSD is from the > RPI3 power brick via the standard power plug. The power is plugged into a > large APC_BackUps UPS for stability. Essentially, its Weewx on an RPi3 > that boots from its microSD card as usual, but has its "/" on the SSD. >
hmmmm - running things requiring power by simply connecting to a pi's USB ports is historically a bit gutsy.... Then in late January, I started seeing a funny problem: the RPi3's WiFi > carrier would suddenly be lost - and not re-established - causing FTP > uploads to fail, and knocking out my SSH access (its a headless system, and > I disabled the RPi3's VNCserver). Without a way to see what is going on or > to issue commands, I have no choice but to pull the RPI3's power plug, wait > a few seconds, and plug it back in. > Yup. No other way to recover if you're headless. VNC wouldn't help you anyway as that needs the network (that disappeared). I ran Weewx with debug=1 for a couple days, but the problem didn't occur. > Of course, when I reset debug=0, the problem returned. What this means, I > don't know. One thing I noticed during debug=1 ... it sure slowed down ssh > login and listing syslog responses - Weewx writes a LOT of info when in > debug mode. > > I'd suggest there's no impact here. It's not THAT much stuff for a modern system. > What the heck is dhcpcd doing to Weewx, and why?? > > > Nothing. Your wlan0 interface disappeared and weewx can't connect to internet (of course). Everything above is due to the NIC disappearing. I haven't heard of this one on the pi3, but it used to happen on the old model-B pi a lot. I have a script at https://github.com/vinceskahan/raspi-odds-and-ends/blob/master/netmon.sh that might help. Basically you call this periodically from cron and it tries to self-heal wifi when it goes away. Check the comments in there for details. This script is several years old, so I can't speculate whether it'll still help on modern systemd-based Raspbian but it should work I'd think. Might be worth a try. Couple other things that might be possibilities: - does any other box similarly lose wifi ? This might indicate a channel overlap problem with a neighboring house etc. causing wifi to bounce a bit too much for the pi. My problem went away when I moved everything that could talk 5GHz there, and switched which 2.4GHz channel we were using to try to avoid the neighbors who were on the wrong channel and hosing up the whole neighborhood as a result. I think if it was me, I'd try my script (link above) and see if that self-heals for you. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
