Guest File Indexing Error

[HannesK]

Hello,
I'm just guessing what I found on the internet and it could be a permission problem as stated here

If that's not the case, I can only suggest to open a case and share the case number here.

Thanks,
Hannes

[mkuch]

A bit late, but I had the same problem on a SuSE Linux Enterprise Server and found a solution:

The source of the error is that apparmor was blocking the executable ("updatedb") from reading/writing from anywhere except the system default directory. The Veeam agent tries to store the index files in /tmp/veeam/index/ which gets blocked by apparmour.

To solve the issue you have to add the files created in this directory to the apparmor configuration file and restart the apparmor service.

Code: Select all

sles:~ # vi /etc/apparmor.d/usr.bin.updatedb

# Last Modified: Fri Apr 13 21:57:17 2018
#include <tunables/global>

/usr/bin/updatedb {
  #include <abstractions/base>

  capability dac_override,
  capability dac_read_search,
  capability fowner,

  / r,
  /**/ r,
  /etc/updatedb.conf r,
  /usr/bin/updatedb mr,
  owner /proc/@{pid}/mounts r,
  /var/lib/mlocate/mlocate.db rwk,
  /var/lib/mlocate/mlocate.db.?????? rw,

  /tmp/veeam/index/mlocate.*.db rwk,
  /tmp/veeam/index/mlocate.*.db.?????? rw,
}

sles:~ # rcapparmour restart

In the usr.bin.updatedb the two lines starting with "/tmp/veeam/index" have been added at the end of the file.
After this change the index error was gone.

[xavierpitz]

I also got the :
Failed to index [/] except ['/cdrom', '/dev', '/media', '/mnt', '/proc', '/tmp', '/lost+found'], ignoring.
error with Veeam 11 for VMs running Suse SLES 15.

I opened a support case and was made aware of the root cause of the problem by opening a support case been Veeam not been able to :

Code: Select all

[10.05.2022 18:25:03] <55> Error        Failed to index [/] except ['/cdrom', '/dev', '/media', '/mnt', '/proc', '/tmp', '/lost+found'], ignoring.
[10.05.2022 18:25:03] <55> Error        Failed to execute SSH command "updatedb -o '/tmp/vindexing_c2c3dca7-ea7a-4ccc-af59-80babb9bcfaf/mlocate_db/mlocate._.db' --database-root / --prunepaths="/cdrom /dev /media /mnt /proc /tmp /lost+found"". Timeout: 3600 sec 
[...]
[10.05.2022 18:25:03] <55> Error        Failed to run command with sudo: updatedb: can not open a temporary file for `/tmp/vindexing_c2c3dca7-ea7a-4ccc-af59-80babb9bcfaf/mlocate_db/mlocate._.db' (System.Exception)

I googled for :
veeam "updatedb -o" failed
and was lucky to find this Veeam forum post on the 1st google result page.
Thank you Michael Kuch !

So, with Veeam 11 temporary mlocate DB files generated by Veeam during FS indexing are generated under :
/tmp/vindexing_*/mlocate_db/mlocate._.db

So the 2 lines that have to be inserted at the end of the /etc/apparmor.d/usr.bin.updatedb are :

Code: Select all

  /tmp/veeam/index/mlocate.*.db rwk,
  /tmp/veeam/index/mlocate.*.db.?????? rw,

Then reload the apparmor config with :

Code: Select all

suselinux:~ # service apparmor reload

This or disable the apparmor module updatedb :

Code: Select all

suselinux:~ # aa-disable /usr/bin/updatedb
Disabling /usr/bin/updatedb.