[Case 86773] home virtfs _lock timed out after 25 attempts

[webicom]

Hello,

I have a user who have problems with cronjobs after (I think) we have ugrade php from 5.2 to 5.3. Anyone knows how to fix this problem?
After cronjob runs he get error: attempt to lock file /home/virtfs/_lock/32674 timed out after 25 attempts; lock still held by pid 0 Could not create lock file: /home/virtfs/_lock/32674

Best regards, Erik

 

[cPanelMichael]

Hello

It looks like that is a stale lock file. An internal case is open to improve the handling of stale locks. For reference, the case number is 86773. You can monitor our change log to determine when a resolution associated with this case number is released.

cPanel - Change Log

In the meantime, the workaround is to forcibly remove the lock file. EX:

rm -f /home/virtfs/_lock/32674

Note that "32674" is UID of the account, so this number would change if you experience the issue with a different account in the future. Please be extra cautious with this command. It's important to only delete the individual lock file itself, and no other data in /home/virtfs.

Thank you.

 

[sparek-3]

Any particular reason why this fix wasn't rolled out to 11.40? Or was it fixed? I see it mentioned in the 11.42 changelog, but not in the 11.40 changelog. 11.40 is still being supported, isn't it?

 

[cPanelMichael]

Any particular reason why this fix wasn't rolled out to 11.40? Or was it fixed? I see it mentioned in the 11.42 changelog, but not in the 11.40 changelog. 11.40 is still being supported, isn't it?

Yes, cPanel version 11.40 is still supported. Resolutions for internal cases are not always backported to earlier versions of cPanel. Are you still using cPanel version 11.40 at this time? If so, let me know, and I can submit a request to have this case backported to version 11.40. Note that you may also want to consider upgrading to version 11.42. It's in the "Stable" build tier and widely used on production machines.

Thank you.

 

[durangod]

I just ran across this post, i received this on a cron that i run every 5 min

lock file /home/virtfs/_lock/512 created by pid xxxxx was not removed before the process died.

so should i run

rm -f /home/virtfs/_lock/512

please advise thanks

 

[cPanelMichael]

lock file /home/virtfs/_lock/512 created by pid xxxxx was not removed before the process died.

What's the date on that lock file? EX:

stat /home/virtfs/_lock/512

Thank you.

 

[durangod]

the 7th of jan

 

[cPanelMichael]

You can remove the stale lock file, however it's important to only delete the individual lock file itself, and no other data in /home/virtfs.

Thank you.

 

[arjanvr]

lockfile

I got this email twice now. What is causing this, and is it a problem?


"lock file /home/virtfs/_lock/560 created by pid 1357 was not removed before the process died."

 

[cPanelMichael]

Re: lockfile

Hello

I've merged this post into the following thread:

home virtfs _lock timed out after 25 attempts

Please consider opening a support ticket so we can verify if a new internal case is necessary.

Thank you.