Adding Linux repository to Veeam hangs on volume discovery and fails silently
| KB ID: | 2019 |
| Product: | Veeam Backup & Replication |
| Version: | 6.x, 7.x, 8.x |
| Published: | 2015-03-26 |
| Last Modified: | 2020-08-13 |
Challenge
When connecting to a Linux repository with Veeam, the connection hangs on the volume discovery step and silently errors out.
Cause
When Veeam connects to a Linux target the SSH session is opened without a TTY. In some versions of Linux (particularly recent releases of CentOS such as 6.6. and 7, and RHEL5 and higher), this is caused by RequireTTY being set as a default option in the /etc/sudoers file.
Solution
Note: A reboot may be required.
To disable RequireTTY globally:
1. Run visudo
2. Find the line for requiretty
3. Comment it out
To disable RequireTTY for a specific user:
1. Run the command visudo
2. Create a new line Defaults:<username> !requiretty
Where <username> is the Linux username given to Veeam Backup & Replication when adding the NFS repository.
To disable RequireTTY globally:
1. Run visudo
2. Find the line for requiretty
3. Comment it out
To disable RequireTTY for a specific user:
1. Run the command visudo
2. Create a new line Defaults:<username> !requiretty
Where <username> is the Linux username given to Veeam Backup & Replication when adding the NFS repository.
More information
The following messages were found related to this:
http://unix.stackexchange.com/questions/65774/is-it-okay-to-disable-requiretty
http://serverfault.com/questions/111064/sudoers-how-to-disable-requiretty-per-user
http://unix.stackexchange.com/questions/65774/is-it-okay-to-disable-requiretty
http://serverfault.com/questions/111064/sudoers-how-to-disable-requiretty-per-user
| KB ID: | 2019 |
| Product: | Veeam Backup & Replication |
| Version: | 6.x, 7.x, 8.x |
| Published: | 2015-03-26 |
| Last Modified: | 2020-08-13 |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
