Veeam Linux Backup Proxie

[arestas]

Hello all,

We are having a strange behaviour on our CentOS 7 proxie.
When we try to add them we get the error:
"Unable to create elevated SSH connection: sudo failed and failover to su option is disabled".

We have check our suduoers file and user as the correct permission. if we use sudo he doesnt ask for password.

Code: Select all

## Allows people in group wheel to run all commands
#%wheel ALL=(ALL)       ALL

## Same thing without a password
# %wheel        ALL=(ALL)       NOPASSWD: ALL
%user  ALL=(ALL)       NOPASSWD: ALL

We have also check /etc/ssh/sshd_config and PasswordAuthentication parameter is set to yes. Yet we cant add the machine as proxie.
Any ideas on where to look?
any input is welcome. We could open a ticket with veeam support but they are very slow and they dont give the needed support. (at least thats the expericence we had in the past support cases)


Regards

[HannesK]

Hello,
you need to ensure that you can log in with the user and then do a "sudo su".

With your configuration that fails. And that's what the error message is saying.

replace "%user" by the username you want to use and it should work.

Best regards,
Hannes

[arestas]

Hello,

Thanks for your awnser, but that doesnt fail. We have check every piece of veeam information we found and evertyhing seems configured correclty.

Any other input?

Regards

[HannesK]

Hello,
the error message is very clear. There is a misconfiguration in the sudo configuration.

If you think that sudo works properly, that you please to open a support case for further investigations. As alternative, you could also use su (the root password).

Please post the case number for reference and also upload logs. Support can only help with logs.

Best regards,
Hannes

[arestas]

Hello,

We have open a support Case #04771868.
We werent able to provide logs since Veeam cant access the proxie servers.

Thanks

[PetrM]

Hello,

Don't worry about it, just leave this task to our support team. They will manage to do it by providing you with instructions for manual logs collection or via remote session.

Thanks!