I have confirmed that the signal involved is SIGKILL and, yes,
apparently OS is simply running out of memory.
Thank you all, again!
Best Regards,
Janis
--
http://mail.python.org/mailman/listinfo/python-list
Janis janis.vik...@gmail.com writes:
I have confirmed that the signal involved is SIGKILL and, yes,
apparently OS is simply running out of memory.
This is the notorious OOM killer, sigh. There are some links from
http://en.wikipedia.org/wiki/OOM_Killer
--
Hello!
I have this problem with my script exiting randomly with Linux OS
status code -9 (most often) or -15 (also sometimes, but much more
rarely). As far as I understand -9 corresponds to Bad file descriptor
and -15 Block device required.
1) Is there a way how I could find out what exactly
On 4/9/2012 5:01 AM, Janis wrote:
I have this problem with my script exiting randomly with Linux OS
status code -9 (most often) or -15 (also sometimes, but much more
rarely). As far as I understand -9 corresponds to Bad file descriptor
and -15 Block device required.
1) Is there a way how I
Janis janis.vik...@gmail.com writes:
I have this problem with my script exiting randomly with Linux OS
status code -9 (most often) or -15 (also sometimes, but much more
rarely). As far as I understand -9 corresponds to Bad file descriptor
and -15 Block device required.
How do you get -9 and
On 4/9/2012 3:47 AM Alain Ketterlin said...
Janisjanis.vik...@gmail.com writes:
I have this problem with my script exiting randomly with Linux OS
status code -9 (most often) or -15 (also sometimes, but much more
rarely).
snip
My guess is that your script hits a limit, e.g., number of open
On Apr 9, 6:47 am, Alain Ketterlin al...@dpt-info.u-strasbg.fr
wrote:
Janis janis.vik...@gmail.com writes:
I have this problem with my script exiting randomly with Linux OS
status code -9 (most often) or -15 (also sometimes, but much more
rarely). As far as I understand -9 corresponds to
On Apr 9, 6:01 am, Janis janis.vik...@gmail.com wrote:
Hello!
I have this problem with my script exiting randomly with Linux OS
status code -9 (most often) or -15 (also sometimes, but much more
rarely). As far as I understand -9 corresponds to Bad file descriptor
and -15 Block device
Thank you all for the help! I will need to think a bit about the other
suggestions.
But, Alan, as to this:
How do you get -9 and -15? Exit status is supposed to be between 0 and
127.
I have the following code that has caught these:
p = subprocess.Popen([Config.PYTHON_EXE,'Load.py',%s %
On 09/04/2012 11:01, Janis wrote:
cut weird exit codes
My experience is that these kind of behaviors are observed when (from
most to least likeliness):
- Your kernel barfs on a limit, e.g. space/inodes/processes/memory/etc.
- You have a linked library mismatch
- You have bit rot on your system
You might try running your Python process with:
strace -f -s 1024 -o /tmp/script.strace python /path/to/script.py
Then you (perhaps with a C programmer) can likely track down what happened
right before the crash by examining the system call tracer near the end of
the file.
On 09Apr2012 12:02, Janis janis.vik...@gmail.com wrote:
| Thank you all for the help! I will need to think a bit about the other
| suggestions.
|
| But, Alan, as to this:
| How do you get -9 and -15? Exit status is supposed to be between 0 and
| 127.
|
| I have the following code that has
12 matches
Mail list logo
