How much memory do you have? can you check with top memory
consumption?
Do you cron jobs take long time?

On Feb 17, 10:45 am, LightOfMooN <[email protected]> wrote:
> if it runs with python web2py.py -i 127.0.0.1 -p 8000
> it works fine at once, and after minute:
>
> Exception in thread Thread-15:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/threading.py", line 532, in
> __bootstrap_inner
>     self.run()
>   File "/home/www-data/web2py/gluon/newcron.py", line 220, in run
>     shell=self.shell)
>   File "/usr/lib/python2.6/subprocess.py", line 633, in __init__
>     errread, errwrite)
>   File "/usr/lib/python2.6/subprocess.py", line 1049, in
> _execute_child
>     self.pid = os.fork()
> OSError: [Errno 12] Cannot allocate memory
>
> If it runs with
> sudo -u www-data nohup python web2py.py -i 127.0.0.1 -p 8000
> or nohup ./web2py.py
> it also works fine once, and not even more.
>
> There is error in nohup.out:
>
> web2py Enterprise Web Framework
> Created by Massimo Di Pierro, Copyright 2007-2011
> Version 1.92.1 (2011-02-16 15:04:40)
> Database drivers available: SQLite3, pymysql, PostgreSQL
> Starting hardcron...
> choose a password:Traceback (most recent call last):
>   File "web2py.py", line 19, in <module>
>     gluon.widget.start(cron=True)
>   File "/home/www-data/web2py/gluon/widget.py", line 860, in start
>     options.password = raw_input('choose a password:')
> IOError: [Errno 9] Bad file descriptor
>
> so I tried to run it with -a "mypassword"
> and have again the same error in nohup.out:
>
> Exception in thread Thread-15:
> Traceback (most recent call last):
>   File "/usr/lib/python2.6/threading.py", line 532, in
> __bootstrap_inner
>     self.run()
>   File "/home/www-data/web2py/gluon/newcron.py", line 220, in run
>     shell=self.shell)
>   File "/usr/lib/python2.6/subprocess.py", line 633, in __init__
>     errread, errwrite)
>   File "/usr/lib/python2.6/subprocess.py", line 1049, in
> _execute_child
>     self.pid = os.fork()
> OSError: [Errno 12] Cannot allocate memory

Reply via email to