@Matthew: Any clue what should be modified (udev rules/group membership) for interceptor driver? When I modify systemctl service to not run under weewx:weewx everything is OK :)
*Feb 6 19:37:43 rocky-weather-machine weewxd[1612889]: INFO weewx.engine: Loading station type Interceptor (user.interceptor)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO user.interceptor: driver version is 0.53* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO user.interceptor: device type: observer* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO user.interceptor: mode is listen* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO user.interceptor: listen on :80* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: ERROR weewx.engine: Import of driver failed: [Errno 13] Operace zamítnuta (<class 'PermissionError'>)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** Traceback (most recent call last):* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** self.console = loader_function(config_dict, self)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/etc/weewx/bin/user/interceptor.py", line 315, in loader* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** return InterceptorDriver(**config_dict[DRIVER_NAME])* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/etc/weewx/bin/user/interceptor.py", line 2522, in __init__* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** self._device = self.DEVICE_TYPES.get(self._device_type)(**stn_dict)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/etc/weewx/bin/user/interceptor.py", line 1285, in __init__* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** Observer.Parser(), handler=Observer.Handler, **stn_dict)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/etc/weewx/bin/user/interceptor.py", line 429, in __init__* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** self._server = Consumer.TCPServer(address, port, handler)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/etc/weewx/bin/user/interceptor.py", line 584, in __init__* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** TCPServer.__init__(self, (address, int(port)), handler)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/usr/lib64/python3.6/socketserver.py", line 456, in __init__* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** self.server_bind()* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** File "/usr/lib64/python3.6/socketserver.py", line 470, in server_bind* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** self.socket.bind(self.server_address)* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL weewx.engine: **** PermissionError: [Errno 13] Operace zamítnuta* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL __main__: Unable to load driver: [Errno 13] Operace zamítnuta* *Feb 6 19:37:44 rocky-weather-machine systemd[1]: weewx.service: Main process exited, code=exited, status=4/NOPERMISSION* *Feb 6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL __main__: **** Exiting...* *Feb 6 19:37:44 rocky-weather-machine systemd[1]: weewx.service: Failed with result 'exit-code* Dne úterý 6. února 2024 v 22:00:36 UTC+1 uživatel gjr80 napsal: > Impossible to say what the issue is with such a short log extract. Please > edit weewx.conf, set debug =1, save weewx.conf and restart WeeWX. Let > WeeWX run for at least two archive intervals and then take a log extract > showing the full WeeWX startup through until the two archive intervals have > elapsed. Post the log extract here. > > Gary > > On Wednesday 7 February 2024 at 05:23:35 UTC+10 [email protected] wrote: > >> Thanks for that tip - it got me off the ground. All is now well except >> that /var/www/html/weewx hasn't been updated since just before I did the >> upgrade to 5.0.1. Anyone else seeing this? >> >> On Tuesday, February 6, 2024 at 8:09:36 AM UTC-8 Tom Hogland wrote: >> >>> In case anyone else runs into this - my Ubuntu server/Davis VP2 and >>> serial datalogger had ownership set to root:dialout, so I had to add the >>> weewx user to the dialout group for things to work. >>> >>> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote: >>> >>>> when you install rtl-sdr, it typically, but not always, installs udev >>>> rules for *many* sdr devices. the udev rules that it installs make it >>>> possible for anyone in the 'plugdev' group to read/write to the sdr >>>> device. (this is true when you install rtl-sdr from source - if you >>>> install rtl-sdr from a deb/rpm package, it might be different - anyone >>>> with >>>> this configuration please let us know) >>>> >>>> weewx v4 runs as root:root, so it has access to the sdr device no >>>> matter what the udev rules might be >>>> >>>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular >>>> non-root user (for pip installs). so udev rules are required. >>>> >>>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did >>>> not (it would continue to run as root - we changed in 5.0.1 because >>>> overall >>>> security and best practice) >>>> >>>> the udev rules installed by rtl-sdr will not help for a deb/rpm >>>> install, since the user 'weewx' is not in the plugdev group. you can >>>> either added the user weewx to the plugdev group, or modify the udev rules >>>> to use 'weewx' instead of 'plugdev' as the group. this is how to do the >>>> former: >>>> >>>> sudo usermod -aG plugdev weewx >>>> >>>> for a pip install, be sure that the user running weewx is in the >>>> 'plugdev' group. >>>> >>>> restart of the weewxd daemon is almost certainly required so that the >>>> daemon process has the right group. reboot is not necessary. >>>> >>>> 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/163528fa-f1e4-4286-8db4-3821685aeef3n%40googlegroups.com.
