Web interface becomes inaccessible (503 Server temporarily overloaded)

I’m using a 1tb MBWE white light, and I’ve found that the web interface is becoming inaccessible, and it gives me the following error message:

UNKNOWN 503 Server temporarily overloadedDate: Wed, 10 Feb 2010 06:47:24 GMTCache-Control: no-cache,no-storeContent-Type: text/html; charset=%sConnection: close<html><head><title>503 Server temporarily overloaded</title></head><body><h3>503 Server temporarily overloaded</h3>The server cannot process the request due to a high load</body></html>

It’s just as above, with HTML tags showing and such.  I’ve tried stopping any network or disk activity, but I still get the error message.  I can’t reboot, since I obviously can’t reach the admin interface, so the only thing that brings it back to normal is shutting it down manually (via the power switch), then booting it back up.

Anyone seen this, or have any clues as to how to keep it from happening, or resolve it when it does happen?

Edit:  oops, I should have also mentioned:  the disk itself is still accessible during this time - it’s only the web interface that goes out.

Do you have SSH acitvated? So login via SSH (take Putty for login)

user: root

pw: welc0me (The 0 is not an O, its the number 0)

Then type “top” (without “”) and look if the HTTP Service (imho mini_http) really have a high CPU useage (service in 1st line uses the most). With SSH you can also shutdown “poweroff” or reboot “reboot”.

Hi, this happened to me today also, I can’t access SSH at this point, but I’ll do so when I get home. Anyone has any ideea on why this happends?

D-u-d-e wrote:

Do you have SSH acitvated? So login via SSH (take Putty for login)

 

user: root

pw: welc0me (The 0 is not an O, its the number 0)

 

Then type “top” (without “”) and look if the HTTP Service (imho mini_http) really have a high CPU useage (service in 1st line uses the most). With SSH you can also shutdown “poweroff” or reboot “reboot”.

Thanks, I’m going to try this, and see if it works.  I need to try to replicate the problem first…

andrei_ wrote:

Hi, this happened to me today also, I can’t access SSH at this point, but I’ll do so when I get home. Anyone has any ideea on why this happends?

I’m not sure, but I’m going to try to replicate it.  If I can figure anything out, I’ll update the post.

I realize it has been 3 weeks, but I just got this same message, and I think I might have an idea why.

About a week ago we installed this unit, and I set it up to re-format to RAID1.

I left the “status” window that automatically updates itself periodically open for the last week or week and a half.

When I checked on it today (haven’t looked at it for at least a week), the HTML was VERY mal-formed, and I got that error any time I tried to go to a settings page.

Bug in the http server’s code?

same problem for me.

type “top” in the shell and the 3 top voices are ctorrent, using the cpu a lot.

how i can stop them? the web interface is locked and i dont’ know how to reeboot.

Then:

powered down with the button and then power up again.

logged with putty and seen that ctorrent was still eating cpu but then the web server was working so i turn it off from the web interface.

after 1 week of test i can say that the web interfce is really slow and sometimes doesntt show images or even css.

I have the same problem: 3 cTorrent processes are using all the free and non-free cpu-speed, so even the webserver is not able to work correctly. Is there any solution, that cTorrent does not use all of the cpu-speed? Perhabs working with priorities? And a last question: Why does 1 cTorrent torrent use so much cpu? Is it because of the peer numbers connected? Or a cTorrent bug? Well, I hope someone can answer my questions. Best regards Michollo

I too come to work yesterday only to find I know longer had access to the ShareSpace.  Not the web control interface ( got the 503 error as mentioned above)  and I could not access the folders until after I recycled power manually.  I was getting “Do not have permission see administrator” message.  After I powered back up I was able to get to my folders, however, I am still unable to access the web interface.  Oh did I mention I do have a few folders that just magically disappeared.

The light on the Power button contiunues to flash green.  WD Support tells me (after talking to 4 different people) that it takes a while for the RAID to “clean itself up”  Hell one the their techs didn’t even know what an UNC name was.  How can you support a device that is suppose to work with Windows and not know what an UNC name is?  Go figure . . .

I am waiting on talking them agin today to see if they recommend doing a reset ( not factory rest ) but the reset that is suppose to reset the password back to default.  I am very leary now to do anything - once bitten, twice shy . . .

I have the same problem, both in Firefox, IE and Chrome. It is when downloading a torrent via the downloader. Only way to access the downloader or admin area is to turn off

This happens to me to with ctorrent, it eats a lot of CPU. I just connect and kill the process. ctorrent’s doc says it’s a “clean shutdown” for a ctorrent download/upload process as data is written to disk before quitting.

http://www.rahul.net/dholmes/ctorrent/userguide.html#stopping

I hope WD can bring a nice update to this, otherwise, I’ll probably will replace it with Transmission or rtorrent.

I have the same problem “inaccessible”.

Logging in via SSH and looking at CPU usage with top and almost noting is running:

the mini_http is doing NOTHING.

Has anyone got an explanation and solution from WDC?

same problem in my unit, and very low performance without using downloads, oly copy folders from other pc, taking 200% of time compare to using two pc instead an pc an the wd.

+1

This is a pain in the **bleep**. The shares work wonderfully, but the cTorrent app does nothing but disallow access to the web interface. I am constantly rebooting the thing.

Any fixes? Anything?

find a way without restart everything…

since the device is linux based, you can restart the single services… the one we need to restart is minihttpd to do so frist log in into the device via ssh, then:

this command to move where the system stores the procedure to boot (and reboot) the single services

/etc/init.d

and this command to force a restart of the web interface:

./S55mini_httpd restart

it worked great at last in my case, but i have no strange torrents processes running on the device… hope this can help somebody, for everything feel free to ask! :slight_smile: bye

sorry i made a mistake the frist command must be:

cd /etc/init.d/

and NOT this

/etc/init.d/

sorry! :slight_smile:

Hey all, 

I seem to have the same problem. At first some only some of the pictures were shown when I accessed the web interface and a few days later I got the 503 error message. 

I have tried to get on the mybook using the putty client, but the the connection gets declined every time. What else beside the IP adress do I have to change to get in there? Sorry for asking so stupid, but I’m using putty for the first time and the extreme mass of options kind of scares me :wink:

Greets, C 

I’v’e been having this problem for over a year now & have not found a solution

Has anoyone found out what to do yet?

UNKNOWN 503 Server temporarily overloadedDate: Sun, 15 Aug 2010 08:17:59 GMTCache-Control: no-cache,no-storeContent-Type: text/html; charset=%sConnection: close

I’m having the same problems and I tried your solutions.

Nevertheless I was stopped by a "permission denied when changing ot the folder /etc/init.d/ and therefor couldn’t restart the process S55mini_httpd. Thus, I guess I would first have to kill the ctorrent processes, shouldn’t I? What would the command be for that?

I’ve re-contacted the WDC support. Let’s see if they react this time.

… it was just syntax errors that stopped me.

Took me some trials to figure out.

So here’s the complete syntax for dummies like me:

/etc/init.d/   (to change to the concerned directory)

top  (to see the process IDs)

q   (to quit top)

kill 12345   (to kill process with ID 12345, repeat for each ctorrent process)

./S55mini_httpd restart   (to relaunch the minihttp interface)

That’s it!

Still waiting for an answer of WD 2nd level support on how to reserve CPU capacity for “vital” processes, so you don’t need this workaround.