Another Davis Vantage unable to start concern

[Neil B]

Hi

I performed an upgrade to 5.0.0 at the weekend and have had two main issues. I'm putting to one side for now that the upgrade seemed to correct the database and I needed to create a new one. The main issue is similar to other Davis Vantage Pro users. Before the upgrade all worked fine, WEEWX started every time without issue. Now if I boot from cold (or a reboot) I get a critical error. My Vantage Pro is connected via ethernet using the IP adaptor. The error below is what I receive. Ironically as my device is remotely housed, I use SSH to connect to it (it's on a Raspberry Pi running debian bookworm). Therefore the network must be working. I wondering if it needs a delay or a dependency when starting WEEWX. Performing a manual start after this error works every time. Also after failing to start if i run 'weectl device --info' it correctly reports the Vantage weather station. Any help would be appreciated (I see others are having a similar issue with USB connected Davis Vantage Pros). Here is the error:

Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL weewx.engine:     ****      Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in __init__
Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL weewx.engine:     ****      self.port.openPort()
Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 359, in openPort
Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL weewx.engine:     ****      raise weewx.WeeWxIOError(ex)
Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL weewx.engine:     ****  weewx.WeeWxIOError: [Errno 101] Network is unreachable
Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL __main__: Unable to load driver: [Errno 101] Network is unreachable
Feb 05 19:15:56 WEATHER weewxd[473]: CRITICAL __main__:     ****  Exiting...
Feb 05 19:15:56 WEATHER systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION
Feb 05 19:15:56 WEATHER systemd[1]: weewx.service: Failed with result 'exit-code'.

Thanks

Neil

[Tom Keffer]

Two things:

1. Try upgrading to v5.0.1. It fixes some permission issues for Debian installs. It's remotely possible that's what you're experiencing.

2. Please set debug=1, then restart. Post from the restart.

We'll figure this out.

-tk

--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b3211a86-cd93-4761-a7ee-08f104614c9en%40googlegroups.com.

[Neil B]

Hi Tom  

Many thanks for the prompt reply. I should have mentioned that I upgraded to v.5.0.1 early today, that made no difference. I've just set 'debug = 1' and restarted. The "weewx" log looks exactly the same (no additional info). Therefore, I haven't repeated it. I'm finding the only log I can see is when using:

sudo journalctl -u weewx -f

If I try the log I used to use on v.4 (i.e. sudo tail -f /var/log/syslog) it just says 'No such file or directory'. Ditto if I replace syslog with messages.

Here is the log without specifically specifying 'weewx' (not sure if this is helpful):

Feb 05 20:40:28 WEATHER ntpd[658]: DNS: dns_take_status: 2.debian.pool.ntp.org=>good, 8
Feb 05 20:40:29 WEATHER ntpd[658]: DNS: dns_probe: 1.debian.pool.ntp.org, cast_flags:8, flags:101
Feb 05 20:40:29 WEATHER ntpd[658]: DNS: dns_check: processing 1.debian.pool.ntp.org, 8, 101
Feb 05 20:40:29 WEATHER ntpd[658]: DNS: Pool skipping: 104.238.174.158
Feb 05 20:40:29 WEATHER ntpd[658]: DNS: Pool skipping: 185.103.119.60
Feb 05 20:40:29 WEATHER ntpd[658]: DNS: Pool skipping: 77.68.81.77
Feb 05 20:40:29 WEATHER ntpd[658]: DNS: Pool skipping: 188.114.116.1
Feb 05 20:40:29 WEATHER ntpd[658]: DNS: dns_take_status: 1.debian.pool.ntp.org=>good, 8
Feb 05 20:40:29 WEATHER sudo[864]:       pi : TTY=pts/0 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/journalctl -f
Feb 05 20:40:29 WEATHER sudo[864]: pam_unix(sudo:session): session opened for user root(uid=0) by pi(uid=1000)
Feb 05 20:40:30 WEATHER ntpd[658]: DNS: dns_probe: 0.debian.pool.ntp.org, cast_flags:8, flags:101
Feb 05 20:40:30 WEATHER ntpd[658]: DNS: dns_check: processing 0.debian.pool.ntp.org, 8, 101
Feb 05 20:40:30 WEATHER ntpd[658]: DNS: Pool skipping: 81.128.218.110
Feb 05 20:40:30 WEATHER ntpd[658]: DNS: Pool skipping: 109.74.206.120
Feb 05 20:40:30 WEATHER ntpd[658]: DNS: Pool skipping: 217.114.59.3
Feb 05 20:40:30 WEATHER ntpd[658]: DNS: Pool skipping: 162.159.200.123
Feb 05 20:40:30 WEATHER ntpd[658]: DNS: dns_take_status: 0.debian.pool.ntp.org=>good, 8
Feb 05 20:40:44 WEATHER ntpd[658]: CLOCK: time stepped by 14.228062
Feb 05 20:40:44 WEATHER ntpd[658]: INIT: MRU 10922 entries, 13 hash bits, 65536 bytes
Feb 05 20:40:46 WEATHER systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Feb 05 20:40:47 WEATHER dhcpcd[554]: eth0: no IPv6 Routers available
Feb 05 20:40:50 WEATHER dhcpcd[554]: wlan0: no IPv6 Routers available
Feb 05 20:40:57 WEATHER systemd[1]: systemd-fsckd.service: Deactivated successfully.
Feb 05 20:41:00 WEATHER systemd[1]: systemd-hostnamed.service: Deactivated successfully.

