Forums

My bash file run was killed with 11429. What does this mean?

11429 was probably your process's pid (process-id). I don't think it's an error code that explains why it was killed.

There are a couple of reasons your process might be killed by our systems. Both of these should be very rare occurrences:

• if it exceeds our soft limit on RAM, which is current 3GB
• if your processes are in the tarpit for too long, and if you've exceeded your CPU quota by a large amount

how long is consider in tarpit for too long?

The conditions you mentioned will be the same if it is a paid account? I mean even with a paid account, I may exceeded the limit to tarpit

Hi there,

We almost never kill paid users processes for being in the tarpit, but if you exceed your quota by more than 10 times, we still reserve the right to kill it.

We also sometimes need to restart the servers for maintenance. If you're looking for a solution for "long-running" or "alway-on" processes, take a look at this page: https://help.pythonanywhere.com/pages/LongRunningTasks

I have upgraded to paid account. However, the same script run fine in bash but still stopped in schedule tasks.It is running for two hours plus only. What is the reason?

Hi vinus,

Did you see how the long running task sets a lock and then re-runs say every hour or so to restart the task if it ever stops?

I believe that for paid accounts you can expect something like 6-12 hours of running time, but your scripts may be killed for maintenance afterwards. (the key is to setup the long running task as described)