On Aug 11, 2008, at 12:10 PM, Alan Zebchuk wrote:
Has anyone ever had issues where Monitor has issues contacting
wotaskd?
Yes.
We have 2 deployment servers, one of them running Monitor, and both
on 10.5 with 5.4.2 versions of wotaskd and Monitor.
All of the applications we're running are 5.3 with embedded
frameworks.
On one of the servers everything is fine, but for the other server
we often receive messages such as "Failed to contact
192.168.1.25-1085" (where 192.168.1.25 is the i of the other server.
As a result none of the applications that we have running on the
other server will respond to any requests.
This usually seems to occur when we try stopping or starting a WO
application on that server.
Any suggestions?
0. Kill wotaskd on the problem server so it relaunches. If that
works then proceed to:
1. Put a "sleep 30" in the script that launches wotaskd.
wotaskd can launch before the network is up, and latch onto a
useless ip address like, say 127.0.0.1, which makes its hard for
anyone to talk to it. It was better before launchd, because with
Startup items it had "Network" in there, so it wouldn't launch until
after the Network was up. Now that its brought up by launchd, it
launches too soon.
2. Turn off DHCP, and copy the 4 magic numbers to manual setup.
DHCP makes problem #1 worse, even if you're just using your DHCP
server to manually hand out IP addresses from a central location.
You can also use netstat to see what addresses wotaskd is bound to
if you don't like my "smack it and see if it works after that"
approach. But I have to confess, I really like smacking wotaskd...
Oh, and you can do: http://appserver:1085/ to see if that works
from your Monitor machine.
But again, its much more satisfying to smack it:
ps wwax | grep "WOPort 1085"
sudo kill <pid>
Pierce
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
