An exit code of 99 means that the App terminated due to a failing internal sanity check. There should be a dump of a "status structure", similar to a stack dump, at the end of stderr_out, indicating the check that failed.
The most common cause of an error of this type is present when the following lines are found at the end of the dump:
[...] Status code 3: Incorrect header in file
[...] function LALSFTdataFind, file SFTfileIO.c, line 270
This means that a data file the App is trying to access has a broken header signature. The md5 checksum of downloaded files is checked by the BOINC Core Client only after downloading, so it might be that at some later point the file went bad on the disk. The fact that it has "cured itself" might be due to that you recently got work that doesn't require this particular file anymore.
There is a chance, though, that something else (I don't know of yet) is going wrong during accessing the file (e.g. it is blocked by a virus scanner) that the boinc_fopen() function that we are using doesn't catch.
Akos, what are the last few lines of stderr_out of the results in question? What other tools accessing the filesystem (virus scanner, malware removal etc.) are you using?
BTW: Anyone knows if the standard Microsoft Malware removal tool has any influence on BOINC Apps?
BTW: Anyone knows if the standard Microsoft Malware removal tool has any influence on BOINC Apps?
The one that you get on Microsoft Patchday? I never had any problems with it, but I guess if it would cause problems, they would kind of "stick out" statistically because most people will execute this tool automatically on MS Patchday, which is always a Wednesday, right? Might be worthwile to group errors by weekdays.
As to file corruption, the MD5 checksums are in client_state.xml, right? So one could check unless the file is now already deleted.
Good shots!
Akos, can you dig out the checksums from client_state.xml and check your data files? There's probably a simple too for Windows that does this (I usually use md5sum from Cygwin).
An exit code of 99 means that
)
An exit code of 99 means that the App terminated due to a failing internal sanity check. There should be a dump of a "status structure", similar to a stack dump, at the end of stderr_out, indicating the check that failed.
The most common cause of an error of this type is present when the following lines are found at the end of the dump:
[...] Status code 3: Incorrect header in file
[...] function LALSFTdataFind, file SFTfileIO.c, line 270
This means that a data file the App is trying to access has a broken header signature. The md5 checksum of downloaded files is checked by the BOINC Core Client only after downloading, so it might be that at some later point the file went bad on the disk. The fact that it has "cured itself" might be due to that you recently got work that doesn't require this particular file anymore.
There is a chance, though, that something else (I don't know of yet) is going wrong during accessing the file (e.g. it is blocked by a virus scanner) that the boinc_fopen() function that we are using doesn't catch.
Akos, what are the last few lines of stderr_out of the results in question? What other tools accessing the filesystem (virus scanner, malware removal etc.) are you using?
BTW: Anyone knows if the standard Microsoft Malware removal tool has any influence on BOINC Apps?
BM
BM
RE: RE: BTW: Anyone knows
)
Good shots!
Akos, can you dig out the checksums from client_state.xml and check your data files? There's probably a simple too for Windows that does this (I usually use md5sum from Cygwin).
BM
BM
Thanks for drawing my
)
Thanks for drawing my attention back to this one.
Pretty weird, the "Required frequency-bins" should be positive integers, but "[-8, 8]" is listed in most of these errors. Looking into it...
BM
BM
See here. BM
)
See here.
BM
BM