Hi Rick,
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
Done!
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/*/*
Done! Can I disable logging again with
/opt/tarantella/bin/tarantella config edit
--tarantella-config-execpeconfig-logfilter
when I am done?
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 )
I get these logs but they don't give me a clue:
...
expect: does "TTA_UID="`LANG=C LC_ALL=C id | sed
's/.*uid=\([0-9][0-9]*\).*/\1/'`"; export TTA_UID\r\n" (spawn_id 0)
match regular expression "ogin:[ ]*$"? no
"[\\\$%>\\\#][ ]*$"? no
$
expect: does "TTA_UID="`LANG=C LC_ALL=C id | sed
's/.*uid=\([0-9][0-9]*\).*/\1/'`"; export TTA_UID\r\n$ " (spawn_id 0)
match regular expression "ogin:[ ]*$"? no
"[\\\$%>\\\#][ ]*$"? yes
expect: set expect_out(0,string) "$ "
expect: set expect_out(spawn_id) "0"
expect: set expect_out(buffer) "TTA_UID="`LANG=C LC_ALL=C id | sed
's/.*uid=\([0-9][0-9]*\).*/\1/'`"; export TTA_UID\r\n$ "
send: sending "TTA_USERNAME='.../_ens/o=organization/cn=ahoesch';
export TTA_USERNAME\n" to { 0 }
expect: does "" (spawn_id 0) match regular expression "ogin:[ ]*$"? no
"[\\\$%>\\\#][ ]*$"? no
TTA_USERNAME='.../_ens/o=organization/cn=ahoesch'; export TTA_USERNAME
expect: does "TTA_USERNAME='.../_ens/o=organization/cn=ahoesch'; export
TTA_USERNAME\r\n" (spawn_id 0) match regular expression "ogin:[ ]*$"? no
"[\\\$%>\\\#][ ]*$"? no
$
expect: does "TTA_USERNAME='.../_ens/o=organization/cn=ahoesch'; export
TTA_USERNAME\r\n$ " (spawn_id 0) match regular expression "ogin:[ ]*$"?
no
"[\\\$%>\\\#][ ]*$"? yes
expect: set expect_out(0,string) "$ "
expect: set expect_out(spawn_id) "0"
expect: set expect_out(buffer)
"TTA_USERNAME='.../_ens/o=organization/cn=ahoesch'; export
TTA_USERNAME\r\n$ "
send: sending "TTA_PRIMARY_DNSNAME='www.bockelmann-holz.de'; export
TTA_PRIMARY_DNSNAME\n" to { 0 }
expect: does "" (spawn_id 0) match regular expression "ogin:[ ]*$"? no
"[\\\$%>\\\#][ ]*$"? no
TTA_PRIMARY_DNSNAME='www.bockelmann-holz.de'; export TTA_PRIMARY_DNSNAME
expect: does "TTA_PRIMARY_DNSNAME='www.bockelmann-holz.de'; export
TTA_PRIMARY_DNSNAME\r\n" (spawn_id 0) match regular expression "ogin:[
]*$"? no
"[\\\$%>\\\#][ ]*$"? no
$
expect: does "TTA_PRIMARY_DNSNAME='www.bockelmann-holz.de'; export
TTA_PRIMARY_DNSNAME\r\n$ " (spawn_id 0) match regular expression
"ogin:[ ]*$"? no
"[\\\$%>\\\#][ ]*$"? yes
expect: set expect_out(0,string) "$ "
expect: set expect_out(spawn_id) "0"
expect: set expect_out(buffer)
"TTA_PRIMARY_DNSNAME='www.bockelmann-holz.de'; export
TTA_PRIMARY_DNSNAME\r\n-bash-3.00#
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:
I haven't altered the prompt. It's
-bash-3.00#
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
My problem changed in the meanwhile. When clicking on Window Maker
Fullscreen (works great with telnet as connection method) I almost see
the desktop but then finally (only adter a couple of seconds) it
collapses and the session ends. I have no idea why. This problem occurs
only when using ssh. telnet works. I can access xclock and dterm via
ssh with no problem!? I cna even access a GNOME fullscreen via ssh. But
the window maker fullscreen still fails (ssh only). :-(
Any idea?
Thanks a lot!
Regards,
Andreas
_______________________________________________
SGD-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sgd-users
