Hi, Bob What kind of operating system is this? I'm wondering if it is having a reaction to the daemonizing strategy weewx uses.
I would also like to see a bit more of the log, starting with the first weewx log entry, through the 15:39:33 termination. -tk On Wed, Mar 22, 2017 at 12:52 PM, <bgrat...@umw.edu> wrote: > Andrew, > > I rebooted with debug on weewx and nothing showed up in syslog or > weewx.log. I searched around for the "(/etc/systemd/system/*weewx.service; > disabled*; vendor preset: enabled)" message and tried the command "*systemctl > enable weewx*." The result after reboot was this: > > root@nuc:~# service weewx status > ? weewx.service - weewx weather system > Loaded: loaded (/etc/systemd/system*/weewx.service; enabled*; vendor > preset: enabled) > Active: inactive (dead) since Wed 2017-03-22 15:29:33 EDT; 38s ago > Process: 810 ExecStart=/home/weewx/bin/weewxd --daemon > --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf (code=exited, > status=0/SUCCESS) > Main PID: 810 (code=exited, status=0/SUCCESS) > > Mar 22 15:29:33 nuc weewxd[810]: Traceback (most recent call last): > Mar 22 15:29:33 nuc weewxd[810]: File "/home/weewx/bin/weewxd", line 64, > in <module> > Mar 22 15:29:33 nuc weewxd[810]: weewx.engine.main(options, args) > Mar 22 15:29:33 nuc weewxd[810]: File "/home/weewx/bin/weewx/engine.py", > line 833, in main > Mar 22 15:29:33 nuc weewxd[810]: daemon.daemonize(pidfile= > options.pidfile) > Mar 22 15:29:33 nuc weewxd[810]: File "/home/weewx/bin/daemon.py", line > 79, in daemonize > Mar 22 15:29:33 nuc weewxd[810]: os.dup2(si.fileno(), > sys.stdin.fileno()) > Mar 22 15:29:33 nuc weewxd[810]: File "/home/weewx/bin/weewx/engine.py", > line 803, in sigTERMhandler > Mar 22 15:29:33 nuc weewxd[810]: raise Terminate > Mar 22 15:29:33 nuc weewxd[810]: weewx.engine.Terminate > > It started fine manually: > > root@nuc:~# service weewx restart > root@nuc:~# service weewx status > ? weewx.service - weewx weather system > Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor > preset: enabled) > Active: active (running) since Wed 2017-03-22 15:31:08 EDT; 3s ago > Main PID: 2519 (weewxd) > CGroup: /system.slice/weewx.service > mq2519 /usr/bin/python /home/weewx/bin/weewxd --daemon > --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf > > There must be some conflict between in the systemctl startup process. I > moved the "weewx.service" (no modifications) according to directions in > startup. > I'm now wise enough in the ways of linux to figure this one out. > > Thanks for the quick reply. > > Bob > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > On Wednesday, March 22, 2017 at 11:55:30 AM UTC-4, Andrew Milner wrote: >> >> what does the weewx log say?? is weewx waiting for the time to be set >> correctly, or a network to be available perhaps?? The key should lie in >> the weewx log (or/and system startup log - syslog) >> >> >> >> On Wednesday, 22 March 2017 16:44:50 UTC+2, bgra...@umw.edu wrote: >> >>> Hello, >>> >>> I've about finished moving weewx to a new computer and from debian to >>> Ubuntu. Everything seems to be working correctly except the auto restart >>> after reboot. I can stop/start/restart from the service or init.d commands >>> and all works correctly. There is something incorrect with my configuration >>> for startup. Here are some log messages: >>> >>> *After computer reboot weewx fails to start:* >>> root@nuc:~# service weewx status >>> ? weewx.service - weewx weather system >>> Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor >>> preset: enabled) >>> Active: inactive (dead) >>> +++++++++++++++++++++++++++++++++++++++ >>> *Manual restart of weewx service:* >>> root@nuc:~# service weewx restart >>> root@nuc:~# service weewx status >>> ? weewx.service - weewx weather system >>> Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor >>> preset: enabled) >>> Active: active (running) since Wed 2017-03-22 10:11:05 EDT; 7s ago >>> Main PID: 2398 (weewxd) >>> CGroup: /system.slice/weewx.service >>> mq2398 /usr/bin/python /home/weewx/bin/weewxd --daemon >>> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf >>> +++++++++++++++++++++++++++++++++++++++ >>> *Manual stop/start from init.d:* >>> root@nuc:/etc/init.d# ./weewx stop >>> [ ok ] Stopping weewx (via systemctl): weewx.service. >>> root@nuc:/etc/init.d# ./weewx start >>> [ ok ] Starting weewx (via systemctl): weewx.service. >>> root@nuc:/etc/init.d# ./weewx status >>> ? weewx.service - weewx weather system >>> Loaded: loaded (/etc/systemd/system/weewx.service; disabled; vendor >>> preset: enabled) >>> Active: active (running) since Wed 2017-03-22 10:13:08 EDT; 13s ago >>> Main PID: 2491 (weewxd) >>> CGroup: /system.slice/weewx.service >>> mq2491 /usr/bin/python /home/weewx/bin/weewxd --daemon >>> --pidfile=/var/run/weewx.pid /home/weewx/weewx.conf >>> >>> Any suggestions will be appreciated. Thanks in advance. >>> >>> Bob >>> >>> >>> >>> -- > 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. > -- 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.
