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*




On Mon, Feb 5, 2024 at 12:43 PM Neil B <[email protected]> wrote:

> 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
>
> On Monday 5 February 2024 at 20:27:06 UTC Tom Keffer wrote:
>
>> 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
>>
>> On Mon, Feb 5, 2024 at 12:22 PM Neil B <[email protected]> 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/b3211a86-cd93-4761-a7ee-08f104614c9en%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/b3211a86-cd93-4761-a7ee-08f104614c9en%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/13f72cec-a97c-4b9e-a03f-db32778d38d5n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/13f72cec-a97c-4b9e-a03f-db32778d38d5n%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/CAPq0zEDwEn526GmNnbLPw11btC1EwkY%2BHs8atYeUYST9oAc4kw%40mail.gmail.com.

Reply via email to