March 27, 201610 yr EDIT: I was thinking of just taking a copy of the changed file (with the suggested line commented out) and putting it on the flash drive and then in the GO file having a line to copy the version with the change over the one generated on every boot. Seems like there must be an easier way of doing this though. Any suggestions? Nope, that's how you would accomplish this. Only downside is that you have to remember to remove that line from the go file if/when you update unRaid versions (or the dynamix webUI) as the monitor script may change when you update. Thanks, I shall do this AND put a nice yellow post it note on the monitor to remind me! And it would appear that 6.2beta 20 already has that change in it: - dynamix: Get rid of SMART db update in monitor Ah, nice reference, thanks again. Nice to see that it is fixed. It will be some while before I put 6.2 on my Main or Backup Servers SO I will just run with this "Fix" for now until such a time as 6.2 FINAL is ready.
March 27, 201610 yr EDIT: I was thinking of just taking a copy of the changed file (with the suggested line commented out) and putting it on the flash drive and then in the GO file having a line to copy the version with the change over the one generated on every boot. Seems like there must be an easier way of doing this though. Any suggestions? Nope, that's how you would accomplish this. Only downside is that you have to remember to remove that line from the go file if/when you update unRaid versions (or the dynamix webUI) as the monitor script may change when you update. Thanks, I shall do this AND put a nice yellow post it note on the monitor to remind me! An alternate fix is to add a line to your go script to actually fix the update-smart-drivedb file rather than prevent it from running: https://lime-technology.com/forum/index.php?topic=47386.0
March 27, 201610 yr EDIT: I was thinking of just taking a copy of the changed file (with the suggested line commented out) and putting it on the flash drive and then in the GO file having a line to copy the version with the change over the one generated on every boot. Seems like there must be an easier way of doing this though. Any suggestions? Nope, that's how you would accomplish this. Only downside is that you have to remember to remove that line from the go file if/when you update unRaid versions (or the dynamix webUI) as the monitor script may change when you update. Thanks, I shall do this AND put a nice yellow post it note on the monitor to remind me! An alternate fix is to add a line to your go script to actually fix the update-smart-drivedb file rather than prevent it from running: https://lime-technology.com/forum/index.php?topic=47386.0 Thanks ljm42 BUT I prefer to disable it. Not that I mind being PM'd but to prevent more PM's - for those who want what I have done step by step - do this: - Drop to the CLI via telnet from the a Terminal Window (example via OS X below). Windows users, use PuTTY (where you enter the host details in the PuTTY GUI): http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html telnet -l root <name of your machine or IP address> Enter your password IF you have set one up. As an example you get something like this: daniels-imac:~ Daniel$ telnet -l root main Trying 192.168.1.2... Connected to main.danioj.lan. Escape character is '^]'. Linux 4.1.18-unRAID. Last login: Sun Mar 27 14:41:29 +1100 2016 on /dev/pts/0 from daniels-imac.danioj.lan. root@main:~# - Edit the monitor file nano /usr/local/emhttp/webGui/scripts/monitor Add // to the line: if (!file_exists($smartDB) || (time()-filemtime($smartDB)>=$interval)) exec('/usr/sbin/update-smart-drivedb 1>/dev/null 2>&1'); making it: // if (!file_exists($smartDB) || (time()-filemtime($smartDB)>=$interval)) exec('/usr/sbin/update-smart-drivedb 1>/dev/null 2>&1'); - Ctrl + X (to exit) and Y (to save changes and overwrite) - Copy the file you've just edited to the flash drive (so it is always available) cp /usr/local/emhttp/webGui/scripts/monitor /boot/monitor - Edit the Go File nano /boot/config/go - Paste the following into tour go file ** DO NOT OVERWRITE ANYTHING ** to ensure that the file now on the flash drive is copied to the right place when the unRAID system is loaded into memory # temp fix for the issue of a broken smartdb update UNTIL the next versison of 6.1.x unRAID has a fix in it or 6.2 STABLE is released (which will have this disabled) cp /boot/monitor /usr/local/emhttp/webGui/scripts/monitor - Ctrl + X (to exit) and Y (to save changes and overwrite) - Exit Telnet Thats it done. As Squid points out 2 posts above, you have to remember to remove that line from the go file if/when you update unRaid versions (or the dynamix webUI) as the monitor script may change when you update.
April 3, 201610 yr I have lowered the amount of SSL connections sabnzbd+ can make from 30 to 16 and the docker hasn't crashed since then. I had almost daily crashes of the sabnzbd+ docker, where it was impossible to restart the docker (unresponsive gui, proces that couldn't be killed) and where I end up killing every proces manually until there is no more disk activity, and then rebooting my server. Just to be sure I also implemented the temp fix mentioned here from danioj.
April 6, 201610 yr Ok, so it seems that there are two reported "fixes" here. One is the smartmon-tools fix that bonienl has brought up, and the other seems to be to lower the number of connections a container makes to a web application (such as sabnzbd or other similar containers). Can anyone confirm for me that the smartmon-tools fix doesn't require you to lower the number of connections your container makes?
April 7, 201610 yr Ok, so it seems that there are two reported "fixes" here. One is the smartmon-tools fix that bonienl has brought up, and the other seems to be to lower the number of connections a container makes to a web application (such as sabnzbd or other similar containers). Can anyone confirm for me that the smartmon-tools fix doesn't require you to lower the number of connections your container makes? Luckily I have a large transfer between me and a client going so I have increased the number of SSL connections back to max (70 in total maxing 25Mb/s external b/w) and for the past 2 hours nothing has become unstable. Will report back after 48 hours and - hopefully - no instability / crash.
April 21, 201610 yr Ok, so it seems that there are two reported "fixes" here. One is the smartmon-tools fix that bonienl has brought up, and the other seems to be to lower the number of connections a container makes to a web application (such as sabnzbd or other similar containers). Can anyone confirm for me that the smartmon-tools fix doesn't require you to lower the number of connections your container makes? Luckily I have a large transfer between me and a client going so I have increased the number of SSL connections back to max (70 in total maxing 25Mb/s external b/w) and for the past 2 hours nothing has become unstable. Will report back after 48 hours and - hopefully - no instability / crash. So what did you find out?!?
April 22, 201610 yr Ok, so it seems that there are two reported "fixes" here. One is the smartmon-tools fix that bonienl has brought up, and the other seems to be to lower the number of connections a container makes to a web application (such as sabnzbd or other similar containers). Can anyone confirm for me that the smartmon-tools fix doesn't require you to lower the number of connections your container makes? Luckily I have a large transfer between me and a client going so I have increased the number of SSL connections back to max (70 in total maxing 25Mb/s external b/w) and for the past 2 hours nothing has become unstable. Will report back after 48 hours and - hopefully - no instability / crash. So what did you find out?!? Sorry, I'm recovering from sickness, it is taking me longer to get to reply. Yes, I can confirm, upped the connections. No issue.
April 24, 201610 yr I've tried the smart-mon tools option and lowered the amount of incoming connections and I'm still having issues. Server has run great until the last few month's and now i'm having this issue constantly .
May 29, 201610 yr danioj, what version of unRAID were you using when experiencing these issues? Are you still experiencing them? And lastly (well almost), if you aren't experiencing them, can I assume you're still running under those modifications you made/listed? Now the rest last question. Since the problem was resolved by disconnecting/reconnecting your NIC. I have to wonder. Is it a NIC driver issue? Could it somehow be even remotely related to it? You have three unRAID's listed. I'm not sure which one these issues were on, so, if you wouldn't mind, sharing either the NIC or the Mobo (assuming you're using onboard NIC) model? I'd wonder too if we all (whom are experiencing similar issues) would benefit from sharing our Mobo/NIC models. I would love to start, but, I have to open up my box and currently I'm running an involuntary parity check (the 2nd in 25 hours), which requires "jolting" the system's case a bit more than I would like with a correcting parity check running (currently no errors but, would be my luck to have one at the most inopportune moment).
May 29, 201610 yr FWIW. I'm using the Intel I210-AT (LAN1) on my SuperMicro MBD-X10SLM-F-O danijo, if you were referring to your MBD-X10SL7-F-O ("Main") system, then it too utilizes the I210-AT Again, fwiw, in case it (NIC getting saturated?) has any bearing on any of this.
June 10, 201610 yr I've tried the smart-mon tools option and lowered the amount of incoming connections and I'm still having issues. Server has run great until the last few month's and now i'm having this issue constantly . Please see Need help? Read me first!, and start a new thread in General Support for v6, and remember to attach your diagnostics zip. Indicate which version of unRAID too.
June 10, 201610 yr The title of this thread is extremely broad, not specific to any one cause. Just a few posts back, it was remarked that there were 2 fixes found, for 2 different problems. Can we say that in the main the general problem is solved? There have been a few other posts, but it's hard to say whether they are related to the original problems, or are a general instability of a new or unknown cause. I'm very tempted to mark this thread as Solved, and ask that new posters start new threads with the symptoms that are *specific* to them.
June 19, 201610 yr Without further input, I'm marking this as solved. If you have problems that appear similar, please start a new thread.
Archived
This topic is now archived and is closed to further replies.