[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Jerry Deibel]

Ok,   It is now working both on restart and shutdown.

It was the SD card.   Last week when I re-installed the pi software and 
weewx on the SD card (remember before I was running with a USB stick and 
that went bad.)
I have 2 pi's, one was a spare, so last week after the reinstall I made a 
image copy to the other  SD card.  ( I don't know which SD card I was using 
this past year with the USB stick)
Well one SD card  was a sandisk 8g and the other was  sandisk 8g ULTRA.
I was using the regular SD card which  was causing the boot up problem.

Today I  put the ULTRA SD card in the pi and  the first boot did not work.
But then I removed the rc script and used systemctl that Mwall gave me a 
few days ago and that did the trick.

Thanks to everyone for their help.
Jerry

On Wednesday, January 4, 2017 at 1:41:46 PM UTC-5, Jerry Deibel wrote:
>
> Hi,
> I have been running weewx with my ambient 1400 Observer for about 2 years. 
> Last year I moved the OP system to a USB stick to save wear and tear on the 
> SD card and  last week the USB had a sector error and would not load.  So 
> much for moving over from a SD card to a USB stick.
>
> I reloaded Jessi OP system on the Raspberry PI, but this time just on the 
> SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up 
> and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or 
> so to make sure everything was ok.  I backup my archive every day so I 
> restored the archive database for the last year as well.   
> The last 2 years I ran a daemon process to run it on power up , so today I 
> did that..
>
> Now my problem is . 
> After doing the following to run it on power up
> sudo util/init.d/weewx.debian to /etc/init.d/weewx)
> sudo chmod +x /etc/init.d/weewx
> sudo update-rc.d weewx defaults 98
>
> I then tried to startsudo /etc/init.d/weewx start : no log 
> outpur and ps aux shows not running
> It DID  not start
> I then stopped it..  sudo /etc/init.d/weewx  stop
> I then started it again.   sudo /etc/init.d/weewx start
> AND IT STARTED    Outputting to log and ...  ps aux | grep weewx   
>  ... shows it running ok.
>
> Also, it does not start on  a power up.  
>
> Here is the log right after power up ..
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/index.bdmv
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/BACKUP/index.bdmv
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org 
> -> 45.79.1.70
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org 
> -> 195.21.137.209
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org 
> -> 104.131.53.252
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org 
> -> 138.68.2.126
> Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
> Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
> Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
> Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopping LSB: weewx weather 
> system...
> Jan  4 13:30:56 raspberrypi weewx[1567]: Stopping weewx weather system: 
> weewx not running
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Initializing weewx 
> version 3.6.2
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Platform 
> Linux-4.4.34-v7+-armv7l-with-debian-8.0
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: pid file is 
> /var/run/weewx.pid
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Using configuration file 
> /home/weewx/weewx.conf
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Loading station type 
> ObserverIP (user.observerip)
> Jan  4 13:31:09 raspberrypi weewx[1616]: Starting weewx weather system: 
> weewx.
> Jan  4 13:31:09 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi weewx[1631]: observerip: version is 0.5mw
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: Unknown firmware 
> version: ��
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: polling interval is 
> 16.0
> Jan  4 13:31:10 raspberrypi 

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Jerry Deibel]

tk

pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.4.34-v7+ #930 SMP Wed Nov 23 15:20:41 GMT 2016 armv7l 
GNU/Linux
and
pi@raspberrypi:~ $ cat /etc/*-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/;
SUPPORT_URL="http://www.raspbian.org/RaspbianForums;
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs;

Jerry


On Wednesday, January 4, 2017 at 1:41:46 PM UTC-5, Jerry Deibel wrote:
>
> Hi,
> I have been running weewx with my ambient 1400 Observer for about 2 years. 
> Last year I moved the OP system to a USB stick to save wear and tear on the 
> SD card and  last week the USB had a sector error and would not load.  So 
> much for moving over from a SD card to a USB stick.
>
> I reloaded Jessi OP system on the Raspberry PI, but this time just on the 
> SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up 
> and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or 
> so to make sure everything was ok.  I backup my archive every day so I 
> restored the archive database for the last year as well.   
> The last 2 years I ran a daemon process to run it on power up , so today I 
> did that..
>
> Now my problem is . 
> After doing the following to run it on power up
> sudo util/init.d/weewx.debian to /etc/init.d/weewx)
> sudo chmod +x /etc/init.d/weewx
> sudo update-rc.d weewx defaults 98
>
> I then tried to startsudo /etc/init.d/weewx start : no log 
> outpur and ps aux shows not running
> It DID  not start
> I then stopped it..  sudo /etc/init.d/weewx  stop
> I then started it again.   sudo /etc/init.d/weewx start
> AND IT STARTED    Outputting to log and ...  ps aux | grep weewx   
>  ... shows it running ok.
>
> Also, it does not start on  a power up.  
>
> Here is the log right after power up ..
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/index.bdmv
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/BACKUP/index.bdmv
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org 
> -> 45.79.1.70
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org 
> -> 195.21.137.209
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org 
> -> 104.131.53.252
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org 
> -> 138.68.2.126
> Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
> Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
> Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
> Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopping LSB: weewx weather 
> system...
> Jan  4 13:30:56 raspberrypi weewx[1567]: Stopping weewx weather system: 
> weewx not running
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Initializing weewx 
> version 3.6.2
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Platform 
> Linux-4.4.34-v7+-armv7l-with-debian-8.0
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: pid file is 
> /var/run/weewx.pid
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Using configuration file 
> /home/weewx/weewx.conf
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Loading station type 
> ObserverIP (user.observerip)
> Jan  4 13:31:09 raspberrypi weewx[1616]: Starting weewx weather system: 
> weewx.
> Jan  4 13:31:09 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi weewx[1631]: observerip: version is 0.5mw
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: Unknown firmware 
> version: ��
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: polling interval is 
> 16.0
> Jan  4 13:31:10 raspberrypi weewx[1631]: engine: StdConvert target unit is 
> 0x1
> Jan  4 13:31:10 raspberrypi weewx[1631]: 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, 
> 

Re: [weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Thomas Keffer]

Jerry, could you give me the result of the commands

uname -a


and

cat /etc/*-release


I'd like to try and reproduce your results.

-tk

On Thu, Jan 5, 2017 at 2:12 PM, Jerry Deibel  wrote:

> Thanks to everyone for their help.   What puzzles me is that I am using
> the same Raspberry Pi (2) that I have been using for 2 years...
> Of course, when my USB went south I had to reload the raspberry pi op
> system...   The last 2 years I have been using the Jessie raspberry pi OP
> system and I now I am using the same OP system.. ( maybe different version
> after 2 years). I download the current version of  Weewx   and the
> obseverip driver.   I did not have a problem the last 2 years on weeew
> started up after a shutdown.. ( its been done more than a few times this
> past 2 years.
> I will now start from scratch and reload the raspberry pi and weewx and
> see if the problem goes away...
> Will post back on the result.
> Jerry
>
>
> On Wednesday, January 4, 2017 at 1:41:46 PM UTC-5, Jerry Deibel wrote:
>>
>> Hi,
>> I have been running weewx with my ambient 1400 Observer for about 2
>> years. Last year I moved the OP system to a USB stick to save wear and tear
>> on the SD card and  last week the USB had a sector error and would not
>> load.  So much for moving over from a SD card to a USB stick.
>>
>> I reloaded Jessi OP system on the Raspberry PI, but this time just on the
>> SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up
>> and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or
>> so to make sure everything was ok.  I backup my archive every day so I
>> restored the archive database for the last year as well.
>> The last 2 years I ran a daemon process to run it on power up , so today
>> I did that..
>>
>> Now my problem is .
>> After doing the following to run it on power up
>> sudo util/init.d/weewx.debian to /etc/init.d/weewx)
>> sudo chmod +x /etc/init.d/weewx
>> sudo update-rc.d weewx defaults 98
>>
>> I then tried to startsudo /etc/init.d/weewx start : no log
>> outpur and ps aux shows not running
>> It DID  not start
>> I then stopped it..  sudo /etc/init.d/weewx  stop
>> I then started it again.   sudo /etc/init.d/weewx start
>> AND IT STARTED    Outputting to log and ...  ps aux | grep weewx
>>  ... shows it running ok.
>>
>> Also, it does not start on  a power up.
>>
>> Here is the log right after power up ..
>> pi@raspberrypi:~ $ tail -f /var/log/syslog
>> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]:
>> index_parse.c:191: indx_parse(): error opening /media/pi/rootfs/BDMV/
>> index.bdmv
>> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]:
>> index_parse.c:191: indx_parse(): error opening
>> /media/pi/rootfs/BDMV/BACKUP/index.bdmv
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org
>> -> 45.79.1.70
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org
>> -> 195.21.137.209
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org
>> -> 104.131.53.252
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org
>> -> 138.68.2.126
>> Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
>> Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
>> Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007
>> ]
>> Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
>> Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007
>> ]
>> Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Jan  4 13:30:56 raspberrypi systemd[1]: Stopping LSB: weewx weather
>> system...
>> Jan  4 13:30:56 raspberrypi weewx[1567]: Stopping weewx weather system:
>> weewx not running
>> Jan  4 13:30:56 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
>> Jan  4 13:31:09 raspberrypi systemd[1]: Starting LSB: weewx weather
>> system...
>> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Initializing weewx
>> version 3.6.2
>> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Using Python 2.7.9
>> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
>> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Platform
>> Linux-4.4.34-v7+-armv7l-with-debian-8.0
>> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: pid file is
>> /var/run/weewx.pid
>> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Using configuration file
>> /home/weewx/weewx.conf
>> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Loading station type
>> ObserverIP (user.observerip)
>> Jan  4 13:31:09 raspberrypi weewx[1616]: Starting weewx weather system:
>> weewx.
>> Jan  4 13:31:09 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Jan  4 13:31:09 raspberrypi weewx[1631]: observerip: version 

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[mwall]

On Thursday, January 5, 2017 at 2:31:46 PM UTC-5, Jerry Deibel wrote:
>
> Here is the whole log after a shutdown..
>
>>
>>
jerry,

according to the log, weewx is starting up well before the network has been 
configured.

so if you want to fix the problem, you'll have to do some systemd research 
to figure out the magic incantations to put in the unit file.  you could 
try adding network-target to the 'Requires' and/or 'After' items.

if you want to work around the problem, set loop_on_init in weewx.conf:

loop_on_init=True

this will make weewx keep trying to start up, no matter what the operating 
system is doing.

m

(where is the official list of systemd targets that works across 
distributions?  every program has incantations, they just tend to be 
'magic' for those who do not know them, or they are *all* magic if the 
grammar is really whacked, or if the software is poorly documented, or if 
the developers are arrogant, or if the software is too advanced for its 
time :)  trying to not be a pot calling out the kettle...)

-- 
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.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Andrew Milner]

Matthew
If you are saying that the above snippet (which I assume is standard) only 
works if the fake clock is disabled on rpi's then perhaps the install 
should attempt to explicitly unload/disable the fakehwclock, or at least 
make it clear to the user.  I've not checkd the docs before this post so 
may be out of order with my comment in which case I accept the slapped 
wrists . ouch!!



On Thursday, 5 January 2017 20:39:24 UTC+2, mwall wrote

> so once again the root cause is that the network is not ready.
>
> i thought that the following systemd unit file snippet should prevent this 
> problem:
>
> Requires=time-sync.target
> After=time-sync.target
>
> weewx should not start until time is synchronized, and time won't 
> synchronize until the network is up and running.
>
> perhaps there as a fake clock installed that is breaking everything?
>
> m
>

-- 
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.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[mwall]

so once again the root cause is that the network is not ready.

i thought that the following systemd unit file snippet should prevent this 
problem:

Requires=time-sync.target
After=time-sync.target

weewx should not start until time is synchronized, and time won't 
synchronize until the network is up and running.

perhaps there as a fake clock installed that is breaking everything?

m

-- 
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.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[vince]

Your logfile is where it gets interesting:

Jan  5 08:10:44 raspberrypi weewx[504]: engine: Loading station type 
ObserverIP (user.observerip)
Jan  5 08:10:44 raspberrypi weewx[504]: observerip: version is 0.5mw
Jan  5 08:10:44 raspberrypi weewx[504]: import of driver failed: [Errno 
101] Network is unreachable ()
Jan  5 08:10:44 raspberrypi weewx[504]: engine: Unable to load driver: 
[Errno 101] Network is unreachable
Jan  5 08:10:44 raspberrypi weewx[504]:   Exiting...

My guess is you're trying to connect to a ip-based station before 
networking is up fully on your computer.   You are only posting a tiny 
snippet of your logfile, so we can't debug more than that really.

I brought up a vagrant VM in simulator mode and saw this interesting 
/var/log/messages stuff after a reboot:

Jan  5 16:39:46 jessie kernel: [6.932995] EXT4-fs (sda1): re-mounted. 
Opts: errors=remount-ro
Jan  5 16:39:46 jessie kernel: [7.131961] snd_intel8x0 :00:05.0: 
intel8x0_measure_ac97_clock: measured 111338 usecs (4820 samples)
Jan  5 16:39:46 jessie kernel: [7.131968] snd_intel8x0 :00:05.0: 
clocking to 53221
Jan  5 16:39:46 jessie kernel: [7.133017] piix4_smbus :00:07.0: 
SMBus Host Controller at 0x4100, revision 0
Jan  5 16:39:46 jessie kernel: [7.248703] IPv6: ADDRCONF(NETDEV_UP): 
eth1: link is not ready
Jan  5 16:39:46 jessie kernel: [7.249703] e1000: eth1 NIC Link is Up 
1000 Mbps Full Duplex, Flow Control: RX
Jan  5 16:39:46 jessie kernel: [7.250016] IPv6: 
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
==> Jan  5 16:39:46 jessie kernel: [7.338384] e1000: eth0 NIC Link is 
Up 1000 Mbps Full Duplex, Flow Control: RX
Jan  5 16:39:46 jessie kernel: [7.348248] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
Jan  5 16:39:46 jessie kernel: [7.348267] IPv6: 
ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan  5 16:39:46 jessie kernel: [7.690252] RPC: Registered named UNIX 
socket transport module.
Jan  5 16:39:46 jessie kernel: [7.690255] RPC: Registered udp transport 
module.
Jan  5 16:39:46 jessie kernel: [7.690256] RPC: Registered tcp transport 
module.
Jan  5 16:39:46 jessie kernel: [7.690257] RPC: Registered tcp NFSv4.1 
backchannel transport module.
Jan  5 16:39:46 jessie kernel: [7.693919] FS-Cache: Loaded
Jan  5 16:39:46 jessie kernel: [7.700313] FS-Cache: Netfs 'nfs' 
registered for caching
Jan  5 16:39:46 jessie kernel: [7.712848] Installing knfsd (copyright 
(C) 1996 o...@monad.swb.de).
==> Jan  5 16:39:46 jessie weewx[469]: engine: Initializing weewx version 
3.6.2
Jan  5 16:39:46 jessie weewx[469]: engine: Using Python 2.7.9 (default, Jun 
29 2016, 13:08:31) #012[GCC 4.9.2]


Notice that eth0 comes up before weewx starts, but we're talking a fraction 
of a second here..might be a timing thing on the pi since its 
usb/wifi/ethernet subsystems are so slow.

You can always kludge it with a "systemctl start weewx" in rc.local if you 
wanted to brute-force it, 

-- 
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.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Andrew Milner]

can you verify the config by
“sudo raspi-config nonint do_wait_for_network Slow” to make sure wait for 
network is set.  It sure looks as though the booting has continued without 
waiting for the network, unless specific access to a specific network node 
is required to obtain the driver - rather than just a network connection.



On Thursday, 5 January 2017 15:22:40 UTC+2, Jerry Deibel wrote:

> Mwall,
>
> HERE is the logat reboot time.It shows unable to load driver   
> network unreachable.
> I do have "Wait for network before booting "   set in Raspi-config
>
> an  5 08:10:44 raspberrypi kernel: [8.385107] IPv6: 
> ADDRCONF(NETDEV_UP): eth0: link is not ready
> Jan  5 08:10:44 raspberrypi weewx[383]: engine: Initializing weewx version 
> 3.6.2
> Jan  5 08:10:44 raspberrypi weewx[383]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Jan  5 08:10:44 raspberrypi weewx[383]: engine: Platform 
> Linux-4.4.34-v7+-armv7l-with-debian-8.0
> Jan  5 08:10:44 raspberrypi weewx[383]: engine: pid file is 
> /var/run/weewx.pid
> Jan  5 08:10:44 raspberrypi systemd[1]: weewx.service: Supervising process 
> 504 which is not our child. We'll most likely not notice when it exits.
> Jan  5 08:10:44 raspberrypi weewx[504]: engine: Using configuration file 
> /home/weewx/weewx.conf
> Jan  5 08:10:44 raspberrypi weewx[504]: engine: Loading station type 
> ObserverIP (user.observerip)
> Jan  5 08:10:44 raspberrypi weewx[504]: observerip: version is 0.5mw
> Jan  5 08:10:44 raspberrypi weewx[504]: import of driver failed: [Errno 
> 101] Network is unreachable ()
> Jan  5 08:10:44 raspberrypi weewx[504]: engine: Unable to load driver: 
> [Errno 101] Network is unreachable
> Jan  5 08:10:44 raspberrypi weewx[504]:   Exiting...
> Jan  5 08:10:44 raspberrypi systemd[1]: weewx.service: main process 
> exited, code=exited, status=4/NOPERMISSION
> Jan  5 08:10:44 raspberrypi systemd[1]: Unit weewx.service entered failed 
> state.
> Jan  5 08:10:45 raspberrypi dhcpcd[382]: eth0: carrier acquired
>
> Jerry
>
> On Wednesday, January 4, 2017 at 1:41:46 PM UTC-5, Jerry Deibel wrote:
>>
>> Hi,
>> I have been running weewx with my ambient 1400 Observer for about 2 
>> years. Last year I moved the OP system to a USB stick to save wear and tear 
>> on the SD card and  last week the USB had a sector error and would not 
>> load.  So much for moving over from a SD card to a USB stick.
>>
>> I reloaded Jessi OP system on the Raspberry PI, but this time just on the 
>> SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up 
>> and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or 
>> so to make sure everything was ok.  I backup my archive every day so I 
>> restored the archive database for the last year as well.   
>> The last 2 years I ran a daemon process to run it on power up , so today 
>> I did that..
>>
>> Now my problem is . 
>> After doing the following to run it on power up
>> sudo util/init.d/weewx.debian to /etc/init.d/weewx)
>> sudo chmod +x /etc/init.d/weewx
>> sudo update-rc.d weewx defaults 98
>>
>> I then tried to startsudo /etc/init.d/weewx start : no log 
>> outpur and ps aux shows not running
>> It DID  not start
>> I then stopped it..  sudo /etc/init.d/weewx  stop
>> I then started it again.   sudo /etc/init.d/weewx start
>> AND IT STARTED    Outputting to log and ...  ps aux | grep weewx   
>>  ... shows it running ok.
>>
>> Also, it does not start on  a power up.  
>>
>> Here is the log right after power up ..
>> pi@raspberrypi:~ $ tail -f /var/log/syslog
>> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
>> index_parse.c:191: indx_parse(): error opening 
>> /media/pi/rootfs/BDMV/index.bdmv
>> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
>> index_parse.c:191: indx_parse(): error opening 
>> /media/pi/rootfs/BDMV/BACKUP/index.bdmv
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org 
>> -> 45.79.1.70
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org 
>> -> 195.21.137.209
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org 
>> -> 104.131.53.252
>> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org 
>> -> 138.68.2.126
>> Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
>> Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
>> Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007 
>> ]
>> Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
>> Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
>> next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007 
>> ]
>> Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Jan  4 13:30:56 raspberrypi systemd[1]: 

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Jerry Deibel]

Mwall,

HERE is the logat reboot time.It shows unable to load driver   
network unreachable.
I do have "Wait for network before booting "   set in Raspi-config

an  5 08:10:44 raspberrypi kernel: [8.385107] IPv6: 
ADDRCONF(NETDEV_UP): eth0: link is not ready
Jan  5 08:10:44 raspberrypi weewx[383]: engine: Initializing weewx version 
3.6.2
Jan  5 08:10:44 raspberrypi weewx[383]: engine: Using Python 2.7.9 
(default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
Jan  5 08:10:44 raspberrypi weewx[383]: engine: Platform 
Linux-4.4.34-v7+-armv7l-with-debian-8.0
Jan  5 08:10:44 raspberrypi weewx[383]: engine: pid file is 
/var/run/weewx.pid
Jan  5 08:10:44 raspberrypi systemd[1]: weewx.service: Supervising process 
504 which is not our child. We'll most likely not notice when it exits.
Jan  5 08:10:44 raspberrypi weewx[504]: engine: Using configuration file 
/home/weewx/weewx.conf
Jan  5 08:10:44 raspberrypi weewx[504]: engine: Loading station type 
ObserverIP (user.observerip)
Jan  5 08:10:44 raspberrypi weewx[504]: observerip: version is 0.5mw
Jan  5 08:10:44 raspberrypi weewx[504]: import of driver failed: [Errno 
101] Network is unreachable ()
Jan  5 08:10:44 raspberrypi weewx[504]: engine: Unable to load driver: 
[Errno 101] Network is unreachable
Jan  5 08:10:44 raspberrypi weewx[504]:   Exiting...
Jan  5 08:10:44 raspberrypi systemd[1]: weewx.service: main process exited, 
code=exited, status=4/NOPERMISSION
Jan  5 08:10:44 raspberrypi systemd[1]: Unit weewx.service entered failed 
state.
Jan  5 08:10:45 raspberrypi dhcpcd[382]: eth0: carrier acquired

Jerry

On Wednesday, January 4, 2017 at 1:41:46 PM UTC-5, Jerry Deibel wrote:
>
> Hi,
> I have been running weewx with my ambient 1400 Observer for about 2 years. 
> Last year I moved the OP system to a USB stick to save wear and tear on the 
> SD card and  last week the USB had a sector error and would not load.  So 
> much for moving over from a SD card to a USB stick.
>
> I reloaded Jessi OP system on the Raspberry PI, but this time just on the 
> SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up 
> and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or 
> so to make sure everything was ok.  I backup my archive every day so I 
> restored the archive database for the last year as well.   
> The last 2 years I ran a daemon process to run it on power up , so today I 
> did that..
>
> Now my problem is . 
> After doing the following to run it on power up
> sudo util/init.d/weewx.debian to /etc/init.d/weewx)
> sudo chmod +x /etc/init.d/weewx
> sudo update-rc.d weewx defaults 98
>
> I then tried to startsudo /etc/init.d/weewx start : no log 
> outpur and ps aux shows not running
> It DID  not start
> I then stopped it..  sudo /etc/init.d/weewx  stop
> I then started it again.   sudo /etc/init.d/weewx start
> AND IT STARTED    Outputting to log and ...  ps aux | grep weewx   
>  ... shows it running ok.
>
> Also, it does not start on  a power up.  
>
> Here is the log right after power up ..
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/index.bdmv
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/BACKUP/index.bdmv
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org 
> -> 45.79.1.70
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org 
> -> 195.21.137.209
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org 
> -> 104.131.53.252
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org 
> -> 138.68.2.126
> Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
> Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
> Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
> Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopping LSB: weewx weather 
> system...
> Jan  4 13:30:56 raspberrypi weewx[1567]: Stopping weewx weather system: 
> weewx not running
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Initializing weewx 
> version 3.6.2
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Jan  4 13:31:09 

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[vince]

On Wednesday, January 4, 2017 at 3:39:35 PM UTC-8, Jerry Deibel wrote:
>
> Mwall,
>
> Here is the log after a shutdown and start.I started the log as soon 
> as it booted,  but how does that tell up anything.
>
> pi@raspberrypi:~ $ tail -f /var/log/syslog
>
>>
>>
try "tail -n 300 -f /var/log/syslog" to go back 300 lines

"tail -f" just shows you the lines from now forward, not stuff that 
happened before you typed the command 

-- 
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.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Jerry Deibel]

Mwall,

Here is the log after a shutdown and start.I started the log as soon as 
it booted,  but how does that tell up anything.

pi@raspberrypi:~ $ tail -f /var/log/syslog
Jan  4 18:33:31 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[655]: 
index_parse.c:191: indx_parse(): error opening 
/media/pi/rootfs/BDMV/index.bdmv
Jan  4 18:33:31 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[655]: 
index_parse.c:191: indx_parse(): error opening 
/media/pi/rootfs/BDMV/BACKUP/index.bdmv
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 0.debian.pool.ntp.org -> 
104.156.99.226
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 1.debian.pool.ntp.org -> 
138.68.2.126
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 2.debian.pool.ntp.org -> 
199.223.248.99
Jan  4 18:33:31 raspberrypi ntpd_intres[533]: DNS 3.debian.pool.ntp.org -> 
108.59.2.24
Jan  4 18:33:36 raspberrypi dhcpcd[412]: eth0: no IPv6 Routers available
Jan  4 18:33:54 raspberrypi systemd[1]: Time has been changed
Jan  4 18:33:54 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
next retry is Wed Jan  4 18:34:24 2017 [try http://www.rsyslog.com/e/2007 ]

jerry


>
>
>

-- 
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.

Re: [weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Jerry Deibel]

mwall,

I tried the weewx unit file and I can start it using

sudo systemctl start weewx

and that works  and I can stop it using...

sudo systemctl stop weewx

But weewx still will not start on a reboot.

I did the 
sudo systemctl enable weewx

Jerry




On Wed, Jan 4, 2017 at 2:34 PM, mwall  wrote:

> jerry,
>
> you might try using a pure systemd configuration instead of using an rc
> script.  the weewx rc script *should* work with systemd, but lately there
> have been postings to this forum that indicate that might be changing.
>
> get rid of the rc script:
>
> sudo /etc/init.d/weewx stop
> sudo update-rc.d weewx remove
> sudo rm /etc/init.d/weewx
>
> install the weewx unit file:
>
> https://github.com/weewx/weewx/wiki/systemd
>
> data are stored in the 'archive' table, which is in the file weewx.sdb if
> you are using sqlite.  the other tables in that database are for daily
> aggregates.
>
> you can use the .schema command to see all of the tables and their
> schemas.
>
> 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/4tqBDJjpKuc/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[mwall]

jerry,

you might try using a pure systemd configuration instead of using an rc 
script.  the weewx rc script *should* work with systemd, but lately there 
have been postings to this forum that indicate that might be changing.

get rid of the rc script:

sudo /etc/init.d/weewx stop
sudo update-rc.d weewx remove
sudo rm /etc/init.d/weewx

install the weewx unit file:

https://github.com/weewx/weewx/wiki/systemd

data are stored in the 'archive' table, which is in the file weewx.sdb if 
you are using sqlite.  the other tables in that database are for daily 
aggregates.

you can use the .schema command to see all of the tables and their schemas.

m

-- 
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.

[weewx-user] Re: Weewx won't start with daemon and by itself on 1st try

[Andrew Milner]

1. Install phpliteadmin to view/amend SQLite databases

2. check user guide for how to remove 'spikes' for your incorrect rain 
reading

3. if you installed via setup.py the daemon is located at sudo 
/etc/init.d/weewx start or sudo /etc/init.d/weewx stop etc etc etc





On Wednesday, 4 January 2017 20:41:46 UTC+2, Jerry Deibel wrote:

> Hi,
> I have been running weewx with my ambient 1400 Observer for about 2 years. 
> Last year I moved the OP system to a USB stick to save wear and tear on the 
> SD card and  last week the USB had a sector error and would not load.  So 
> much for moving over from a SD card to a USB stick.
>
> I reloaded Jessi OP system on the Raspberry PI, but this time just on the 
> SD card  using the SETUP.PI procedure ( no USB this time) and weewx is up 
> and running using  [ sudo ./bin/weewxd weewx.conf ].  I ran it for a day or 
> so to make sure everything was ok.  I backup my archive every day so I 
> restored the archive database for the last year as well.   
> The last 2 years I ran a daemon process to run it on power up , so today I 
> did that..
>
> Now my problem is . 
> After doing the following to run it on power up
> sudo util/init.d/weewx.debian to /etc/init.d/weewx)
> sudo chmod +x /etc/init.d/weewx
> sudo update-rc.d weewx defaults 98
>
> I then tried to startsudo /etc/init.d/weewx start : no log 
> outpur and ps aux shows not running
> It DID  not start
> I then stopped it..  sudo /etc/init.d/weewx  stop
> I then started it again.   sudo /etc/init.d/weewx start
> AND IT STARTED    Outputting to log and ...  ps aux | grep weewx   
>  ... shows it running ok.
>
> Also, it does not start on  a power up.  
>
> Here is the log right after power up ..
> pi@raspberrypi:~ $ tail -f /var/log/syslog
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/index.bdmv
> Jan  4 10:50:18 raspberrypi org.gtk.Private.UDisks2VolumeMonitor[664]: 
> index_parse.c:191: indx_parse(): error opening 
> /media/pi/rootfs/BDMV/BACKUP/index.bdmv
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 0.debian.pool.ntp.org 
> -> 45.79.1.70
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 1.debian.pool.ntp.org 
> -> 195.21.137.209
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 2.debian.pool.ntp.org 
> -> 104.131.53.252
> Jan  4 10:50:20 raspberrypi ntpd_intres[542]: DNS 3.debian.pool.ntp.org 
> -> 138.68.2.126
> Jan  4 10:50:24 raspberrypi dhcpcd[420]: eth0: no IPv6 Routers available
> Jan  4 10:51:12 raspberrypi systemd[1]: Time has been changed
> Jan  4 10:51:12 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:51:42 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:51:12 raspberrypi systemd[560]: Time has been changed
> Jan  4 10:53:11 raspberrypi rsyslogd-2007: action 'action 17' suspended, 
> next retry is Wed Jan  4 10:53:41 2017 [try http://www.rsyslog.com/e/2007 
> ]
> Jan  4 10:53:11 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopping LSB: weewx weather 
> system...
> Jan  4 13:30:56 raspberrypi weewx[1567]: Stopping weewx weather system: 
> weewx not running
> Jan  4 13:30:56 raspberrypi systemd[1]: Stopped LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi systemd[1]: Starting LSB: weewx weather 
> system...
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Initializing weewx 
> version 3.6.2
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Using Python 2.7.9 
> (default, Sep 17 2016, 20:26:04) #012[GCC 4.9.2]
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: Platform 
> Linux-4.4.34-v7+-armv7l-with-debian-8.0
> Jan  4 13:31:09 raspberrypi weewx[1627]: engine: pid file is 
> /var/run/weewx.pid
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Using configuration file 
> /home/weewx/weewx.conf
> Jan  4 13:31:09 raspberrypi weewx[1631]: engine: Loading station type 
> ObserverIP (user.observerip)
> Jan  4 13:31:09 raspberrypi weewx[1616]: Starting weewx weather system: 
> weewx.
> Jan  4 13:31:09 raspberrypi systemd[1]: Started LSB: weewx weather system.
> Jan  4 13:31:09 raspberrypi weewx[1631]: observerip: version is 0.5mw
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: Unknown firmware 
> version: ��
> Jan  4 13:31:10 raspberrypi weewx[1631]: observerip: polling interval is 
> 16.0
> Jan  4 13:31:10 raspberrypi weewx[1631]: engine: StdConvert target unit is 
> 0x1
> Jan  4 13:31:10 raspberrypi weewx[1631]: 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, 
>