Hi David
Thanks for the suggestion however that didn't fix my issue. I would have
expected the backuppc user to be created as part of the package install
in any case.
The problem appears to be one of PEBKAC :( I tried accessing the GUI on
another browser and it's fine. My (normally reliable) F
On 11/07 12:20 , Tom Fallon wrote:
> The problem appears to be one of PEBKAC :( I tried accessing the GUI on
> another browser and it's fine. My (normally reliable) Firefox install
> appears to be the culprit not the backuppc installation as I can access
> in Chromium absolutely fine. Should rea
Hi I have a backuppc 3.3 server running but I would like to test the 4.0
version on a spare server I have, can someone provide a link with
detialed install instructions for Debian . I have followed these
instructions http://www.lycom.net/blog/?p=160 but so far with no success
and I cant seem to
I'm SSH'ing into each server and in turn SSH'ing into each server that is
having a backup issue to determine if they can connect.
Some can, some can't. 'Strict checking' is currently enabled and I am getting a
. If I simply disabled 'strict checking' and determined that all systems could
Resolve
On Fri, Nov 7, 2014 at 12:30 PM, tschmid4 wrote:
>
> I'm SSH'ing into each server and in turn SSH'ing into each server that is
> having a backup issue to determine if they can connect.
> Some can, some can't. 'Strict checking' is currently enabled and I am getting
> a
> . If I simply disabled 's
The broken pipe could have been my haste to sudo -s after SSH into the box.
If I go into known_hosts and # out the specific line of the server with the
issue, so I can have the data for reference,
is that the same as deleting the line or do I really have to remove the entire
line from the known
You can just comment it out.
Keeping it as reference is, most likely, useless though.
If You reinstalled or, somehow, You regenerated the "host keys" in the
"server" (actually that's the BackupPC *client*) the old ones are lost
for good.
I strongly urge You to make pretty sure (testing by hand)
On Fri, Nov 7, 2014 at 1:12 PM, tschmid4 wrote:
> The broken pipe could have been my haste to sudo -s after SSH into the box.
>
> If I go into known_hosts and # out the specific line of the server with the
> issue, so I can have the data for reference,
> is that the same as deleting the line or d
Not concerned at all.
I'd rather start from scratch at this point if it's possible.
I've made a list of which servers can connect to others and for the most part,
they can connect with a few stray disconnects.
To start with a clean slate, would I SSH into the backup server and SSH to each
Linux
On Fri, Nov 7, 2014 at 1:58 PM, tschmid4 wrote:
>
> I'd rather start from scratch at this point if it's possible.
> I've made a list of which servers can connect to others and for the most
> part, they can connect with a few stray disconnects.
>
> To start with a clean slate, would I SSH into the
Ok,
let's try to start from beginning and clarify some terminology, so we
can understand each other.
On 11/07/2014 08:58 PM, tschmid4 wrote:
Not concerned at all.
I'd rather start from scratch at this point if it's possible.
I've made a list of which servers can connect to others and for the
11 matches
Mail list logo
