Fix common problems recently started showing this error.

 

I've included the diagnostics zip.

 

Restarting didn't solve the issue.

 

Thank your for your help ! 

tower-diagnostics-20200829-1753.zip

Log files aren't all that large.

 

What do you get from the command line with this?

du -h /var/log

 

0       /var/log/swtpm/libvirt/qemu
0       /var/log/swtpm/libvirt
0       /var/log/swtpm
0       /var/log/samba/cores/winbindd
0       /var/log/samba/cores/nmbd
0       /var/log/samba/cores/smbd
0       /var/log/samba/cores
12K     /var/log/samba
0       /var/log/plugins
4.0K    /var/log/pkgtools/removed_scripts
128K    /var/log/pkgtools/removed_packages
132K    /var/log/pkgtools
0       /var/log/nvidia/64
0       /var/log/nvidia/32
0       /var/log/nvidia
4.0K    /var/log/nginx
0       /var/log/nfsd
52K     /var/log/libvirt/qemu
60K     /var/log/libvirt
126M    /var/log

And what do you get with this?

ls -lah /var/log

 

total 126M
drwxr-xr-x 10 root   root  680 Aug 23 04:40 ./
drwxr-xr-x 14 root   root  320 Aug  8 13:07 ../
-rw-r--r--  1 root   root   85 Aug 23 04:40 apcupsd.events
-rw-r--r--  1 root   root  299 Aug 23 04:40 apcupsd.events.1
-rw-r--r--  1 root   root  299 Aug 16 04:40 apcupsd.events.2
-rw-------  1 root   root    0 Mar  8 21:06 btmp
-rw-r--r--  1 root   root    0 Mar  8 21:06 cron
-rw-r--r--  1 root   root    0 Mar  8 21:06 debug
-rw-rw-rw-  1 root   root  58K Aug  8 13:07 dmesg
-rw-rw-rw-  1 root   root    0 Aug  8 13:08 docker.log
-rw-r--r--  1 root   root    0 Mar  8 21:06 faillog
-rw-r--r--  1 root   root  292 Aug 29 18:14 lastlog
drwxr-xr-x  3 root   root  120 Aug  8 13:08 libvirt/
-rw-r--r--  1 root   root    0 Mar  8 21:06 maillog
-rw-r--r--  1 root   root    0 Mar  8 21:06 messages
drwxr-xr-x  2 root   root   40 Mar  8 21:06 nfsd/
drwxr-x---  2 nobody root   60 Aug  8 13:08 nginx/
drwxr-xr-x  4 root   root   80 Mar  8 21:06 nvidia/
-rw-r--r--  1 root   root 157K Aug 29 17:37 nvidia-container-runtime-hook.log
-rw-r--r--  1 root   root 3.3K Mar  8 20:45 nvidia-installer.log
lrwxrwxrwx  1 root   root   24 Mar  8 21:05 packages -> ../lib/pkgtools/packages/
drwxr-xr-x  4 root   root   80 Mar  8 21:05 pkgtools/
drwxr-xr-x  2 root   root  420 Aug 16 01:00 plugins/
lrwxrwxrwx  1 root   root   25 Mar  8 21:06 removed_packages -> pkgtools/removed_packages/
lrwxrwxrwx  1 root   root   24 Mar  8 21:06 removed_scripts -> pkgtools/removed_scripts/
drwxr-xr-x  3 root   root  180 Aug  8 13:11 samba/
lrwxrwxrwx  1 root   root   23 Mar  8 21:05 scripts -> ../lib/pkgtools/scripts/
-rw-r--r--  1 root   root    0 Mar  8 21:06 secure
lrwxrwxrwx  1 root   root   21 Mar  8 21:05 setup -> ../lib/pkgtools/setup/
-rw-r--r--  1 root   root    0 Mar  8 21:06 spooler
drwxr-xr-x  3 root   root   60 Mar  8 21:06 swtpm/
-rw-r--r--  1 root   root 1.2M Aug 29 18:14 syslog
-rw-r--r--  1 root   root 125M Aug 10 03:03 syslog.1
-rw-rw-r--  1 root   utmp 8.3K Aug 29 18:14 wtmp

I forgot to mention another issue that shows sometimes in Fix common problems: a share that was previously cached but no longer is sometimes has files on the cache.

1 minute ago, Hamilcar said:

-rw-r--r--  1 root   root 125M Aug 10 03:03 syslog.1

The diagnostics you posted only had 2MB for this. Did you edit your diagnostics?

1 minute ago, trurl said:

The diagnostics you posted only had 2MB for this. Did you edit your diagnostics?

Nope didn't touch it.

Looks like you filled cache and then log was filling with move errors.

 

You have a user share anonymized as n-------d set to cache-prefer. Prefer means try to keep all of that share on cache. Possibly this is the reason you filled cache. What is the purpose of this user share?

 

Normally, only appdata, domains, system shares would be set cache-prefer. Your appdata has some files on disk2, maybe because there wasn't room on cache.

that share contains nextcloud synced files.

Edited August 29, 20205 yr by Hamilcar

Why do you have it set to stay on cache?

I've set it to no, I don't really remember why it was set to prefer, seems overkill.

Mover ignores cache-no user shares. You must set it to cache-yes to get it moved to the array.

Got it, so was that the issue ?

A full cache seems to be the likely cause of your logs filling.

 

You will have to reboot to clear the logs.

 

Then set your nextcloud share to cache-yes and run mover. After it completes there are some other things you will need to do to get the rest of appdata moved to cache since mover can't move open files. So post new diagnostics after you get nextcloud share moved.

Alright everything seems to be fixed after a reboot, setting the share to cache-yes and running the mover.

 

Log has emptied, also appdata is now only on cache.

 

thank you for your help