The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

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

Discussion in 'General Discussion' started by webicom, Jan 20, 2014.

  1. webicom

    webicom Well-Known Member

    Joined:
    Mar 30, 2004
    Messages:
    54
    Likes Received:
    0
    Trophy Points:
    6
    Location:
    Slovenia
    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
     
  2. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    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:

    Code:
    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.
     
  3. sparek-3

    sparek-3 Well-Known Member

    Joined:
    Aug 10, 2002
    Messages:
    1,384
    Likes Received:
    23
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    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?
     
  4. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    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.
     
  5. durangod

    durangod Well-Known Member

    Joined:
    May 12, 2012
    Messages:
    251
    Likes Received:
    10
    Trophy Points:
    18
    cPanel Access Level:
    Website Owner
    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

    Code:
    
    rm -f /home/virtfs/_lock/512
    
    

    please advise thanks :)
     
  6. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    What's the date on that lock file? EX:

    Code:
    stat /home/virtfs/_lock/512
    Thank you.
     
  7. durangod

    durangod Well-Known Member

    Joined:
    May 12, 2012
    Messages:
    251
    Likes Received:
    10
    Trophy Points:
    18
    cPanel Access Level:
    Website Owner
    the 7th of jan
     
  8. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
    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.
     
  9. arjanvr

    arjanvr Well-Known Member

    Joined:
    Dec 13, 2013
    Messages:
    58
    Likes Received:
    1
    Trophy Points:
    8
    cPanel Access Level:
    Root Administrator
    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."
     
  10. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,854
    Likes Received:
    676
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page