On Wed, 2005-07-27 at 08:22 +0200, Stephan Holl wrote:
> I am doing exactly what you are trying to achieve. One thought I was
> struggeling when using an ssh-tunnel.
>
> I had to redirect the output of the ssh-command to /dev/null
> (> /dev/null) in order to make the RunBeforeJob-directive work pr
Hello Jesse,
On Tue, 26 Jul 2005 13:32:37 -0700 Jesse Keating
<[EMAIL PROTECTED]> wrote:
> On Tue, 2005-07-26 at 13:21 -0700, Jesse Keating wrote:
> > Wait, I'm on to something here. The ssh process goes away almost
> > immediately when called by Run Before Job. If I run it myself it
> > stays
On Tue, 2005-07-26 at 16:50 -0700, Karl Cunningham wrote:
>
> Jesse --
>
> It may be that since you are not logged in to the system on which the
> tunnel is being opened the operating system closes it as soon as the script
> exits. You may need to invoke the tunnel with nohup or something simila
--On Tuesday, July 26, 2005 2:06 PM -0700 Jesse Keating
<[EMAIL PROTECTED]> wrote:
> On Tue, 2005-07-26 at 21:44 +0100, Martin Simmons wrote:
>> Strange. The use of the -N option to ssh is supposed to make it wait.
>> Maybe there is a problem with which user is running ssh?
>
> Well, bacula is r
On Tue, 2005-07-26 at 21:44 +0100, Martin Simmons wrote:
> Strange. The use of the -N option to ssh is supposed to make it wait. Maybe
> there is a problem with which user is running ssh?
Well, bacula is running as root, and I was doing my tunnel testing as
root. It seems from the console outpu
> On Tue, 26 Jul 2005 13:32:37 -0700, Jesse Keating <[EMAIL PROTECTED]>
> said:
Jesse> On Tue, 2005-07-26 at 13:21 -0700, Jesse Keating wrote:
>> Wait, I'm on to something here. The ssh process goes away almost
>> immediately when called by Run Before Job. If I run it myself it
On Tue, 2005-07-26 at 13:21 -0700, Jesse Keating wrote:
> Wait, I'm on to something here. The ssh process goes away almost
> immediately when called by Run Before Job. If I run it myself it
> stays
> running. Thoughts?
>
And I'll reply to myself one more time. In fact, if i call the ssh
scrip
On Tue, 2005-07-26 at 13:18 -0700, Jesse Keating wrote:
>
> This is very strange. The backup job kicks off the ssh script, which
> supposedly opens all the tunnels. The client however is never able to
> connect to 'localhost:9103' as seen by logs:
Wait, I'm on to something here. The ssh proces
On Tue, 2005-07-26 at 11:58 -0700, Jesse Keating wrote:
>
> So I tried this, and same thing. Looks like the ssh tunnel gets
> started, and the client gets the word to start a backup, however it just
> hangs when trying to contact the sd. Thoughts?
>
This is very strange. The backup job kicks
On Tue, 2005-07-26 at 19:36 +0100, Martin Simmons wrote:
> Yes. See
> http://www.bacula.org/rel-manual/Using_Bacula_Encryp_Commun.html
> (although this talks about stunnel, the same kind of Bacula
> configuration
> issues will apply to ssh-tunnel.sh).
So I tried this, and same thing. Looks like
> On Tue, 26 Jul 2005 11:12:31 -0700, Jesse Keating <[EMAIL PROTECTED]>
> said:
Jesse> So here is my situation. I have a set of remote servers that I'd like
Jesse> to backup. I can ssh to these servers from the bacula-dir (which is
Jesse> also the bacula-sd) however these servers
So here is my situation. I have a set of remote servers that I'd like
to backup. I can ssh to these servers from the bacula-dir (which is
also the bacula-sd) however these servers cannot ssh back to bacula.
(nat is involved). I've been playing w/ the ssh-tunnel.sh script as it
seems to create a
12 matches
Mail list logo
