DS220+ Resource Monitor stopped showing any values

Synology
1

Hello everyone,
since yesterday evening, when I had a voltage drop at home the NAS turned off, the resource monitor stopped showing any values ​​- it’s totally empty :confused:

Silence in logs and notifications. What can I do with this ?
thanks and best regards

DS220+
DSM 7.2-64570 Update 1

2

Weird, I have seen that short term when the NAS is slammed, but normally fixed within a few min

3

I also found this

probably a bigger problem

4

Interesting. Their is an update 2 to DSM 7.2 that just came out yesterday. that may fix this

5

I updated DS220+ to DSM 7.2-64570 Update 2 but unfortunately it didn’t help
The problem is related to SNMP, which stopped getting up ;/

# systemctl status snmpd.service

snmpd.service - SNMP Daemon
Loaded: loaded (/usr/lib/systemd/system/snmpd.service; static; vendor preset: disabled)
Active: activating (auto-restart) (Result: core-dump) since Tue 2023-07-25 17:42:33 CEST; 860ms ago
Process: 9845 ExecStart=/usr/syno/lib/systemd/scripts/snmpd.sh (code=dumped, signal=ABRT)
Main PID: 9845 (code=dumped, signal=ABRT)
CGroup: /snmp.slice/snmpd.service

# journalctl -xe

Jul 25 17:42:33 Pablo systemd[1]: snmpd.service: main process exited, code=dumped, status=6/ABRT
Jul 25 17:42:33 Pablo systemd[1]: Failed to start SNMP Daemon.
Jul 25 17:42:33 Pablo systemd[1]: Unit snmpd.service entered failed state.
Jul 25 17:42:33 Pablo systemd[1]: snmpd.service failed.
Jul 25 17:40:29 Pablo synoscgi[7948]: socket_process_manager.cpp:797 child 1995 exited with signal 13
Jul 25 17:40:30 Pablo systemd[1]: snmpd.service holdoff time over, scheduling restart.
Jul 25 17:40:30 Pablo systemd[1]: Starting SNMP Daemon…
Jul 25 17:40:30 Pablo snmpd.sh[2008]: *** buffer overflow detected ***: terminated

Jul 25 17:40:30 Pablo rm[2028]: uid: 0, euid: 0, arguments:[“-f” “/volume1/@snmpd.synology_geminilake_220+.64570.core.gz”]

Jul 25 17:40:30 Pablo coredump[2020]: Process snmpd2008 dumped core on signal [6]. Core file [/volume1/@snmpd.synology_geminilake_220+.64570.core.gz]. Cmdline [/usr/bin/snmpd -fLn -c /etc/snmp/snmpd.conf -p /var/run/snmpd.pid udp:161,ud
p6:161,tcp:161,tcp6:161 ]

Jul 25 17:40:30 Pablo coredump[2020]: Core file [/volume1/@snmpd.synology_geminilake_220+.64570.core.gz] size [688689]
Jul 25 17:40:30 Pablo systemd[1]: snmpd.service: main process exited, code=dumped, status=6/ABRT
Jul 25 17:40:30 Pablo systemd[1]: Failed to start SNMP Daemon.
Jul 25 17:40:30 Pablo systemd[1]: Dependency failed for Daemon for Resource Monitor.
Jul 25 17:40:30 Pablo systemd[1]: Job synosnmpcd.service/start failed with result ‘dependency’.

6

I asked synology service for help. They stated that

After reviewing the log, there are multiple core dumps of SNMP occurred that caused the abnormal status of enabling SNMP[1] which might be caused by the 3rd party RAM issue. Our engineers are currently investigating this issue and will roll out updates/patches addressing the issue. We apologize for any inconvenience caused.

I had to take out 8 GB of RAM and run some commands to restart SNMP

mv /var/lib/net-snmp/snmpd.conf /var/lib/net-snmp/snmpd.conf.bk
systemctl restart snmpd
systemctl status snmpd

Kindly check if the status show “active(running).”
mv /var/lib/net-snmp/snmpd.conf.bk /var/lib/net-snmp/snmpd.conf
systemctl restart snmp

and so I confirm that this time SNMP was successfully launched, statistics in Resource Monitor are working again, and by the way integration with Home Assistant has started working again.

I asked if they’d improved anything else, but so far I have no information

1 Like
7

It seems that certain processes are unable to start correctly and are encountering buffer overflow issues. The root cause has not been determined yet, and our engineers are actively investigating this matter.

1 Like
8

This is really great info thanks!

I have seen actually a few different things in DSM 7.2 that had memory allocation issues. I wonder if they did some serious tweaking under the hood