TOSDaemon filling up /tmp

[thewieger]

Running TOS 6.0.794 on a F2-425. My docker containers are failing health checks because /tmp is full. Looking into /tmp, the biggest file is metricsd.db, which is opened by TOSDaemon. What is the best way to keep TOSDaemon structurally (so not restarting the NAS on a regular schedule) from filling up metricsd.db to the limits of /tmp?

NAS-admin@DE-WOLK:/# du -a /tmp | sort -n -r | head -n 10
524288 /tmp
381820 /tmp/metricsd.db
138236 /tmp/databack
69112 /tmp/databack/TNAS_TNAS-F2-425_config_backup.tar
69112 /tmp/databack/TNAS_TNAS-F2-425_config_backup.bin
4120 /tmp/log
988 /tmp/log/TOSDaemon.log
864 /tmp/log/samba
744 /tmp/log/samba/log.smbrichacl
584 /tmp/log/user.log
NAS-admin@DE-WOLK:/# lsof /tmp/metricsd.db
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
TOSDaemon 11108 NAS-admin 12r REG 0,28 390983680 140 /tmp/metricsd.db
TOSDaemon 11108 NAS-admin 16u REG 0,28 390983680 140 /tmp/metricsd.db
NAS-admin@DE-WOLK:/# lsof /tmp/databack/TNAS_TNAS-F2-425_config_backup.bin
NAS-admin@DE-WOLK:/#

[CursaYang]

This database is used to store the overview data on the right side of the TOS desktop, and under normal circumstances, it should not be writing this much data. We need to check this issue remotely, so please find the online customer service option in the bottom right corner of the official website to schedule a remote session.

[thewieger]

Thanks, will schedule a session soon!