Generex UPS Adapter 1.86.30 lost real-time information table

DB schema was not updated (resolved in discord discussion).

I propose to find for the problem together through discussion on Discord Channel: Observium

Ignore this message (about not found), mib still defined for os.
See my previous message about walk from device.

Also probably lost communication between UPS and Generex module.

Checked again, this agent not return any numeric data (except model/version).
This is full walk of UPS-MIB from your dump:

UPS-MIB::upsIdentManufacturer.0 = STRING: UPS Service

UPS-MIB::upsIdentModel.0 = STRING: Amberwave AMB ATS

UPS-MIB::upsIdentUPSSoftwareVersion.0 = STRING: n/a

UPS-MIB::upsIdentAgentSoftwareVersion.0 = STRING: CS141-SNMP V1.86.30 191203

UPS-MIB::upsAlarmsPresent.0 = Gauge32: 0

UPS-MIB::upsObjects.13.1.0 = INTEGER: 1

UPS-MIB::upsObjects.13.2.0 = INTEGER: 0

UPS-MIB::upsObjects.13.3.0 = INTEGER: 1

UPS-MIB::upsObjects.13.4.0 = INTEGER: 1

UPS-MIB::upsObjects.13.6.0 = INTEGER: 1

Than answer same, something changed on device.

We havent updated any of our UPSes lately.

When I run discovery -d , i can see this table:

MIBdefined for os but not found.

 In the same time APC UPSes is reporting as usual.

Or wait.. there is used only common UPS-MIB. Will see..

Hrm, as I see this is not Observium issue.
I think you also update or change something on device, because it's not return any data in SNMP ent tree.
As in your snmpwalk:

.1.3.6.1.4.1 = No Such Object available on this agent at this OID

Im sorry, I marked wrong version of observium. Its not CE (community edition). It is:

Observium 21.6.11442 (stable)

Professional

Updated with attachment snmpwalk.zip

Please make and attach additional information about the device:

• full snmp dump from device:

  snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk

  snmpwalk -v2c -c <community> --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

  If device not support SNMP version 2c, replace -v2c with -v1.

• If you have problems with discovery or poller processes, please do and attach these debugs:

  ./discovery.php -d -h <device>

  ./poller.php -d -h <device>

• additionally attach device and/or vendor specific MIB files

Note, this comment is added automatically.