| Hi Jeff,
I’ve had troubles like this before and they are always a pain to figure out. It’s like a stray semicolon in your code and you wonder why it doesn’t compile but can’t see it with your own eyes.
Hmmm… yeah. Ok, but if the apps are launching just not communicating with wotaskd, etc. then there is still something here. Since it looks like you ruled out reverse lookup being a problem it still could be a subtle change in httpd.conf for server name, or something like that. See this copy of an old post below:
On 9 Mar 2004, at 23:53, Jonathan Rochkind wrote:
I'm not sure how generalizable this lesson is, but I'll tell my story.
Let's say your on Solaris with apache. You have an apache httpd.conf
that does not specify a ServerName. This causes apache to complain
every time you start it up, and has other weird oddities, but nothing
too disastrous.
But then you figure, okay, let's fix it by specifying a ServerName.
You bring down apache, change the httpd.conf, and then bring apache up
again. But meanwhile, you've left wotaskd running, and you've left
various deployed WO apps running. This turns out to be really bad.
Wotaskd gets really confused, and has trouble communicating with all
the instances. Don't do it.
Before making a change to the httpd.conf (any change? I don't know;
but definitely ServerName), bring down ALL WO apps, and bring down
wotaskd with "WOServices stop". Then make your change, restart
apache, and bring everything back up. Much happier.
Also, my general long standing observation: If your machine only has
ONE IP address (one network interface), but has multiple DNS names
(aliases and such)---you should ONLY use the DNS name that the numeric
IP will reverse lookup to, when configuring anything that might
involve WO. For instance, in that ServerName thing, even though you
might want to do different, you are best off specifying the
'canonical' DNS name, the one the numeric ip reverse lookup will
reveal. Use this same DNS name for specifying the 'host' in Monitor,
etc.
--Jonathan
On Mar 4, 2014, at 10:25 AM, Jeffrey Schmitz < email@hidden> wrote: Definitely random. Every reboot is an adventure :-)
Here's the host info. I think it looks good. On Mar 4, 2014, at 9:01 AM, Aaron Rosenzweig < email@hidden> wrote: Hi Jeff,
I wonder if you are having NSLOOKUP trouble.
If the DNS isn’t just right, WO can get easily confused and probably will cause sporadic problems like you are experiencing.
Right? If I understand it correctly things are failing somewhat randomly. It’s not like they never work, they sometimes do. That smells of DNS trouble.
In particular:
"Check that the machine is properly identified in the DNS including the reverse lookup."
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
|