dcruff Posted February 4 Share Posted February 4 I've been putting off posting this and have just reset the server a couple of times. Now I'm ready for some constructive ideas on how I can solve this. This server is only being used as an Emby Server and works wonderfully. Thanks everyone. embyserver-diagnostics-20240204-0720.zip Quote Link to comment
itimpi Posted February 4 Share Posted February 4 If you run the command du -h /var/log it might give a clue as to what is taking up the space. Quote Link to comment
dcruff Posted February 4 Author Share Posted February 4 I don't know what the actual available capacity is so I don't know if 109M is a problem. root@EmbyServer:~# du -h /var/log 0 /var/log/pwfail 0 /var/log/swtpm/libvirt/qemu 0 /var/log/swtpm/libvirt 0 /var/log/swtpm 0 /var/log/samba/cores/rpcd_winreg 0 /var/log/samba/cores/rpcd_classic 0 /var/log/samba/cores/rpcd_lsad 0 /var/log/samba/cores/samba-dcerpcd 0 /var/log/samba/cores/winbindd 0 /var/log/samba/cores/nmbd 0 /var/log/samba/cores/smbd 0 /var/log/samba/cores 640K /var/log/samba 0 /var/log/sa 0 /var/log/plugins 0 /var/log/pkgtools/removed_uninstall_scripts 0 /var/log/pkgtools/removed_scripts 4.0K /var/log/pkgtools/removed_packages 4.0K /var/log/pkgtools 48M /var/log/nginx 0 /var/log/nfsd 0 /var/log/libvirt/qemu 0 /var/log/libvirt/ch 0 /var/log/libvirt 109M /var/log Quote Link to comment
itimpi Posted February 4 Share Posted February 4 There is 48MB being used for nginx logs which is excessive. Maybe also worth running ls -l /var/log As it looks like there is a lot of space being used that is not in a sub-folder. Normally the space for logs is set to 128MB which is more than enough in normal use. Quote Link to comment
dcruff Posted February 4 Author Share Posted February 4 Do I need another command line switch to get deeper details? btmp cron debug dhcplog dmesg docker.log faillog lastlog libvirt/ maillog mcelog messages nfsd/ nginx/ packages@ pkgtools/ plugins/ pwfail/ removed_packages@ removed_scripts@ removed_uninstall_scripts@ sa/ samba/ scripts@ secure setup@ spooler swtpm/ syslog syslog.1 syslog.2 vfio-pci vfio-pci-errors wtmp Quote Link to comment
itimpi Posted February 4 Share Posted February 4 Does not look like you used the -l option as that should have shown more detail about each entry. Quote Link to comment
dcruff Posted February 4 Author Share Posted February 4 Sorry, I thought it was a 1. -rw------- 1 root root 0 Dec 1 12:44 btmp -rw-r--r-- 1 root root 0 Apr 28 2021 cron -rw-r--r-- 1 root root 0 Apr 28 2021 debug -rw-r--r-- 1 root root 515 Jan 29 17:36 dhcplog -rw-r--r-- 1 root root 62666 Jan 29 17:36 dmesg -rw-r--r-- 1 root root 1048 Jan 29 17:36 docker.log -rw-r--r-- 1 root root 0 Feb 13 2021 faillog -rw-r--r-- 1 root root 0 Apr 7 2000 lastlog drwxr-xr-x 4 root root 140 Jan 29 17:36 libvirt/ -rw-r--r-- 1 root root 0 Apr 28 2021 maillog -rw-r--r-- 1 root root 0 Jan 29 17:36 mcelog -rw-r--r-- 1 root root 0 Apr 28 2021 messages drwxr-xr-x 2 root root 40 Aug 10 2022 nfsd/ drwxr-x--- 2 nobody root 100 Feb 4 04:40 nginx/ lrwxrwxrwx 1 root root 24 Dec 1 12:43 packages -> ../lib/pkgtools/packages/ drwxr-xr-x 5 root root 100 Feb 4 07:17 pkgtools/ drwxr-xr-x 2 root root 280 Feb 4 07:17 plugins/ drwxr-xr-x 2 root root 40 Jan 29 17:36 pwfail/ lrwxrwxrwx 1 root root 25 Dec 1 12:45 removed_packages -> pkgtools/removed_packages/ lrwxrwxrwx 1 root root 24 Dec 1 12:45 removed_scripts -> pkgtools/removed_scripts/ lrwxrwxrwx 1 root root 34 Feb 4 07:17 removed_uninstall_scripts -> pkgtools/removed_uninstall_scripts/ drwxr-xr-x 2 root root 40 Jan 30 2023 sa/ drwxr-xr-x 3 root root 320 Jan 29 17:36 samba/ lrwxrwxrwx 1 root root 23 Dec 1 12:43 scripts -> ../lib/pkgtools/scripts/ -rw-r--r-- 1 root root 0 Apr 28 2021 secure lrwxrwxrwx 1 root root 21 Dec 1 12:43 setup -> ../lib/pkgtools/setup/ -rw-r--r-- 1 root root 0 Apr 28 2021 spooler drwxr-xr-x 3 root root 60 Sep 26 2022 swtpm/ -rw-r--r-- 1 root root 5012 Feb 4 15:43 syslog -rw-r--r-- 1 root root 1519616 Feb 3 04:30 syslog.1 -rw-r--r-- 1 root root 62058496 Feb 2 04:40 syslog.2 -rw-r--r-- 1 root root 0 Jan 29 17:36 vfio-pci -rw-r--r-- 1 root root 0 Jan 29 17:36 vfio-pci-errors -rw-rw-r-- 1 root utmp 6912 Jan 29 17:36 wtmp Quote Link to comment
dcruff Posted February 5 Author Share Posted February 5 So, how might I find out what is filling up my syslog.1 and syslog.2? Quote Link to comment
itimpi Posted February 5 Share Posted February 5 14 minutes ago, dcruff said: So, how might I find out what is filling up my syslog.1 and syslog.2? They are text files so can be opened and examined easily enough. Quote Link to comment
dcruff Posted February 5 Author Share Posted February 5 I'm still a neophyte on Unraid. Is there an app or pluggin or standard part of the graphics interface that will allow me to see inside the syslog files? Quote Link to comment
dcruff Posted February 9 Author Share Posted February 9 It's interesting - I refrained from re-booting my Unraid Server so that I could maintain the information that might aid me at finding a cause. I notice that on the Dashboard, under the System section (which shows active bar graphs of memory usage) it showed that I was over 90% on Log. It stayed there for several days. Now it is showing only about 21% utilization. I'm not sure how that might relate to the '/var/log' directory, but now my /var/log only shows that it has 26M. Quote Link to comment
itimpi Posted February 9 Share Posted February 9 On 2/5/2024 at 9:02 PM, dcruff said: Is there an app or pluggin or standard part of the graphics interface that will allow me to see inside the syslog files? There is an icon at top right of the GUI for looking at the contents of the current syslog which is in RAM. Quote Link to comment
dcruff Posted February 9 Author Share Posted February 9 Here's what I see - almost every line is an error. Feb 9 08:52:25 EmbyServer nginx: 2024/02/09 08:52:25 [error] 10584#10584: nchan: Out of shared memory while allocating message of size 13913. Increase nchan_max_reserved_memory. Feb 9 08:52:25 EmbyServer nginx: 2024/02/09 08:52:25 [error] 10584#10584: *7552400 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 9 08:52:25 EmbyServer nginx: 2024/02/09 08:52:25 [error] 10584#10584: MEMSTORE:01: can't create shared message for channel /disks Feb 9 08:52:26 EmbyServer nginx: 2024/02/09 08:52:26 [crit] 10584#10584: ngx_slab_alloc() failed: no memory Feb 9 08:52:26 EmbyServer nginx: 2024/02/09 08:52:26 [error] 10584#10584: shpool alloc failed Feb 9 08:52:26 EmbyServer nginx: 2024/02/09 08:52:26 [error] 10584#10584: nchan: Out of shared memory while allocating message of size 13913. Increase nchan_max_reserved_memory. Feb 9 08:52:26 EmbyServer nginx: 2024/02/09 08:52:26 [error] 10584#10584: *7552409 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 9 08:52:26 EmbyServer nginx: 2024/02/09 08:52:26 [error] 10584#10584: MEMSTORE:01: can't create shared message for channel /disks Feb 9 08:52:27 EmbyServer nginx: 2024/02/09 08:52:27 [crit] 10584#10584: ngx_slab_alloc() failed: no memory Feb 9 08:52:27 EmbyServer nginx: 2024/02/09 08:52:27 [error] 10584#10584: shpool alloc failed Feb 9 08:52:27 EmbyServer nginx: 2024/02/09 08:52:27 [error] 10584#10584: nchan: Out of shared memory while allocating message of size 13913. Increase nchan_max_reserved_memory. Feb 9 08:52:27 EmbyServer nginx: 2024/02/09 08:52:27 [error] 10584#10584: *7552420 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 9 08:52:27 EmbyServer nginx: 2024/02/09 08:52:27 [error] 10584#10584: MEMSTORE:01: can't create shared message for channel /disks Feb 9 08:52:30 EmbyServer nginx: 2024/02/09 08:52:30 [crit] 10584#10584: ngx_slab_alloc() failed: no memory Feb 9 08:52:30 EmbyServer nginx: 2024/02/09 08:52:30 [error] 10584#10584: shpool alloc failed Feb 9 08:52:30 EmbyServer nginx: 2024/02/09 08:52:30 [error] 10584#10584: nchan: Out of shared memory while allocating message of size 13913. Increase nchan_max_reserved_memory. Feb 9 08:52:30 EmbyServer nginx: 2024/02/09 08:52:30 [error] 10584#10584: *7552450 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 9 08:52:30 EmbyServer nginx: 2024/02/09 08:52:30 [error] 10584#10584: MEMSTORE:01: can't create shared message for channel /disks Feb 9 08:52:32 EmbyServer nginx: 2024/02/09 08:52:32 [crit] 10584#10584: ngx_slab_alloc() failed: no memory Feb 9 08:52:32 EmbyServer nginx: 2024/02/09 08:52:32 [error] 10584#10584: shpool alloc failed Feb 9 08:52:32 EmbyServer nginx: 2024/02/09 08:52:32 [error] 10584#10584: nchan: Out of shared memory while allocating message of size 13913. Increase nchan_max_reserved_memory. Feb 9 08:52:32 EmbyServer nginx: 2024/02/09 08:52:32 [error] 10584#10584: *7552475 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 9 08:52:32 EmbyServer nginx: 2024/02/09 08:52:32 [error] 10584#10584: MEMSTORE:01: can't create shared message for channel /disks Feb 9 08:52:34 EmbyServer nginx: 2024/02/09 08:52:34 [crit] 10584#10584: ngx_slab_alloc() failed: no memory Feb 9 08:52:34 EmbyServer nginx: 2024/02/09 08:52:34 [error] 10584#10584: shpool alloc failed Feb 9 08:52:34 EmbyServer nginx: 2024/02/09 08:52:34 [error] 10584#10584: nchan: Out of shared memory while allocating message of size 13913. Increase nchan_max_reserved_memory. Feb 9 08:52:34 EmbyServer nginx: 2024/02/09 08:52:34 [error] 10584#10584: *7552516 nchan: error publishing message (HTTP status code 500), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Feb 9 08:52:34 EmbyServer nginx: 2024/02/09 08:52:34 [error] 10584#10584: MEMSTORE:01: can't create shared message for channel /disks Feb 9 10:58:57 EmbyServer emhttpd: spinning down /dev/sdc Feb 9 11:10:44 EmbyServer emhttpd: read SMART /dev/sdc Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.