UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused

tfran1990

Patron
Joined
Oct 18, 2017
Messages
294
I am having a problem with my ups all or the sudden after a reboot, on version 11.3-U2.1
Its odd to me that after over a year im just all of the sudden having problems.

The error im getting is
Code:
Nov 20 17:43:13 freenas upsmon[2921]: upsmon parent: read
Nov 20 17:43:13 freenas collectd[3157]: nut plugin: nut_connect: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
Nov 20 17:43:33 freenas collectd[3157]: nut plugin: nut_connect: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
Nov 20 17:44:13 freenas collectd[3157]: nut plugin: nut_connect: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
Nov 20 17:45:33 freenas collectd[3157]: nut plugin: nut_connect: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
Nov 20 17:45:46 freenas root: /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut
Nov 20 17:45:46 freenas upsmon[3332]: UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused
Nov 20 17:45:46 freenas upsmon[3332]: Communications with UPS ups@localhost:3493 lost
Nov 20 17:45:46 freenas collectd[3378]: nut plugin: nut_connect: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
Nov 20 17:45:51 freenas upsmon[3332]: UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused
Nov 20 17:45:51 freenas upsmon[3332]: UPS ups@localhost:3493 is unavailable
Nov 20 17:45:56 freenas upsmon[3332]: UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused
Nov 20 17:46:01 freenas upsmon[3332]: UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused
Nov 20 17:46:06 freenas upsmon[3332]: UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused
Nov 20 17:46:06 freenas collectd[3378]: nut plugin: nut_connect: upscli_connect (localhost, 3493) failed: Connection failure: Connection refused
Nov 20 17:46:11 freenas upsmon[3332]: UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused
Nov 20 17:46:16 freenas upsmon[3332]: UPS [ups@localhost:3493]: connect failed: Connection failure: Connection refused


The output of dmesg | grep -i usbus | grep -i --color 'american power conversion' is
Code:
ugen0.3: <American Power Conversion Back-UPS RS 1350MS FW951.e4 .D USB FWe4> at usbus0


the output of upsc ups@localhost is
Code:
root@freenas:~ # upsc ups@localhost
Error: Connection failure: Connection refused


I used this guide to set it up when i first got it, had no problem with it within the last year or so.
https://www.cyberciti.biz/faq/how-to-install-apc-ups-on-freenas-server/


So far i have looked at google and the forum and i found some older threads.
https://www.truenas.com/community/threads/apc-ups-issues.83415/
https://jira.ixsystems.com/browse/NAS-103944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

I have tried different drivers in the drop down conf
I even tried a different cable


The email it sends me says
Code:
NOTIFICATION: 'COMMBAD'<br>UPS: 'ups'<br><br>Statistics could not be recovered<br>

and

NOTIFICATION: 'NOCOMM'<br>UPS: 'ups'<br><br>Statistics could not be recovered<br>
 
Last edited:

tfran1990

Patron
Joined
Oct 18, 2017
Messages
294
Looking for some input on this, anyone have this ups?

maybe thinking about reloading a config from a couple months ago.
 

Ofloo

Explorer
Joined
Jun 11, 2020
Messages
60
Same problem UPS Nut is not working. Neither the report page is working did new install, then recovered configuration, from backup of 12.x
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Sounds like your UPS hardware has gone bad. Try replacing the UPS.
 

Ofloo

Explorer
Joined
Jun 11, 2020
Messages
60
What made you make that conclusion. pfsense is connected to it TrueNAS is slave configuration. I think TrueNAS is bad !
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
You replaced the cable, but NUT is still reporting COMBAD or NOCOM to the UPS. This sounds like a bad controller in the UPS.
 

Ofloo

Explorer
Joined
Jun 11, 2020
Messages
60
I did no such thing. Also pfsense is reporting fine ! Again TrueNAS is nut slave to pfsense so cable is bad for TrueNas while that same cable is ok for pfsense. Did you actually read my responds?

1659221676105.png

You should pay more attention to what some people say. TrueNAS 13 is just broken. Not sure why nothing on the report page is reporting anything. And i constantly get emails from nut, "statistics could not be recovered"

Again so you understand. It's an IP slave there is no cable ! It's slave to pfsense which reports fine ! So hardware is fine !!!!!!!
 

Attachments

  • 1659221618462.png
    1659221618462.png
    69.1 KB · Views: 139

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Apologies, this is what happens when you necro a 2 year old thread. Please start a new thread in the future.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
As for access, NUT on TrueNAS is probably trying to access the default port 3493 on the master, instead of 3551, which could be the cause of the comm issue.
 

Ofloo

Explorer
Joined
Jun 11, 2020
Messages
60
Was the port changed or something? Because this configuration just worked fine in 12.x
 

Ofloo

Explorer
Joined
Jun 11, 2020
Messages
60
no going back to the 12.x and restoring configuration doesn't make it work either something is wrong with the restore configuration. Also I need to run midclt call smb.synchronize_passdb to make smb work.
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
However the report page is still broken.
Which version of TrueNAS? 12.0-U7, in particular, was known for reporting not working.
 

Ofloo

Explorer
Joined
Jun 11, 2020
Messages
60
latest U8, it's the same issue in 13 latest. Downgraded back but same problem.

However on the dash there's info

1659224438304.png
 

Ofloo

Explorer
Joined
Jun 11, 2020
Messages
60
Also when I check /var/db/collectd there's not hing there, and when i ls /usr/local/etc there seems to be an unexisting uid 60 and uid/gid 601.
 
Top