Andreas,unfortunately, this particular log function isn't well documented. Basically, you'll want to:
1. edit /opt/tarantella/var/serverresources/expect/unix.exp and locate the line:
# startdebug Uncomment this line, and save the file. 2. Enable verbose execpe logging with the following command:/opt/tarantella/bin/tarantella config edit --tarantella-config-execpeconfig-logfilter execpe/*/*
Now, after starting some applications, you'll find various logfiles in /opt/tarantella/var/log, with filenames beginning "execpe". And, take note, all logfiles are stored here as well. (here's some info on logging - http://docs.sun.com/source/820-1088/jserver_logging.html )
From what I can gather, at least one of your problems is you're having a mismatch in the expect script - that is, the expect script is looking for a string from the application server that it's not seeing, waits a bit, (30 seconds) then continues on. One very common problem is the use of an "unusual" shell prompt, that is, not "$", "#", "%", etc. There's a list of such shell prompts stored in /opt/tarantella/var/serverresources/expect/vars.exp; I think the line reads something like:
set prompts(prompt) {list-of-prompts}
Adding the 'unusual' shell prompt to this list will fix this problem.
There may be other prompts your system is sending that our script
doesn't expect, like:
There is new news, read now?(y/n):The login will stall on the implied 'read' statement, as the expect script doesn't recognize the prompt, and can't respond intelligently. These kinds of things require a bit more work in expect - made much simpler if you can just remove these kinds of things from your .profiles, etc.
Rick Andreas Höschler wrote:
Hello David thanks for your responses so far.Do you have any /etc/issue, /etc/motd, special prompt for the user?No, nothing I would be aware of.Is it possible to catch the launch details and tell us where it's waiting?Excuse my ignorance, but how do I do that? In spite of reading the documentation I haven't figured out yet how the log stuff works in SGD. I was looking for an example for switching logging on and may be getting hands on it viatail -f /var/log/syslog or the like but I haven't figured that out yet. :-(Launch Details shows me almost nothing for a very long time and if the start succeeds the panel vanishes to quick for making a screen shot. No idea whether or in which file this stuff is logged.Thanks, Andreas _______________________________________________ SGD-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sgd-users
-- Rick Butland E-Mail: [EMAIL PROTECTED] AccessLine: (703) 579-1947 x53261 Direct: (703) 444-9398 Mobile: (703) 328-8130 _______________________________________________ SGD-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sgd-users
