I am running version 5-rc5. A few minutes ago, I started a parity check. Normally, when I do this the web interface changes to show the progression of the parity check. However, this time the web page is blank. I was able connect to the server via telnet, and was able to generate a smart report for one of the drives, however no syslog is available. Also, I can connect to files on the server via the windows network, although it is somewhat slow to respond. I would appreciate some guidance as to how to proceed.

Cheers

I found this thread - http://lime-technology.com/forum/index.php?topic=19561.0 - which suggested restarting the web gui through telnet using:

killall emhttp

nohup /usr/local/sbin/emhttp &

 

After running this and attempting to access the web gui, I get a page that says "Unable to connect - Firefox can't establish a connection to the server at media."

I finally powered down the system by holding down the power button and then powered it on again. I am still not able to access the gui. I expect that it started a parity check upon restarting. What do I do?

As a last resort, I cleared the flash drive and reloaded my backup of the v5.0-rc4 files. I restarted the server and the webgui appeared, thankfully without starting a parity check. I'm going to bed and shall investigate further in the morning.

If it happens again with the new install, I suggest telneting into the server and getting a syslog. Don't think anyone can help you without that.

 

http://lime-technology.com/wiki/index.php/Troubleshooting

I had a similar experience with a parity check and emhttp hanging (with SimpleFeatures with cache_dir, apcupsd, powerdown, stats, disk health, email notify, active streams, system info, and activity monitor plugins installed)

 

Other than a syslog, there isn't much to do except reboot. I used to have some success with the killall emhttp command on 4.7, but can only get a segfault (which Tom mentions will happen)

http://lime-technology.com/forum/index.php?topic=13187.msg182915#msg182915

 

http://lime-technology.com/forum/index.php?topic=19560.msg188745#msg188745

 

I don't know under which conditions, other than heavy I/O that will cause emhttp to hang. I don't believe it is directly related to 5RC, as I have had it happen on 4.7..  It does come back eventually.  One of the items that is on Tom's roadmap for..v5.1?

Thanks for your responses.

 

As I mentioned in my first post, I was able to telnet into the server, but it would not generate a syslog.

Thanks for your responses.

 

As I mentioned in my first post, I was able to telnet into the server, but it would not generate a syslog.

 

After connecting via telnet what is the output of:

cat /var/log/syslog

Thanks for the suggestion dgaschk. I have attached the output of "cat /var/log/syslog.

syslog.txt

Thanks for the suggestion dgaschk. I have attached the output of "cat /var/log/syslog.

 

Need to see the entire log. See here: http://lime-technology.com/forum/index.php?topic=9880.0

When I typed in "cat /var/log/syslog" into telnet I copied everything that was generated into the text document that was attached. There was nothing else to copy.

You are using the mvsas driver and getting the BLK_EH_NOT_HANDLED

 

http://lime-technology.com/forum/index.php?topic=21377.msg189883.msg#189883

Sent from my SAMSUNG-SGH-I897 using Tapatalk 2

 

You can stop an in process parity check by typing "mdcmd nocheck" in the terminal. Does that bring the web gui back after ending the parity check?

Thanks mbryanr for the link. I have reverted the server back to v5.0 beta 14 and so far so good.

Thanks mbryanr for the link. I have reverted the server back to v5.0 beta 14 and so far so good.

 

You don't need to revert to beta 14, the link he provided was for the current version that solves the mvsas driver issue.