Jump to content

[Solved] Help! - Parity check started - unable to connect via web gui


Recommended Posts

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

Link to comment

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?

Link to comment

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.

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...