Logs show almost daily UPS "disconnection"

[BigDave]

Should I be worried about this?

Code:

Nov 22 09:11:59 freenas kernel: ugen1.3: <CP1000PFCLCD> at usbus1 (disconnected)
Nov 22 09:11:59 freenas root: Unknown USB device: vendor 0x0764 product 0x0501 bus uhub3
Nov 22 09:11:59 freenas kernel: ugen1.3: <CP1000PFCLCD> at usbus1
Nov 22 09:12:01 freenas kernel: ugen1.3: <CP1000PFCLCD> at usbus1 (disconnected)
Nov 22 09:12:02 freenas root: Unknown USB device: vendor 0x0764 product 0x0501 bus uhub3
Nov 22 09:12:02 freenas kernel: ugen1.3: <CP1000PFCLCD> at usbus1
Nov 22 09:12:11 freenas upsd[6286]: Data for UPS [CP1000pfclcd] is stale - check driver
Nov 22 09:12:11 freenas root: Unknown USB device: vendor 0x0764 product 0x0501 bus uhub3
Nov 22 09:12:11 freenas upsmon[6311]: Poll UPS [CP1000pfclcd] failed - Data stale
Nov 22 09:12:11 freenas upsmon[6311]: Communications with UPS CP1000pfclcd lost
Nov 22 09:12:13 freenas upsd[6286]: UPS [CP1000pfclcd] data is no longer stale
Nov 22 09:12:16 freenas upsmon[6311]: Communications with UPS CP1000pfclcd established

I'm gonna try another USB port and see if this happens again or goes away...

 

[Fraoch]

What make and model of UPS?

 

[BigDave]

CyberPower CP1000PFCLCD

 

[BigDave]

I switched USB ports just for grins.
Log spit out this...

Code:

Broadcast Message from root@freenas.local
  (no tty) at 20:01 CST...

Communications with UPS CP1000pfclcd lost


Broadcast Message from root@freenas.local
  (no tty) at 20:01 CST...

Communications with UPS CP1000pfclcd established

 

[BigDave]

Seems this is bug related (#4647)

 

[SweetAndLow]

A documented bug the workaround is to set maxage to 25 in the upsd.conf

 

[Ericloewe]

There was talk that 9.3 fixes this. I'm looking forward to checking that it is solved (APC Back-UPS Pro in my case) when 9.3 hits release candidate.

 

[BigDave]

A documented bug the workaround is to set maxage to 25 in the upsd.conf

For the moment that would be beyond my abilities. WARNING: massive reading ahead

There was talk that 9.3 fixes this. I'm looking forward to checking that it is solved (APC Back-UPS Pro in my case) when 9.3 hits release candidate.

Then again, I could be lazy and just wait...

 

[Ericloewe]

Then again, I could be lazy and just wait...

My thoughts exactly.

 

[BigDave]

There was talk that 9.3 fixes this. I'm looking forward to checking that it is solved (APC Back-UPS Pro in my case) when 9.3 hits release candidate.

Eric, just thought you may have not seen this from Jordan.
06:34 PM Bug #4914 (3rd party to resolve): upsd reporting data for UPS is stale -check driver
Upstream FreeBSD bug. We're not going to make any progress with this. Jordan Hubbard

 

[Ericloewe]

Eric, just thought you may have not seen this from Jordan.
06:34 PM Bug #4914 (3rd party to resolve): upsd reporting data for UPS is stale -check driver
Upstream FreeBSD bug. We're not going to make any progress with this. Jordan Hubbard

Just our luck, thanks for the info.

 

[budmannxx]

Damn, bad news about the proper fix.

@BigDave here's the thread that talks about the workaround:

https://forums.freenas.org/index.php?threads/20898/

It's actually pretty straightforward. Bad news is it won't survive a reboot. Good news is if you reboot and forget to reapply the setting to upsd.conf, there's a built-in reminder (the COMMBAD messages :))

 

[BigDave]

@budmannxx Thanks for the link! I actually read that and that's how I discovered
my log issue was a bug. Further research lead me to the bug file/post where I found
Jordan's decision about it.
It's weird, but since switching to the other USB port on my X9SCM-F-O motherboard,
I have not gotten that log message for the past two days. Knocking on wood and
crossing my fingers that it stays that way

 

[Ericloewe]

@budmannxx Thanks for the link! I actually read that and that's how I discovered
my log issue was a bug. Further research lead me to the bug file/post where I found
Jordan's decision about it.
It's weird, but since switching to the other USB port on my X9SCM-F-O motherboard,
I have not gotten that log message for the past two days. Knocking on wood and
crossing my fingers that it stays that way

Yeah, that was one of the weird things about the bug.

I'll probably just move it over to pfSense, since for some reason pfSense can't reach the UPS via the network on FreeNAS. They say pfSense's NUT implementation is a bit better, so I'll use that one as the server.

 

[Mlovelace]

Can you add

Code:

MAXAGE 25

to the Auxiliary parameters field in the UPS settings tab?

 

[rogerh]

Can you add

Code:

MAXAGE 25

to the Auxiliary parameters field in the UPS settings tab?

Unfortunately those parameters go in the wrong configuration file for this purpose.

 

[SweetAndLow]

Here ate the steps to do it be the command line

Code:

mount -rw /
echo "MAXAGE 25" >> /use/local/etc/nut/upsd.conf
mount -r /
service nut restart

 

[BigDave]

I switched USB ports just for grins.
Log spit out this...

Code:

Broadcast Message from root@freenas.local
  (no tty) at 20:01 CST...

Communications with UPS CP1000pfclcd lost


Broadcast Message from root@freenas.local
  (no tty) at 20:01 CST...

Communications with UPS CP1000pfclcd established

Just wanted to post a follow up on this. Since I switched cable from my UPS
to the other USB port on my motherboard, the log messages have completely stopped.
No news, is good news...

 

[PowerWiesel]

Here ate the steps to do it be the command line

Code:

mount -rw /
echo "MAXAGE 25" >> /use/local/etc/nut/upsd.conf
mount -r /
service nut restart

4 errors in 5 lines.. n1

thanks for helping NOT
--------------------------------------


these are the right steps:

Code:

mount -uw /
echo "MAXAGE 25" >> /etc/local/nut/upsd.conf
mount -ur /
service nut restart

 

[Ericloewe]

4 errors in 5 lines.. n1

thanks for helping NOT
--------------------------------------


these are the right steps:

Code:

mount -uw /
echo "MAXAGE 25" >> /etc/local/nut/upsd.conf
mount -ur /
service nut restart

You're well-advised to spare the sarcasm when people are trying to help you.