All of the listed commands are orders passed by the wotaskd to the application. The security on this is based on where the orders came from. Not who, no login/password, just the IP/hostname (something like gethostbyname) to check if it is local or not. For not having trouble, you have to make the command hostname -f returning the full qualified name of the server: server.domain.tld , in order to do that you have : _ to get a proper /etc/hosts file like: 127.0.0.1 localhost.localdomain localhost 1.2.3.4 server.domainX.tld server cname.domainY.tld 3.5.6.7 other.domainZ.tld other ... (by default it file isn't correct on OS X too but it must be sufficiently correct for having wostaskd orders accepted by instances) _ to get the hostname correctly defined in /etc/sysconfig/network (for redhat's based distribution)
Also I would recommend that you use IP address instead of the hostname in the JavaMonitor Hosts tab's in order to avoid DNS problems. Aurélien On 11/19/2010 05:24 PM, Kieran Kelleher wrote: > Does anyone know why a WOA app running on a physical linux (centos) machine > would not respond to WOMonitor "Stop" or "Refuse New Sessions" and not > display the instance statistics? > > What doesn't work: > - WOMonitor "Stop" does not stop the instance on linux and neither does it > indicate stopped in WOMonitor (as if action is ignored) > - WOMonitor "Refuse New Sessions" does not stop refusing sessions on the > instance and does not indicate refusing sessions in WOMonitor (as if action > is ignored) > - WOMonitor displays none of the statistics for the linux instance in app > Detail View in WOMonitor. All zeroes. > > What does work for Linux instances: > - WOMonitor Start does > - WOMonitor Auto Recover does > > To save time on obvious questions, here is the configuration: > - This is a mixed environment of 1 Linux and 5 OS X WOA servers. > - wotaskd is Apple's 5.4.3 version on all machines > - WOMonitor is Apple's 5.4.3 a Mac OS X machine > - The linux machine has eth0 and eth1. eth1 is on the WOA network. > - The wotaskd on the Linux box Properties file has WOHost=<eth1-ip-address> > - The linux host in WOMonitor is identified by its eth1-ip-address > > > Right now the only way to kill app instance on linux is: > 1) remote login, lsof -i tcp:xxxx and then kill pid > 2) Click an admin action in the instance itself that calls System.exit > ... after which WOMonitor "sees" that the instance is stopped > > Right now the only way to refuse sessions on linux instance is: > 1) Fire an admin action that calls application.refuseSessions() > .... after which WOMonitor "sees" that the instance is Refusing Sessions > > > WOMonitor functions fine for insatnces on all Mac OS X woa servers. > > Does anyone know what might be the problem? > > Regards, Kieran _______________________________________________ > 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/aurelien.minet%40univ-provence.fr > > This email sent to [email protected] _______________________________________________ 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]
