NUT restart not showing in log after update

Status
Not open for further replies.

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
I checked my email this morning and found an update notice for FreeNAS. I logged in to the FN GUI
and backed up my config, then applied the update. After FN re-booted, I checked the log files and
noticed something strange. At midnight there was this log entry;
Apr 16 00:00:00 freenas syslog-ng[3941]: Configuration reload request received, reloading configuration;
The above happens every night with the change of date and is perfectly normal.
Then, when the update was applied, the reboot process started, again, perfectly normal...
The NUT service can be seen shutting down (please notice line #37 thru 44).
But then when everything comes back up, it never shows the NUT service re-connecting:eek:
I'm just curious, is this normal?
http://pastebin.com/embed_js.php?i=G6tPQDBi
 
D

dlavigne

Guest
Can you manually start the UPS service? If not, post the error messages.
 

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
From the GUI I turned off the UPS service and then turned it back on. The log showed this:
Code:
Apr 16 09:00:22 freenas kernel: pid 1850 (syslog-ng), uid 0: exited on signal 6 (core dumped)
Apr 16 11:03:03 freenas notifier: Stopping nut_upslog.
Apr 16 11:03:03 freenas notifier: Waiting for PIDS: 2596.
Apr 16 11:03:03 freenas notifier: Stopping nut_upsmon.
Apr 16 11:03:03 freenas upsmon[2599]: upsmon parent: read
Apr 16 11:03:03 freenas notifier: Waiting for PIDS: 2601.
Apr 16 11:03:03 freenas notifier: Stopping nut.
Apr 16 11:03:03 freenas upsd[2593]: mainloop: Interrupted system call
Apr 16 11:03:03 freenas notifier: Waiting for PIDS: 2593.
Apr 16 11:03:03 freenas notifier: Network UPS Tools - UPS driver controller 2.7.2
Apr 16 11:03:14 freenas notifier: Using subdriver: CyberPower HID 0.3
Apr 16 11:03:14 freenas notifier: Network UPS Tools - Generic HID driver 0.38 (2.7.2)
Apr 16 11:03:14 freenas notifier: USB communication driver 0.32
Apr 16 11:03:14 freenas notifier: Network UPS Tools - UPS driver controller 2.7.2
Apr 16 11:03:14 freenas notifier: Starting nut.
Apr 16 11:03:14 freenas notifier: fopen /var/db/nut/upsd.pid: No such file or directory
Apr 16 11:03:14 freenas notifier: listening on 127.0.0.1 port 3493
Apr 16 11:03:14 freenas notifier: Connected to UPS [CP1000pfclcd]: usbhid-ups-CP1000pfclcd
Apr 16 11:03:14 freenas notifier: /usr/local/etc/nut/cmdvartab not found - disabling descriptions
Apr 16 11:03:14 freenas notifier: Starting nut_upsmon.
Apr 16 11:03:14 freenas notifier: kill: No such process
Apr 16 11:03:14 freenas notifier: UPS: CP1000pfclcd (master) (power value 1)
Apr 16 11:03:14 freenas notifier: Using power down flag file /etc/killpower
Apr 16 11:03:14 freenas notifier: Starting nut_upslog.
[root@freenas] ~#


From the shell typed:
<upsc CP1000pfclcd at localhost> this output shows UPS online.
 
Last edited:

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
D

dlavigne

Guest
If it used to restart on its own, I'd say yes. If you file a bug report, post the issue number here.
 

BigDave

FreeNAS Enthusiast
Joined
Oct 6, 2013
Messages
2,479
Bug Issue #9252
 
Status
Not open for further replies.
Top