I know this thread has been dormant for some time, and I don't see that a solution has been determined, but I've got the same problem with my weewx install on an RPi3, and it's been a bit frustrating.
The RPi is on battery backup, so glitches in AC don't impact it, but still, when for some reason I have to reboot it, I have to start the weewx service, then stop it, then restart it before it will actually launch successfully. My other programs queued to autostart seem to behave alright, the webserver and ftp server come up fine. Setup is RPi3 running Debian 8.0, uname shows: Linux raspberrypi 4.4.21-v7+ #911 SMP Thu Sep 15 14:22:38 BST 2016 armv7l GNU/Linux Uses a Pi drive (rotating) to prevent early demise of the NVRAM. Davis VantagePro2 wired with IP connection. Running weewx 3.5.0 At least on my build, there is no modemmanager, Similar to W7JBG's situation, after boot up, there's no python or weewx in top or ps aux | grep --- Again, after boot up, I can issue a sudo /etc/init.d/weewx start and there's no record of it in the running processes. if I then issue a sudo /etc/init.d/weewx stop there's no delay in the prompt returning. Then, i issue sudo /etc/init.d/weewx start and this time both python and weewx are found as one of the running processes. Has this been resolved? Cheers and 73 - Jon N7UV On Saturday, February 13, 2016 at 2:40:34 PM UTC-7, Tom Keffer wrote: > > Yes, that's true, but it's easier to teach a user how to nuke modemmanager > than to mess with UDEV rules. > > But, hey, do you know anything about upstart? > > -tk > > On Sat, Feb 13, 2016 at 1:20 PM, P Simmons <[email protected] > <javascript:>> wrote: > >> >> >> On Saturday, February 13, 2016 at 1:14:51 PM UTC-6, Tom Keffer wrote: >>> >>> There is very definitely something of interest in the log files, namely >>> the line, >>> >>> Feb 13 16:07:02 trimslice weewx[1872]: engine: Unable to load driver: >>> [Errno 11] Resource temporarily unavailable >>> >>> Unless you actually have a modem, try removing modemmanager >>> >>> sudo apt-get remove modemmanager >>> >>> >>> It's looking for a modem at /dev/ttyUSB0 and competing with weewx. >>> Eventually it gives up and relinquishes the port, but not until after weewx >>> exits. >>> >>> >>> >> Hey there, Tom... if there's a udev rule for the USB device, one can add >> *ENV{ID_MM_DEVICE_IGNORE}="1"* to the rule, and modemmanager will leave >> it alone. >> >> Best, >> Paul >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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.
