Resource Collection

Language, region, time zone, power, navigation, notification and more.
Locked
User avatar
Gremlin
Gold Member
Posts: 1625
Joined: 02 Dec 2022, 22:31
Great Britain

Resource Collection

Post by Gremlin »

Tos6.0.535

yesterday I enabled 'continuous resource collection' in control panel.
Today, on startup, I noticed 'ResourceCollection.service' failed.
Tried checking status individually via cli {systemctl -status {item name}
This came back as 'unit not found'
I then checked 'systemctl status'

Code: Select all

*********************@NAS-T1:~# systemctl status
    NAS-T1
    State: degraded
     Jobs: 0 queued
   Failed: 15 units
    Since: Wed 2024-11-20 08:31:17 GMT; 6h ago
   CGroup: /
                Çinit.scope
                    Ç  1 /sbin/init
                    Ç167 /usr/sbin/uart_key /dev/ttyS0 touch /.resetFlag
                Çsystem.slice
                  Çnetplug.service
                      Ç2252 /sbin/netplugd -p /var/run/netplugd.pid
                  Çrsync.service
                      Ç2703 /usr/bin/rsync --daemon --config=/etc/rsyncd.conf
                  Çsystemd-udevd.service
                      Ç524 /lib/systemd/systemd-udevd
                  Çcron.service
                      Ç2164 /usr/sbin/cron -f -P
                  ÇSnapshot.service
                      Ç3705 /Volume1/@apps/Snapshot/sbin/Snapshot-amd64
                  Çwsdd.service
                      Ç2720 python3 /usr/sbin/wsdd --shortlog --chroot=/run/wsdd -d SMT-QUALITY
             Ôö£ÔöÇnginx.service
             Ôöé Ôö£ÔöÇ1999 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
             Ôöé Ôö£ÔöÇ2000 nginx: worker process
             Ôöé Ôö£ÔöÇ2001 nginx: worker process
             Ôöé Ôö£ÔöÇ2002 nginx: worker process
             Ôöé ÔööÔöÇ2003 nginx: worker process
             Ôö£ÔöÇdocker.service
             Ôöé ÔööÔöÇ3874 /Volume1/@apps/docker/sbin/DockerApi
             Ôö£ÔöÇpolkit.service
             Ôöé ÔööÔöÇ562 /usr/libexec/polkitd --no-debug
                  Çnetworkd-dispatcher.service
                      Ç560 /usr/bin/python3 /usr/bin/networkd-dispatcher --run-startup-triggers
                  Çxl2tpd.service
                      Ç2195 /usr/sbin/xl2tpd
                  ÇMultimediaServer.service
                      Ç3347 ../sbin/MultimediaServer
                  Çrarpd.service
                      Ç2169 /usr/sbin/rarpd -e -v
                  ÇDockerEngine.service
                      Ç2848 /Volume1/@apps/DockerEngine/dockerd/bin/dockerd --config-file=/Volume1/@apps/DockerEngine/conf/da Ç
                      Ç2866 containerd --config /var/run/docker/containerd/containerd.toml --log-level info
                  Çwpa_supplicant.service
                      Ç573 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant
                  ÇModemManager.service
                      Ç588 /usr/sbin/ModemManager
                  Çnmbd.service
                      Ç2089 /usr/sbin/nmbd --foreground --no-process-group
                  Çsamba.service
                      Ç2721 /usr/sbin/smbd --foreground --configfile=/etc/samba/smb.conf --no-process-group
                      Ç2726 /usr/sbin/smbd --foreground --configfile=/etc/samba/smb.conf --no-process-group
                      Ç2727 /usr/sbin/smbd --foreground --configfile=/etc/samba/smb.conf --no-process-group
                      Ç2733 /usr/lib/x86_64-linux-gnu/samba/samba-bgqd --ready-signal-fd=45 --parent-watch-fd=12 --debuglevel Ç
                  Çsystemd-journald.service
                      Ç472 /lib/systemd/systemd-journald
                  Çmdmonitor.service
                      Ç353 /sbin/mdadm --monitor --scan --daemonise --syslog --delay=10 --program=/etc/init.d/nas/mdadm-monit Ç
                  ÇLogCenter.service
                      Ç3102 ../bin/LogCenter
                  Çssh.service
                      Ç684 sshd: /usr/sbin/sshd -D -f /etc/ssh/sshd_config [listener] 0 of 10-100 startups
                  ÇScheduledTask.service
                      Ç554 /usr/sbin/ScheduledTask
                  ÇNetworkManager.service
                      Ç558 /usr/sbin/NetworkManager --no-daemon
                  Çsystem-postgresql.slice
                      Ç[email protected]
                        Ç 487 /usr/lib/postgresql/13/bin/postgres -D /etc/postgresql/13/main -c unix_socket_directories=/var/ Ç
                        Ç 489 postgres: checkpointer Ç
                        Ç 490 postgres: background writer Ç
                        Ç 491 postgres: walwriter Ç
                        Ç 492 postgres: logical replication launcher Ç
                        Ç2578 postgres: terramaster postgres 127.0.0.1(52960) idle Ç
                  Çrsyslog.service
                      Ç1871 /usr/sbin/rsyslogd -n -iNONE
                  Çtnas-smartfan.service
                      Ç1241 /usr/sbin/ter_smartfan
                      Ç1429 vmtouch -l /usr/bin/ipmitool /usr/sbin/xunduntools /usr/bin/ec_stat /sbin/hdparm /usr/sbin/smartc Ç
                  Çrpcbind.service
                      Ç432 /sbin/rpcbind -f -w
                  Çnasips.service
                      Ç2006 /sbin/nasips
                  Çmsg.service
                      Ç2112 vmtouch -ld /sbin/arp-scan -P /var/run/msg_vmtouch.pid
                      Ç2125 /usr/bin/msgcenter >/var/log/msgcenter.log
                      Ç2775 /usr/sbin/ter_vg_monitor
                  ÇClamAV.service
                 ÔööÔöÇ2709 /Volume1/@apps/ClamAV/sbin/ClamAV-amd64
             Ôö£ÔöÇredis-server.service
             Ôöé ÔööÔöÇ1217 /usr/bin/redis-server 127.0.0.1:6379
             Ôö£ÔöÇTOSDaemon.service
             Ôöé ÔööÔöÇ2081 /usr/sbin/TOSDaemon
             Ôö£ÔöÇmediaindex.service
             Ôöé Ôö£ÔöÇ3344 /usr/sbin/mediaindex -f /etc/media.conf -P /run/mediaindex/mediaindex.pid -S
             Ôöé Ôö£ÔöÇ3577 /usr/sbin/thumbnailDaemon
             Ôöé ÔööÔöÇ3756 /usr/sbin/thumbnailSearch
                  Çsmartmontools.service
                      Ç563 /usr/sbin/smartd -n
                  Çttyd.service
                      Ç625 /usr/bin/ttyd -b /v2/ttyd -P 1 -i lo -t theme {background": "#0C0C0C"} -p 7681 bash --login
                  Çdovecot.service
                      Ç2083 /usr/sbin/dovecot -F
                      Ç2208 dovecot/anvil
                      Ç2209 dovecot/log
                      Ç2213 dovecot/config
                  Çsystemd-resolved.service
                      Ç568 /lib/systemd/systemd-resolved
                  Çphp7.4-fpm.service
                      Ç3121 php-fpm: master process (/etc/nginx/php-fpm.conf)
                      Ç3126 php-fpm: pool TOS
                      Ç3127 php-fpm: pool TOS
                      Ç3128 php-fpm: pool TOS
                      Ç3129 php-fpm: pool TOS
                      Ç3130 php-fpm: pool TOS
                  Çmediadb.service
                      Ç3326 /usr/lib/postgresql/13/bin/postgres -D /Volume1/@system/media/pgsql
                      Ç3338 postgres: checkpointer
                      Ç3339 postgres: background writer
                      Ç3340 postgres: walwriter
                      Ç3341 postgres: logical replication launcher
                      Ç3361 postgres: postgres postgres 127.0.0.1(44212) idle
                      Ç3374 postgres: postgres postgres 127.0.0.1(44230) idle
                  Çiscsid.service
                      Ç2153 /sbin/iscsid
                      Ç2154 /sbin/iscsid
                  Çnut-monitor.service
                      Ç3173 /lib/nut/upsmon
                      Ç3174 /lib/nut/upsmon
                  ÇUSBCopy.service
                      Ç3803 /Volume1/@apps/USBCopy/sbin/USBCopy
                  Çdbus.service
                      Ç557 @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
                  Çtnas-storage-device-tool.service
                      Ç502 /usr/sbin/ter_storage_device_tool
                  ÇResourceCollection.service
                      Ç4511 vmtouch -P /var/run/rc-vmtouch.pid -ld /usr/bin/ec_stat /usr/sbin/smartctl
                      Ç4531 /usr/sbin/ResourceCollection
                  Çsystem-getty.slice
                      Ç[email protected]
                        Ç2192 /sbin/agetty -o -p -- \u --noclear tty1 linux
                  Çtelnet.service
                      Ç  2167 /usr/sbin/telnetd -p 23
                      Ç273718 /bin/login
                      Ç273938 -bash
                      Ç274334 systemctl status
                  Çavahi-daemon.service
                      Ç750 avahi-daemon: running [NAS-T1.local]
                      Ç757 avahi-daemon: chroot helper
                  Çonlined.service
                      Ç2502 /usr/sbin/onlined -log-file /var/log/online2.log -pprof
                  Çsystemd-logind.service
                    Ç564 /lib/systemd/systemd-logind
DEGRADED
...
FAILED UNITS: 15


where would I find details of all these units that failed?
Resource collection still seems to be working, so I don't know the point of this unit.
Any enlightenment from the collective audience?
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
User avatar
bugacha
Posts: 59
Joined: 09 Nov 2024, 16:25
Algeria

Re: Resource Collection

Post by bugacha »

Mine shows these failed :

Code: Select all

# systemctl list-units --state=failed
  UNIT                          LOAD   ACTIVE SUB    DESCRIPTION
● console-setup.service         loaded failed failed Set console font and keymap
● [email protected]       loaded failed failed Netscript ifup for bond0
● [email protected]     loaded failed failed Netscript ifup for erspan0
● [email protected]        loaded failed failed Netscript ifup for eth0
● [email protected]        loaded failed failed Netscript ifup for eth1
● [email protected]        loaded failed failed Netscript ifup for gre0
● [email protected]     loaded failed failed Netscript ifup for gretap0
● [email protected]     loaded failed failed Netscript ifup for ip6tnl0
● [email protected]        loaded failed failed Netscript ifup for sit0
● [email protected]       loaded failed failed Netscript ifup for tunl0
● [email protected] loaded failed failed Netscript ifup for veth89c4a2d
● [email protected] loaded failed failed Netscript ifup for veth8fc66da
● [email protected] loaded failed failed Netscript ifup for vethe295e29
● [email protected]       loaded failed failed Netscript ifup for wwan0
● [email protected]       loaded failed failed Netscript ifup for wwan1
User avatar
Gremlin
Gold Member
Posts: 1625
Joined: 02 Dec 2022, 22:31
Great Britain

Re: Resource Collection

Post by Gremlin »

Interesting that they are nearly all for network services.

(I don't care about your opinions.)
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
User avatar
TMzethar
TM Support
Posts: 2817
Joined: 27 Oct 2020, 16:43

Re: Resource Collection

Post by TMzethar »

We have noticed that in some cases the service fails during startup as you mentioned. This may be due to the fact that other necessary resources are not ready when the service is started. When the service fails to start, it will try to start again, so you don't need to worry about this.
You can check the status with the following command:

Code: Select all

systemctl status ResourceCollection.service
To contact our team, please send email to following addresses, remember to replace (at) with @:
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
User avatar
Gremlin
Gold Member
Posts: 1625
Joined: 02 Dec 2022, 22:31
Great Britain

Re: Resource Collection

Post by Gremlin »

TMzethar wrote: 21 Nov 2024, 16:28
Thanks. I did find this particular service in the original post eventually. {note to self: get new glasses}
so it did restart after failure.

I also took a look at actual failed status units:

Code: Select all

systemctl list-units --state=failed
  UNIT                          LOAD   ACTIVE SUB    DESCRIPTION
    console-setup.service         loaded failed failed Set console font and keymap
    [email protected]       loaded failed failed Netscript ifup for bond0
    [email protected]     loaded failed failed Netscript ifup for erspan0
    [email protected]        loaded failed failed Netscript ifup for eth0
    [email protected]        loaded failed failed Netscript ifup for eth1
    [email protected]        loaded failed failed Netscript ifup for gre0
    [email protected]     loaded failed failed Netscript ifup for gretap0
    [email protected]     loaded failed failed Netscript ifup for ip6tnl0
    [email protected]        loaded failed failed Netscript ifup for sit0
    [email protected]       loaded failed failed Netscript ifup for tunl0
    [email protected]       loaded failed failed Netscript ifup for wwan0
ÔùÅ [email protected]       loaded failed failed Netscript ifup for wwan1
ÔùÅ nut-driver.service            loaded failed failed Network UPS Tools - power device driver controller
ÔùÅ nut-server.service            loaded failed failed Network UPS Tools - power devices information server
ÔùÅ systemd-journal-flush.service loaded failed failed Flush Journal to Persistent Storage

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
15 loaded units listed.
and noticed the 'nut-driver.service' and 'nut-server.service' as failed (in code section). Wondered if this had any impact on the other issues users have had with ups functioning.
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
User avatar
Gremlin
Gold Member
Posts: 1625
Joined: 02 Dec 2022, 22:31
Great Britain

Re: Resource Collection

Post by Gremlin »

I did another check (previous resulted in 'not found' as per OP)

Code: Select all

 systemctl status -l ResourceCollection.service
    ResourceCollection.service - ResourceCollection
     Loaded: loaded (/lib/systemd/system/ResourceCollection.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2024-11-21 08:31:26 GMT; 2h 7min ago
   Main PID: 2257 (ResourceCollect)
      Tasks: 13 (limit: 9172)
     Memory: 24.4M
        CPU: 1min 8.280s
     CGroup: /system.slice/ResourceCollection.service
                  Ç2006 vmtouch -P /var/run/rc-vmtouch.pid -ld /usr/bin/ec_stat /usr/sbin/smartctl
                  Ç2257 /usr/sbin/ResourceCollection

Nov 21 08:31:25 NAS-T1 systemd[1]: Starting ResourceCollection...
Nov 21 08:31:25 NAS-T1 systemd[1]: ResourceCollection.service: Found left-over process 2006 (vmtouch) in control group while starting unit. Ignoring.
Nov 21 08:31:25 NAS-T1 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Nov 21 08:31:26 NAS-T1 systemd[1]: ResourceCollection.service: Can't open PID file /run/ResourceCollection.pid (yet?) after start: Operation not permitted
Nov 21 08:31:26 NAS-T1 systemd[1]: Started ResourceCollection.
Have to say that, back in "my" day, "service implementation deficiencies" would not be allowed to go unchecked/fixed. :ugeek:
F5-221 TOS7.0.0777 - 4x4TB (Ironwolf) Traid
F2-424 TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (HGST) Traid
F2-221 TOS7.0.0777 - 1x3TB Ext4, 1x4TB Btrfs
F2-425+ TOS7.0.0777 - 2x500GB nvme (P3) Traid, 2x6TB HDD (EXOS) Traid
User avatar
FredMutter
Posts: 89
Joined: 17 Jan 2025, 20:11
France

Re: Resource Collection

Post by FredMutter »

I may have found something

journalctl|grep cron
Feb 14 12:12:19 TNAS cron[3272]: (CRON) INFO (pidfile fd = 3)
Feb 14 12:12:19 TNAS cron[3272]: (*system*) INSECURE MODE (group/other writable) (/etc/crontab)
Feb 14 12:12:19 TNAS cron[3272]: (CRON) INFO (Running @reboot jobs)
Feb 14 12:12:29 TNAS sysinit[3948]: /etc/tos/scripts/powertimer: line 114: /etc/cron: No such file or directory
Feb 14 12:13:02 TNAS cron[3272]: (*system*) INSECURE MODE (group/other writable) (/etc/crontab)

but I already wrote "etc/tos/scripts/powertimer: line 114" in one of my first posts
Model: F2-424 with TOS 7.0.0777 Bios V08
you can discuss with me in French, German and English
Locked

Return to “System Configuration”