Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Marco - Would you provide more information to help us understand your system ? See the new Problem Reporting Questionnaire (link) for the kind of information we need in order to try to help much better. Thank you. On

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Hi vince! sestatus gives disabled... Il giorno mercoledì 1 maggio 2024 alle 01:57:29 UTC+2 vince ha scritto: > Marco are you running with selinux in enforcing mode ? Can you check for > selinux errors in your logs or perhaps temporarily run with selinux > disabled to see if that helps ? > > So

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

It should certainly permit ports over 1024 but if selinux blocks stuff due to an executable not being labelled correctly you can get quiet failures unless you notice it in the logs. It’s not always self-evident when he victim program logs what it thinks happened. I just can’t remember the file

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Vince, Redhat doesn't necessarily allow socket access for ports over 1024? On Tue, Apr 30, 2024 at 4:57 PM vince wrote: > Marco are you running with selinux in enforcing mode ? Can you check for > selinux errors in your logs or perhaps temporarily run with selinux > disabled to see if that helps

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Marco are you running with selinux in enforcing mode ? Can you check for selinux errors in your logs or perhaps temporarily run with selinux disabled to see if that helps ? Sorry but I’m away from a computer so I can’t give you the precise commands, but selinux can rather quietly stop things f

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

I am not that familiar with the IP logger, but I assume you would obey the same echo TEST as a regular logger. If it doesn't, then it sounds like there is a connectivity problem. Yes, it worked under WeeWX V3.8, but you have also changed servers since then. Double check any firewalls. For example

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

I've tried to change weewx.service but without results. Telent doesn't echo anything. The network should work because the old weewx (3.8.xxx) on the other webserver is working. Il giorno martedì 30 aprile 2024 alle 19:03:43 UTC+2 Tom Keffer ha scritto: > I am wondering whether the network is up

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

I am wondering whether the network is up and running by the time weewxd tries to access it. Try editing your weewx systemd service file (normally located in /lib/systemd/system/weewx.service) so it looks something like the following: [Unit] Description=WeeWX Documentation=https://weewx.com/docs Re

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Yes it's ethernet. Here it is the log: apr 30 18:07:10 web4.xxx systemd[1]: Started WeeWX. apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Initializing weewxd version 5.0.2 apr 30 18:07:10 web4.xxx weewxd[22596]: INFO __main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/wee

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Apologies. You have an ethernet device, right? So, it's going to connect to a network port, not a USB port. Could you please post the full log? The systemctl status reports are very brief and don't give line numbers. Set debug=1, then try restarting weewx. Post the log. Thanks. On Tue, Apr 30,

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

the problem is that if I stop the service and I restart it works for just a glimpse. I try again status and I get the error. weewx.service - WeeWX Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2024-04-30 12:00:

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

The device has an ethernet port. Now it is working in another webserver. I've also tried to stop the service in the other web server but the result is the same. If I do lsusb I don't get anything. Il giorno lunedì 29 aprile 2024 alle 20:14:20 UTC+2 Tom Keffer ha scritto: > It seems that your dev

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

It seems that your device is not being recognized by the udev rule, perhaps because it is has an ethernet port. Check the vendor and product ID of your logger with the command "lsusb". It will output something like Bus 001 Device 003: ID 18e8:6238 Qcom Bus 001 Device 001: ID 1d6b:0002 Linux Found

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Hi! I've checked the article you suggested and looking the permissions in /etc/udev/rules.d/60-weewx.rules I see in the file: *# davis vantage via usb-serial* SUBSYSTEM=="tty",ATTRS{idVendor}=="10c4",ATTRS{idProduct}=="ea60",MODE="0664",GROUP="weewx",SYMLINK+="vantage" SUBSYSTEM=="tty",ATT

Re: [weewx-user] weewx.service: Failed with result 'exit-code'

Looks like a permissions issue accessing the port. See the wiki article How to fix device permissions and see if that helps. On Mon, Apr 29, 2024 at 9:48 AM Marco Citossi wrote: > Hi! I've installed wee

[weewx-user] weewx.service: Failed with result 'exit-code'

Hi! I've installed weewx in Oracle Linux 8.9 following the guide for RedHat. The installation has completed without errors. It has been installed in default folders, in /var/www/html/weewx (weewx:weewx), /usr/share/weewx (root:root) and /etc/weewx (weewx:weewx) for bin and weewx.conf Only we