{"action":"created","issue":{"url":"https://api.github.com/repos/FoldingAtHome/fah-client-pub/issues/1165","repository_url":"https://api.github.com/repos/FoldingAtHome/fah-client-pub","labels_url":"https://api.github.com/repos/FoldingAtHome/fah-client-pub/issues/1165/labels{/name}","comments_url":"https://api.github.com/repos/FoldingAtHome/fah-client-pub/issues/1165/comments","events_url":"https://api.github.com/repos/FoldingAtHome/fah-client-pub/issues/1165/events","html_url":"https://github.com/FoldingAtHome/fah-client-pub/issues/1165","id":153624225,"number":1165,"title":"FAHClient hangs","user":{"login":"bb30994","id":5483435,"avatar_url":"https://avatars.githubusercontent.com/u/5483435?v=3","gravatar_id":"","url":"https://api.github.com/users/bb30994","html_url":"https://github.com/bb30994","followers_url":"https://api.github.com/users/bb30994/followers","following_url":"https://api.github.com/users/bb30994/following{/other_user}","gists_url":"https://api.github.com/users/bb30994/gists{/gist_id}","starred_url":"https://api.github.com/users/bb30994/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bb30994/subscriptions","organizations_url":"https://api.github.com/users/bb30994/orgs","repos_url":"https://api.github.com/users/bb30994/repos","events_url":"https://api.github.com/users/bb30994/events{/privacy}","received_events_url":"https://api.github.com/users/bb30994/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2016-05-07T23:28:48Z","updated_at":"2016-05-09T03:47:57Z","closed_at":null,"body":"Something strange is going on, and FAHClient enters a loop, consuming one CPU and preventing FAHControl from seeing updates to the log,\r\n\r\nThere is a high  probability that Project 116xx is putting something in the FAHCore's log that FAHClient cannot handle.  It's unclear whether this could/should be fixed in  either the Core or the Client.\r\n\r\nThe following characteristics are commonly observed::\r\n\r\n    FAH has just completed a 116xx WU.\r\n    Client processes the WU completion but then hangs\r\n    Fahcontrol locally or remotely cannot connect\r\n    No further messages are logged. The other FAH work units continue to be processed but even if they complete they are not uploaded.\r\n    If the client restarts they do not upload (in my experience), and simply start over folding from 0%.\r\n\r\nNote: Point 5 is most likely the known problem [#1166] where if a WU is interrupted after reaching 100% but before completing the tar/zip of the files, it cannot be resumed. There's no checkpoint-like recovery of a WU that will restart the tar/zip processing."},"comment":{"url":"https://api.github.com/repos/FoldingAtHome/fah-client-pub/issues/comments/217770636","html_url":"https://github.com/FoldingAtHome/fah-client-pub/issues/1165#issuecomment-217770636","issue_url":"https://api.github.com/repos/FoldingAtHome/fah-client-pub/issues/1165","id":217770636,"user":{"login":"bb30994","id":5483435,"avatar_url":"https://avatars.githubusercontent.com/u/5483435?v=3","gravatar_id":"","url":"https://api.github.com/users/bb30994","html_url":"https://github.com/bb30994","followers_url":"https://api.github.com/users/bb30994/followers","following_url":"https://api.github.com/users/bb30994/following{/other_user}","gists_url":"https://api.github.com/users/bb30994/gists{/gist_id}","starred_url":"https://api.github.com/users/bb30994/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bb30994/subscriptions","organizations_url":"https://api.github.com/users/bb30994/orgs","repos_url":"https://api.github.com/users/bb30994/repos","events_url":"https://api.github.com/users/bb30994/events{/privacy}","received_events_url":"https://api.github.com/users/bb30994/received_events","type":"User","site_admin":false},"created_at":"2016-05-09T03:47:57Z","updated_at":"2016-05-09T03:47:57Z","body":"OK, but somehow FAHClient should be able to insolate itself from whatever the FAHCore can  do before exiting.  How would a FILE_IO_ERROR during the core shutdown produce a loop in FAHClient without it being able to force the problematic code to abort so FAHClient, itself, can continue?.\r\n\r\n\r\nI see one case where the end of the cores logfile_01.txt looks like this:\r\n\r\nLeaving Run\r\n- Writing 16337025 bytes of core data to disk...\r\nDone: 16336513 -> 15971116 (compressed to 97.7 percent)\r\n  ... Done.\r\nError deleting frame files\r\n- Shutting down core\r\n\r\nFolding@home Core Shutdown: FILE_IO_ERROR\r\n"}}