Not possible to recover from "unable to parse account file"

Message boards : Questions and problems : Not possible to recover from "unable to parse account file"
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Joseph Stateson
Volunteer tester
Avatar

Send message
Joined: 27 Jun 08
Posts: 641
United States
Message 111007 - Posted: 6 Feb 2023, 16:15:05 UTC
Last modified: 6 Feb 2023, 16:20:13 UTC

I had a video card overheat and freeze the system. The card problem was fixed but after booting up the message log shows the unable to parse message for both the milkyway account and statistics xml files.

In addition, there were 900 messages about "project not in state file". I assume one message for each of the 900 jobs waiting to run. The Milkyway job "txt" file was 43 mb in size.

Both those xml files were empty although their size was not 0. Since the account files for milkyway are identical on all my systems, I copied over both an account file and a statistics file to replace the corrupted files.

Although this "worked", all 900 jobs were marked as "abandoned" on the server and another 900 were downloaded. By "worked" I mean I did not have to delete the project and reattach it to fix the corrupted files

There must have been more files corrupted other than the account and statistics.
I am not sure why the account files was being re-written since it never changes unless the project changes their html. It seems to me the account file should be opened in read only mode. I am guessing it was opened in read-write mode and was still open when the graphics board hung. The account and statistics file for wuprop was also corrupted. I did not bother to copy those files over and the project disappeared completely after rebooting. I will have to add that project back in if I want it unlike milkyway.

Since the 900 files were "abandoned" I assume they cannot be re-sent as a "ghost task"
I am tempted to have the OS set the attribute of the account file to be read-only to prevent it from being corrupted.
ID: 111007 · Report as offensive

Message boards : Questions and problems : Not possible to recover from "unable to parse account file"

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.