At some point in time, what was once a working communication between the UPS and the server, the communication seemed to have died. When I run lsusb, I see the device...

Bus 001 Device 002: ID 051d:0002 American Power Conversion Uninterruptible Power Supply

Model is APC BX1500M, unraid version is 7.1.4

When I go to the UPS settings section, its just a black screen with the title "UPS Settings" on top, nothing else.

When I run apctest I get a segmentation fault error.

2025-09-04 16:16:54 apctest 3.14.14 (31 May 2016) slackware

Checking configuration ...

: Bogus configuration value (*invalid-cable*)

: Bogus configuration value (*invalid-ups-type*)

apctest FATAL ERROR in apcconfig.c at line 672

Terminating due to configuration file errors.

Segmentation fault

Looking at cat /etc/apcupsd/apcupsd.conf I see its setup as autodetect...

UPSTYPE

DEVICE

it just stopped working one day. Thoughts?

Edited September 4, 2025Sep 4 by mlody

Here are some more log entries...

<6>Sep 4 16:14:22 Tower kernel: hid-generic 0003:051D:0002.0003: hiddev96,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS XS 1500M FW:947.d10 .D USB FW:d10 ] on usb-0000:00:14.0-1/input0

<12>Sep 4 16:16:54 Tower apctest: : Bogus configuration value (*invalid-ups-type*)

<6>Sep 4 16:16:54 Tower kernel: apctest[45326]: segfault at 0 ip 000000000040a1db sp 00007ffc9d9d5070 error 4 in apctest[a1db,403000+2f000] likely on CPU 4 (core 8, socket 0)

<12>Sep 4 16:16:54 Tower apctest: : Bogus configuration value (*invalid-cable*)

<6>Sep 4 16:16:54 Tower kernel: Code: e9 c4 fa ff ff ba 28 54 43 00 be 79 09 00 00 bf 4d 39 43 00 31 c0 e8 24 8b 01 00 0f 1f 40 00 55 48 89 fd 48 8b bf f0 92 00 00 <48> 8b 07 ff 50 18 48 89 ef e8 b7 9f 01 00 e8 72 90 01 00 bf 40 57

The cable hasn't changed... I also happen to have another of the same ups and cable, swapped cables, same thing. Did the UPS port die? Could it be? But it does see the USB... and why isn't the UPS settings page working?

Edited September 4, 2025Sep 4 by mlody

Boot with a different flash drive using a stock install and retest, no key needed, that will confirm if it's a config issue or a different problem.

One hint that once saved my life:

• UPS connection was always lost after some period of time

• USB port was blocked (needed reboot)

What cured this really evil nagging thing (the UPS works flawlessly for ages under Windows, just Linux kills the connection sooner or later) was to insert a small Raspberry-PI USB hub!

These have been especially designed (other MIGHT work, but are not guranteed to!) to fix the conflict when devices on both ends supply 5V USB power to the line.

In this cases it is not defined which device "wins" and if the other shuts off 5V to that port or not.

So there might come up bad situations that create spikes, overload the port or something.

The linux driver is very sensitive to this and shuts down the whole port or even controller!

(Windows ignores the overload situation and waits some time before it stops the port. In case of a spike nothing happens)

So, if you reboot, everything works again, but after some time the loss of connection reappears, give this little (and cheap) hub a chance...

On 9/5/2025 at 12:45 AM, JorgeB said:

Boot with a different flash drive using a stock install and retest, no key needed, that will confirm if it's a config issue or a different problem.

Booted with a new flash drive and the UPS reports everything, np. How do I reset the UPS configuration?

edit: copied the config from the working stock key and pasted into /etc/apcupsd/apcupsd.conf, started the daemon. The widget shows on the dashboard, with no data, and the UPS settings page still isn't loading.

Edited September 6, 2025Sep 6 by mlody

If it works with a stock install, it suggests a config problem, you can try redoing the flash drive, backup the current one first and then recreate it using the USB tool and just restore the bare minimum, like the key, super.dat and the pools folder for the assignments, also copy the docker user templates folder (\config\plugins\dockerMan\templates-user), if all works you can then reconfigure the server or try restoring a few config files at a time from the backup to see if you can find the culprit.