Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread geni08...@gmail.com
Thank you very much, everything seems to be working matthew wall schrieb am Freitag, 16. Februar 2024 um 16:35:20 UTC+1: > On Friday, February 16, 2024 at 10:13:19 AM UTC-5 geni08...@gmail.com > wrote: > > Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: PermissionError: [Errno 13] > Keine Berecht

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread matthew wall
On Friday, February 16, 2024 at 10:13:19 AM UTC-5 geni08...@gmail.com wrote: Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: PermissionError: [Errno 13] Keine Berechtigung: '/var/www/html/weewx/json/24h.json' Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread 'michael.k...@gmx.at' via weewx-user
The user which ist running weewxd has no permission to generate/modify the resource "/var/www/html/weewx/json/24h.json" Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: [Errno 13] Keine Berechtigung: '/var/www/html/weewx/json/24h.json' geni08...@gmail.com

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread geni08...@gmail.com
I have used this sudo usermod -aG dialout weewx sudo systemctl restart weewx Weewx is running but there is another authorization problem Feb 16 16:10:27 Wetter-Raspi4 weewxd[440995]: DEBUG user.rainrate: new_loop(1708096227): Added/updated pkt[rainRate] of 0.00 Feb 16 16:10:27 Wetter-Raspi

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread matthew wall
On Friday, February 16, 2024 at 7:57:08 AM UTC-5 geni08...@gmail.com wrote: where can i see which user starts weewxd? if weewxd is running, do this: ps aux | grep weewxd the first word is the user running weewxd if weewxd is not running, then check the value for 'User' in the systemd unit

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread geni08...@gmail.com
where can i see which user starts weewxd? It worked with weewx matthew wall schrieb am Freitag, 16. Februar 2024 um 13:47:00 UTC+1: > On Friday, February 16, 2024 at 7:43:26 AM UTC-5 geni08...@gmail.com > wrote: > > After the restore a new attempt, what is missing? > > -- Journal begins at Fri 2

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread matthew wall
On Friday, February 16, 2024 at 7:43:26 AM UTC-5 geni08...@gmail.com wrote: After the restore a new attempt, what is missing? -- Journal begins at Fri 2024-02-02 10:19:01 CET. -- Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: self.port.openPort() Feb 16 13:18:

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread geni08...@gmail.com
After the restore a new attempt, what is missing? -- Journal begins at Fri 2024-02-02 10:19:01 CET. -- Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: self.port.openPort() Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: File "/u

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-13 Thread matthew wall
On Tuesday, February 13, 2024 at 4:13:27 AM UTC-5 geni08...@gmail.com wrote: The third time I tried the Apt configuration, it found weewx. The installation worked so far except for the dpkg: Warnung: Altes Verzeichnis. Unfortunately, weewx did not react after that and a reboot did not work any

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-13 Thread geni08...@gmail.com
The third time I tried the Apt configuration, it found weewx. The installation worked so far except for the dpkg: Warnung: Altes Verzeichnis. Unfortunately, weewx did not react after that and a reboot did not work anymore. Now I have to restore the backup and try again. What went wrong? pi@Wette

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-12 Thread Tom Keffer
It would be easiest if you just followed the directions in the Debian quick start guide again. It will cause the correct line to be put in /etc/apt/sources.list.d -tk On Mon, Feb 12, 2024 at 9:00 AM geni08...@gmail.com wrote: > @vince > Which