Hide Forgot
Description of problem: I have a nut network client which fails to connect after booting, however it can connect if I restart the nut-monitor service. Version-Release number of selected component (if applicable): nut-2.7.4-4.fc25.x86_64 nut-client-2.7.4-4.fc25.x86_64 How reproducible: Always Steps to Reproduce: 1. dnf install nut-client 2. Configure upsmon.conf. The helio hostname resolves fine and the server is already configured with the username and password. MONITOR salicru@helio 1 upsslave password slave 3. Configure nut.conf MODE=netclient 4. systemctl enable nut-monitor.service 5. reboot Actual results: # journalctl -b -u nut-monitor nov 29 11:24:01 xenon systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller... nov 29 11:24:02 xenon upsmon[3352]: fopen /var/run/nut/upsmon.pid: No such file or directory nov 29 11:24:02 xenon upsmon[3352]: UPS: salicru@helio (slave) (power value 1) nov 29 11:24:02 xenon upsmon[3352]: Using power down flag file /etc/killpower nov 29 11:24:02 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:24:02 xenon upsmon[3352]: Communications with UPS salicru@helio lost nov 29 11:24:02 xenon upsmon[3352]: wall: no se puede obtener el nombre del terminal: Inappropriate ioctl for device nov 29 11:24:02 xenon upsmon[3352]: Network UPS Tools upsmon 2.7.4 nov 29 11:24:01 xenon systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller. nov 29 11:24:06 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:24:06 xenon upsmon[3352]: UPS salicru@helio is unavailable nov 29 11:24:06 xenon upsmon[3352]: wall: no se puede obtener el nombre del terminal: Inappropriate ioctl for device nov 29 11:24:06 xenon upsmon[3352]: Network UPS Tools upsmon 2.7.4 nov 29 11:24:11 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:24:16 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host [...] Expected results: When I reboot the service by hand, it connects as expected: # systemctl restart nut-monitor # journalctl -b -u nut-monitor [...] nov 29 11:58:26 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:58:31 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:58:36 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:58:41 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:58:46 xenon upsmon[3352]: UPS [salicru@helio]: connect failed: No such host nov 29 11:58:48 xenon upsmon[3352]: Signal 15: exiting nov 29 11:58:48 xenon upsmon[3352]: Network UPS Tools upsmon 2.7.4 nov 29 11:58:48 xenon systemd[1]: Stopping Network UPS Tools - power device monitor and shutdown controller... nov 29 11:58:48 xenon systemd[1]: Stopped Network UPS Tools - power device monitor and shutdown controller. nov 29 11:58:48 xenon systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller... nov 29 11:58:48 xenon systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller. nov 29 11:58:48 xenon upsmon[10787]: fopen /var/run/nut/upsmon.pid: No such file or directory nov 29 11:58:48 xenon upsmon[10787]: UPS: salicru@helio (slave) (power value 1) nov 29 11:58:48 xenon upsmon[10787]: Using power down flag file /etc/killpower
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.