Veeam don't detect mlocate
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
I have two photon 3 vms. Both with the same packages installed. Both with mlocate installed. One vm gets indexed by Veeam, the other always says "Failed to index guest file system. mlocate was not found." The only difference is the install date. The one I installed earlier works, the newer not.
Any ideas what could be the problem that Veeam don't detect mlocate correctly?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no repository files, tests, or entry points. Start by comparing the two Photon 3 VMs beyond their install dates, including their installed packages and mlocate availability, then reproduce Veeam's guest-file-system indexing check. Done means identifying why one VM is detected and the other is not, with a repository change only if the cause is in Photon.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100