OPNsense Forum

English Forums => 26.1, 26,4 Series => Topic started by: mrzaz on May 24, 2026, 05:12:04 AM

Title: Previously working os-apcupsd plugin has stopped working.
Post by: mrzaz on May 24, 2026, 05:12:04 AM
Hello,
I have a APC UPS SMT750IC but uses "APC PowerShute Serial Shutdown" in my server
to handle shutdown of the server (as my old standalone SNMP card was to old for the new UPS)
but also act as a NIS for other devices like Synology DS920+ and OpnSense via the "os-apcupsd"
plugin and it has been working fine for a couple of years.
Both from Synology but also from OpnSense.

I have relied on that it was working good for a very long time so i forgot to check it in more
details in OpnSense but tonight I realised that it was broken.  No info in the dashboard widget,
no info in the apcupsd plugin status screen. Found one problem that was related to NIS port 3551
being used but changed to 3552 to test but still not resolved.

I use "Ether, snmp, 192.168.x.x:161:APC:private" as config which has been working for years but now stopped working.

Log shows
2026-05-24T03:11:37 Notice apcupsd apcupsd 3.14.14 (31 May 2016) freebsd startup succeeded

I have traced the port 161 signalling out of OpnSense on LAN going out OK.
I then traced the port 161 signalling in to server with "PowerShute Serial Shutdown" application and it is comming in.
But still nothing.

I then checked Synology UPS settings and it is working fine, both on SNMP v2c (using private) and also v3 with username/psw.

I tried to start it manually to get startup log entries but nothing found really apart from
Selected community: "private"
Selected MIB: "APC"
But there are NO successful SNMP reads afterward.

Have no clue why this started happening, especially as it works totally fine from Synology NAS and also from OpnSense for a long time.

Does anyone else use "os-apsupsd" plugin that also experience the same issue ?

I am running on latest version of OpnSense/Apsupsd.

BR,
Dan Lundqvist
Stockholm, Sweden