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.targetAfter=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 On Wednesday 7 February 2024 at 20:38:56 UTC Tom Keffer wrote: > 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. > > On Wed, Feb 7, 2024 at 12:06 PM Michael Swain <[email protected]> wrote: > >> 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.targetAfter=network-online.target* >> >> into the weewx.service file in /lib/systemd/system >> >> fixed my issue. Weewx now loads and connects on a system reboot. >> >> On Monday, February 5, 2024 at 3:22:28 PM UTC-5 Neil B wrote: >> >>> 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 >>> >> -- >> > 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]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/weewx-user/3583ce91-078c-497f-9b21-b70d3be1fce7n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/weewx-user/3583ce91-078c-497f-9b21-b70d3be1fce7n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/ea12c49a-56b9-4346-8453-2b44b64d70b7n%40googlegroups.com.