I don't use DHCP - I have a static IP address assigned to the Pi and am using the LAN port, connected to a gigabit ethernet switch. I also prefer IPv4.

I should point out that I have a very basic knowledge of Linux, hence my posting to the group.

Thanks

Neil

[Tom Keffer]

Are you saying that if you use the command "journalctl -u weewx", you get only the 10 lines you included in the original post? 

NB: you want

journalctl -u weewx

NOT

journalctl -u weewx -f

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/13f72cec-a97c-4b9e-a03f-db32778d38d5n%40googlegroups.com.

[Neil B]

Me again!!  Just thought I would add some more info.

I terms of your last reply to me, yes I only get the 10 lines before all grinds to a halt. I am showing below what I get after a reboot and then immediately after I manually start the software running.

==================

Once I reboot the box the only WEEWX messages I get are (no change):

Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL weewx.engine:     ****      Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in __init__
Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL weewx.engine:     ****      self.port.openPort()
Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL weewx.engine:     ****    File "/usr/share/weewx/weewx/drivers/vantage.py", line 359, in openPort
Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL weewx.engine:     ****      raise weewx.WeeWxIOError(ex)
Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL weewx.engine:     ****  weewx.WeeWxIOError: [Errno 101] Network is unreachable
Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL __main__: Unable to load driver: [Errno 101] Network is unreachable
Feb 05 20:53:10 WEATHER weewxd[523]: CRITICAL __main__:     ****  Exiting...
Feb 05 20:53:10 WEATHER systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION
Feb 05 20:53:10 WEATHER systemd[1]: weewx.service: Failed with result 'exit-code'.

If I then manually start WEEWX (sudo systemctl start weewx), there is more of a detailed log (I know the WOW errors are not important and I stopped the log as it was about to do the webpage processing):

