I have not seen this specifically, but someone was saying earlier this week that if they reboot the server their apps won't run. If they use the serveradmin tool to stop and restart wotaskd/JavaMonitor, then it works. It sounds to me like the same problem. Sorry, no solution, but it seems that you are not alone.
Chuck
On Jun 7, 2006, at 4:25 PM, Greg Finnegan wrote:
We're replacing an aging G4 server with a shiny new G5 server. However, we can't even get HelloWorld to deploy because it appears that the new launchd mechanism under Tiger Server fires up wotaskd and womonitor too early in the process, and womonitor does not bind to our IP address (instead defaults to 127.0.0.1).
If we disable launchd and copy over the old startup script from the G4/Panther server, which runs later in the boot sequence, both wotaskd and womonitor correctly bind to our IP address. All our apps then run fine.
Has anyone tackled this problem?
Greg.
-------------------------
Greg Finnegan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription:
--
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Help/Unsubscribe/Update your Subscription: