Matthew, I might have included this information: drwxr-xr-x. 1 weewx weewx 578 Jan 23 18:15 . drwxr-xr-x. 1 root root 6320 Jan 23 12:06 .. drwxr-xr-x. 1 weewx weewx 8 Jan 19 18:36 bin drwxr-xr-x. 1 weewx weewx 160 Jan 21 12:18 examples drwxr-xr-x. 1 weewx weewx 178 Jan 21 12:18 import drwxr-xr-x. 1 weewx weewx 10 Jan 21 12:18 logrotate.d drwxr-xr-x. 1 weewx weewx 22 Jan 21 12:18 logwatch drwxr-xr-x. 1 weewx weewx 20 Jan 21 12:18 rsyslog.d drwxr-xr-x. 1 weewx weewx 78 Jan 21 12:18 skins drwxr-xr-x. 1 weewx weewx 54 Jan 21 12:18 systemd drwxr-xr-x. 1 weewx weewx 22 Jan 21 12:18 udev -rw-r--r--. 1 weewx weewx 19474 Jan 23 18:15 weewx.conf -rw-r--r--. 1 weewx weewx 23138 Jan 30 2023 weewx.conf-4.10.1 -rw-r--r--. 1 weewx weewx 23146 Jan 19 18:36 weewx.conf-4.10.2-5.0.0 -rw-r--r--. 1 weewx weewx 23142 Jun 8 2021 weewx.conf-4.5.1 -rw-r--r--. 1 weewx weewx 23137 Feb 6 2022 weewx.conf-4.6.0 -rw-r--r--. 1 weewx weewx 23137 Feb 11 2022 weewx.conf-4.6.1 -rw-r--r--. 1 weewx weewx 23137 Feb 11 2022 weewx.conf-4.6.2 -rw-r--r--. 1 weewx weewx 23137 Mar 5 2022 weewx.conf-4.7.0 -rw-r--r--. 1 weewx weewx 23137 Apr 24 2022 weewx.conf-4.8.0 -rw-r--r--. 1 weewx weewx 23220 Oct 25 2022 weewx.conf-4.9.1 -rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf-5.0.0 -rw-r--r--. 1 weewx weewx 23138 Feb 23 2023 weewx.conf.prev -rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf.rpmnew -rw-r--r--. 1 weewx weewx 23138 Feb 23 2023 weewx.conf.rpmsave
joev.mi _ _ _ _ _ _ _ _ _ _ On Wednesday, January 24, 2024 at 2:38:38 PM UTC-5 Joseph Verreau wrote: > Matthew, > answers to above: > 1) located in /usr/lib/systemd/system I have these two: > -rw-r--r--. 1 root root 368 Jan 21 12:18 weewx.service > -rw-r--r--. 1 root root 876 Jan 21 12:18 weewx@.service > > 2) located in xps13-9305:/etc/systemd/system/multi-user.target.wants/ I > have the following but no weewx files in /etc/init.d or /etc/sysetmd/system > lrwxrwxrwx. 1 root root 37 Jan 21 12:18 weewx.service -> > /usr/lib/systemd/system/weewx.service > > 3) xps13-9305:/etc/init.d# grep weewx /etc/passwd > weewx:x:971:960::/home/weewx:/sbin/nologin > > 4) 60-weewx.rules attached > > and thank you for your response. > > joev.mi > _ _ _ _ _ _ _ _ _ _ > > On Wednesday, January 24, 2024 at 7:20:47 AM UTC-5 matthew wall wrote: > >> On Tuesday, January 23, 2024 at 10:49:43 PM UTC-5 joev...@gmail.com >> wrote: >> >> My upgrade from 4.10 to 5.0 on my laptop, i.e. not connected to a real >> weather station thus running with the simulator device, has actually gone >> very nicely but for one puzzling report. I thought installing on my laptop >> would better prepare me for installing on my desktop that is actually >> connected to my weather station. >> >> Jan 23 12:06:12 xps13-9305 systemd-udevd[632]: >> /usr/lib/udev/rules.d/60-weewx.rules:4 Unknown group '{weewx}', ignoring. >> >> >> 1) what is User and Group in /usr/lib/systemd/system/weewx.service? >> >> 2) do any of these files exist on your system: >> /etc/systemd/system/weewx.service >> /etc/init.d/weewx >> /etc/init.d/weewx-multi >> >> 3) what do you see when you do this: >> grep weewx /etc/passwd >> >> 4) please post the contents of the file >> /usr/lib/udev/rules.d/60-weewx.rules >> >> installation history: >> >> initially installed on this server running fedora in 2014 via the >> setup.py method. In 2020 I switched to the dnf repo method. When I first >> ran this upgrade to ver 5.0 using dnf upgrade I noticed that I ended up >> with the application using root:root for user:group assignments of >> directories and files. Reading the installation guide some more I noted >> there was a transition to weewx:weewx for those assignments. So I erased >> the application then ran dnf install weewx following along the instructions >> for fedora versions 34+. That seemed to correct the issue of ownership by >> creating the missing user and group. >> >> I don’t observe anything else out of place. My install starts against the >> simulator device, and enters the main loop where it updates the database as >> I would expect. >> >> Question: does the error reported above as in the journal imply a >> mis-configuration? Why is the group weewx identified as unknown? >> >> >> when you upgrade from v4 to v5 using dnf, weewxd should run as >> root:root. this is because the installer will try to respect your previous >> installation, and continue to run with the same user and permissions as the >> previous install. >> >> when you do a new install of v5 using dnf, weewxd should run as >> weewx:weewx. >> >> note that when you 'erase' an installation with dnf, the database, >> located in /var/lib/weewx, will not be deleted. so if you were to run the >> v5 installer at this point, even though it is technically a new install, >> because of the /var/lib/weewx with root:root ownership, the 'new' install >> will run as root:root. >> >> if you saw that v5 was running as root:root, that means you must have >> deleted /var/lib/weewx, or changed its permissions. could you verify this? >> >> m >> > -- 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/19e482b8-a240-4094-ad9b-523a56e20524n%40googlegroups.com.