Feb 05 20:54:10 WEATHER weewxd[877]: INFO __main__: Entry path: /usr/share/weewx/weewxd.py
Feb 05 20:54:10 WEATHER weewxd[877]: INFO __main__: WEEWX_ROOT: /etc/weewx
Feb 05 20:54:10 WEATHER weewxd[877]: INFO __main__: Configuration file: /etc/weewx/weewx.conf
Feb 05 20:54:10 WEATHER weewxd[877]: INFO __main__: User module: /etc/weewx/bin/user
Feb 05 20:54:10 WEATHER weewxd[877]: INFO __main__: Debug: 1
Feb 05 20:54:10 WEATHER weewxd[877]: DEBUG __main__: Initializing engine
Feb 05 20:54:10 WEATHER weewxd[877]: INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
Feb 05 20:54:10 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Driver version is 3.6.2
Feb 05 20:54:10 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Option loop_request=1
Feb 05 20:54:10 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Opened up ethernet host 192.168.1.249 on port 22222. timeout=4.0, tcp_send_delay=0.5
Feb 05 20:54:11 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Feb 05 20:54:12 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Hardware type is 16
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: ISS ID is 1
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Hardware name: Vantage Pro2
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.engine.StdTimeSynch
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.engine.StdTimeSynch
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.engine.StdConvert
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.engine: StdConvert target unit is 0x1
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.engine.StdConvert
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.engine.StdCalibrate
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.engine.StdCalibrate
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.engine.StdQC
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.engine.StdQC
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.wxservices.StdWXCalculate
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.manager: Daily summary version is 4.0
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.wxservices.StdWXCalculate
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdWXXTypes
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdWXXTypes
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdPressureCooker
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdPressureCooker
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdRainRater
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdRainRater
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.wxxtypes.StdDelta
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.wxxtypes.StdDelta
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.engine.StdArchive
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.engine: Archive will use data binding wx_binding
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.engine: Record generation will be attempted in 'hardware'
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.engine: The archive interval in the configuration file (300) does not match the station hardware interval (60).
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.engine: Using archive interval of 60 seconds (specified by hardware)
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Use LOOP data in hi/low calculations: 1
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.engine.StdArchive
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.restx.StdStationRegistry
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.restx: StationRegistry: Registration not requested.
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.restx.StdStationRegistry
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.restx.StdWunderground
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.restx: Wunderground: Posting not enabled.
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.restx.StdWunderground
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.restx.StdPWSweather
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.restx: PWSweather: Posting not enabled.
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.restx.StdPWSweather
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.restx.StdCWOP
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.restx: CWOP: Posting not enabled.
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.restx.StdCWOP
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.restx.StdWOW
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.restx: WOW: Data for station 1205799 will be posted
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.restx.StdWOW
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.restx.StdAWEKAS
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.restx: AWEKAS: Posting not enabled.
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.restx.StdAWEKAS
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.engine.StdPrint
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.engine.StdPrint
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Loading service weewx.engine.StdReport
Feb 05 20:54:16 WEATHER weewxd[877]: INFO weewx.engine: 'pyephem' detected, extended almanac data is available
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.engine: Finished loading service weewx.engine.StdReport
Feb 05 20:54:16 WEATHER weewxd[877]: INFO __main__: Starting up weewx version 5.0.1
Feb 05 20:54:16 WEATHER weewxd[877]: DEBUG weewx.manager: Daily summary version is 4.0
Feb 05 20:54:17 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Feb 05 20:54:18 WEATHER weewxd[877]: INFO weewx.engine: Clock error is -1.46 seconds (positive is fast)
Feb 05 20:54:18 WEATHER weewxd[877]: INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Feb 05 20:54:18 WEATHER weewxd[877]: INFO weewx.manager: Starting backfill of daily summaries
Feb 05 20:54:18 WEATHER weewxd[877]: INFO weewx.manager: Daily summaries up to date
Feb 05 20:54:18 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Getting archive packets since 2024-02-05 20:52:00 GMT (1707166320)
Feb 05 20:54:19 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Feb 05 20:54:21 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Retrieving 1 page(s); starting index= 1
Feb 05 20:54:22 WEATHER weewxd[877]: INFO weewx.manager: Added record 2024-02-05 20:53:00 GMT (1707166380) to database 'weewx.sdb'
Feb 05 20:54:22 WEATHER weewxd[877]: INFO weewx.manager: Added record 2024-02-05 20:53:00 GMT (1707166380) to daily summary in 'weewx.sdb'
Feb 05 20:54:22 WEATHER weewxd[877]: INFO weewx.manager: Added record 2024-02-05 20:54:00 GMT (1707166440) to database 'weewx.sdb'
Feb 05 20:54:22 WEATHER weewxd[877]: INFO weewx.manager: Added record 2024-02-05 20:54:00 GMT (1707166440) to daily summary in 'weewx.sdb'
Feb 05 20:54:22 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: DMPAFT complete: page timestamp 2024-02-04 02:15:00 GMT (1707012900) less than final timestamp 2024-02-05 20:54:00 GMT (1707166440)
Feb 05 20:54:22 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Catch up complete.
Feb 05 20:54:22 WEATHER weewxd[877]: INFO weewx.engine: Starting main packet loop.
Feb 05 20:54:22 WEATHER weewxd[877]: DEBUG weewx.restx: WOW: Failed upload attempt 1: HTTP Error 429: Too frequent observations.
Feb 05 20:54:24 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Feb 05 20:54:24 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Requesting 200 LOOP packets.
Feb 05 20:54:26 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Feb 05 20:54:28 WEATHER weewxd[877]: DEBUG weewx.restx: WOW: Failed upload attempt 2: HTTP Error 429: Too frequent observations.
Feb 05 20:54:33 WEATHER weewxd[877]: DEBUG weewx.restx: WOW: Failed upload attempt 3: HTTP Error 429: Too frequent observations.
Feb 05 20:54:33 WEATHER weewxd[877]: ERROR weewx.restx: WOW: Failed to publish record 2024-02-05 20:53:00 GMT (1707166380): Failed upload after 3 tries
Feb 05 20:54:33 WEATHER weewxd[877]: DEBUG weewx.restx: WOW: wait interval (60 < 300) has not passed for record 2024-02-05 20:54:00 GMT (1707166440)
Feb 05 20:55:15 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Getting archive packets since 2024-02-05 20:54:00 GMT (1707166440)
Feb 05 20:55:16 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Successfully woke up Vantage console
Feb 05 20:55:18 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Retrieving 1 page(s); starting index= 3
Feb 05 20:55:18 WEATHER weewxd[877]: INFO weewx.manager: Added record 2024-02-05 20:55:00 GMT (1707166500) to database 'weewx.sdb'
Feb 05 20:55:18 WEATHER weewxd[877]: INFO weewx.manager: Added record 2024-02-05 20:55:00 GMT (1707166500) to daily summary in 'weewx.sdb'
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: DMPAFT complete: page timestamp 2024-02-04 02:16:00 GMT (1707012960) less than final timestamp 2024-02-05 20:55:00 GMT (1707166500)
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.restx: WOW: wait interval (120 < 300) has not passed for record 2024-02-05 20:55:00 GMT (1707166500)
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Catch up complete.
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Running reports for latest time in the database.
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Requesting 200 LOOP packets.
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Report 'SeasonsReport' not enabled. Skipping.
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Report 'SmartphoneReport' not enabled. Skipping.
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Report 'MobileReport' not enabled. Skipping.
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Running report 'StandardReport'
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Found configuration file /etc/weewx/skins/neowx-material/skin.conf for report 'StandardReport'
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Cannot read localization file /etc/weewx/skins/neowx-material/lang/en.conf for report 'StandardReport': Config file not found: "/etc/weewx/skins/neowx-material/lang/en.conf".
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: **** Using defaults instead.
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.reportengine: Running generators for report 'StandardReport' in directory '/etc/weewx/skins/neowx-material'
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.cheetahgenerator: Using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.DisplayOptions', 'weewx.cheetahgenerator.Extras', 'weewx.cheetahgenerator.Gettext', 'weewx.cheetahgenerator.JSONHelpers', 'weewx.cheetahgenerator.PlotInfo', 'weewx.cheetahgenerator.SkinInfo', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo']
Feb 05 20:55:19 WEATHER weewxd[877]: DEBUG weewx.manager: Daily summary version is 4.0

