Hi, Last week I upgraded my Ubuntu on my server from 14.04 to 16.04. And after the upgrade I can't start weewx on boot any more.
I have tried both whit upstart script and systemd. I've tried waiting after the boot is totatally completed and then "sudo /etc/init.d/weewx start" or "*sudo systemctl start weewx.service*" With the following exec: "*/usr/bin/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf"* And the user is set to root in both init.d and systemd But the result is the same: Nov 4 22:08:04 server systemd[1]: Started weewx weather system. Nov 4 22:08:04 server weewx[10465]: engine: Initializing weewx version 3.6. 1 Nov 4 22:08:04 server weewx[10465]: engine: Using Python 2.7.12 (default, Jul 1 2016, 15:12:24) #012[GCC 5.4.0 20160609] Nov 4 22:08:04 server weewx[10465]: engine: Platform Linux-4.4.0-45-generic -x86_64-with-Ubuntu-16.04-xenial Nov 4 22:08:04 server weewx[10465]: engine: pid file is /var/run/weewx.pid Nov 4 22:08:04 server weewx[10470]: engine: Using configuration file /etc/ weewx/weewx.conf Nov 4 22:08:04 server weewx[10470]: engine: Initializing engine Nov 4 22:08:04 server weewx[10470]: engine: Loading station type FineOffsetUSB (weewx.drivers.fousb) Nov 4 22:08:04 server weewx[10470]: engine: Received signal TERM. Nov 4 22:08:04 server weewx[10470]: engine: Terminating weewx version 3.6.1 But if i ssh and tires to start the demon from command line it works perfect: Nov 8 12:08:14 server weewx[18210]: engine: Initializing weewx version 3.6. 1 Nov 8 12:08:14 server weewx[18210]: engine: Using Python 2.7.12 (default, Jul 1 2016, 15:12:24) #012[GCC 5.4.0 20160609] Nov 8 12:08:14 server weewx[18210]: engine: Platform Linux-4.4.0-45-generic -x86_64-with-Ubuntu-16.04-xenial Nov 8 12:08:14 server weewx[18210]: engine: pid file is /var/run/weewx.pid Nov 8 12:08:14 server weewx[18214]: engine: Using configuration file /etc/ weewx/weewx.conf Nov 8 12:08:14 server weewx[18214]: engine: Loading station type FineOffsetUSB (weewx.drivers.fousb) Nov 8 12:08:17 server weewx[18214]: fousb: driver version is 1.9 Nov 8 12:08:17 server weewx[18214]: fousb: polling mode is PERIODIC Nov 8 12:08:17 server weewx[18214]: fousb: polling interval is 60 Nov 8 12:08:23 server weewx[18214]: fousb: found station on USB bus= device = Nov 8 12:08:23 server weewx[18214]: engine: StdConvert target unit is 0x1 Nov 8 12:08:23 server weewx[18214]: wxcalculate: The following values will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware, heatindex=prefer_hardware, maxSolarRad= prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, cloudbase=prefer_hardware Nov 8 12:08:23 server weewx[18214]: wxcalculate: The following algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS Nov 8 12:08:23 server weewx[18214]: engine: Archive will use data binding wx_binding Nov 8 12:08:23 server weewx[18214]: engine: Record generation will be attempted in 'hardware' Nov 8 12:08:24 server weewx[18214]: engine: Using archive interval of 300 seconds (specified by hardware) Nov 8 12:08:34 server weewx[18214]: engine: Using binding 'wx_binding' to database 'weewx' Any one have any ideas what I am missing? Can it be something with systemd starting Python script? But then why is the demon starting and then exits after loading the driver? -- 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.
