I installed a fresh NethServer system and attempted to install UPS support, which failed. I first did so without selecting the nethserver-collectd and collectd-nut options, but then attempted to add them. If anybody can tell me what to do next I will be most grateful.
Thanks in advance.
Here is the log:
Feb 16 16:42:38 roy pkgaction[2417]: install: @nethserver-nut
Feb 16 16:42:41 roy yum[2417]: Installed: nethserver-nut-1.3.1-1.ns7.noarch
Feb 16 16:42:44 roy esmith::event[2449]: Event: nethserver-nut-update
Feb 16 16:42:44 roy esmith::event[2449]: Action: /etc/e-smith/events/nethserver-nut-update/S00initialize-default-databases SUCCESS [0.438813]
Feb 16 16:42:44 roy esmith::event[2449]: expanding /etc/collectd.d/nut.conf
Feb 16 16:42:44 roy esmith::event[2449]: expanding /etc/ups/nut.conf
Feb 16 16:42:44 roy esmith::event[2449]: Action: /etc/e-smith/events/nethserver-nut-update/S20nethserver-nut-conf SUCCESS [0.15003]
Feb 16 16:42:45 roy systemd-tmpfiles: Failed to open â/etc/tmpfiles.d/nut-run.confâ, ignoring: No such file or directory
Feb 16 16:42:45 roy esmith::event[2449]: [INFO] nut-monitor has been started
Feb 16 16:42:45 roy upsmon: fopen /var/run/nut/upsmon.pid: No such file or directory
Feb 16 16:42:45 roy wall[2514]: wall: user nut broadcasted 1 lines (44 chars)
Feb 16 16:42:45 roy systemd-tmpfiles: Failed to open â/etc/tmpfiles.d/nut-run.confâ, ignoring: No such file or directory
Feb 16 16:42:45 roy systemd: nut-driver.service: control process exited, code=exited status=1
Feb 16 16:42:45 roy systemd: Job nut-server.service/start failed with result âdependencyâ.
Feb 16 16:42:45 roy systemd: Unit nut-driver.service entered failed state.
Feb 16 16:42:45 roy systemd: nut-driver.service failed.
Feb 16 16:42:45 roy esmith::event[2449]: A dependency job for nut-server.service failed. See âjournalctl -xeâ for details.
Feb 16 16:42:45 roy esmith::event[2449]: [INFO] service nut-server restart
Feb 16 16:42:45 roy systemd-tmpfiles: Failed to open â/etc/tmpfiles.d/nut-run.confâ, ignoring: No such file or directory
Feb 16 16:42:45 roy esmith::event[2449]: A dependency job for nut-server.service failed. See âjournalctl -xeâ for details.
Feb 16 16:42:45 roy systemd: nut-driver.service: control process exited, code=exited status=1
Feb 16 16:42:45 roy esmith::event[2449]: [WARNING] restart service nut-server failed!
Feb 16 16:42:45 roy systemd: Job nut-server.service/start failed with result âdependencyâ.
Feb 16 16:42:45 roy systemd: Unit nut-driver.service entered failed state.
Feb 16 16:42:45 roy systemd: nut-driver.service failed.
Feb 16 16:42:45 roy esmith::event[2449]: Event: nethserver-nut-update FAILED
Feb 16 16:42:46 roy systemd-tmpfiles: Failed to open â/etc/tmpfiles.d/nut-run.confâ, ignoring: No such file or directory
Feb 16 16:42:47 roy systemd: nut-driver.service: control process exited, code=exited status=1
Feb 16 16:42:47 roy systemd: Job nut-server.service/start failed with result âdependencyâ.
Feb 16 16:42:47 roy systemd: Unit nut-driver.service entered failed state.
Feb 16 16:42:47 roy systemd: nut-driver.service failed.
Feb 16 16:42:47 roy esmith::event[2554]: A dependency job for nut-server.service failed. See âjournalctl -xeâ for details.
Feb 16 16:42:50 roy wall[3716]: wall: user nut broadcasted 1 lines (34 chars)
Feb 16 16:47:55 roy wall[3914]: wall: user nut broadcasted 1 lines (34 chars)
Feb 16 16:53:00 roy wall[3973]: wall: user nut broadcasted 1 lines (34 chars)
Feb 16 16:58:05 roy wall[4022]: wall: user nut broadcasted 1 lines (34 chars)
Feb 16 16:59:34 roy pkgaction[4319]: install: nethserver-collectd, collectd-nut
Feb 16 16:59:36 roy yum[4319]: Installed: collectd-nut-5.8.0-1.el7.x86_64
Feb 16 16:59:42 roy systemd-tmpfiles: Failed to open â/etc/tmpfiles.d/nut-run.confâ, ignoring: No such file or directory
Feb 16 16:59:42 roy systemd: nut-driver.service: control process exited, code=exited status=1
Feb 16 16:59:42 roy systemd: Job nut-server.service/start failed with result âdependencyâ.
Feb 16 16:59:42 roy systemd: Unit nut-driver.service entered failed state.
Feb 16 16:59:42 roy systemd: nut-driver.service failed.
Feb 16 16:59:42 roy esmith::event[4484]: A dependency job for nut-server.service failed. See âjournalctl -xeâ for details.
Jeroen, thanks for replying. I removed all the packages except OpenVPN, and Basic firewall. I then did :
yum --enablerepo=* clean all
After than, installing UPS support fails.
I captured the specific messages that pop up in red in server-manager. It says:
Task completed with errors
Adjust service nut-server #22 (exit status 1)
restart service nut-server failed!
Adjust service nut-server #42 (exit status 1)
failed
I probably havenât read all of the documentation, but I didnât see anything specifying installation order. If you could elaborate on your recommendation, I would appreciate it.
Again, I am not hampered by any knowledge on the topic, and am just echoing a very general thing. You stated that you attempted to install UPS support without nethserver-collectd and collectd-nut. Then you added them. Theoretically that could mean that these later two options should be present when installing the first. Again, without being hampered by any knowledge on the topic.
If uninstalling all, and reinstalling with either these options immediately selected OR installed first, doesnt help, then I am not going to be of help Iâm affraid.
I do know that the servermanager is not always useful with errors. It creates errors by default when I create users, but did everything it had to do anyway ⌠sometimes just repeating the exact same thing that caused the error, will pass the second time.
As I am unsure yet if this is my own fault or NethServer implementation specific, I just ignore them for now. A good example of this is installing the AD account provider, which always fails the first time for me, then I press OK again, and it works. Perhaps due to doing everything from first boot (install, add, etc.) or because I do not want to use the proposed AD.DOMAIN.TLD but just DOMAIN.TLD.
Those latter packages are presented in the Software Center as optional, and Iâve had the UPS support working without them installed. No real idea where the problem is, but the absence of these packages shouldnât be it.
I see the same âno such fileâ errors, at start-up, on my system where the UPS is doing itâs job as I expect, so Iâm not sure they are relevant to your issue.
What is the issue you are seeing. Are the UPS services starting correctly, as Iâm guessing that may be the real issue here.
I am trying to get a fresh install of Nethserver working on the same system worked correctly before.
I have tried installing with and without the add-on nethserver-collectd and collectd-nut.
From Nethserver-manager, the UPS tab on Dashboard shows "No UPS information available.
From /var/log/messages:
Feb 18 15:04:16 roy systemd: Starting Virtualization daemonâŚ
Feb 18 15:04:16 roy upsdrvctl: Fatal error: unusable configuration
Feb 18 15:04:16 roy upsdrvctl: Network UPS Tools - CyberPower text/binary protocol UPS driver 0.26 (2.7.2)
Feb 18 15:04:16 roy upsdrvctl: Warning: This is an experimental driver.
Feb 18 15:04:16 roy upsdrvctl: Some features may not function correctly.
Feb 18 15:04:16 roy upsdrvctl: Unable to open auto: No such file or directory
Feb 18 15:04:16 roy upsdrvctl: Things to try:
Feb 18 15:04:16 roy upsdrvctl: - Check âport=â in ups.conf
Feb 18 15:04:16 roy upsdrvctl: - Check owner/permissions of all parts of path
Feb 18 15:04:16 roy upsdrvctl: Driver failed to start (exit status=1)
Feb 18 15:04:16 roy upsdrvctl: Network UPS Tools - UPS driver controller 2.7.2
Feb 18 15:04:16 roy systemd: Starting Permit User SessionsâŚ
Feb 18 15:04:16 roy systemd: Started OpenSSH server daemon.
Feb 18 15:04:16 roy systemd: nut-driver.service: control process exited, code=exited status=1
Feb 18 15:04:16 roy systemd: Failed to start Network UPS Tools - power device driver controller.
Feb 18 15:04:16 roy systemd: Dependency failed for Network UPS Tools - power devices information server.
Feb 18 15:04:16 roy systemd: Job nut-server.service/start failed with result âdependencyâ.
Feb 18 15:04:16 roy systemd: Unit nut-driver.service entered failed state.
Feb 18 15:04:16 roy systemd: nut-driver.service failed.
Feb 18 15:04:16 roy systemd: Started Permit User Sessions.
SOLVED. The driver for my Cyber Power Systems model chosen is named âpowerpanelâ. I selected a different model, which chose the driver named âusbhid-upsâ. which now works correctly.
Which driver are you using? And which model of UPS do you have? When I was using a Cyberpower UPS with a USB connection, I was using the ups-hid driver, which is a pretty robust one. The message your getting suggests youâre using a different driver.
Thanks for responding.