upgrade 6.1 SCP sudo error

[dhallam]

i have upgraded to backup and replication 6.1 which looks very nice by the way, but all the backups error with the following error:
STDERR: SCP sudo: sorry, you must have a tty to run sudo

no i assume this is a user error on our dr site esx box but cannot get it working.
i have tried this fix on the esx box but then the job just sits at 0% for hours with no error.

if anyone has any quick ideas, i have currentally gone back to 6.0 so not mission critical but would love to upgrade

many thanks

David

[Vitaliy S.]

I guess you should edit this line in sudoers file on your target ESX host, at least it does work for all Linux-based servers:

Code: Select all

vi /etc/sudoers 
comment out: #Default requiretty

[dhallam]

Hi sorry i did try that fromt this thred Error in elavating to superuser....


i basically changed from
Defaults requiretty
to
#Defaults requiretty

But with this set the backup just sits at 0% has been for the past 20 mins

will do some more testing

[dhallam]

Sorted now ammended directally at the esx console and now working.

P.S new version seems a bit faster too so very happy with the new version.


cheers

[hannisch]

Have the same problem since updating 6.0 to 6.1. My backup repository is on an ESX 4.1. It worked perfect. I configured a non root user with shell access and elevted him to root and set Add account to the sudoers file automatically, too.
After in place Update, without changing anything I got the scp sudo error.

The veeam 2nd level support told me to set up these 2 settings in the sudoers file.:

Defaults:<username> !requiretty
<username> ALL=(ALL) NOPASSWD:ALL

The supporter told me,too this has alwys been so, the sudoers file has to be configured by me. But I don´t understand this. I have never touched the sudoers before, and it worked before upgrading to 6.0.

In my opinion, please correct me, if I´m wrong, the Veeam backup job customizes the sudoers file, for the time the backup is running, when "Add account to the sudoers file automatically is set". This seems not to work correctly in 6.1
The timestamp of the sudoers file changes 2 times, 1 time after starting the job and 1 time when it fails, but I saw changes in the file.

Sven

[hannisch]

The supporter gave this issue to the R&D department, now

Sven

[Gostev]

What is the support case ID for this issue please?

[hannisch]

The case ID is: 5210416

[foggy]

In my opinion, please correct me, if I´m wrong, the Veeam backup job customizes the sudoers file, for the time the backup is running, when "Add account to the sudoers file automatically is set". This seems not to work correctly in 6.1

This was confirmed to be an issue in 6.1. Will be addressed in the future update.