In the case that in resource monitor, task manager, service a constant high writes per second are reported by syslog-ng you can use the following steps to troubleshoot and find the service responsible for the high writes per second reported for syslog-ng.
Access via SSH the NAS
turn on SSH at your own risk and login via the following instruction, click here.
Check the config files used by syslog-ng
cd/usr/local/etc/syslog-ng/patterndb.d
Run command for listing:
ll
Check the path logs
check every conf file and search for destination file
for example:
DNSServer.conf:/var/packages/DNSServer/target/named/var/log/SYNODNSLOGDB
Calendar.conf:/var/log/synocal.log
Note all destination locations
Check log file or check db file
- to check a log file for excessive activity
Run: sudo tail -f <file>
for example:
sudo tail -f /var/log/synocal.log
- to check a db file
Don’t use tail -f for a db file. Instead open the application and check the logging to this specific application.
for example for DNS:
/var/packages/DNSServer/target/named/var/log/SYNODNSLOGDB
Open DNS server and check the logging. If DNS server is responsible for the excessive writes change the log settings in this application.