Proxmox - CRON ERROR

[czdavid]

Hello,

it is second day wnen I got to my email address this email from my server.

Subject: Cron <root@xx-xx-222-xx> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )
Message:
/etc/cron.daily/mlocate:
/usr/bin/updatedb.mlocate: `/var/lib/mlocate/mlocate.db' is locked (probably by an earlier updatedb)
run-parts: /etc/cron.daily/mlocate exited with return code 1

What is wrong? How can I fix it?

Thank you.

David

 

[redmop]

Updatedb is still running from yesterday. This usually happens when you have a lot of files. I'm not sure if it is needed, but I usually remove it I proxmox servers.

 

[czdavid]

Updatedb is still running from yesterday. This usually happens when you have a lot of files. I'm not sure if it is needed, but I usually remove it I proxmox servers.

Its fourth day today (I get this message every day). Should I try restart server (node)?

 

[redmop]

I would disable, or remove mlocate. Restarting the node won't do much of anything, as it will just run again. As an alternative, you can remove /var/lib/vz from the directory that mlocate scans. Check the man page.

 

[czdavid]

I would disable, or remove mlocate. Restarting the node won't do much of anything, as it will just run again. As an alternative, you can remove /var/lib/vz from the directory that mlocate scans. Check the man page.

Thank you.

How can I disable mlocate or remove directory /var/lib/vz? Where is configuration file for mlocate?

Thank you.

 

[mir]

/etc/updatedb.conf should already have disabled /var/lib/vz:
PRUNEPATHS="/tmp /var/spool /media /var/lib/vz"

 

[czdavid]

/etc/updatedb.conf should already have disabled /var/lib/vz:
PRUNEPATHS="/tmp /var/spool /media /var/lib/vz"

Yes, /var/lib/vz is already disabled.

 

[redmop]

Do you have data on the server outside of that, such as a mounted network share?

 

[czdavid]

Do you have data on the server outside of that, such as a mounted network share?

I have containers on local storage. I have mounted NFS for backups, templates and ISO.

 

[mir]

Maybe you should exclude the NFS mount points from /etc/updatedb.conf

 

[czdavid]

I have containers on local storage. I have mounted NFS for backups, templates and ISO.

Good idea. I think thats it.

 

[redmop]

That should indeed fix you up.

 

[czdavid]

That should indeed fix you up.

Is possible kill/restart currentdb update process (remove lock)? I have still running currentdb update from first day. Probably because in /mnt/pve is one of NFS storages offline.

 

[redmop]

It is perfectly safe to kill updatedb and mlocate whenever you like.