No I didn't. In fact I didn't play around with nice levels etc. The "original" RPi is a Pi 2 (more by accident than intention, but it should have enough "welly") - it now runs just weewx and a single camera and its CPU utilisation is very low.
In fact, the original "lockouts" weren't coincident with weewx's reporting and seemed pretty random (and infrequent). I still suspect that the whole issue had something to do with the fact that this "original" machine stores "/" on my NFS and consequently Ethernet traffic is high. Cheers PS: The RPi now running 3 cameras, several Adafruit sensors and audio streaming has had a traumatic history. It is a "Model B+ and was originally housed outdoors in a weatherproof clear plastic case. Unfortunately, this case wasn't as rugged as hoped and about 12 months ago - after it had crashed and following a few days of high wind and heavy rain - I found the RPi lying in the grass, soaking wet and covered in a kind of powdery grey gunk. I cleaned it up (toothbrush + alcohol + compressed air) and it then worked fine agin. The only lasting damage being the failure of the spring/clip thing that holds the SD card in place - this is now secured by a plastic cable tie. The original SD card was completely fried. On Sunday, October 30, 2016 at 8:53:44 AM UTC+1, Andrew Milner wrote: > > when you had cams and weewx on one machine did you have turbo mode > enabled? It would have needed it I expect. > > weewx will have failed because the camera were hogging resources - you > could have tried raising the priority. weewx will trundle along at very > low cpu usage UNTIL it generates reports and plots - then it will need very > high resources. > > > > On Sunday, 30 October 2016 09:42:12 UTC+2, Macha wrote: > >> OK, status report on my "lockout" with weewx and my FOUSB station. >> >> I moved 2 webcams from the RPi running weewx onto a different machine >> (another RPi, I have quite a few). >> >> Result? No weewx lockouts for nearly 10 days. I'm not sure if this passes >> the "5 sigma" test, but it's certainly a record uptime. >> >> Still a few puzzlements - on the previous setup, it was always weewx >> (well Python I suppose) that "failed", the webcams (run with mjpg-streamer) >> were always rock-solid. On the new setup, the RPi which now has the "moved" >> webcams is quite busy - it runs the 2 new cameras, plus an RPi camera (all >> driven with mjpg-streamer) and also icecast2+darkice (monitoring bird >> tweets, etc.) - CPU utilisation is around 35%. This machine never fails. >> >> The previous RPi is now chuffing along at <1% >> >> Anyway, thanks again for the advice and comments ... >> >> -- 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 weewx-user+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
