wotaskd bombing out, known error codes?
John Pollard <[email protected]> Mon, 05 Sep 2005 11:18:55 +0100
| Newsgroups | gmane.comp.web.webobjects.admin |
|---|---|
| Message-ID | <[email protected]> |
Our server has a cron reboot once a week which normally causes no problems, except this weekend wotaskd bombed out after the restart following reboot, leaving all our apps inaccessible. I found the following in /var/log/webobjects.log.1 ------------------------------------------------------------------------- javawoservice.sh: `wotaskd' is starting up ... [2005-09-03 02:00:54 BST] <main> Multicast Response Disabled [2005-09-03 02:00:54 BST] <Thread-0> Created UDP socket; listening for requests... [2005-09-03 02:00:54 BST] <main> The URL for webserver connect is: http://plug/cgi-bin/WebObjects/wotaskd.woa/-1085 The URL for direct connect is: http://plug:1085/cgi-bin/WebObjects/wotaskd.woa [2005-09-03 02:00:55 BST] <main> null [2005-09-03 02:00:54 BST] <main> Waiting for requests... javawoservice.sh: `wotaskd' exited. . `wotaskd' terminated with an error (`143'). Scaling wait time ... . Execution not counted as a success. javawoservice.sh: `wotaskd' will restart in 5 seconds ... I don't know what happened after 5 seconds, as there is no more logging. All my WO apps appeared to start up ok and were waiting in vain for requests to arrive. Is there a mapping of error code magic numbers (143) to "meaningful message" somewhere? Has anyone else experienced anything similar? If I can't get to the bottom of what went wrong, what safeguards / workarounds could I put in place? Thank you for your time John