Hi,

I ma trying to set up a new backup environment and everything seems to
be working except the nodes that needs be backed up via ssh.

I have a dedicated backupuser, amandabackup , that I would like to use.

Ssh from the backupserver to the client works perfectly:

amandabackup@backupserver:~$ ssh client1
amandabackup@client1:~$

But when running selfcheck at the client, or via amcheck from the
backupserver, it keeps wanting to run as the backup user which is
normally disabled on all our machines.

amandabackup@client1:~$ /usr/lib/amanda/selfcheck
OK version 3.3.6
OK distro unknown
OK platform unknown
selfcheck: running as user "amandabackup" instead of "backup"

The debug log gives the following:

Thu Apr 26 09:50:23 2018: thd-0x55fcb52a5600: amandad: critical (fatal):
running as user "amandabackup" instead of "backup"

The dumptype config is as follows:

define dumptype simple-tar-ssh-remote {
        auth "ssh"
        client_username "amandabackup"
        amandad-path "/usr/lib/amanda/amandad"
        compress client best
        program "GNUTAR"
        exclude list "/etc/amanda/excludes"
}

Is there a way to configure the user on the client in this scenario ? I
can't seem to find anything regarding this in the documentation.

The current workaround is to enable the backup user locally, but I
rather not.

Regards

//Mika



Reply via email to