[Help] Resource Monitor - Continuous Monitoring not Working

[fcs001fcs]

I am on TOS 6.0.650 on a F4-423 NAS and have not had Resource Monitor - Continuous Monitoring working for at least the 3 last TOS updates.

So, when you go to the settings of "Resource Monitoring" and enable the check box "Enable continuous system resource monitoring" (default is 30 days) nothing appears on the graphs. When this check box is not selected I get real time data showing the last 5 data points that keeps being overwritten as time moves forward.

It did work for me at one time, but I can't seem to get it working any more.

With my basic knowledge of Linux I tried to find the issue but have hit a dead end.

I started and restarted the "ResourceCollection" service, but it did not help. I did notice there is a warning when I start it but do not now if it is normal or not.

See below output from Putty and I am wondering if the warning is a clue I should follow and how would I do that. Any help would be appreciated.

Code: Select all

xxxSuperUser@NAS-xxxxxx:/run# systemctl restart ResourceCollection
xxxSuperUser@NAS-xxxxxx:/run# systemctl status ResourceCollection
● ResourceCollection.service - ResourceCollection
     Loaded: loaded (/lib/systemd/system/ResourceCollection.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2025-03-16 17:10:59 CET; 6s ago
    Process: 158453 ExecStartPre=vmtouch -P /var/run/rc-vmtouch.pid -ld /usr/bin/ec_stat /usr/sbin/smartctl (code=exited, status=0/SUCCESS)
    Process: 158456 ExecStart=/usr/sbin/ResourceCollection -D (code=exited, status=0/SUCCESS)
   Main PID: 158470 (ResourceCollect)
      Tasks: 10 (limit: 38274)
     Memory: 26.3M
        CPU: 606ms
     CGroup: /system.slice/ResourceCollection.service
             ├─158455 vmtouch -P /var/run/rc-vmtouch.pid -ld /usr/bin/ec_stat /usr/sbin/smartctl
             └─158470 /usr/sbin/ResourceCollection

Mar 16 17:10:58 NAS-xxxxxx systemd[1]: Starting ResourceCollection...
Mar 16 17:10:58 NAS-xxxxxx systemd[1]: ResourceCollection.service: Found left-over process 158455 (vmtouch) in control group while starting unit. Ignoring.
Mar 16 17:10:58 NAS-xxxxxx systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. 
Mar 16 17:10:58 NAS-xxxxxx systemd[1]: ResourceCollection.service: Can't open PID file /run/ResourceCollection.pid (yet?) after start: Operation not permitted
Mar 16 17:10:59 NAS-xxxxxx systemd[1]: Started ResourceCollection.

[Helengrace22]

I’m experiencing something similar after updating to 5.1.66 — random reboots and occasional UI freezes. Did rolling back to the previous version fix it for you completely?

[CursaYang]

You can check the current size of the system partition. If it is 2GB, you can revert to the stable version 5.0.176, or after reallocating the system partition, reinstall the 5.1 system. You can refer to this forum post for guidance: back up your data, reallocate the system partition size, and reinstall the system:

viewtopic.php?t=4912