[Tom Keffer]

That's better.

Looks to me like everything is working as it should. Perhaps it only needed a reboot?

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/3a8c431e-5de2-42f9-b540-f2e6019139bfn%40googlegroups.com.

[Neil B]

Hi Tom.

Perhaps I wasn't clear with what I meant. Let me try this....

When I do a reboot WEEWX does not run. It always STOPS with the critical error (the 10 lines) and I have to manually START the service myself. It is very consistent - reboot and service does not start, issue the manual command to start and it works. This has only happened since going to v5. All was fine on v.4. Is there any more data I can provide you with?

Thanks

Neil

[bell...@gmail.com]

It looks like it is trying to start WeeWX before the network is available. Hopefully someone can help from here. 

[Graham Eddy]

vantage device is on LAN. wireless interface normally not ready until long after weewx tries to start, unusual (but not impossible) for ethernet interface to be so late. try the ‘loop-on-init = 1’ in weewx.conf, or insert a delay in the startup file

⊣GE⊢

[Tom Keffer]

All good suggestions.

For loop_on_init, see this link.

--
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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/F018B0FD-2319-41C3-88B1-10EC577E47FB%40geddy.au.

[Neil B]

Morning.

Good suggestion on "loop on init", however I already have this setting enabled (and have for a long time). I believe this setting applies once the main loop starts, which is much later in the process.

