I raised the log level to debug:
./manage.py celeryd -l debug
That's the new piece of information:
Out of memory (Needed 24492 bytes)
Out of memory (Needed 24492 bytes)
Out of memory (Needed 24492 bytes)
Out of memory (Needed 24492 bytes)
Out of memory (Needed 24492 bytes)
Out of memory (Needed 24
Den 10/10/2010 kl. 17.55 skrev Massimiliano della Rovere:
> > * Which process(es) on the server is using 100% CPU time?
> directly from htop:
> PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command
> 544 mader 20 0 969M 953M 1444 R 96.0 47.4 50:09.85 python
> ./manage.py ce
On Sun, Oct 10, 2010 at 17:12, Erik Cederstrand wrote:
>
> * Are you keeping a connection open to MySQL the whole time?
I do not know what is the default behaviour of django, but I did not specify
any custom option.
> * What are the values of your timeout settings in the MySQL server
configuratio
Den 10/10/2010 kl. 16.34 skrev Massimiliano della Rovere:
> Using django 1.2.3 with celery 2.0.3 and django-celery 2.0.3 and mysql
> 5.1.41 on kubuntu 10.04, I receive the following error:
> OperationalError(2013, 'Lost connection to MySQL server during query').
>
> The error occurs every time t
Using django 1.2.3 with celery 2.0.3 and django-celery 2.0.3 and mysql
5.1.41 on kubuntu 10.04, I receive the following error:
OperationalError(2013, 'Lost connection to MySQL server during query').
The error occurs every time the task is executed and seems to be
related to the execution time, in
5 matches
Mail list logo
