Dennis -

In my experience FQDN is definitely the way to go - make sure your apps, 
monitor, and wotaskd all have the exact same thing. Run nslookup or similar at 
the command line to make sure the name resolves to the IP address of the NIC on 
the box, and the IP address resolves back to the name that you're using as the 
WOHost parameter. A handful of additional thoughts:

1)  have you made sure that your adaptor config correctly has the correct 
hostnames and ports for the wotaskd(s) it needs to know about? What does the 
adaptor config page tell you about what apache thinks the world looks like? 
(Apologies if you already covered that... I just caught the last couple of 
posts).

2) have you checked your launchd boot scripts for wotaskd and monitor (if 
that's how you are launching them) to make sure that you don't have alternative 
WOHost entries in there as command line arguments? (if they aren't there 
already, maybe try adding them there, to make sure that the values you want are 
getting picked up).

3) I had an issue today (and I noticed someone else post something similar 
recently in connection with SSD boot drives) that wotaskd and womonitor were 
binding to the loopback address (only) not the ones I was asking them to - 
apparently because the nics weren't properly initialized at the time the apps 
were starting up at boot time.

For me, killing the two java processes manually and allowing launchd to restart 
them fixed the problem. They came back up on the correct interfaces, and the 
IP's matched what they were expecting, and all was good.  Have you tried 
manually killing/restarting the processes after the machine has booted up?

4) FWIW, I generally specify the WOHost for my apps as an additional command 
line argument in the app config in WOMonitor, rather than in the properties 
file. You may want to try that.



I know from experience how frustrating the dance is to get things to work 
right, but it's generally always worked out for me, and I am deploying apps on 
Lion Server just fine, with the Wonder versions of monitor and wotaskd.

Regards,

Simon





On Feb 28, 2012, at 3:26 PM, Gaastra Dennis - WO Lists wrote:

Hi Tim,

Thanks for your email.

Yes DNS works correctly with 'changeip -checkhostname'; put full host names in 
wotask and JavaMonitor Properties files; and still nothing works. This is the 
most frustrating part of WO on Lion Server, however, this has always just 
worked for us in the past.

Greetings,

Dennis.



--

Simon J. Oliver
MA (Cantab.)
CISSP-ISSAP, ISSMP, GWAPT, OSWP

Information, Architecture & Data Security Consultant
Applied Information Technology Center/SBBER
University of Memphis, TN

Phone: 901 313 4485
Skype: SJO0923
AIM/Yahoo: simonjoliver










 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to