glad to see it is resolved
On 11/19/2010 10:50 PM, Kieran Kelleher wrote:
OK, first of all. Thanks to all who tried to help.
Miguel Arroz - you are a very smart man, and you should never give up your WO
career for goat-herding or farming in Portugal! :-)
So here is what worked for the finicky multi-IP linux box and its on/off
relationship with wotaskd:
I added Miguel's WOHostUtilities to ERExtensions, built and deployed the app.
I don't know Miguel's WOHostUtilities what is it made for ?
Note, WOHost needed to be set in wotaskd's Properties to the WoHost=192.168.3.168.
Setting it specifically to 127.0.0.1 resulted in WOMonitor red error message "Failed
to contact 192.168.3.168-1085".
Yes it's normal the WOPort of wotaskd isn't binded to 192.168.3.168 but 127.0.0.1 so no connection from the outside
could be made. using 127.0.0.1 is for setup with only one server.
Not setting it at all resulted in that Linux wotaskd not even receiving
requests from WOMonitor (confirmed with wotaskd debugging enabled) and not
responding at all to START instance requests.
If your hostname is localhost.localdomain as it correspond to 127.0.0.1 you have to declare the host in JavaMonitor as
127.0.0.1 but with this setup you can only have one server.
Only use localhost.localdomain for hostname if the server will be the only WebObjects server (declared in the
JavaMonitor as 127.0.0.1 or localhost.localdomain)
In your case:
* no DNS server
* private LAN
* multiple WebObjects servers
you need :
* to set a hostname, ex: srvwo168.wo.local (or anything else but not
localhost.localdomain)
* add the line: "192.168.3.168 srvwo168.local srvwo168" in /etc/hosts on srvwo168 (eventually on the server where
JavaMonitor is running)
(even if DNS server can have hight availability, I don't rely on them only, I always put in /etc/hosts all WO
servers, Apache servers and databases servers)
* no need to use WOHost, all applications including wotaskd will bind their
WOPort to all IP
with this kind of setup :
_ applications will accept orders from the wotaskd as when they lookup where the orders came from they found they
were coming from the local server
_ wotaskd will start applications as it knows itself in the SiteConfig.xml as 192.168.3.168 and finds that
192.168.3.168 is one of the server's IP .
note that it isn't specific to Linux, but applies to OS X, Solaris, FreeBSD ...
In WOMonitor I added a single argument with a list of all IP addresses of all
wotaskd hosts in the WOA subnet, like this:
-Dcom.survs.localhostIps=(192.168.3.140,192.168.3.160,192.168.3.163,192.168.3.165,192.168.3.161,192.168.3.161,192.168.3.168)
this is needed by Miguel's WOHostUtilities ? I understand that is the IP list of your WebObjects servers but it's used
to provide what functionality ?
( IP/hostname of WebObjects servers are in the SiteConfig.xml)
Now WOMonitor works for linux instances the same as for Mac OS X instances.
Yay! :-)
I am guessing (but not going messing with this server right now since it has
other services running on it that cannot be stopped for me to experiment) that
if the eth0 was on the WOA subnet, none of this might be neccessary.
No, you only need to make the server configuration right at the "dns" (/etc/hosts) and hostname level, regardless the
number of network cards or IP addresses the server got.
In the case you don't want the hostname (ex: mysrv.local) to match a specific IP, network card or subnet , you can
declare it to 127.0.0.1 in /etc/hosts on the server with a line like :
127.0.0.1 localhost.localdomain localhost mysrv.local mysrv
I hope all the mails in the thread will help future WebObjects servers setup
Regards
Aurélien
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com
This email sent to [email protected]
