500 internal error

[carmar1791]

500 internal error.
I often receive this message on imslp.
I find it very very slow, and when I want to move pages or change something and after..... that message ..
It's only for me?

Greetings

Carmar

[Davydov]

I've been getting the same for at least the last 6 hours or so

[homerdundas]

I've received this about once a day for the last few days... trashed my new work entries this time... I'm curious as to the reason... are we getting too busy for our own good?

[KGill]

I too have been getting this quite a lot - it's very annoying. It's giving me that right now, in fact (which is why I abruptly stopped work tagging).

[vinteuil]

I think it's a mirror server issue (?).
And Feldmahler mentioned something about great new capacity, but the programming needs to catch up?
I think it varies by area...

[imslp]

At this point I have no idea what causes the 500 errors... I will be conducting tests to see what the cause is. Hopefully it will be resolved in a few days.

The reason 500 errors are given is because the server as no vacant spot for another query. Why this is so is something I am trying to investigate.

[vinteuil]

I still got this this afternoon.

[imslp]

I was still working on the server this afternoon (even though it was mostly online), so it is possible that you came at a bad time (for the server). See if you still get it going forward.

The maintenance technically does not eliminate 500 errors; it just makes it such that you should almost never get them, essentially by reducing the server load (which is the cause of the 500 errors). If you do get them, wait for 5 seconds and reload the page.

I will be monitoring the number of 500 errors via the statistics. It is pretty much impossible to completely eliminate 500 errors, but I would be satisfied if it went down to 1/10000 of all requests instead of 1/200 before the maintenance.

Also, for anyone following the statistics, it is perfectly normal for the statistics to drop by 80% (the number of hits that is). The ultimate test of whether this maintenance was successful depends on how many 500 errors are given on Monday, the busiest day of the week.

[vinteuil]

I noticed (80%!)...and guessed...

[vinteuil]

ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: http://localhost/wiki/

The following error was encountered:

* Unable to forward this request at this time.

This request could not be forwarded to the origin server or to any parent caches. The most likely cause for this error is that:

* The cache administrator does not allow this cache to make direct connections to origin servers, and
* All configured parent caches are currently unreachable.

Your cache administrator is webmaster.
Generated Sun, 07 Feb 2010 22:23:29 GMT by mysquid (squid/2.6.STABLE18)

[KGill]

I got that too, until I tried switching browsers (from Chrome to Opera).

[Davydov]

I'm getting the "new" error message around 80% of the time now

[imslp]

Which browser?

[bujakerl]

ERROR
The requested URL could not be retrieved

While trying to retrieve the URL: http://localhost/wiki/

The following error was encountered:

* Unable to forward this request at this time.

This request could not be forwarded to the origin server or to any parent caches. The most likely cause for this error is that:

* The cache administrator does not allow this cache to make direct connections to origin servers, and
* All configured parent caches are currently unreachable.

Your cache administrator is webmaster.
Generated Sun, 07 Feb 2010 22:23:29 GMT by mysquid (squid/2.6.STABLE18)

I am also receiving the same message.

[imslp]

Please post browser! I have no idea how to fix it otherwise.