Re: [UPDATE] Re: wotaskd on 10.4
Re: [UPDATE] Re: wotaskd on 10.4
- Subject: Re: [UPDATE] Re: wotaskd on 10.4
- From: Sacha Mallais <email@hidden>
- Date: Tue, 28 Jun 2005 11:23:46 -0700
On Jun 26, 2005, at 11:24 AM, Baiss Eric Magnusson wrote:
On Jun 21, 2005, at 6:42 PM, Sacha Mallais wrote:
What does "uname -a" report?
It reports:
Darwin cascade.suddentechnology.com 8.1.0 Darwin Kernel Version
8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/
RELEASE_PPC Power Macintosh powerpc
What is in /etc/resolv.conf?
cascade:/etc baiss$ cat resolv.conf
nameserver 216.162.215.195
nameserver 216.162.215.196
In <hostconfig>
HOSTNAME=-AUTOMATIC-
Try changing this. IIRC, you can do so from the Sharing pref panel.
The machine does not have multiple IP addresses, but it is a DNS
server for a second machine at <216.162.215.195>.
Hmm... According to your resolv.conf, this machines is looking to
216.162.215.195 for it's DNS information first, then
216.162.215.196. This file is filled from the Network pref panel.
I finally got up the nerve to start working with <SiteConfig.xml>
on Sunday morning.
Contrary to my notes, deleting it and the re-booting did not re-
generate it, so I don't know it's inheritance.
It is generated by JavaMonitor and wotaskd, but it is your
configuration, so deleting it makes JavaMonitor and wotaskd think
there is no config.
I re-established <SiteConfig.xml> from the backup, with <localhost>
replacing <216.162.215.196> for the host directive, none of the WO
Apps were listed and there was no host in the <wotaskd> host list.
I edited out all the references to <216.162.215.196> in
<SiteConfig.xml> and replaced them with <localhost>.
The situation was the same, when Monitor comes up it says that it
cannot connect to <http://localhost:xxx>.
I re-started <wotaskd> from Terminal and all hell broke lose with
nothing running.
So I re-set <localhost> to <216.162.215.196> for all the
occurrences in <SiteConfig.xml> and re-booted, then manually re-
started <wotaskd>, and was at the same place as I started in the
morning, i.e. <wotaskd> won't start automatically with the server
giving the message
<http://localhost:xxx> could not connect to server <localhost:xxx>
at start-up.
<localhost> wants to be <127.0.0.1> it seems to me.
Does that make everything work as you expect?
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.
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