[weewx-user] Re: can't seem to find epel-release for fedora fc38
that works. that is the rpm option. rpm is happy, dnf distro-sync is happy and weewx is reporting to my configured services. I think the yum.dnf --skip-broken will just pass on the install/update. On Sunday, February 11, 2024 at 12:41:35 PM UTC-5 matthew wall wrote: > joe, > > the epel-release dependency has been removed for the redhat el8 and el9 > packages. this will appear in the next weewx release (probably 5.0.3, but > perhaps 5.1). > > meanwhile, you can tell rpm to ignore that dependency, since you already > have installed the prereqs that weewx actually uses. > > rpm --nodeps > > for yum/dnf, you could try the skip broken option > > yum --skip-broken > > 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/064c30fe-1594-4dbe-8faf-29c49524e625n%40googlegroups.com.
[weewx-user] Re: can't seem to find epel-release for fedora fc38
Vince, curiously, I tried following those instructions. they worked for upgrading from 4.10 to 5.0.0 but not for upgrading from 5.0.0 to 5.0.2. the first upgrade ran without installing epel-release but yet not requiring to upgrade weewx; the second upgrade just won't. Go figure. joev.mi On Saturday, February 10, 2024 at 6:52:45 PM UTC-5 vince wrote: > Try reading https://www.weewx.com/docs/5.0/quickstarts/redhat/ > > On Saturday, February 10, 2024 at 3:31:48 PM UTC-8 Joseph Verreau wrote: > >> here's another piece, looking at this list of dependencies as below I >> checked to see if they were installed. All but epel-release are on my >> system. >> The issue I'm anticipating is that desktop is running fc38. I won't be >> able to install fc39 unless all the packages have a path to an upgrade >> source. >> Of course I could erase weewx upgrade the OS and then reinstall weewx. >> seems clugey. >> >> Joe Verreau >> >> [jverreau@xps8700 epel-repo]$ sudo dnf repoquery --depends weewx >> Last metadata expiration check: 1:42:39 ago on Sat 10 Feb 2024 04:44:34 >> PM EST. >> /bin/sh >> /usr/bin/getent >> /usr/sbin/groupadd >> /usr/sbin/useradd >> epel-release >> python3 >> python3-cheetah >> python3-configobj >> python3-pillow >> python3-pyserial >> python3-pyusb >> [jverreau@xps8700 epel-repo]$ >> >> On Saturday, February 10, 2024 at 6:19:46 PM UTC-5 Joseph Verreau wrote: >> >>> currently running weewx v 5.0.0-1 following an erase of 4.10. I did >>> finally sort out a few issues, like I didn't know I needed to re-run the >>> device script to add the vantage driver but I got there. Then there was >>> the issue of udev rules but another thread helped me sort that out. My >>> version of 5.0.0-1 is running and reporting to my selected weather services >>> (WOW, CWOP and Wunderground). >>> So moving ahead I thought I could just update from 5.0.0.1 to 5.0.2-1. >>> But I'm getting the error about no path to epel-release. Apparently I had >>> a path to install v5.0.0-1. I've tried a couple alternatives including a >>> fedora site that claimed I could install that package but I either get a >>> response saying it isn't available or I need to install >>> subscription-manager first. >>> >>> [jverreau@xps8700 epel-repo]$ *dnf repolist weewx list* >>> repo id >>> repo name >>> status >>> weewx >>> weewx >>> enabled >>> [jverreau@xps8700 epel-repo]$ *dnf repolist weewx list available* >>> repo id >>> repo name >>> status >>> weewx >>> weewx >>> enabled >>> [jverreau@xps8700 epel-repo]$ *dnf repoquery weewx list available* >>> Last metadata expiration check: 5:17:03 ago on Sat 10 Feb 2024 12:51:11 >>> PM EST. >>> weewx-0:5.0.0-1.el9.noarch >>> weewx-0:5.0.1-1.el9.noarch >>> weewx-0:5.0.1-2.el9.noarch >>> weewx-0:5.0.1-3.el9.noarch >>> weewx-0:5.0.2-1.el9.noarch >>> [jverreau@xps8700 epel-repo]$ *dnf list weewx* >>> Last metadata expiration check: 5:18:10 ago on Sat 10 Feb 2024 12:51:11 >>> PM EST. >>> Installed Packages >>> weewx.noarch >>> 5.0.0-1.el9 >>> @weewx >>> Available Packages >>> weewx.noarch >>> 5.0.2-1.el9 >>> weewx >>> [jverreau@xps8700 epel-repo]$ *sudo dnf upgrade weewx* >>> Last metadata expiration check: 1:25:12 ago on Sat 10 Feb 2024 04:44:34 >>> PM EST. >>> Dependencies resolved. >>> >>> Problem: cannot install the best update candidate for package >>> weewx-5.0.0-1.el9.noarch >>> - nothing provides epel-release needed by weewx-5.0.2-1.el9.noarch >>> from weewx >>> >>> ==
[weewx-user] Re: can't seem to find epel-release for fedora fc38
Matt, I find under fc39 python3-pillow and python3-configobj in @updates repo and python3-cheetah in @fedora repo. These have been on my system since fc34 for the first two and fc39 for python3-cheetah. Curiously, when I ran the update from weewx 4.10 to v5.0.0 it installed. Both my laptop and desktop are running fedora altho I upgraded weewx after upgrading from fc38 to fc39 whereas I upgraded weewx on my desktop before upgrading my desktop to fc39. I mean I'm not implying that was relevant just different in my process. as to installing epel-release on fedora following redhat instructions: I tried that. It requires a subscription to redhat, starting with installing subscription-manager. joev.mi On Saturday, February 10, 2024 at 7:38:53 PM UTC-5 matthew wall wrote: how did you install the other dependencies, i.e., python3-cheetah, python3-pillow, python3-configobj? you could try installing epel-release as per the redhat installation instructions - that will satisfy the epel-release dependency. i guess we should remove the 'epel-release' dependency from the redhat packages. the intent was that by specifying epel as a dependency, one would not have to install epel explicitly. but fedora and redhat are completely different systems; its a challenge to make a package that will work consistently on both, even when your dependencies are few and simple. -- 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/55037a60-7018-476b-8a7a-174217ceb04cn%40googlegroups.com.
[weewx-user] Re: can't seem to find epel-release for fedora fc38
here's another piece, looking at this list of dependencies as below I checked to see if they were installed. All but epel-release are on my system. The issue I'm anticipating is that desktop is running fc38. I won't be able to install fc39 unless all the packages have a path to an upgrade source. Of course I could erase weewx upgrade the OS and then reinstall weewx. seems clugey. Joe Verreau [jverreau@xps8700 epel-repo]$ sudo dnf repoquery --depends weewx Last metadata expiration check: 1:42:39 ago on Sat 10 Feb 2024 04:44:34 PM EST. /bin/sh /usr/bin/getent /usr/sbin/groupadd /usr/sbin/useradd epel-release python3 python3-cheetah python3-configobj python3-pillow python3-pyserial python3-pyusb [jverreau@xps8700 epel-repo]$ On Saturday, February 10, 2024 at 6:19:46 PM UTC-5 Joseph Verreau wrote: > currently running weewx v 5.0.0-1 following an erase of 4.10. I did > finally sort out a few issues, like I didn't know I needed to re-run the > device script to add the vantage driver but I got there. Then there was > the issue of udev rules but another thread helped me sort that out. My > version of 5.0.0-1 is running and reporting to my selected weather services > (WOW, CWOP and Wunderground). > So moving ahead I thought I could just update from 5.0.0.1 to 5.0.2-1. > But I'm getting the error about no path to epel-release. Apparently I had > a path to install v5.0.0-1. I've tried a couple alternatives including a > fedora site that claimed I could install that package but I either get a > response saying it isn't available or I need to install > subscription-manager first. > > [jverreau@xps8700 epel-repo]$ *dnf repolist weewx list* > repo id > repo name > status > weewx > weewx > enabled > [jverreau@xps8700 epel-repo]$ *dnf repolist weewx list available* > repo id > repo name > status > weewx > weewx > enabled > [jverreau@xps8700 epel-repo]$ *dnf repoquery weewx list available* > Last metadata expiration check: 5:17:03 ago on Sat 10 Feb 2024 12:51:11 PM > EST. > weewx-0:5.0.0-1.el9.noarch > weewx-0:5.0.1-1.el9.noarch > weewx-0:5.0.1-2.el9.noarch > weewx-0:5.0.1-3.el9.noarch > weewx-0:5.0.2-1.el9.noarch > [jverreau@xps8700 epel-repo]$ *dnf list weewx* > Last metadata expiration check: 5:18:10 ago on Sat 10 Feb 2024 12:51:11 PM > EST. > Installed Packages > weewx.noarch > 5.0.0-1.el9 > @weewx > Available Packages > weewx.noarch > 5.0.2-1.el9 > weewx > [jverreau@xps8700 epel-repo]$ *sudo dnf upgrade weewx* > Last metadata expiration check: 1:25:12 ago on Sat 10 Feb 2024 04:44:34 PM > EST. > Dependencies resolved. > > Problem: cannot install the best update candidate for package > weewx-5.0.0-1.el9.noarch > - nothing provides epel-release needed by weewx-5.0.2-1.el9.noarch from > weewx > > == > PackageArchitecture > Version Repository >Size > > == > Skipping packages with broken dependencies: > weewx noarch > 5.0.2-1.el9 weewx > 1.2 M > > Transaction Summary > > == > Skip 1 Package > > Nothing to do. > Complete! > [jverreau@xps8700 epel-repo]$ > -- 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/c97d5202-cfc0-485e-b439-7ae94a77517en%40googlegroups.com.
[weewx-user] can't seem to find epel-release for fedora fc38
currently running weewx v 5.0.0-1 following an erase of 4.10. I did finally sort out a few issues, like I didn't know I needed to re-run the device script to add the vantage driver but I got there. Then there was the issue of udev rules but another thread helped me sort that out. My version of 5.0.0-1 is running and reporting to my selected weather services (WOW, CWOP and Wunderground). So moving ahead I thought I could just update from 5.0.0.1 to 5.0.2-1. But I'm getting the error about no path to epel-release. Apparently I had a path to install v5.0.0-1. I've tried a couple alternatives including a fedora site that claimed I could install that package but I either get a response saying it isn't available or I need to install subscription-manager first. [jverreau@xps8700 epel-repo]$ *dnf repolist weewx list* repo id repo name status weewx weewx enabled [jverreau@xps8700 epel-repo]$ *dnf repolist weewx list available* repo id repo name status weewx weewx enabled [jverreau@xps8700 epel-repo]$ *dnf repoquery weewx list available* Last metadata expiration check: 5:17:03 ago on Sat 10 Feb 2024 12:51:11 PM EST. weewx-0:5.0.0-1.el9.noarch weewx-0:5.0.1-1.el9.noarch weewx-0:5.0.1-2.el9.noarch weewx-0:5.0.1-3.el9.noarch weewx-0:5.0.2-1.el9.noarch [jverreau@xps8700 epel-repo]$ *dnf list weewx* Last metadata expiration check: 5:18:10 ago on Sat 10 Feb 2024 12:51:11 PM EST. Installed Packages weewx.noarch 5.0.0-1.el9 @weewx Available Packages weewx.noarch 5.0.2-1.el9 weewx [jverreau@xps8700 epel-repo]$ *sudo dnf upgrade weewx* Last metadata expiration check: 1:25:12 ago on Sat 10 Feb 2024 04:44:34 PM EST. Dependencies resolved. Problem: cannot install the best update candidate for package weewx-5.0.0-1.el9.noarch - nothing provides epel-release needed by weewx-5.0.2-1.el9.noarch from weewx == PackageArchitecture Version Repository Size == Skipping packages with broken dependencies: weewx noarch 5.0.2-1.el9 weewx 1.2 M Transaction Summary == Skip 1 Package Nothing to do. Complete! [jverreau@xps8700 epel-repo]$ -- 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/7218d192-00bb-48f1-ac85-dd8b17f7a433n%40googlegroups.com.
Re: [weewx-user] Weewx v5 fresh install Errno 13
p.p.s I just noticed that I didn't have the subsystem prefix on my rule.
So my entry in 50-localusb.rules is:
SUBSYSTEM=="tty",ATTRS{serial}=="1344794749", ATTRS{manufacturer}=="Silicon
Labs", SYMLINK+="DavisVP"
and I rebooted; altho I still don't have a symlink for /dev/DavisVP
all the same my station is back online, submitting reports to all three
configured weather services
On Saturday, February 10, 2024 at 3:22:52 PM UTC-5 Joseph Verreau wrote:
> p.s. just noticed I'm not getting a symlink for the DavisVP rule but I
> haven't rebooted since I added that local rule.
>
> Joe Verreau
>
> On Saturday, February 10, 2024 at 3:05:41 PM UTC-5 Joseph Verreau wrote:
>
>> hmm. this seems to be my issue on installing 5.0.0 following erasing
>> 4.10. On my own I tried adding weewx user to the wheel group and to
>> sudoers file. I tried what Matt and Paul were discussing about rule
>> changes and yet I still get the "ERROR weewx.engine: Import of driver
>> failed: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission
>> denied:" When I run as root from command line all seems to be good.
>> Should I do a full report with journal log?
>>
>> Joe Verreau KMIOKEMO13
>> Okemos, MI
>>
>> On Wednesday, January 31, 2024 at 11:09:41 AM UTC-5 matthew wall wrote:
>>
>>> On Wednesday, January 31, 2024 at 3:29:36 AM UTC-5 pshep...@gmail.com
>>> wrote:
>>>
>>> Hi Matthew
>>>
>>> Thanks for the information about the various udev folders which helps me
>>> understand their interaction.
>>>
>>> I created a file /etc/udev/50-localusb.rules and inserted the rule.
>>> Also, inherited from Linux Mint 20.1 running Weewx 4.8, I also have the
>>> following line in /etc/udev/descriptive-names.rules
>>>
>>> ATTRS{serial}=="1344794749", ATTRS{manufacturer}=="Silicon Labs",
>>> SYMLINK+="DavisVP"
>>>
>>> and that SYMLINK is created.
>>>
>>> /usr/lib/udev/rules.d/60-weewx.rules contains 10+ lines for different
>>> stations and includes the following for Vantage:
>>>
>>> # davis vantage via usb-serial
>>>
>>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>>
>>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTR{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>>
>>> The vantage SYMLINK is not being created.
>>>
>>> Not sure if I should leave 'as is' or edit 60-weewx.rules and remove
>>> 50-localusb.rules
>>>
>>>
>>> you can keep your 50-localusb.rules. you might want to consolidate the
>>> vpro rule in localusb.rules with the vpro rule in descriptive-names.rules.
>>> or not. depends on how you like to manage things. and your weewx.conf
>>> must already refer to 'DavisVP'...
>>>
>>> if you modify /usr/lib/udev/rules.d/60-weewx.rules, it will be
>>> overwritten when you next upgrade weewx, so just leave it.
>>>
>>> on your system, is there a /dev/vantage that is a symlink to the
>>> usb-serial adapter? if so, that indicates the weewx.rules in /usr/lib/udev
>>> is working.
>>>
>>> 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/55770862-b52b-4d2d-939e-b3476c40b2bbn%40googlegroups.com.
Re: [weewx-user] Weewx v5 fresh install Errno 13
p.s. just noticed I'm not getting a symlink for the DavisVP rule but I
haven't rebooted since I added that local rule.
Joe Verreau
On Saturday, February 10, 2024 at 3:05:41 PM UTC-5 Joseph Verreau wrote:
> hmm. this seems to be my issue on installing 5.0.0 following erasing
> 4.10. On my own I tried adding weewx user to the wheel group and to
> sudoers file. I tried what Matt and Paul were discussing about rule
> changes and yet I still get the "ERROR weewx.engine: Import of driver
> failed: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission
> denied:" When I run as root from command line all seems to be good.
> Should I do a full report with journal log?
>
> Joe Verreau KMIOKEMO13
> Okemos, MI
>
> On Wednesday, January 31, 2024 at 11:09:41 AM UTC-5 matthew wall wrote:
>
>> On Wednesday, January 31, 2024 at 3:29:36 AM UTC-5 pshep...@gmail.com
>> wrote:
>>
>> Hi Matthew
>>
>> Thanks for the information about the various udev folders which helps me
>> understand their interaction.
>>
>> I created a file /etc/udev/50-localusb.rules and inserted the rule. Also,
>> inherited from Linux Mint 20.1 running Weewx 4.8, I also have the following
>> line in /etc/udev/descriptive-names.rules
>>
>> ATTRS{serial}=="1344794749", ATTRS{manufacturer}=="Silicon Labs",
>> SYMLINK+="DavisVP"
>>
>> and that SYMLINK is created.
>>
>> /usr/lib/udev/rules.d/60-weewx.rules contains 10+ lines for different
>> stations and includes the following for Vantage:
>>
>> # davis vantage via usb-serial
>>
>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>
>> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTR{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>>
>> The vantage SYMLINK is not being created.
>>
>> Not sure if I should leave 'as is' or edit 60-weewx.rules and remove
>> 50-localusb.rules
>>
>>
>> you can keep your 50-localusb.rules. you might want to consolidate the
>> vpro rule in localusb.rules with the vpro rule in descriptive-names.rules.
>> or not. depends on how you like to manage things. and your weewx.conf
>> must already refer to 'DavisVP'...
>>
>> if you modify /usr/lib/udev/rules.d/60-weewx.rules, it will be
>> overwritten when you next upgrade weewx, so just leave it.
>>
>> on your system, is there a /dev/vantage that is a symlink to the
>> usb-serial adapter? if so, that indicates the weewx.rules in /usr/lib/udev
>> is working.
>>
>> 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/382a675e-92ac-43d5-83bd-f4206a588e35n%40googlegroups.com.
Re: [weewx-user] Weewx v5 fresh install Errno 13
hmm. this seems to be my issue on installing 5.0.0 following erasing
4.10. On my own I tried adding weewx user to the wheel group and to
sudoers file. I tried what Matt and Paul were discussing about rule
changes and yet I still get the "ERROR weewx.engine: Import of driver
failed: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Permission
denied:" When I run as root from command line all seems to be good.
Should I do a full report with journal log?
Joe Verreau KMIOKEMO13
Okemos, MI
On Wednesday, January 31, 2024 at 11:09:41 AM UTC-5 matthew wall wrote:
> On Wednesday, January 31, 2024 at 3:29:36 AM UTC-5 pshep...@gmail.com
> wrote:
>
> Hi Matthew
>
> Thanks for the information about the various udev folders which helps me
> understand their interaction.
>
> I created a file /etc/udev/50-localusb.rules and inserted the rule. Also,
> inherited from Linux Mint 20.1 running Weewx 4.8, I also have the following
> line in /etc/udev/descriptive-names.rules
>
> ATTRS{serial}=="1344794749", ATTRS{manufacturer}=="Silicon Labs",
> SYMLINK+="DavisVP"
>
> and that SYMLINK is created.
>
> /usr/lib/udev/rules.d/60-weewx.rules contains 10+ lines for different
> stations and includes the following for Vantage:
>
> # davis vantage via usb-serial
>
> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>
> SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTR{idProduct}=="ea61",MODE="0664",GROUP="weewx",SYMLINK+="vantage"
>
> The vantage SYMLINK is not being created.
>
> Not sure if I should leave 'as is' or edit 60-weewx.rules and remove
> 50-localusb.rules
>
>
> you can keep your 50-localusb.rules. you might want to consolidate the
> vpro rule in localusb.rules with the vpro rule in descriptive-names.rules.
> or not. depends on how you like to manage things. and your weewx.conf
> must already refer to 'DavisVP'...
>
> if you modify /usr/lib/udev/rules.d/60-weewx.rules, it will be overwritten
> when you next upgrade weewx, so just leave it.
>
> on your system, is there a /dev/vantage that is a symlink to the
> usb-serial adapter? if so, that indicates the weewx.rules in /usr/lib/udev
> is working.
>
> 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/17587be4-bc74-4904-af41-ed023a7f3134n%40googlegroups.com.
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
Matthew,
that I can do. thank you for your time and very prompt responses.
joev.mi
_ _ _ _ _ _ _ _ _ _
On Wednesday, January 24, 2024 at 7:42:25 PM UTC-5 matthew wall wrote:
> i think i was mistaken about dnf not creating the weewx user. i thought
> we had implemented useradd so that the HOME for a new weewx user is
> /var/lib/weewx, but apparently we did that for debian, but not for
> redhat/suse. i will fix that. however, that is not relevant to your
> problem.
>
> anyway, i am an idiot.
>
> if you look at the rules file, you will see that it is incorrect. instead
> of this:
>
> GROUP="weewx"
>
> we see this:
>
> GROUP="{weewx}"
>
> that is because there is a bug in the suse and redhat scriptlets that does
> an incorrect substitution.
>
> fixed at commit b32ca406, to appear real-soon-now in 5.0.1
>
> meanwhile, you can fix it by editing /usr/lib/udev/rules.d/60-weewx.rules
>
> replace "{weewx}" with "weewx"
>
>
--
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/8e77a62e-aabf-444a-8026-cbc99683a40dn%40googlegroups.com.
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
... are you suggesting my plan to delete /var/lib/weewx and then erase weewx 4.10 then following the instructions to install v5 should work? I believe I can save the database and re-add it after installing. joev.mi _ _ _ _ _ _ _ _ _ _ -- 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/72c497f1-2b9f-48e0-9e6c-9a02aba148c7n%40googlegroups.com.
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
... none of that is to say I didn't get something else wrong in the install. joev.mi _ _ _ _ _ _ _ _ _ _ On Wednesday, January 24, 2024 at 5:34:18 PM UTC-5 Joseph Verreau wrote: > Matthew, > actually I was afraid to create either user or group manually as I was > not confident about whether there might be specifications I was not > familiar with thus both the user and group resulted when I first deleted > the directory /var/lib/weewx then ran dnf install weewx following the > install instructions for fedora 34+. I had checked both passwd and group > prior to running the install and the user and group were not present. > from grep weewx /etc/group I get: > xps13-9305:~$ grep weewx /etc/group > weewx:x:960: > > @xps13-9305:~$ ll /etc/group > -rw-r--r--. 1 root root 1296 Jan 21 12:18 /etc/group > @xps13-9305:~$ ll /etc/passwd > -rw-r--r--. 1 root root 3400 Jan 21 12:18 /etc/passwd > @xps13-9305:~$ sudo dnf history list weewx > ID | Command line > | Date and time| Action(s) | > Altered > > - >668 | install weewx > | 2024-01-21 12:18 | Install| >5 > > joev.mi > _ _ _ _ _ _ _ _ _ _ > > On Wednesday, January 24, 2024 at 3:29:51 PM UTC-5 matthew wall wrote: > >> On Wednesday, January 24, 2024 at 2:38:38 PM UTC-5 joev...@gmail.com >> wrote: >> >> 3) xps13-9305:/etc/init.d# grep weewx /etc/passwd >> weewx:x:971:960::/home/weewx:/sbin/nologin >> >> >> it looks like your 'weewx' user has uid 971, and it is in group '960'. >> it also has home directory '/home/weewx', which tells me that this weewx >> user was not created by the weewx v5 installer and dnf. >> >> what do you get from this: >> >> grep weewx /etc/group >> >> >> > -- 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/49d04929-bc9a-45e9-a0a5-da60d1447389n%40googlegroups.com.
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
Matthew, actually I was afraid to create either user or group manually as I was not confident about whether there might be specifications I was not familiar with thus both the user and group resulted when I first deleted the directory /var/lib/weewx then ran dnf install weewx following the install instructions for fedora 34+. I had checked both passwd and group prior to running the install and the user and group were not present. from grep weewx /etc/group I get: xps13-9305:~$ grep weewx /etc/group weewx:x:960: @xps13-9305:~$ ll /etc/group -rw-r--r--. 1 root root 1296 Jan 21 12:18 /etc/group @xps13-9305:~$ ll /etc/passwd -rw-r--r--. 1 root root 3400 Jan 21 12:18 /etc/passwd @xps13-9305:~$ sudo dnf history list weewx ID | Command line | Date and time| Action(s) | Altered - 668 | install weewx | 2024-01-21 12:18 | Install| 5 joev.mi _ _ _ _ _ _ _ _ _ _ On Wednesday, January 24, 2024 at 3:29:51 PM UTC-5 matthew wall wrote: > On Wednesday, January 24, 2024 at 2:38:38 PM UTC-5 joev...@gmail.com > wrote: > > 3) xps13-9305:/etc/init.d# grep weewx /etc/passwd > weewx:x:971:960::/home/weewx:/sbin/nologin > > > it looks like your 'weewx' user has uid 971, and it is in group '960'. it > also has home directory '/home/weewx', which tells me that this weewx user > was not created by the weewx v5 installer and dnf. > > what do you get from this: > > grep weewx /etc/group > > > -- 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/b08d0ab3-ea98-4ed0-9b41-b815dd87af97n%40googlegroups.com.
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
I see I didn't reference the container of the list of files above; the
directory is /etc/weewx/
On Wednesday, January 24, 2024 at 2:57:22 PM UTC-5 Joseph Verreau wrote:
> Matthew,
> Ooops, i neglected my other response:
>I neglected that detail, I did delete the directory /var/lib/weewx and
> the database therein. I did not change the directory /etc/weewx and I
> noticed that when I ran dnf install weewx it updated the ownership and
> group of that directory and files therein. I was tempted to conclude from
> that change that the install would update the ownership and group of the
> directory /var/lib/weewx if I hadn't deleted it. I was tempted to merely
> add user:group of weewx:weewx and assign them to /var/lib/weewx and the
> database but I wasn't sure if there were special requirements for that user
> and group.
>I have rebooted since I ran the install. Since then I get the error
> about weewx group being unknown in sets of ten once per day.
>
>
> On Wednesday, January 24, 2024 at 2:40:30 PM UTC-5 Joseph Verreau wrote:
>
>> 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 weewx10 Jan 21 12:18 logrotate.d
>> drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 logwatch
>> drwxr-xr-x. 1 weewx weewx20 Jan 21 12:18 rsyslog.d
>> drwxr-xr-x. 1 weewx weewx78 Jan 21 12:18 skins
>> drwxr-xr-x. 1 weewx weewx54 Jan 21 12:18 systemd
>> drwxr-xr-x. 1 weewx weewx22 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
>
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
Matthew,
Ooops, i neglected my other response:
I neglected that detail, I did delete the directory /var/lib/weewx and
the database therein. I did not change the directory /etc/weewx and I
noticed that when I ran dnf install weewx it updated the ownership and
group of that directory and files therein. I was tempted to conclude from
that change that the install would update the ownership and group of the
directory /var/lib/weewx if I hadn't deleted it. I was tempted to merely
add user:group of weewx:weewx and assign them to /var/lib/weewx and the
database but I wasn't sure if there were special requirements for that user
and group.
I have rebooted since I ran the install. Since then I get the error
about weewx group being unknown in sets of ten once per day.
On Wednesday, January 24, 2024 at 2:40:30 PM UTC-5 Joseph Verreau wrote:
> 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 weewx10 Jan 21 12:18 logrotate.d
> drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 logwatch
> drwxr-xr-x. 1 weewx weewx20 Jan 21 12:18 rsyslog.d
> drwxr-xr-x. 1 weewx weewx78 Jan 21 12:18 skins
> drwxr-xr-x. 1 weewx weewx54 Jan 21 12:18 systemd
> drwxr-xr-x. 1 weewx weewx22 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
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
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 weewx10 Jan 21 12:18 logrotate.d
drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 logwatch
drwxr-xr-x. 1 weewx weewx20 Jan 21 12:18 rsyslog.d
drwxr-xr-x. 1 weewx weewx78 Jan 21 12:18 skins
drwxr-xr-x. 1 weewx weewx54 Jan 21 12:18 systemd
drwxr-xr-x. 1 weewx weewx22 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
&g
[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0
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/af136a00-3a85-4b7e-b925-482928bebb77n%40googlegroups.com.
60-weewx.rules
Description: Binary data
[weewx-user] Re: ValueError: y1 must be greater than or equal to y0 in fresh installed weewx 4.10.2
thanks to all for their help on this one. I see it didn't present on my installation until Nov 25th and I didn't notice it right away to boot but all is humming again. On Tuesday, May 23, 2023 at 9:52:57 PM UTC-4 gjr80 wrote: > If you are running the current WeeWX release you should be fairly safe in > downloading the patched utilities.py in place of your current version. To > do this: > > 1. move aside your current utilities.py so your can revert to it if you > run into catastrophic problems, for a WeeWX package install: > > $ sudo mv /usr/share/weewx/weeplot/utilities.py > /usr/share/weewx/weeplot/utilities_orig.py > > if you have a setup.py install use /home/weewx/bin in place of > /usr/share/weewx > > 2. download the patched utilities.py from GitHub, for a WeeWX package > install: > > $ sudo wget -P /usr/share/weewx/weeplot > https://raw.githubusercontent.com/weewx/weewx/master/bin/weeplot/utilities.py > > again, if you have a setup.py install use /home/weewx/bin in place of > /usr/share/weewx > > 3. restart WeeWX > > If you mess up the process simply copy utilities_orig.py back as > utilities.py and restart WeeWX. > > Gary > On Sunday, 21 May 2023 at 17:35:00 UTC+10 seano...@gmail.com wrote: > >> Hi, >> >> I seem to be having this same error but I don't understand exactly how to >> rectify it. Please can you explain in a simple way how to apply the patch? >> >> Appreciate it, thank you. >> >> On Wednesday, April 12, 2023 at 1:01:59 AM UTC+4 Marius Schamschula wrote: >> >>> I ran into the same error after a routine update to FreeBSD 13.1 >>> packages. >>> >>> I applied the patch and reinstalled weewx 4.10.2, and all is again >>> working as expected! >>> >>> On Tuesday, April 4, 2023 at 2:33:53 AM UTC-5 c s (224) wrote: >>> Thank you very much for digging deeper! My solution will then be to simply install an older version of the Pillow library. Thanks a lot! c s (224) schrieb am Montag, 3. April 2023 um 13:18:39 UTC+2: > Hello, > > I have just installed weewx as described here: > https://weisser-zwerg.dev/posts/ecowitt-gw2000-weewx-docker > > And I run into an error that prevents the images from being drawn: > > weewx-weewx-1 | Apr 3 13:11:03 weewx[20] ERROR > weewx.reportengine: Generator terminated > weewx-weewx-1 | Traceback (most recent call last): > weewx-weewx-1 | File "/home/weewx/bin/weewx/reportengine.py", > line 197, in run > weewx-weewx-1 | obj.start() > weewx-weewx-1 | File "/home/weewx/bin/weewx/reportengine.py", > line 385, in start > weewx-weewx-1 | self.run() > weewx-weewx-1 | File > "/home/weewx/bin/weewx/imagegenerator.py", line 42, in run > weewx-weewx-1 | self.gen_images(self.gen_ts) > weewx-weewx-1 | File > "/home/weewx/bin/weewx/imagegenerator.py", line 114, in gen_images > weewx-weewx-1 | image = plot.render() > weewx-weewx-1 | ^ > weewx-weewx-1 | File "/home/weewx/bin/weeplot/genplot.py", > line 222, in render > weewx-weewx-1 | self._renderDayNight(sdraw) > weewx-weewx-1 | File "/home/weewx/bin/weeplot/genplot.py", > line 266, in _renderDayNight > weewx-weewx-1 | sdraw.rectangle(((xleft,self.yscale[0]), > weewx-weewx-1 | File "/home/weewx/bin/weeplot/utilities.py", > line 442, in rectangle > weewx-weewx-1 | self.draw.rectangle(box_scaled, **options) > weewx-weewx-1 | File > "/opt/venv/lib/python3.11/site-packages/PIL/ImageDraw.py", line 294, in > rectangle > weewx-weewx-1 | self.draw.draw_rectangle(xy, fill, 1) > weewx-weewx-1 | ValueError: y1 must be greater than or equal to > y0 > > I have followed the complete set-up process as described in "WeeWX: > Installation using setup.py", except that I do use a conda environment > and > pip packages rather than the OS packages: > > > mamba create -n weewx python=3.9 > > conda activate weewx > > pip3 install configobj paho-mqtt pyserial pyusb Cheetah3 Pillow > ephem > > wget https://weewx.com/downloads/weewx-4.10.2.tar.gz > > tar -xzvf weewx-4.10.2.tar.gz > > cd weewx-4.10.2 > > python3 ./setup.py build > > python3 ./setup.py install > > # create the weewx.conf.patch from here: > https://weisser-zwerg.dev/posts/ecowitt-gw2000-weewx-docker/ > > patch -p1 weewx.conf < weewx.conf.patch > > wget -O weewx-mqtt.zip > https://github.com/matthewwall/weewx-mqtt/archive/master.zip > > ./bin/wee_extension --install ./weewx-mqtt.zip > > wget -O weewx-interceptor.zip > https://github.com/matthewwall/weewx-interceptor/archive/master.zip > > ./bin/wee_extension --install ./weewx-interceptor.zip > > # --- > >
