Hi,
Do you try to start application from the command line ? with fewer
arguments than the wotaskd ?
( ./app -WOPort 1234 )
Even if /etc/hosts looks ok, does hostname -f on the linux server gives
you the same host declared in the monitor ?|
(you may try to declare the linux server in the monitor with his IP)
|
In addition to what Chuck wrote:
Somethings to try:
- add WOHost=<host name> to the Properties file in
wotaskd.woa/Contents/Resources on each machine
- add WOHost=<host name> to the app launch params for each machine
(instance specific)
- verify the permissions again:
http://www.gvcsitemaker.com/gvc.webobjects/faq&mode=single&recordID=66181
- enable logging from wotaskd:
http://www.gvcsitemaker.com/gvc.webobjects/faq&mode=single&recordID=41413
- I thought there was an (undocumented?) parameter to debug wotaskd,
but I can't locate it now.
I haven't time to look in the source but AFAIK classical parameters like
WOOutputPath, NSDebugGroups and NSDebugLevel would give a very verbose
log file.
Some weeks ago I was doing a migration from old Sun servers running
solaris on sparc to new Intel ones with Linux and some applications
doesn't start :/
_ starting application from the command line works
_ adding verbosity to wotaskd log, doesn't help
_ SpawnOfWOTask.sh was redirecting stdout and stderr to a file, no error
in it, just useful to know that it tries to start
the application. One time I have found a "broken" directory (/opt) in
a ext3 filesystem from which SpawnOfWOTaskd.sh couldn't be launched from
the wotaskd whereas lauching WO application form command line in this
directory works ... so now I always check if the SpawnOfWOTaskd.sh is
launched.
_ tcpdump on lo / ethX to see http exchanges between wotaskd and
javamonitor doesn't show any problems.
_ strace wasn't realy helpful to much logs
Finaly I modified the SpawnOfWOTaskd.sh, not for logging as all the
output isn't sent to stdout/stderr , but
to show the startup in live on my workstation :
#!/bin/bash
export DISPLAY=_my_private_ip_on_the_lan:0.0
#just to be sure remote display usable
xclock
#try to start the app
xterm $@
I added sleep 10 and read just before and after the last line of the
application startup script in the .woa,
sleep 10
eval exec ${JAVA_EXECUTABLE} ....
read akey
sleep is to resize the xterm
read is to prevent the xterm to close up and for having time to analyze
the output (press enter and the xterm ends)
On my workstation I do xhost + wo-server-ip and click start in the monitor
as a result xclock and after closing it, an xterm show up.
I haven't found a better way to find out that was a missing reading
permission on an Info.plist in a framework which prevented starting
application from the monitor.
(strangely the application started in the command line without a problem)
I hope this could help
Aurélien
_______________________________________________
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 arch...@mail-archive.com
