Title: Remote Telnet command crashes Servers Alive V5.1.1964
We didn't get any reports of this.
Each telnet connection should be logged within the logfile
of SA (with maximum logging)., also SA can accept (by default) upto 10 telnet
connections at the same time.
One thing you could do is reduce this number to 1, that way
one can never interfer with the other.
dirk.
From: Carroll, Andrew
[mailto:[EMAIL PROTECTED] Sent: Tuesday, April 04, 2006
1:10 PMTo: Servers Alive Discussion ListSubject: [SA-list]
Remote Telnet command crashes Servers Alive V5.1.1964
Dirk,
I have successfully implemented remote telnet
commands that can be run from a remote web frontend, this gives me the ability
to put a check into MAINTENANCE, ACTIVE or perform a CHECK NOW. This has been
implemented using a mixture of HTML, ASP and PERL.
However, although these commands work fine, if there
are a number of these commands being performed at the same or in quick
succession, it can cause the Servers Alive application to crash.
From my investigations I believe this to be due to
the fact that the telnet session is either being terminated before the process
has successfully completed, or the next telnet session is killing the current
telnet session.
There are no useful entries being logged to the log
file.
Can you see anyway around this problem, has anybody
else reported a similar problem?
Regards,
Andy To unsubscribe send a message
with UNSUBSCRIBE as subject to salive@woodstone.nu
To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu
