Bug 1468835
| Summary: | usbhid-ups will exit on error instead of retrying | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Hill <dhill> | ||||
| Component: | nut | Assignee: | Michal Hlavinka <mhlavink> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 27 | CC: | dhill, mhlavink | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-11-30 17:52:21 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
David Hill
2017-07-08 16:02:41 UTC
This seems like usb device stealing. Do you have ModemManager installed? Do you use it/needed? If not, try to uninstall it and see if it helps. The service is not running: [root@zappa .ssh]# systemctl list-unit-files | grep -i modem ModemManager.service disabled Should I still uninstall it? I uninstalled it and restarted the services but it still goes away every now and then. Yes, uninstallation is necessary, as it is triggered by dbus and hw detection, not usual service. Please reboot your machine. Wait for the problem to occur and then attach: 1) dmesg output $ dmesg >dmesg.log 2) journal "since boot" output $ journalctl -b >journal.log 3) your ups configuration Also, before attaching here, check your configuration does not contain any passwords. If they do, replace passwords with some other strings. PS: Please do not overuse needinfo feature. It's for specific use cases: 1) answer is really urgent - like blocker bugs that needs to be solved so product can be released on schedule 2) you get no answer for a really long time 3) you need answer from someone else than reporter/assignee Created attachment 1300082 [details]
logs and /etc/ups folder
Thanks for the logs. As a first attempt, please try to change your [myups] configuration in ups.conf to the following: [myups] driver = usbhid-ups pollinterval = 10 vendorid = 09ae port = auto restart all nut related services (or reboot the computer) and check if it helps. Thanks It did the same thing. Need the logs? Is rebooting really necessary because of systemd or something or it's only because you want to make sure nut-* were restarted ? Logs are not needed this time. Rebooting is not necessary if you restart nut properly. Better way is to stop all nut-*.service and then start it Try to edit /usr/lib/systemd/system/nut-driver.service and in the [Service] section, add RestartSec=1 Restart=on-failure StartLimitIntervalSec=120 and see if it helps. You will need to reboot OR reload systemd config with $ systemctl daemon-reload and stop+start nut services $ systemctl stop nut-driver.service nut-server.service nut-monitor.service $ systemctl start nut-server.service nut-monitor.service (nut-driver service will be start automatically as a dependency) If it does not help, please attach the journal log. I will look at it once I'm back from vacation I got this now: Init SSL without certificate database Error: Data stale Init SSL without certificate database Error: Data stale Init SSL without certificate database Error: Data stale Where do you see those messages? Did the restart configuration help or not? I see that when I run "upsc myups" and at some point, the drivers will stop loading and the only way I've found to recover from that is to actually disconnect the USB cable and reconnect it. This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'. This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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. |