> On Mar 30, 2025, at 22:52, n7uv...@gmail.com <n7uv....@gmail.com> wrote:
>
> Sorry for the long delay. A power outage had caused the Davis IP Data Logger
> to drop off the network. I unplugged the console from the network, then
> recycled power on the console. However, I lost several hours of data that way.
>
> Today I had another power outage, the IP Data logger doesn't ping anymore,
> instead of just doing what I did before and losing data I thought I'd post
> the log.
>
> ...
> Mar 30 19:38:43 rpi-weewx weewxd[1334]: CRITICAL weewx.engine: ****
> weewx.WeeWxIOError: [Errno 113] No route to host
> Mar 30 19:38:43 rpi-weewx weewxd[1334]: CRITICAL __main__: Unable to load
> driver: [Errno 113] No route to host
> Mar 30 19:38:43 rpi-weewx weewxd[1334]: CRITICAL __main__: ****
> Exiting...
> Mar 30 19:38:43 rpi-weewx systemd[1]: weewx.service: Main process exited,
> code=exited, status=4/NOPERMISSION
> Mar 30 19:38:43 rpi-weewx systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
> Raspberry Pi 4, Bookworm 64-bit, Davis console connected via Davis IP data
> logger to the local network. Currently does not ping. The console is showing
> current data, but weewx attempts to read and then exits.
>
> Any ideas would be muchly appreciated!
possible problems:
1) 'no route to host' usually indicates that weewx is starting before the
network has initialized on the pi. if this is the problem, you can:
a) use the loop-on-init option so that weewx keeps retrying on startup
b) configure your init system so that weewx will not start until network is up
2) the davis console does not show up on the network until after weewx has
tried to connect to it. if this is the problem, use loop-on-init so weewx will
keep retrying when it starts up.
3) the NOPERMISSION coming from systemd is probably a red herring, since you
are using the ip interface to the davis, not usb. hopefully the NOPERMISSION
goes away when you fix 1 and/or 2.
4) your last comment about the davis not being ping-able might indicate a
bigger network problem, such as the davis and the pi being on different
subnets, or your dhcp server is messed up, or you have multiple dhcp servers on
the same network segment that are offering conflicting netmask/routing
information, or ... be sure that your network is configured properly.
--
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.
To view this discussion visit
https://groups.google.com/d/msgid/weewx-user/D8EFED57-94B9-4EC8-B517-63E1A3E88F4E%40gmail.com.
