[RESOLVED] Server Down

timstring

After battling a 403 error for a couple of days, I am now faced with this problem:

The website encountered an error while retrieving http://localhost/classes/05featuredemo. It may be down for maintenance or configured incorrectly.

This only happens on one site. All of the others are working well. Chrome returns the above error. Safari and Thunderbird just display blank screens. Everything was cooking yesterday morning when the 403 error started. Now, I'm faced with the current error.

I'm using
Mac OS 10.8.4, OS X Server 2.2.1
on a 2009 MacBook Pro, 2 GB RAM, 160 GB HD.

What Gives?

dalecosp

Gotta love those "meaningful" error messages. So user-friendly, right?

In my experience, which doesn't involve OSX or OSX Server, you're looking at a 500-series error now. Checked logs? Does "05featuredemo" (assuming its a real resource) lint properly?

timstring

Here's the errors for Chrome that are repeated several times:

7/10/13 11:15:42.931 AM Google Chrome[652]:         This exception was thrown inside thread: <NSThread: 0x78e89cb0>{name = (null), num = 1}.  This thread is the main thread.
7/10/13 11:58:35.022 AM WindowServer[128]: CGXDisableUpdate: UI updates were forcibly disabled by application "Google Chrome" for over 1.00 seconds. Server has re-enabled them.
7/10/13 11:58:35.596 AM WindowServer[128]: reenable_update_for_connection: UI updates were finally reenabled by application "Google Chrome" after 1.58 seconds (server forcibly re-enabled them after 1.00 seconds)

Safari reports a similar error:

7/10/13 12:19:18.142 PM WindowServer[128]: CGXDisableUpdate: UI updates were forcibly disabled by application "Safari" for over 1.00 seconds. Server has re-enabled them.
7/10/13 12:19:18.986 PM WindowServer[128]: reenable_update_for_connection: UI updates were finally reenabled by application "Safari" after 1.85 seconds (server forcibly re-enabled them after 1.00 seconds)

Don't ask me what I did, but the problem has been fixed.

dalecosp

timstring;11031049 wrote:
Don't ask me what I did, but the problem has been fixed.

Ok, I won't; but, could I ask you to mark this resolved? 😉 😉