hamish_18

I too have the same thing. Randomly just reboots, nothing in the logs that pertains to any issue. @john014, did you ever figure out what was causing this? The last log entry for me is: Mar 4 03:49:46 UnRaid emhttpd: read SMART /dev/sdo And the next is after I powered it back up, and the system was starting. It has done this for quite sometime, and it is super annoying. Is there any sort of additional debugging we could enable?

Just following up, that I am again running in to where the server will lock up during the night at some point. I am a bit surprised that I have not had any responses? Did I stump everybody??

when you edit the docker, click the advanced switch in the upper right. Then when you edit the docker, click the advanced view switch in the upper right. Next, you paste that line above in to the Extra Parameters spot: Click Apply, and you won't see the error any longer. I found this thread just now as I too noticed the error when looking at logs, and tried this, and it works. Cheers!

Thanks for this! Fixed me up as well.

Greetings, I was trying to use plex this morning, and it wouldn't load. I checked unraid, and it was very sluggish, and one of my cores was pegged at 100%. Which is very unusual. I checked the system log, and found numerous entries such as this: Aug 31 07:08:01 UnRaid kernel: Call Trace: Aug 31 07:08:01 UnRaid kernel: __schedule+0x45e/0x4a4 Aug 31 07:08:01 UnRaid kernel: schedule+0x73/0x99 Aug 31 07:08:01 UnRaid kernel: schedule_timeout+0xa7/0xe0 Aug 31 07:08:01 UnRaid kernel: ? __next_timer_interrupt+0xe8/0xe8 Aug 31 07:08:01 UnRaid kernel: rcu_gp_kthread+0x417/0x7a9 Aug 31 07:08:01 UnRaid kernel: ? kfree_rcu_work+0x19e/0x19e Aug 31 07:08:01 UnRaid kernel: kthread+0xe5/0xea Aug 31 07:08:01 UnRaid kernel: ? __kthread_bind_mask+0x57/0x57 Aug 31 07:08:01 UnRaid kernel: ret_from_fork+0x22/0x30 Aug 31 07:09:01 UnRaid kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: Aug 31 07:09:01 UnRaid kernel: rcu: 10-...!: (0 ticks this GP) idle=f4c/0/0x0 softirq=58410444/58410444 fqs=2 (false positive?) Aug 31 07:09:01 UnRaid kernel: (detected by 22, t=60002 jiffies, g=143930057, q=204228) Aug 31 07:09:01 UnRaid kernel: Sending NMI from CPU 22 to CPUs 10: Aug 31 07:09:01 UnRaid kernel: NMI backtrace for cpu 10 skipped: idling at acpi_idle_do_entry+0x31/0x37 Aug 31 07:09:01 UnRaid kernel: rcu: rcu_sched kthread starved for 60003 jiffies! g143930057 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=10 Aug 31 07:09:01 UnRaid kernel: rcu: Unless rcu_sched kthread gets sufficient CPU time, OOM is now expected behavior. Aug 31 07:09:01 UnRaid kernel: rcu: RCU grace-period kthread stack dump: Aug 31 07:09:01 UnRaid kernel: task:rcu_sched state:I stack: 0 pid: 10 ppid: 2 flags:0x00004000 I don't know linux good enough to determine what the cause of this could be? I tried to kill the vm that is pinned to cpu 10/22(which is it's physical and logical core) and that did not help. It actually made things worse. I ended up having to hard reset the box. I've also have come in to work in the morning and plex was down. And checking unraid, the whole box was unresponsive. syslog never showed me anything out of the ordinary. the last few lines were just things like a drive spinning down, or the fans spinning up or down due to drive temps. I think I may have been running in to this issue for a few weeks now, and only now was able to see it happening in real time to see better data? I can grab splunk logs if that would help as I am willing to bet the diagnostic zip won't have this data in it, as I had to reboot to get back in to unraid. I was unable to pull logs prior as the ui was basically unresponsive.. Any help would be greatly appreciated here! Thanks!!! unraid-diagnostics-20210831-0808.zip

Found this thread from searching for the same thing. It'd be super nice to be able to track when a user accesses a share. in troubleshooting another issue, I was trying to determine whether a firewall rule was working correctly or not, and wanted to track on both sides. This was for blocking smb. I know it's not working as I obviously can't access the share from the local machine, but wanted to see if there was an attempt at all on unraid.

YAY! thank you!! Will be very nice for diagnostics.

I too would like to see an option in the gui for syslog forwarding.

I think all I needed was to start this thread. I have pretty much everything the way I want it now. for the first time too I now saw my parity drive even spin down lol. Plex is running from the cache drive, and everything survived the array going down, reboots, etc.. Thanks for the quick responses! I think this can now be closed. And Johnnie.black. Thanks for the note, I will take care of libvirt. I plan on re-doing my whole vm setup once I get another ssd put in. I'll just have all the stuff like vm's appdata on my current cache ssd, and then use the new ssd as the sole cache drive. or however the best way to set it up will be. Haven't really looked in to that quite yet. Thanks again!!!

interesting. I totally read that wrong. I read prefer as it will use the cache until full and then the data will just go to the array. So if I am copying over more than what my cache drive's total size is before the mover script runs, then the data will start being written to the array. Will setting that setting to yes perform in this manner? I did just change it and transferred some data to the share, and it's being written to the cache drive like it's supposed to! the real test is whether the mover will work. Thanks for the help so far. Hopefully this was all that was wrong.. Will report back after a couple more tests.

Here is another issue. Why would that be touched? It's been on my array for a long time. since.. well 2014. haha. It's like I have some setting and everything is trying to go to the cache drive? on my cache drive I see a bunch of movie folders. When there should only be new data on the cache drive, getting ready to be moved to the array with the mover script. It's almost like the data is going in the wrong direction? If that makes sense?

Hi All, First I would like to apologize. I have searched and searched, and I am just at a loss as to what is going on. For quite some time I have not had any issues with my unraid setup. I use a cache drive and the mover worked fine. After a number of months, something happened, and the mover stopped working. I had to move everything manually. From then on nothing would copy to cache drive. I ended up turning off using the cache drive for a while. I recently re-enabled it through the global share settings. The drive filled up, and I am having the same issue again. I have adjusted min free space for my movie share, and maybe a couple other things that I can't think of. Mover is stuck running now. I can't stop the array, kill mover, and now get plex to work due to the cache drive being full I presume. I don't know what else to check. I am at a loss and need your help. If I need to rebuild the system I am willing to as long as I don't lose any data. I can pull docker off the cache drive, and format the cache drive, whatever I need to do. I have attached current logs, hopefully they will prove to be useful. Thanks! unraid-diagnostics-20170809-1342.zip

HOLY CRAP!!! so I shut it down, instead of just a restart.. Since I was going to pull the flash drive out. well I thought hmm I wonder if a cold boot will work. and BOOM I am in the webgui.. So weird that a shutdown was needed.. What the heck could persist? something in RAM? I guess? At any rate. I will monitor it for a few days, and if the issue returns I will post back. Well I will post back either way. I hate leaving threads open. Thanks for the basically immediate response!!! This was my first time posting to the forums. I have been an unraid user for a over a year now. Great support. Great forum! THanks!

yes I changed the startup for Docker to no. can I confirm that it's not running somehow?

okay so I thought I found how to kill the ftp daemon but it's still there. I commented the ftp line from inetd.conf, and did this: sed -i "s/^ftp/#ftp/" /etc/inetd.conf killall -s HUP inetd to the go script. restarted, and the entry is still showing in the syslog: May 13 17:22:06 UnRaid vsftpd[22701]: connect from 127.0.0.1 (127.0.0.1) not sure what else to do. also still no webgui I think I will shut the box down and check the flash drive for corruption.. I haven't touched this box for weeks. not sure how anything could have happened

there was no vsftp.user_list. I have no idea what that is. I have set it to no and restarted the box. no dice. Here is all the log has from the reboot: May 13 17:05:26 UnRaid shutdown[19909]: shutting down for system reboot May 13 17:05:26 UnRaid vsftpd[19913]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:01 UnRaid vsftpd[20031]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:02 UnRaid vsftpd[20036]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:04 UnRaid vsftpd[20043]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:07 UnRaid vsftpd[20052]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:11 UnRaid vsftpd[20064]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:16 UnRaid vsftpd[20077]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:22 UnRaid vsftpd[20092]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:29 UnRaid vsftpd[20110]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:37 UnRaid vsftpd[20129]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:46 UnRaid vsftpd[20150]: connect from 127.0.0.1 (127.0.0.1) May 13 17:06:56 UnRaid vsftpd[20174]: connect from 127.0.0.1 (127.0.0.1) May 13 17:07:06 UnRaid vsftpd[20200]: connect from 127.0.0.1 (127.0.0.1) May 13 17:07:16 UnRaid vsftpd[20224]: connect from 127.0.0.1 (127.0.0.1) May 13 17:07:26 UnRaid vsftpd[20250]: connect from 127.0.0.1 (127.0.0.1) May 13 17:07:33 UnRaid in.telnetd[20267]: connect from 192.168.1.10 (192.168.1.10) May 13 17:07:36 UnRaid vsftpd[20275]: connect from 127.0.0.1 (127.0.0.1) May 13 17:07:41 UnRaid login[20268]: ROOT LOGIN on '/dev/pts/4' from 'haymak3r' May 13 17:07:46 UnRaid vsftpd[20306]: connect from 127.0.0.1 (127.0.0.1) May 13 17:07:56 UnRaid vsftpd[20330]: connect from 127.0.0.1 (127.0.0.1)

Im home now. performing those steps, and will report back.

oh ya I have unraid version 6.1.9.. I have Emby and Plex docker apps, and the preclear plugin. Cheers!

Hi All, I have been searching and searching for a couple hours now to try and figure out what is going on. I was in the webgui because plex stopped responding. I restarted the plugin, and that was it. webgui went away. I have restarted the box a couple times, and checked logs. I can telnet in just fine. Just can't connect to the webgui anymore. I am seeing the segmentation fault error that others have seen in past builds. unraid segfault at 0 ip 00002b6f6a87a527 sp 00007ffc2a985200 error 4 in libc-2.17.so[2b6f6a83f000+1bf000] I can't access anything on the box, so I am trying to figure out how to get the syslog up for you guys... I have a putty output log. This is the best I can do remotely while I am at work. I really need this up and running!! It's the weekend! Hopefully there is something that I can do other than redoing unraid entirely. putty.zip