You're not showing us very much --- see the guidelines. It looks like you did a keyboard interrupt (Ctrl-C) on the process. Are you sure this was a daemon?
-tk On Fri, May 19, 2017 at 1:26 PM, Craig Kimble <[email protected]> wrote: > sorry, I hope this is helpful > > pi@raspberrypi:~ $ sudo /etc/init.d/weewx start > [ ok ] Starting weewx (via systemctl): weewx.service. > pi@raspberrypi:~ $ tail -f /var/log/syslog > May 19 14:13:05 raspberrypi weewx[1664]: sdr: MainThread: close stdout > May 19 14:13:05 raspberrypi weewx[1664]: sdr: MainThread: close stderr > May 19 14:13:05 raspberrypi weewx[1664]: sdr: MainThread: kill process > May 19 14:13:05 raspberrypi weewx[1664]: engine: Keyboard interrupt. > May 19 14:17:02 raspberrypi rsyslogd-2007: action 'action 17' suspended, > next retry is Fri May 19 14:18:02 2017 [try http://www.rsyslog.com/e/2007 > ] > May 19 14:17:02 raspberrypi CRON[1799]: (root) CMD ( cd / && run-parts > --report /etc/cron.hourly) > May 19 14:17:33 raspberrypi systemd[1]: Starting Cleanup of Temporary > Directories... > May 19 14:17:33 raspberrypi systemd[1]: Started Cleanup of Temporary > Directories. > May 19 14:18:24 raspberrypi rsyslogd-2007: action 'action 17' suspended, > next retry is Fri May 19 14:19:24 2017 [try http://www.rsyslog.com/e/2007 > ] > May 19 14:18:24 raspberrypi systemd[1]: Started LSB: weewx weather system. > > Thats it > > Craig > > On Friday, May 19, 2017 at 1:53:29 PM UTC-6, Craig Kimble wrote: >> >> I am a noob and need some help getting weewx to run at startup. weewx >> will run fine if I start it manually. I believe I have tracked the problem >> down to the ntp time server. I installed weewx on a pi using the >> documentation in the user guide. >> >> pi@raspberrypi:~ $ /etc/init.d/weewx status >> ● weewx.service - LSB: weewx weather system >> Loaded: loaded (/etc/init.d/weewx) >> Active: active (exited) since Wed 1969-12-31 17:00:23 MST; 47 years 4 >> months ago >> Process: 347 ExecStart=/etc/init.d/weewx start (code=exited, >> status=0/SUCCESS) >> >> >> pi@raspberrypi:~ $ ntpq -pn >> remote refid st t when poll reach delay offset >> jitter >> ============================================================ >> ================== >> +198.206.133.14 115.21.111.66 3 u 18 64 377 46.059 0.672 >> 0.412 >> -148.167.132.200 LOCAL(0) 2 u 53 64 147 49.062 -7.131 >> 16.491 >> +154.16.245.246 152.2.253.126 2 u 28 64 377 57.598 4.819 >> 0.290 >> *67.40.5.51 127.67.113.92 2 u 57 64 377 49.765 2.080 >> 0.496 >> >> >> pi@raspberrypi:~ $ systemctl list-unit-files | grep enabled >> [email protected] enabled >> avahi-daemon.service enabled >> bluetooth.service enabled >> cron.service enabled >> dbus-org.bluez.service enabled >> dbus-org.freedesktop.Avahi.service enabled >> dhcpcd.service enabled >> display-manager.service enabled >> hciuart.service enabled >> hwclock-save.service enabled >> lightdm.service enabled >> rpi-display-backlight.service enabled >> rsyslog.service enabled >> ssh.service enabled >> sshswitch.service enabled >> syslog.service enabled >> vncserver-x11-serviced.service enabled >> avahi-daemon.socket enabled >> remote-fs.target enabled >> >> >> I hope I supplied enough info >> Craig >> > -- > 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. > -- 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.
