• 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-3] wotaskd on 10.4
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [UPDATE-3] wotaskd on 10.4


  • Subject: Re: [UPDATE-3] wotaskd on 10.4
  • From: Baiss Eric Magnusson <email@hidden>
  • Date: Tue, 28 Jun 2005 17:06:04 -0700

I should have said I had done a little digging in the post concerning the Group membership, including looking at the Unix documentation.

From /etc/group
    appserverusr:*:79:
    admin:*:80:root
    appserveradm:*:81:

When I look at Workgroup Manager/Groups for Short Name: <baiss>
    Primary Group ID: 501
    Other Groups:
    Administrators 80
    App Server Admins 81
    Application Server 79

So, I conclude that the call
localhost launchd: com.webobjects.wotaskd: getgrnam ("appserverusr") failed
should succeed with <Application Server 79>.  I'm filing a bug on this.

I can't run <Netinfo Manager>, this is a remotely administered server, I can only run Workgroup Manager and Server Admin, and, of course, Terminal.

BTW: I can run <wotaskd> from the command line with no problem.

Sacha asks:
In <hostconfig>
HOSTNAME=-AUTOMATIC-
Try changing this.  IIRC, you can do so from the Sharing pref panel.
I don't see how you can change that from the Sharing pane of Workgroup Manager.
In researching this I don't see any hints as to this being something to do?


In vague recesses of my mind, I recall editing /System/Library/ WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/ Properties to add WOHost=<myhost>. This will force wotaskd to start up listening to that host. You might want to try that too.
From <...WebObjects_5/DeployingWebObjects >
WOHost
Description Specifies the network interface that an instance binds to. This argument should only be used on hosts with multiple network interfaces (IP addresses).
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?
I read that this is a known configuration error, but is not a problem.
************************************************************************ *****
Addendum:
While working on this I went to the Software Update tab in Server Admin, whatever I did there caused the following error:
cascade servermgrd: servermgr_info: [46] unexpected Software Update state: crashed
What I didn't notice is that a process was left running which threw the above error message into a log file every minute, the side affect being that the WOApp which is a SSL site would quit with a timed out message when you tried to access a large page. I spent a frustrating day and a half trying to figure out that site problem. I am working with Apple on a bug report I filed on this issue.


On Jun 28, 2005, at 11:53 AM, Jerry W. Walker wrote:

Eric,

The first failure was:
localhost launchd: com.webobjects.wotaskd: getgrnam ("appserverusr") failed


From the Unix documentation:
       The  getgrnam()  function returns a pointer to a structure
       containing the group information from /etc/group  for  the
       entry that matches the group name name.

This would suggest that you might be having file ownership, permission or deleted group problems here.

I would look for appserverusr in the NetInfo Manager groups domain. If it's not there, I would suggest adding it, but its absence would probably reflect deeper problems. It's a standard group that comes with MacOS X.

If you decide to add it, add yourself as a user in the group and try the re-boot again.

Good luck.
Jerry

On Jun 28, 2005, at 2:19 PM, 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
cascade launchd: com.webobjects.wotaskd: too many failures in a row for a job that should be alive all the time
...----
Baiss Eric Magnusson
<http://www.Track-Your-Finances.com>
<http://www.CascadeWebDesign.com>


_______________________________________________ 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
  • Follow-Ups:
    • Re: [UPDATE-3] wotaskd on 10.4
      • From: Sacha Mallais <email@hidden>
    • Re: [UPDATE-3] wotaskd on 10.4
      • From: Art Isbell <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>)
 >Re: [UPDATE-2] Re: wotaskd on 10.4 (From: "Jerry W. Walker" <email@hidden>)

  • Prev by Date: pods
  • Next by Date: Re: [UPDATE-3] wotaskd on 10.4
  • Previous by thread: Re: [UPDATE-2] Re: wotaskd on 10.4
  • Next by thread: Re: [UPDATE-3] wotaskd on 10.4
  • Index(es):
    • Date
    • Thread