jang430 Posted April 30, 2020 Share Posted April 30, 2020 I executed the following commands. df -h /var/log du -sm /var/log/* It's my syslog.1 getting big. Contents of syslog.1 below: Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [crit] 7708#7708: ngx_slab_alloc() failed: no memory Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: shpool alloc failed Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: *477280 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [crit] 7708#7708: ngx_slab_alloc() failed: no memory Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: shpool alloc failed Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: *477281 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [crit] 7708#7708: ngx_slab_alloc() failed: no memory Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: shpool alloc failed Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [error] 7708#7708: nchan: Out of shared memory while allocating channel /var. Increase nchan_max_reserved_memory. Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [alert] 7708#7708: *477282 header already sent while keepalive, client: 192.168.1.148, server: 0.0.0.0:80 Apr 30 00:55:20 Tower kernel: nginx[7708]: segfault at 0 ip 0000000000000000 sp 00007ffd6a707898 error 14 in nginx[400000+21000] Apr 30 00:55:20 Tower kernel: Code: Bad RIP value. Apr 30 00:55:20 Tower nginx: 2020/04/30 00:55:20 [alert] 14983#14983: worker process 7708 exited on signal 11 Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [crit] 7893#7893: ngx_slab_alloc() failed: no memory Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: shpool alloc failed Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: *477285 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [crit] 7893#7893: ngx_slab_alloc() failed: no memory Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: shpool alloc failed Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: nchan: Out of shared memory while allocating channel /shares. Increase nchan_max_reserved_memory. Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: *477286 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/shares?buffer_length=1 HTTP/1.1", host: "localhost" Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [crit] 7893#7893: ngx_slab_alloc() failed: no memory Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: shpool alloc failed Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: *477287 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [crit] 7893#7893: ngx_slab_alloc() failed: no memory Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: shpool alloc failed Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [error] 7893#7893: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_memory. Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [alert] 7893#7893: *477288 header already sent while keepalive, client: 192.168.1.148, server: 0.0.0.0:80 Apr 30 00:55:21 Tower kernel: nginx[7893]: segfault at 0 ip 0000000000000000 sp 00007ffd6a707898 error 14 in nginx[400000+21000] Apr 30 00:55:21 Tower kernel: Code: Bad RIP value. Apr 30 00:55:21 Tower nginx: 2020/04/30 00:55:21 [alert] 14983#14983: worker process 7893 exited on signal 11 Apr 30 00:55:22 Tower nginx: 2020/04/30 00:55:22 [crit] 7905#7905: ngx_slab_alloc() failed: no memory Apr 30 00:55:22 Tower nginx: 2020/04/30 00:55:22 [error] 7905#7905: shpool alloc failed Apr 30 00:55:22 Tower nginx: 2020/04/30 00:55:22 [error] 7905#7905: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_memory. Apr 30 00:55:22 Tower nginx: 2020/04/30 00:55:22 [error] 7905#7905: *477289 nchan: error publishing message (HTTP status code 507), client: unix:, server: , request: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Any ideas? Quote Link to comment
JorgeB Posted April 30, 2020 Share Posted April 30, 2020 Syslog snippets are seldom enough, please post the complete diagnostics. Quote Link to comment
jang430 Posted May 1, 2020 Author Share Posted May 1, 2020 Maybe because my logs is full, I can't download the diagnostics. Or where can I download it manually? Another problem, I don't know whether related or not, whenever I click on Terminal on upper right, I get 'Connection Closed.' Using putty works though. Quote Link to comment
trurl Posted May 1, 2020 Share Posted May 1, 2020 16 hours ago, jang430 said: It's my syslog.1 getting big. syslog.1 isn't getting big because it has already rotated. It is as full as it's going to get. Since you are likely out of space you probably aren't even getting anything in the current syslog. Copy that syslog.1 from /var/log/syslog.1 to one of your user shares where you can get it from your PC, then reboot and get new diagnostics and post them along with the zipped syslog.1 Quote Link to comment
jang430 Posted May 1, 2020 Author Share Posted May 1, 2020 (edited) tower-diagnostics-20200501-1209.zip My logs are not anonymized. Will pm logs.zip password logs.zip Edited May 1, 2020 by jang430 Quote Link to comment
trurl Posted May 1, 2020 Share Posted May 1, 2020 Your syslog was being filled with these: Apr 29 07:13:20 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token Apr 29 07:13:26 Tower root: error: /plugins/preclear.disk/Preclear.php: wrong csrf_token which is explained in this FAQ: Quote Link to comment
jang430 Posted May 2, 2020 Author Share Posted May 2, 2020 OK. Thank you for pointing that out. Will take a look. Quote Link to comment
jang430 Posted June 5, 2020 Author Share Posted June 5, 2020 Hi. My logs still getting full. I was able to successfully download a copy of my diagnostics just now. Please help point out what's filling up my logs. tower-diagnostics-20200605-2103.zip Quote Link to comment
Squid Posted June 5, 2020 Share Posted June 5, 2020 You're being bombed by un 4 04:40:04 Tower kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s). Jun 4 04:40:04 Tower kernel: NVRM: This can occur when a driver such as: Jun 4 04:40:04 Tower kernel: NVRM: nouveau, rivafb, nvidiafb or rivatv Jun 4 04:40:04 Tower kernel: NVRM: was loaded and obtained ownership of the NVIDIA device(s). Jun 4 04:40:04 Tower kernel: NVRM: Try unloading the conflicting kernel module (and/or Jun 4 04:40:04 Tower kernel: NVRM: reconfigure your kernel without the conflicting Jun 4 04:40:04 Tower kernel: NVRM: driver(s)), then try loading the NVIDIA kernel module Jun 4 04:40:04 Tower kernel: NVRM: again. Best to ask about this in the support thread for the Unraid-nVidia plugin Quote Link to comment
jang430 Posted June 6, 2020 Author Share Posted June 6, 2020 (edited) Recently, my VM with GPU passed through GTX1080 experiencing slow performance. Frames dropping to 50 fps, but when I started, it was 100 fps. Everything the same. I just created a fresh new VM, with GPU passed through, experiencing the same results. Originally, Nvidia plugin was supposed to be used for my Handbrake, but I seldom use it. Can removing this plugin remove the error? Update: I just recalled, recently, while following an instruction on how to setup Gaming VM for use with Parsec, I did have to modify the boot parameters, and deleted some, to follow what's been instructed. I think that may have been the Unraid-Nvidia Plugin. Maybe that's the reason why the logs show that error. I've since removed the plugin from the flash drive, rebooted, and installed the Unraid-Nvidia plugin, and using that plugin, restored the original Unraid stock 6.8.3. Rebooted the NAS, and now, the gaming performance improved to 90-100 fps, near normal already. I'll need to walk back again to see if I've made other changes to Unraid. Thanks @Squid for pointing this out. Really helped a lot. Edited June 6, 2020 by jang430 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.