Hi Vince, Not quite solved. It still fails to start after reboot. I think I solved it before by adding a line somewhere.
I have this in my notes: Wait for network before startup: Add $network to # Required-Start I can't remember where I placed this before or if there's a better way to delay weewx start until the network is ready. Any suggestions? Thanks, Bill On Saturday, January 27, 2024 at 10:27:52 AM UTC-7 vince wrote: > Cool you solved it. Wouldn't have thought that a baud rate thing would > get you network unreachable. > > On Saturday, January 27, 2024 at 8:59:15 AM UTC-8 Bill Hattel wrote: > >> Hi Vince, >> Thank you for replying. It turns out, it was something simple as usual. >> It's not starting at power-up and in my haste to recognize that, I reset >> the Ethernet to serial adapter to factory defaults which set the baud rate >> to 115200. Once I set it back to 19200 and started weewx, it began >> reporting. I'm still having an issue with it starting after reboot, but I >> think I can resolve it without too much trouble. I'd like to hear any >> suggestions you have for that issue though. >> >> As far as the complexity of my setup, I originally started out with the >> Davis Instruments serial module on a PC which was kind of pricey back in >> the early 2000s. The NetBurner approach let me keep my existing hardware >> and add it to my home network for a reasonable cost. >> >> Thanks again! >> Bill >> >> On Friday, January 26, 2024 at 11:11:19 AM UTC-7 vince wrote: >> >>> On Friday, January 26, 2024 at 9:33:35 AM UTC-8 Bill Hattel wrote: >>> >>> I'm having the same issue after an upgrade to 5.0.0-1. I inspected the >>> configuration file even though I selected no changes and found everything >>> was correct. I also completely removed weewx and reinstalled it with a new >>> configuration file. I can communicate with the Davis console through >>> WeatherLink with the same settings and interface with no issue. The port is >>> closed when WeatherLink exits. >>> >>> Davis Vantage Vue >>> Raspberry PI >>> NetBurner SBL2E Dual Serial to Ethernet converter >>> Homemade RS-232 level shifter. >>> >>> >>> Hmmm....that's pretty unusual/exotic hardware connecting the Vue to the >>> pi.... >>> >>> >>> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.drivers.vantage: >>> Socket error while opening port 23 to ethernet host 192.168.50.39. >>> <<<< ******************** this line ************************ >>> Jan 25 19:44:10 raspberrypi weewxd[298]: ERROR weewx.engine: Import of >>> driver failed: [Errno 101] Network is unreachable (<class >>> 'weewx.WeeWxIOError'>) >>> ] >>> >>> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__: Unable to >>> load driver: [Errno 101] Network is unreachable >>> Jan 25 19:44:10 raspberrypi weewxd[298]: CRITICAL __main__: **** >>> Exiting... >>> Jan 25 19:44:10 raspberrypi systemd[1]: weewx.service: Main process >>> exited, code=exited, status=4/NOPERMISSION >>> >>> >>> Network unreachable is a different issue than others are having. >>> >>> What's your weewx system ip ? What is the ip you are trying to talk to >>> ? If they're on different networks you are possibly missing a route on >>> your weewx system. From the weewx system you might try "traceroute -n >>> 192.168.50.39" if the destination address in your logs is correct. >>> >>> This one looks like a routing or packet filter issue on a router in >>> between the weewx box and the serial-to-ethernet converter 'if' they are on >>> different subnets >>> >>> -- 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 on the web visit https://groups.google.com/d/msgid/weewx-user/9db00ef6-f5cf-43f0-a78b-a5bd435944fen%40googlegroups.com.
