Proxmox - CRON ERROR

C

czdavid

Member
May 17, 2012
31
0
6
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
 
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.
 
redmop said:
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.
Click to expand...

Its fourth day today (I get this message every day). Should I try restart server (node)?
 
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.
 
redmop said:
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.
Click to expand...

Thank you.

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

Thank you.
 
Do you have data on the server outside of that, such as a mounted network share?
 
redmop said:
That should indeed fix you up.
Click to expand...

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.
 
You must log in or register to reply here.
Top Bottom