Re: Monitor Gone because of bad xml, why?

Subject: Re: Monitor Gone because of bad xml, why?

From: Gaastra Dennis - WO Lists <email@hidden>

Date: Wed, 16 Jul 2008 13:43:18 -0400

Delivered-to: email@hidden

Hi Chuck,

Thanks for your help.

Why would this happen out of the blue, this morning?

We never touch the file manually, and have not changed the configuration in weeks. This is a brand new Xserve running RAID 5 for extra protection.

With Kind Regards,

Dennis Gaastra, M.B.A.[sfu.ca], B.Sc.[ubc.ca]

Chief Technology Officer,

WEBAPPZ

On 16-Jul-08, at 1:28 PM, Chuck Hill wrote:

On Jul 16, 2008, at 10:17 AM, Gaastra Dennis - WO Lists wrote:

Hi List,

Out of the blue, monitor was gone - just empty applications screen-, no sessions could be created anymore, then upon reboot, we saw:

(using WO 5.4.1 - Mac OS X Server 10.5.3, then upgraded to 5.4.2/10.5.4, and rebooted):

Jul 16 09:20:15 cluster2 com.webobjects.womonitor[65]: [Fatal Error] SiteConfig.xml:542:50: The element type "schedulingWeeklyStartTime" must be terminated by the matching end-tag "</schedulingWeeklyStartTime>".

rebooted again, and it everything was OK again.

why???

When wotaskd can't read the config file, it creates a new, blank one. I don't know what caused the corruption. Hand editing certainly can. ;-) Usually it does not come back, so you are lucky!

Moral: keep a manual backup of SiteConfig.xml

Chuck

--

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects

_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden

References:
	>Monitor Gone because of bad xml, why? (From: Gaastra Dennis - WO Lists <email@hidden>)
	>Re: Monitor Gone because of bad xml, why? (From: Chuck Hill <email@hidden>)