-
- Expert
- Posts: 189
- Liked: 27 times
- Joined: Apr 24, 2013 8:53 pm
- Full Name: Chuck Stevens
- Location: Seattle, WA
- Contact:
Failed to Index with Indexing Disabled
Here's an odd one. I recently turned off guest indexing for my backup jobs. Since then one VM has been giving me a warning for failing to index the guest OS. The error is:
"Failed to index guest file system. STDERR: SCP sudo STDERR: SCP : STDERR: SCP no tty present and no askpass program specified STDERR: SCP "
The VM in question is a small Linux appliance. Any ideas?
"Failed to index guest file system. STDERR: SCP sudo STDERR: SCP : STDERR: SCP no tty present and no askpass program specified STDERR: SCP "
The VM in question is a small Linux appliance. Any ideas?
Veeaming since 2013
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Failed to Index with Indexing Disabled
Chuck, how have you turned indexing off? Have you just cleared the 'Enable guest file system indexing' check box at the Guest Processing step of the job wizard? Have you contacted support with this?
-
- Expert
- Posts: 189
- Liked: 27 times
- Joined: Apr 24, 2013 8:53 pm
- Full Name: Chuck Stevens
- Location: Seattle, WA
- Contact:
Re: Failed to Index with Indexing Disabled
Yes, just unchecked that box. No, I haven't yet contacted support; seemed a bit trivial.
Veeaming since 2013
-
- Veeam Software
- Posts: 21139
- Liked: 2141 times
- Joined: Jul 11, 2011 10:22 am
- Full Name: Alexander Fogelson
- Contact:
Re: Failed to Index with Indexing Disabled
Please open a case, since logs review is required. There were similar issues in v8, however all were addressed in the latest v9.
-
- Veteran
- Posts: 411
- Liked: 31 times
- Joined: Nov 21, 2014 10:05 pm
- Contact:
[MERGED] bug? Guest filesystem indexing warning after upgrad
Hi!
(ticket # 01675860 )
I just upgraded from v8 to v9.
After upgrading I started to get errors from my Linux vm backup:
Failed to index guest file system. STDERR: SCP sudo: sorry, you must have a tty to run sudo
The funny thing is, I dont want to do guest file system indexing and for that I have had that option deselected in guest processing tab.
(ticket # 01675860 )
I just upgraded from v8 to v9.
After upgrading I started to get errors from my Linux vm backup:
Failed to index guest file system. STDERR: SCP sudo: sorry, you must have a tty to run sudo
The funny thing is, I dont want to do guest file system indexing and for that I have had that option deselected in guest processing tab.
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: bug? Guest filesystem indexing warning after upgrading t
Hi. Do you have application-aware processing enabled? This will also result in guest logon attempts. You can disable it in the advanced settings on the same step for this specific VM. Regardless, the actual error message is misleading, so at least this is a bug for sure. Thanks!
-
- Veteran
- Posts: 411
- Liked: 31 times
- Joined: Nov 21, 2014 10:05 pm
- Contact:
Re: bug? Guest filesystem indexing warning after upgrading t
HI!
Yes, I have aaip enabled. Any idea why this worked with v8, but started giving me errors after upgrade?
I will disable aaip on monday.
Yes, I have aaip enabled. Any idea why this worked with v8, but started giving me errors after upgrade?
I will disable aaip on monday.
Bed?! Beds for sleepy people! Lets get a kebab and go to a disco!
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE
MS MCSA, MCITP, MCTS, MCP
VMWare VCP5-DCV
Veeam VMCE
-
- Veteran
- Posts: 635
- Liked: 174 times
- Joined: Jun 18, 2012 8:58 pm
- Full Name: Alan Bolte
- Contact:
Re: bug? Guest filesystem indexing warning after upgrading t
I would guess it has something to do with our implementation of transaction log backup for Oracle on Linux, but I'm not sure.
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: bug? Guest filesystem indexing warning after upgrading t
Correct, most likely this is the reason.
-
- Novice
- Posts: 8
- Liked: 1 time
- Joined: Jul 22, 2016 8:27 am
- Full Name: Eneko
- Contact:
Re: Failed to Index with Indexing Disabled
Hi,
we solved this issue by checking in oracle credentials under "Non-root account":
Elevate specified account to root
Add account to sudoers file automatically
After running the job you will notice that the next 2 lines are added to "/etc/sudoers" file:
Defaults:oracle !requiretty
oracle ALL=(root) NOPASSWD: ALL
Later, there will not be more warnings and it is safe to uncheck the option "Add account to sudoers file automatically".
Hope this will help
we solved this issue by checking in oracle credentials under "Non-root account":
Elevate specified account to root
Add account to sudoers file automatically
After running the job you will notice that the next 2 lines are added to "/etc/sudoers" file:
Defaults:oracle !requiretty
oracle ALL=(root) NOPASSWD: ALL
Later, there will not be more warnings and it is safe to uncheck the option "Add account to sudoers file automatically".
Hope this will help
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Apr 05, 2018 6:34 pm
- Contact:
[MERGED] Failed to index guest file system. Channel w
On one of my SLES 12 SP2 VMs I am getting a warning with the details: "Failed to index guest file system. Channel was closed." I have other similar Suse Vms running in the environment but this server is the only one getting the warning. In the backup job I do not have Enable guest file system indexing checked so I am not sure where this error is coming from. The application-aware processing is enabled but only for SQL. When the server was first created it was backing up fine but recently have been getting this warning. Has anyone else experienced this?
-
- Product Manager
- Posts: 6551
- Liked: 765 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: Failed to Index with Indexing Disabled
Hi and welcome to the community,
Considering that you do not have (and never had, I guess) indexing enabled, at least the error message is wrong and should be corrected. Also there must be a reason for the message to appear. Please contact our support team and post you case ID.
Thanks
Considering that you do not have (and never had, I guess) indexing enabled, at least the error message is wrong and should be corrected. Also there must be a reason for the message to appear. Please contact our support team and post you case ID.
Thanks
Who is online
Users browsing this forum: No registered users and 49 guests