{"action":"created","issue":{"url":"https://api.github.com/repos/pzs-ng/pzs-ng/issues/30","repository_url":"https://api.github.com/repos/pzs-ng/pzs-ng","labels_url":"https://api.github.com/repos/pzs-ng/pzs-ng/issues/30/labels{/name}","comments_url":"https://api.github.com/repos/pzs-ng/pzs-ng/issues/30/comments","events_url":"https://api.github.com/repos/pzs-ng/pzs-ng/issues/30/events","html_url":"https://github.com/pzs-ng/pzs-ng/issues/30","id":301036885,"number":30,"title":"Headdata.lock and rescan issue","user":{"login":"teqnodude","id":36924638,"avatar_url":"https://avatars0.githubusercontent.com/u/36924638?v=4","gravatar_id":"","url":"https://api.github.com/users/teqnodude","html_url":"https://github.com/teqnodude","followers_url":"https://api.github.com/users/teqnodude/followers","following_url":"https://api.github.com/users/teqnodude/following{/other_user}","gists_url":"https://api.github.com/users/teqnodude/gists{/gist_id}","starred_url":"https://api.github.com/users/teqnodude/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/teqnodude/subscriptions","organizations_url":"https://api.github.com/users/teqnodude/orgs","repos_url":"https://api.github.com/users/teqnodude/repos","events_url":"https://api.github.com/users/teqnodude/events{/privacy}","received_events_url":"https://api.github.com/users/teqnodude/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":8,"created_at":"2018-02-28T14:07:52Z","updated_at":"2018-03-05T19:05:25Z","closed_at":null,"author_association":"NONE","body":"I get this problem every now and then on some but not all releases on a site and it happens regardless of the size of files involved. What I have to do to correct this problem is to do \"killall rescan\" and remove both headdata and headdata.lock from the pzs-ng folder. Do any of you have an idea how to solve this? I've tried to recompile and used various settings like ignore_lock_timeout <TRUE|FALSE> but the problem still remains. \r\n\r\n> git-master-a8a5fa23 - rescan: Creating directory to store racedata in\r\n> git-master-a8a5fa23 - rescan: Locking release\r\n> git-master-a8a5fa23 - create_lock: lock active - putting you in queue. (0/2)\r\n> git-master-a8a5fa23 - rescan: Failed to lock release.\r\n> git-master-a8a5fa23 - rescan: sleeping for .1 second before trying to get a lock (queue: 1).\r\n> git-master-a8a5fa23 - create_lock: link failed (1/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (2/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (3/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (4/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (5/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (6/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (7/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (8/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (9/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (10/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed: Operation not permitted\r\n> git-master-a8a5fa23 - rescan: sleeping for .1 second before trying to get a lock (queue: 1).\r\n> git-master-a8a5fa23 - create_lock: link failed (1/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (2/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (3/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (4/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (5/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (6/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (7/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (8/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (9/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed (10/10) - sleeping .1 seconds: File exists\r\n> git-master-a8a5fa23 - create_lock: link failed: Operation not permitted\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/pzs-ng/pzs-ng/issues/comments/370527400","html_url":"https://github.com/pzs-ng/pzs-ng/issues/30#issuecomment-370527400","issue_url":"https://api.github.com/repos/pzs-ng/pzs-ng/issues/30","id":370527400,"user":{"login":"Skeddie","id":2313209,"avatar_url":"https://avatars1.githubusercontent.com/u/2313209?v=4","gravatar_id":"","url":"https://api.github.com/users/Skeddie","html_url":"https://github.com/Skeddie","followers_url":"https://api.github.com/users/Skeddie/followers","following_url":"https://api.github.com/users/Skeddie/following{/other_user}","gists_url":"https://api.github.com/users/Skeddie/gists{/gist_id}","starred_url":"https://api.github.com/users/Skeddie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Skeddie/subscriptions","organizations_url":"https://api.github.com/users/Skeddie/orgs","repos_url":"https://api.github.com/users/Skeddie/repos","events_url":"https://api.github.com/users/Skeddie/events{/privacy}","received_events_url":"https://api.github.com/users/Skeddie/received_events","type":"User","site_admin":false},"created_at":"2018-03-05T19:05:25Z","updated_at":"2018-03-05T19:05:25Z","author_association":"MEMBER","body":"And can you look in the debug files for those two locked subdirs for the pid's mentioned (13389 and 21112). The pid in the debug files is the number between the date and the \"git-master-abcdef09\" version number. Or provide the debugfiles again."}}
{"actor":{"display_login":"Skeddie"}}