James,
I replied to Andrew Hall about something similar:
http://lists.opsview.org/lurker/message/20090507.205628.f3a75051.en.html
Can you try? This sounds like the responsibility of autossh
Ton
On 15 May 2009, at 03:44, James Whittington wrote:
I’m still trying to track down common patterns with some slave
servers periodically dropping the reverse ssh tunnel from master to
slave.
While looking around for resources talking about using autossh I
have noticed the syntax usage is slightly different on the ssh options
For Opsview the command is being called with option and value
separated with an “=” sign.
$prefix/bin/autossh -M 0 -f -N -T -2 -o TCPKeepAlive=yes -o
ServerAliveCountMax=3 -o ServerAliveInterval=10 -R $SLAVE_
PORT:127.0.0.1:22 -L 5667:127.0.0.1:5667 -L 2345:127.0.0.1:2345
nag...@$master
I have seen a couple of examples in articles on the net where
options have quotes but no “=” sign.
http://en.gentoo-wiki.com/wiki/Autossh
autossh -M 0 -q -f -N -o "ServerAliveInterval 60" -o
"ServerAliveCountMax 3" -R 8081:localhost:80 my.linuxbox.at.home
I haven’t had a chance to play around with the options any to see if
it makes a difference or not but it was an observation.
My other approach is to set up a check on the slave server to
somehow check for the existence of the reverse tunnel and restart
the slave service if it is detected as being down.
I can do a process listing (from the slave to the master) and see
ssh sessions but I’m not sure how I would detect the existence of
the correct reverse ssh process?
If I come up with anything interesting I will be sure to share it in
case others have issues with the reverse ssh setup of Opsview.
James Whittington
VC3, Inc.
_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/listinfo/opsview-users
