Good it’s working. Weewx used to run as root so a lot of permission
problems didn’t happen previously.
With the switch to running as a unprivileged user, you need to ensure that
user can attach to peripherals (your case) or listening ports (some
interceptor and sdr users) as well as hook it into your webserver properly.
So it’s a little heavier lift in some situations.
For your situation with /dev/ttyUSB0 adding the user weewx runs as to group
dialout usually fixes the issue on a raspi but it really depends on your
os and which customizations have been done to it.,.
On Tuesday, February 20, 2024 at 3:38:46 PM UTC-8 Jason Patton wrote:
> Hi Vince, et al,
> Yes, all working well. I was looking at it, from a device permissions
> point-of-view. Software weewx, for some reason, no-longer had rights to,
> in my case /dev/ttyUSB0 (which has been working for 11 years). Ownership
> of the device were set to root:dialout (as are the serial ports). I saw
> that weewx was running as user weewx (hmm, don't recall that...). User
> weewx was a member of group weewx, so amended the device ownership to:
> root:weewx.
>
> Cheers, Jason.
>
> On Tuesday 20 February 2024 at 17:10:27 UTC+11 vince wrote:
>
>> Is it working now ? What thoughts are you looking for in particular ?
>>
>> On Monday, February 19, 2024 at 5:47:48 PM UTC-8 Jason Patton wrote:
>>
>>> Hello All,
>>> After trying to pick-up the pieces of a borked upgrade, I just
>>> encountered the same 'could not open port /dev/ttyUSB0'. Entirely possible
>>> that I've missed documentation somewhere, but is would seem that weewx, is
>>> now running as usr:grp weewx:weewx (which is where the upgrade script
>>> borked, setting user permissions)? My fix was amending permissions on:
>>> '/dev/ttyUSB0' to: root:weewx, and weewx started fine. Until, it tried to
>>> write the HTML, where weewx no-longer had permissions. Upon granting weewx
>>> permission to that folder / sub-folders, all seems well. Thoughts, anyone?
>>>
>>> Best regards, Jason.
>>>
>>> On Sunday 11 February 2024 at 07:36:30 UTC+11 Joseph Verreau wrote:
>>>
>>>> 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
>>>>>>> [email protected] 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/e29a78ac-213c-489b-ad76-336bfec304b2n%40googlegroups.com.
