UPS Spamming logs

[Spencer Skinner]

I have been having this issue for about 3-4 weeks now but chose to ignore it, not sure why. But i get one of these logs every 5 seconds after a restart unless I disconnect and reconnect the UPS physically

Code:

Nov  1 17:51:33 AlphaServer upsmon[2667]: UPS [ups]: connect failed: Connection failure: Connection refused

Absolutely no idea why its happening, but it needs physical intervention to fix everytime it happens, is there a way i can just stop this spam for good?

Freenas 11.2-RC1 (Was also happening on 11.2 U6)

Thanks

 

[DrKK]

Almost certainly this will stop if you stop-start the service in the services menu, sir.

So that's better than physically having to do something. What make/model UPS is it while we figure out what's causing the problem in the first place?

 

[Spencer Skinner]

Almost certainly this will stop if you stop-start the service in the services menu, sir.

So that's better than physically having to do something. What make/model UPS is it while we figure out what's causing the problem in the first place?

Forgot to add that ahaha, its an Eaton 52700i connected over USB

 

[Spencer Skinner]

Almost certainly this will stop if you stop-start the service in the services menu, sir.

Also forgot to mention, the service is stopped and cant be started until i reconnect the UPS

 

[DrKK]

Also forgot to mention, the service is stopped and can't be started until i reconnect the UPS

I'm confused. How are you getting messages if the service is stopped?

 

[Spencer Skinner]

I'm confused. How are you getting messages if the service is stopped?

This is the question I am asking myself, it tries to start upon startup so all i can conclude is that its trying to repeatedly start but cant?

 

[mpfusion]

I can confirm this (FreeNAS-11.1-U4). We had the same happening. The UPS connection broke, and the log was spammed every five seconds. The UPS service won't start without finding the UPS.

It's nice to know that something went wrong, but a message every five seconds is a bit chatty and clutters the log.

 

[Spencer Skinner]

I can confirm this (FreeNAS-11.1-U4). We had the same happening. The UPS connection broke, and the log was spammed every five seconds. The UPS service won't start without finding the UPS.

It's nice to know that something went wrong, but a message every five seconds is a bit chatty and clutters the log.

Have you still got the issue now or did you manage to fix it?

 

[mpfusion]

Have you still got the issue now or did you manage to fix it?

I fixed it. But I can't tell you how. After a reboot the log was spammed and no UPS connection. I tried different ports (maybe it changed after a reboot, dunno) to no avail. After some time fiddling and trying to (re)start the UPS service the log spamming stopped. But I can't tell you what exactly I did to make it stop. All I can confirm is that it keeps spamming although it's turned off (according to the GUI).

Also see my other thread about the issue.

 

[DrKK]

OK well I guess that's simply the FreeNAS responding to your "turn on this service at boot", so it keeps trying to turn it on. One stopgap measure would be to turn that auto-start off, and then just remember to start your ups service manually when there are reboots...not a great solution, of course.

 

[Delvien]

I can confirm that this happens to me (11.2), I have the service off, auto start turned off, and I get spammed by the message.

I did have a UPS connected with this service a while ago, but I turned it off and switched where the UPS monitoring goes...

This is ultra annoying, and there is no way to fix it in the GUI.

 

[DrKK]

You're saying, you have "upsmon" messages in your log, and the UPS service is TURNED OFF?

First, let's do a sanity check:

Code:

ps -auxg | grep upsmon

 

[Delvien]

And I have rebooted several times, trying to turn on UPS service errors out.

 

[DrKK]

OK, well, the UPS service appears to be on.

This is very odd. You are stating you have the UPS service off, and NOT auto-starting at boot, but the upsmon is running? That's very, very odd.