The idea of delaying the start up of WEEWX is good, and I am in favour of this approach. Question is (for the Linux novice) - how can you implement this? Any thoughts?

Thanks

Neil

[Tom Keffer]

One other thing to try: ask systemd to wait until the network is up before trying to start weewxd.

Because you did a DEB install, your systemd unit file should be located in /lib/systemd/system/weewx.service. Under the [Unit] section, add the following two lines:

[Unit]
Wants=network-online.target
After=network-online.target

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b223aeb6-4150-4644-9d41-bc39bbed268en%40googlegroups.com.

[matthew wall]

as i understand it, the "systemd way" is one of these two:

1) override.  to change behavior of a systemd unit that was installed by a deb/rpm package, use the ".d" pattern.

in this case, create the overrides directory:

sudo mkdir /etc/systemd/system/weewx.service.d

then put this into the file /etc/systemd/system/weewx.service.d/waitfornetwork.conf

[Unit]

Wants=network-online.target

After=network-online.target

2) modify. to change the beavior of a systemd unit that was installed by the user/sysadmin, modify the systemd unit in /etc/systemd/system

in this case, add two lines to the [Unit] section of /etc/systemd/system/weewx.service

Wants=network-online.target

After=network-online.target

the other pattern is to use environment variables, but (a) systemd explicitly discourages doing that the standard way by using /etc/default (any linux) or /etc/sysconfig (redhat-specific), and (b) the weewx devs prefer to have everything in a single conf file since environment variables can be difficult to diagnose/support.

i have not done extensive testing with either (1) or (2) above, so apologies for providing examples without solid testing.  but there are just too many systemd variations out there.  maybe when systemd has gotten past its toddler years...

m

[Michael Swain]

I was having a similar issue with my weewx 5.0.0 fresh install on a Raspberry PI 4 running Version 12 (bookworm)  trying to connect to a wifi logger 2 on a Vantage Pro 2 console.  On startup it would exit with a network unreachable error.  Running the start command right after it would start just fine.

Adding 

Wants=network-online.target
After=network-online.target

into the weewx.service file in /lib/systemd/system 

fixed my issue.  Weewx now loads and connects on a system reboot.

[Tom Keffer]

Thanks, Michael. This is good to know. 

There may be standalone installations where there is no network connection, but in general, it's probably a good idea for us to add this to the default unit file.

--

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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/3583ce91-078c-497f-9b21-b70d3be1fce7n%40googlegroups.com.

[Neil B]

Evening all.

Firstly apologies for my delay in replying, I have been away from home on business for two days.

Thanks to you all for your suggestions. Here is what I found on testing these tonight:

1. The solution noted by Tom, Michael and also one of those noted by Matthew (editing weewx.service) didn't work for me. On a reboot the start up still exited with the same error.

2. The slightly different solution (using the same file parameters) noted by Matthew did work on my setup.

So, in summary I used the following:

1. Created the weewx.service.d directory in /etc/systemd/system

2. Created a new waitfornetwork.conf file in the new directory

3. Added in the following configuration:

[Unit]
Wants=network-online.target
After=network-online.target

Now when I reboot the Raspberry Pi the start up progresses normally, indeed by the time I get to check the log file it is well into updating data.

Thank you ALL for your help and excellent suggestions. If anyone fancies helping me with my other issue of recovering lost data after it was "lost" during the upgrade, please let me know and I will start a new conversation. I won't go anywhere near mention how my neowx-material skin is now throwing up warnings as that seems less important. :-)

Thanks

Neil