Track down error --- pid 53509 (python), uid 0: exited on signal 11

[anika200]

I get 25 or so of these siginit errors reported every night and have a couple of questions.

Is there a way for me to easily track down the process or module that is causing the error? Most of the pid in that range are owned by 40002.
How many other users on 8.3.1 seeing these kind of errors?

Is anyone in FreeNAS development aware of the problem already or is there a bugzilla/mailing list I can search?

 

[James]

Signal 11 is often a hardware (usually bad RAM) error. You can search the bug tracking system at support.freenas.org.

 

[anika200]

Hi, Thanks for the reply. I am going to check on the ram right now.
I have also been checking out some other signal 11 python errors and it seems it could also be a software problem. This is why I asked if anyone else is seeing the problem. Since no one else has reported any issue I guess I am on my own.

 

[anika200]

making progress..... There was a "Turbo Memory" setting flipped on in the system BIOS. I switched it off and now only have three errors for 12hrs instead of 25 or so.

 

[warri]

Three errors are still three too many. If they don't disappear better try a new RAM module or you could end up corrupting your data.

 

[anika200]

Three errors are still three too many. If they don't disappear better try a new RAM module or you could end up corrupting your data.

You guys were right of course, It was one module of bad memory. Corsair failed but the Kingston stick is still good. Thanks for the help. :)