• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: [UPDATE-2] Re: wotaskd on 10.4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [UPDATE-2] Re: wotaskd on 10.4


  • Subject: Re: [UPDATE-2] Re: wotaskd on 10.4
  • From: Sacha Mallais <email@hidden>
  • Date: Tue, 28 Jun 2005 11:44:31 -0700

On Jun 28, 2005, at 11:19 AM, Baiss Eric Magnusson wrote:

Parsing thru the Server Admin/System Log right after a re-boot I see the following disturbing messages:
Is the solution to the <wotaskd> startup failure hinted in the below, and if so, any suggestions on what to do to alleviate it?


cascade reboot: rebooted by baiss

localhost launchd: com.webobjects.wotaskd: getgrnam("appserverusr") failed

Definitely possible: check that the appserverusr group still exists.


localhost launchd: com.webobjects.wotaskd: exited with exit code: 1
localhost launchd: com.webobjects.wotaskd: respawning too quickly! throttling
localhost launchd: com.webobjects.wotaskd: 9 more failures without living at least 60 seconds will cause job removal
localhost launchd: com.webobjects.wotaskd: will restart in 10 seconds
localhost servermgrd: servermgr_dns: Couldn't get the primary address
...

Uh oh...


cascade configd[34]: setting hostname to "cascade.local"
...
cascade launchd: Server 3367 in bootstrap 1103 uid 0: "/usr/sbin/ lookupd"[105]: exited abnormally: Hangup
cascade configd[34]: setting hostname to "cascade.suddentechnology.com"
...
cascade named[52]: /private/etc/named.conf:11: option 'statistics- interval' is not implemented
...

Looks like your named configuration is messed too... check that named is actually running. Do you edit these files by hand or just use the Apple Server Admin GUI?



cascade launchd: com.webobjects.wotaskd: 1 more failure without living at least 60 seconds will cause job removal
cascade launchd: com.webobjects.wotaskd: exited with exit code: 1
cascade launchd: com.webobjects.wotaskd: too many failures in a row for a job that should be alive all the time


sacha

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


References: 
 >wotaskd on 10.4 (From: Baiss Eric Magnusson <email@hidden>)
 >[UPDATE] Re: wotaskd on 10.4 (From: Baiss Eric Magnusson <email@hidden>)
 >Re: [UPDATE] Re: wotaskd on 10.4 (From: Chuck Hill <email@hidden>)
 >Re: [UPDATE] Re: wotaskd on 10.4 (From: Sacha Mallais <email@hidden>)
 >Re: [UPDATE] Re: wotaskd on 10.4 (From: Baiss Eric Magnusson <email@hidden>)
 >Re: [UPDATE-2] Re: wotaskd on 10.4 (From: Baiss Eric Magnusson <email@hidden>)

  • Prev by Date: full urls from WOImage and friends
  • Next by Date: Re: [UPDATE-2] Re: wotaskd on 10.4
  • Previous by thread: Re: [UPDATE-2] Re: wotaskd on 10.4
  • Next by thread: Re: [UPDATE-2] Re: wotaskd on 10.4
  • Index(es):
    • Date
    • Thread