Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

/var/log reported as full...very little there

Featured Replies

Morning folks.  the Fix Common Problems tool is reporting that my /var/log folder is 100% full.  I've increased it's size in my go file to:

 

# Enlarge the LOG partition (because Dynamix System Stats needs at least 186Mb, default LOG is 128Mb)
mount -o remount,size=512m /var/log

 

and have rebooted the system.  The contents of the folder, though, 1) haven't updated in quite some time, 2) there's not much in there:

 

image.thumb.png.ea30d0ed5c24cb780fa59b70e441a6cc.png

 

image.thumb.png.d476334c22c6f50a666d13d7f25073ff.png

 

I've attached my diagnostics as well.

 

Any ideas?

mediaserver2-diagnostics-20181221-0844.zip

12 minutes ago, JasonK said:

because Dynamix System Stats needs at least 186Mb

Not applicable anymore. Changed a long time ago and dynamix system stats stores the information files in a different location.

What is the output of

df
Filesystem         1K-blocks        Used   Available Use% Mounted on
rootfs              65832552      833328    64999224   2% /
tmpfs                  32768         368       32400   2% /run
devtmpfs            65906112           0    65906112   0% /dev
tmpfs               65986988           0    65986988   0% /dev/shm
cgroup_root             8192           0        8192   0% /sys/fs/cgroup
tmpfs                 262144        1564      260580   1% /var/log
/dev/sda1           15170560     2221744    12948816  15% /boot

 

  • Author

Yeah - I had copy/pasted the comment from an older thread previously about increasing the size.

 

here's the df output:

 

image.png.aa4e8c35a79a9b864185a623f066ca76.png

Well, Fix Common Problems isn't lying. Your /var/log is 100% used.

Try this

# ls -lsa /var/log
total 1116
  0 drwxr-xr-x  9 root   root    540 Dec  3 18:44 .
  0 drwxr-xr-x 14 root   root    320 Dec  3 18:44 ..
  0 -rw-------  1 root   root      0 Dec  1 20:35 btmp
  0 -rw-r--r--  1 root   root      0 Jun 28 04:22 cron
  0 -rw-r--r--  1 root   root      0 Jun 28 04:22 debug
 96 -rw-rw-rw-  1 root   root  95418 Dec  3 18:44 dmesg
 60 -rw-rw-rw-  1 root   root  57382 Dec 21 13:01 docker.log
  4 -rw-r--r--  1 root   root   1920 Dec 21 12:23 faillog
  8 -rw-r--r--  1 root   root  17520 Dec 21 12:23 lastlog

 

  • Author
# ls -lsa /var/log
total 524260
     0 drwxr-xr-x  9 root   root       620 Dec 21 10:49 ./
     0 drwxr-xr-x 13 root   root       300 Dec  1 13:37 ../
     0 -rw-------  1 root   root         0 Dec  1 13:35 btmp
     0 -rw-r--r--  1 root   root         0 Jun 27 21:22 cron
     0 -rw-r--r--  1 root   root         0 Jun 27 21:22 debug
     8 -rw-rw-rw-  1 root   root      4776 Dec 20 08:47 diskinfo.log
    96 -rw-rw-rw-  1 root   root     98234 Dec 20 08:46 dmesg
     8 -rw-rw-rw-  1 root   root      6875 Dec 21 08:46 docker.log
     4 -rw-r--r--  1 root   root      1920 Dec 21 10:49 faillog
  1116 -rw-rw-rw-  1 root   root   1142784 Dec 21 10:49 file.activity.log
     4 -rw-r--r--  1 root   root     17520 Dec 21 10:49 lastlog
     0 drwxr-xr-x  3 root   root       120 Dec 20 08:48 libvirt/
     0 -rw-r--r--  1 root   root         0 Jun 27 21:22 maillog
     0 -rw-r--r--  1 root   root         0 Jun 27 21:22 messages
     0 drwxr-xr-x  2 root   root        40 May 15  2001 nfsd/
     0 drwxr-x---  2 nobody root        60 Dec 20 08:46 nginx/
     0 lrwxrwxrwx  1 root   root        24 Dec  1 13:35 packages -> ../lib/pkgtools/packages/
     0 drwxr-xr-x  4 root   root        80 Jun 19  2018 pkgtools/
     0 drwxr-xr-x  2 root   root       460 Dec 21 08:48 plugins/
     0 -rw-rw-rw-  1 root   root         0 Dec 20 08:46 preclear.disk.log
     0 lrwxrwxrwx  1 root   root        25 Dec  1 13:36 removed_packages -> pkgtools/removed_packages/
     0 lrwxrwxrwx  1 root   root        24 Dec  1 13:36 removed_scripts -> pkgtools/removed_scripts/
     0 drwxr-xr-x  3 root   root       160 Dec 20 08:46 samba/
     0 lrwxrwxrwx  1 root   root        23 Dec  1 13:35 scripts -> ../lib/pkgtools/scripts/
     0 -rw-r--r--  1 root   root         0 Jun 27 21:22 secure
     0 lrwxrwxrwx  1 root   root        21 Dec  1 13:35 setup -> ../lib/pkgtools/setup/
     0 -rw-r--r--  1 root   root         0 Jun 27 21:22 spooler
     0 drwxr-xr-x  3 root   root        60 Oct 16 22:19 swtpm/
     0 -rw-r--r--  1 root   root         0 Dec 21 10:49 syslog
523016 -rw-r--r--  1 root   root 535568384 Dec 21 04:40 syslog.1
     8 -rw-rw-r--  1 root   utmp      7680 Dec 21 10:49 wtmp

 

  • Author

Looks like syslog is somehow getting filled up.

 

Jason

  • Author

Looking at the end of the log file, tons of these:

 

Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
Dec 21 00:22:24 MEDIASERVER2 kernel: i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!

 

  • Community Expert

Seems to have something to do with sensors. Remove system temp plugin and reboot.

  • Author
1 hour ago, trurl said:

Seems to have something to do with sensors. Remove system temp plugin and reboot.

Thanks.  Have removed it and rebooted.  We'll see how it goes.

 

J

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.