Thanks for using the TrueNAS Community Edition issue tracker! TrueNAS Enterprise users receive direct support for their reports from our support portal.

Issues

Select view

Select search mode

 
1-50 of 113
1 of 113

TrueNAS Scale: UPS (NUT) service fails to start correctly

Complete

Description

After configuring the UPS service and setting it to automatically start, it does not start up correctly after a full power cycle.

Instead, an alert is SOMETIMES generated, reflecting communication loss with the UPS:

And the system logs show the following:

At this point, the UPS cannot be seen via "upsc -l".

Issuing "systemctl restart nut-monitor" fixes the situation and the UPS is again visible via "upsc -l", implying that the NUT configuration being saved is correctly but that configuration is perhaps not available to the service at the correct time.

Related to and (debug available on the latter).

Problem/Justification

None

Impact

None

SmartDraw Connector

Katalon Manual Tests (BETA)

Pinned fields
Click on the next to a field label to start pinning.

Details

Assignee

Reporter

Impact

High

Components

Priority

More fields

Katalon Platform

Created February 21, 2021 at 11:58 AM
Updated July 1, 2022 at 5:13 PM
Resolved March 30, 2021 at 10:49 AM

Activity

Show:

Bug Clerk March 29, 2021 at 9:55 PM

Scott Harris March 19, 2021 at 6:18 AM

Im happy to provide diagnostic stuff if craig can't as this was affecting me also.  Although i have fixed using the following command 

On reboot everything is happy.

Waqar Ahmed March 18, 2021 at 7:08 PM

ping

Waqar Ahmed March 9, 2021 at 6:00 PM

I wonder if it has something to do with the fact of NUT trying to start before networking is configured and then failing in the process. Can you please share the file created by "systemd-analyze plot > bootorder.svg" ?

Craig King February 23, 2021 at 7:19 PM
Edited

Here you go , with a bit more information for good measure.

 

Immediately after restart:

The UI shows the service is running:

The output you requested:

 

 

(Test system, so password is random and not sensitive)

 

 

Note that nut-server is not running...

 

... so nut-monitor can't connect.

... and the UPS cannot be listed.

Then, restarting the nut-server service:

... happy days:

 

 

 

Edit: formatting

Edit #2: formatting, for real this time

 

Loading...