I had a look at the log directory using SSH:
[root@unnamedsrv log]# ls -l
total 488
drwxr-xr-x 2 root root 60 Jan 28 12:56 audit
-rw-r--r-- 1 root root 2084 Jan 31 06:16 auth.log
drwxr-xr-x 3 root root 60 Nov 26 02:34 cron
-rw-r--r-- 1 root root 143159 Jan 31 09:33 crond.log
-rw-r--r-- 1 root root 48287 Nov 26 02:34 dovecot-info.log
-rw-r--r-- 1 root root 16877 Nov 26 02:34 dovecot.log
drwxr-xr-x 2 root root 80 Nov 26 02:34 httpd
drwxr-xr-x 2 root root 40 Nov 26 02:34 inadyn
-rw-r--r-- 1 root root 220152 Jan 31 09:32 messages
-rw-r--r-- 1 root root 2028 Nov 26 02:34 minidlna.log
-rw-r--r-- 1 root root 444 Jan 28 12:57 mntdata.log
-rw-r--r-- 1 root root 2912 Jan 31 09:32 msgcenter_Tue_Jan_28_12_57_45_2020.log
-rw-r--r-- 1 root root 7453 Nov 26 02:34 mt-daapd.log
drwxr-xr-x 7 root root 180 Nov 26 02:34 nginx
drwxr-xr-x 2 root root 60 Nov 26 02:34 noip2
drwxr-xr-x 2 root root 60 Nov 26 02:34 phddns
drwxr-xr-x 2 root root 60 Jan 28 12:56 php-fpm
drwxr-xr-x 2 redis redis 60 Jan 28 12:57 redis
-rw-r--r-- 1 root root 29 Nov 26 02:34 resolv.conf
drwxr-xr-x 3 root root 100 Jan 28 12:57 samba
-rw-r--r-- 1 root root 4225 Jan 29 07:57 scripts.log
drwxr-xr-x 2 root root 40 Nov 26 02:34 session
-rw-r--r-- 1 root root 0 Nov 26 02:34 sshd
drwxr-xr-x 2 root root 120 Nov 26 02:34 subsys
-rw-r--r-- 1 root root 1389 Nov 26 02:34 upnp.xml
-rw-r--r-- 1 root root 23470 Jan 31 09:25 user.log
lrwxrwxrwx 1 root root 14 Jan 28 15:07 zlog -> /mnt/md1/@zlog
[root@unnamedsrv log]# cat messages
…
Jan 31 09:25:01 unnamedsrv TOS_STANDBY: Wake up now...
Jan 31 09:32:31 unnamedsrv smbd[4303]: [2020/01/31 09:32:31.592773, 0] ../source3/printing/print_standard.c:71(std_pcap_cache_reload)
Jan 31 09:32:31 unnamedsrv smbd[4303]: Unable to open printcap file /etc/printcap for read!
…
(This seems to happen constantly,Unable to open printcap file /etc/printcap for read!
To stop this the config file needs to be updated:
https://schmidi2itblog.wordpress.com/20 ... -for-read/
Can this be included in the next build of TOS?
SMB filling up messages log
SMB filling up messages log
Last edited by Scrums on 31 Jan 2020, 21:57, edited 1 time in total.
Re: SMB filling up messages log
I tried making this change myself to no avail
Re: SMB filling up messages log
Hmm, this is probably why my SMB logs take so long to load in TOS, causing high CPU usage for a while (viewtopic.php?f=71&t=57)
- mathygreen
- Posts: 2
- Joined: 23 Dec 2020, 05:48
Re: SMB filling up messages log
i have the same problem
OPM load in seconds.... the problem is that after it loads SMB/CIFS takes too long to come up.
how can i solve this...
OPM load in seconds.... the problem is that after it loads SMB/CIFS takes too long to come up.
how can i solve this...
Re: SMB filling up messages log
How long does it take you to start SMB service? Could you please provide the TNAS, hard disk model and TOS version?
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)
Technical team: support(at)terra-master.com (for technical support)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
- mathygreen
- Posts: 2
- Joined: 23 Dec 2020, 05:48
Re: SMB filling up messages log
TerraMaster U4-211
hard disk 1 terabyte and TOS 4.0
hard disk 1 terabyte and TOS 4.0
Re: SMB filling up messages log
Will fix it in future release.
To contact our team, please send email to following addresses, remember to replace (at) with @:
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)
Support team: support(at)terra-master.com (for technical support only)
Service team: service(at)terra-master.com (for purchasing, return, replacement, RMA service)