exit code: 99 (0x63)
![Venturini Dario[VENETO]](https://einsteinathome.org/sites/default/files/68470_6.jpg?1470249932 "Venturini Dario[VENETO]")
17 Oct 2008 16:26:00 UTC
Topic 193982
(moderation:
All my last WUs ended up with that exit code (invalid).
Task details can be seen for the following task: 107925387
Anyone knows what that means?
P.S. I started Einstein again after 1-2 months of inactivity. The only change was BOINC version, changed from 5.10.45 to 6.3.14.
exit code: 99 (0x63)
)
Hi Dario!
Is it possible that the Linux Kernel on that machine was updated in between? There is a Linux Kernel bug that can cause this kind of errors.
What Linux distribution are you using?
CU
Bikeman
Ehi there man! Well, for
)
Ehi there man!
Well, for sure I didn't update the kernel during 6 different WUs (the ones that risulted invalid).
I also didn't update it at all (as far as I remember). I installed some updates though, which could have touched the kernel, but they were not "kernel version update"
I probably didn't reboot after installing them.
I'm using Ubuntu 64bit, with the ia32-libs packet installed.
I'll try to run 1-2 more Einstein WUs to see if it was those updates causing the errors (I rebooted 5 minutes ago)
RE: Ehi there man! Well,
)
I meant whether you might have updated the kernel during the time between your last successful E@H run (as you wrote this was some time ago) and the current problems.
CU
Bikeman
Try to reset the project,
)
Try to reset the project, hopefully forcing it to download a new data file.
RE: RE: Ehi there
)
Ah. Sure I did. So... what to do now?
Btw, resetting didn't help. I tried another WU and it failed
RE: RE: RE: Ehi there
)
To find out whether your Linux kernel may be affected by this particular bug, please do the following (copy-and-paste to a shell will work best):
cd /usr/src
cd linux-headers-`uname -a | cut -f3 -d\ `
grep CONFIG_PREEMPT .config
The output should tell whether the kernel variable "CONFIG_PREEMPT" is set to "y" or not. If it's set to "y" then it's likely that this particular kernel bug is to blame and there's little that can be done, except waiting for a kernel update.
Otherwise we have to look further for the reason of your problem.
CU
Bikeman
RE: RE: RE: RE: Ehi
)
Hmmmm....that seems to
)
Hmmmm....that seems to indicate the kernel bug is not affecting your kernel.
RE: Hmmmm....that seems to
)
Ok. Any indication?
I'm ready to test weird solutions if you need
You could try to detach from
)
You could try to detach from and reattach to Einstein, see if that gives you a whole new datafile to play with. But with the new back-end being more stable every update, I doubt it, you may well get the one (or ones) you have resent on the same hostID.