understood. Just wanted to acknowledge that I wasn't ignoring. Sincerely, Jon
Jon Adams, PE, MSEE Senior Member, IEEE +1 480.628.6686 On Fri, Dec 2, 2016 at 9:05 AM, Andrew Milner <[email protected]> wrote: > Posting the log to go with your actions is *always* better than just > detailing the actions, so that we can relate the actions taken with what > the system was doing /or waiting for at the time the action was taken. > > > On Friday, 2 December 2016 17:55:27 UTC+2, Jon Adams wrote: > >> Good day, Susan - >> >> Thanks for the response. I tried this but it doesn't seem to solve my >> situation. When I do a reboot of the RPi, this is what happens: >> >> 1) reboot pi >> 2) wait (I wait several minutes, just in case) for pi to come up and load >> weewx, pureftpd, lighttpd, ntpd >> 3) surf in via web browser to weewx web page via lighttpd. get webpage >> (network is up and running) but stale data. >> 4) check pureftpd. works fine. Network is running. >> 5) start network ssh via PuTTY to Pi. Log in. Everything looks good, but >> there's no Python or weewx processes running. >> 6) Issue a start weewx command. Command line returns *immediately*, no >> errors thrown. Check ps, no python or weewx running. >> 7) issue a stop weewx command. Command line returns *immediately*, no >> errors thrown. >> 8) issue a start weewx command. Command line hesitates maybe a second, no >> errors thrown. Check ps, both python and weewx are there. Web page updates >> with current info. >> 9) issue a stop weewx command. Command line hesitates several seconds, no >> errors thrown. Check ps, both python and weewx are gone. >> 10) start weewx again. Everything is up. >> >> I've tried skipping 6), but 6) seems necessary. The network is obviously >> up and running if pureftpd, ssh, lightpd are all running. It appears to >> require the start/stop/start to get going.I do not have console access, so >> I can only access this via network. >> >> I will look at this more soon and try to post more logs. Got to get back >> to the day job right now. >> >> Thanks again for the assistance. >> >> Cheers - Jon >> >> >> On Sunday, November 27, 2016 at 7:52:24 PM UTC-7, [email protected] wrote: >>> >>> I had the same problem. A bit of research shows that I needed to edit >>> the /etc/init.d/weewx file so that the >>> >>> # Required-Start: >>> >>> line contains '$network'. >>> >>> This is converted by the tools that translate the SysVInit code to >>> 'systemd' code to wait until the network is operational. >>> >>> Susan >>> >>> On Saturday, November 26, 2016 at 7:14:35 AM UTC+11, mwall wrote: >>>> >>>> >>>> >>>> On Friday, November 25, 2016 at 2:53:34 PM UTC-5, Jon Adams wrote: >>>>> >>>>> 083529 (row 547): weewx exits because it can't find a network (but >>>>> there was a network already set up?) >>>>> >>>> >>>> jon, >>>> >>>> your configuration requires a network connection to the vantage >>>> station, and weewx is bailing out when it finds no network (see lines 546 >>>> and 547 of the syslog you posted). >>>> >>>> by the time you try to start weewx directly, then network is functional. >>>> >>>> you need to tell systemd that weewx needs a fully functional network >>>> before it is started up. >>>> >>>> or you can add the loop-on-init option to your weewx configuration file: >>>> >>>> loop_on_init = True >>>> >>>> that will make weewx keep retrying the startup process instead of >>>> exitting. >>>> >>>> m >>>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/weewx-user/ayOGoCOySx0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > 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.
