Message from discussion
Rhodecode hangs every day since 1.3 upgrade
Received: by 10.52.72.230 with SMTP id g6mr14706637vdv.5.1331528665267;
Sun, 11 Mar 2012 22:04:25 -0700 (PDT)
X-BeenThere: rhodecode@googlegroups.com
Received: by 10.52.73.134 with SMTP id l6ls6405301vdv.7.gmail; Sun, 11 Mar
2012 22:04:24 -0700 (PDT)
Received: by 10.52.100.167 with SMTP id ez7mr1212973vdb.13.1331528664873;
Sun, 11 Mar 2012 22:04:24 -0700 (PDT)
Date: Sun, 11 Mar 2012 22:04:24 -0700 (PDT)
From: Marcin Kuzminski <marcin...@gmail.com>
To: rhodecode@googlegroups.com
Message-ID: <4229770.506.1331528664381.JavaMail.geo-discussion-forums@vbai14>
In-Reply-To: <5399166.3293.1331431905999.JavaMail.geo-discussion-forums@vbas10>
References: <21036321.21.1331170658153.JavaMail.geo-discussion-forums@vbla14>
<1420546.5.1331424641500.JavaMail.geo-discussion-forums@vbnd9>
<5399166.3293.1331431905999.JavaMail.geo-discussion-forums@vbas10>
Subject: Re: Rhodecode hangs every day since 1.3 upgrade
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_Part_504_6238301.1331528664378"
------=_Part_504_6238301.1331528664378
Content-Type: multipart/alternative;
boundary="----=_Part_505_23087266.1331528664379"
------=_Part_505_23087266.1331528664379
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
change the level of handlers to DEBUG, there are just two handlers
[handler_console]
class = StreamHandler
args = (sys.stderr,)
level = INFO <----------change this to DEBUG
formatter = generic
On Sunday, March 11, 2012 4:11:45 AM UTC+2, Frederic Latour wrote:
>
> I haven't any repository that have statistic enabled...
> As a matter of fact I didn't change anything apart from upgrading... 1.2.x
> was working like a charm.
>
> Don't know anything about python.
> Would you mind clarifying which file exactly I must modify? production.ini?
>
> If so, I don't even understand how LOGGERS with INFO levels are displayed
> from what I'm seeing in the production.ini.
> Care to describe what I need to change in the file?
>
> Where am I supposed to get some log file?
> Thanks
>
>
> On Sunday, March 11, 2012 1:10:41 AM UTC+1, Marcin Kuzminski wrote:
>>
>> I recommend turning DEBUG logleve and check what's going on there that
>> the tasks can take so long. (my first guess statistics ?)
>>
>> enable detailed debug
>> ---------------------
>>
>> RhodeCode uses standard python logging modules to log it's output.
>> By default only loggers with INFO level are displayed. To enable full
>> output
>> change `level = DEBUG` in .ini file for all logging handlers. After this
>> you
>> can check much more detailed output of actions happening on RhodeCode
>> system.
>>
>>
>>
>> On Thursday, March 8, 2012 3:37:38 AM UTC+2, Frederic Latour wrote:
>>>
>>> I had an 1.2 rhodecode installation working fine on Windows 2008 R2.
>>> Since I upgraded to 1.3 the server hangs everyday. My only solution is
>>> to restart it.
>>>
>>> Here are the information I get in the command windows when the server
>>> locks down:
>>> 2012-03-08 00:54:54.572 INFO [paste.httpserver.ThreadPool] No idle
>>> tasks, and only 0 busy tasks; adding 5 more workers
>>> 2012-03-08 00:54:54.657 INFO [rhodecode.lib.auth] user jenkins_user
>>> authenticated correctly
>>> 2012-03-08 00:56:54.315 INFO [paste.httpserver.ThreadPool] Culling 20
>>> extra workers (4 idle workers present)
>>> 2012-03-08 01:00:54.795 INFO [paste.httpserver.ThreadPool] No idle
>>> tasks, and only 0 busy tasks; adding 5 more workers
>>> 2012-03-08 01:00:54.806 WARNI [paste.httpserver.ThreadPool] Thread 1896
>>> hung (working on task for 2396 seconds)
>>>
>>> No need to say this is really annoying.
>>> Any ideas? Anything I can test?
>>>
>>
------=_Part_505_23087266.1331528664379
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
change the level of handlers to DEBUG, there are just two handlers<br><br>[=
handler_console]<br>class =3D StreamHandler<br>args =3D (sys.stderr,)<br>le=
vel =3D INFO <----------change this to DEBUG<br>formatter =3D generic<br=
><br><br>On Sunday, March 11, 2012 4:11:45 AM UTC+2, Frederic Latour wrote:=
<blockquote class=3D"gmail_quote" style=3D"margin: 0;margin-left: 0.8ex;bor=
der-left: 1px #ccc solid;padding-left: 1ex;">I haven't any repository that =
have statistic enabled...<div>As a matter of fact I didn't change anything =
apart from upgrading... 1.2.x was working like a charm.</div><div><br></div=
><div>Don't know anything about python.</div><div>Would you mind clarifying=
which file exactly I must modify? production.ini?</div><div><br></div><div=
>If so, I don't even understand how LOGGERS with INFO levels are displayed =
from what I'm seeing in the production.ini.</div><div>Care to describe what=
I need to change in the file?</div><div><br></div><div>Where am I supposed=
to get some log file?</div><div>Thanks</div><div><br></div><div><br>On Sun=
day, March 11, 2012 1:10:41 AM UTC+1, Marcin Kuzminski wrote:<blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0;margin-left:0.8ex;border-left:1px #cc=
c solid;padding-left:1ex">I recommend turning DEBUG logleve and check what'=
s going on there that the tasks can take so long. (my first guess statistic=
s ?)<br><br>enable detailed debug<br>---------------------<br><br>RhodeCode=
uses standard python logging modules to log it's output.<br>By default onl=
y loggers with INFO level are displayed. To enable full output<br>change `l=
evel =3D DEBUG` in .ini file for all logging handlers. After this you<br>ca=
n check much more detailed output of actions happening on RhodeCode system.=
<br><br><br><br>On Thursday, March 8, 2012 3:37:38 AM UTC+2, Frederic Latou=
r wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0;margin-left:0.8=
ex;border-left:1px #ccc solid;padding-left:1ex">I had an 1.2 rhodecode inst=
allation working fine on Windows 2008 R2.<div>Since I upgraded to 1.3 the s=
erver hangs everyday. My only solution is to restart it.</div><div><br></di=
v><div>Here are the information I get in the command windows when the serve=
r locks down:</div><div><div>2012-03-08 00:54:54.572 INFO [paste.http=
server.ThreadPool] No idle tasks, and only 0 busy tasks; adding 5 more work=
ers</div><div>2012-03-08 00:54:54.657 INFO [rhodecode.lib.auth] user =
jenkins_user authenticated correctly</div><div>2012-03-08 00:56:54.315 INFO=
[paste.httpserver.ThreadPool] Culling 20 extra workers (4 idle worke=
rs present)</div><div>2012-03-08 01:00:54.795 INFO [paste.httpserver.=
ThreadPool] No idle tasks, and only 0 busy tasks; adding 5 more workers</di=
v><div>2012-03-08 01:00:54.806 WARNI [paste.httpserver.ThreadPool] Thread 1=
896 hung (working on task for 2396 seconds)</div></div><div><br></div><div>=
No need to say this is really annoying.</div><div>Any ideas? Anything I can=
test?</div></blockquote></blockquote></div></blockquote>
------=_Part_505_23087266.1331528664379--
------=_Part_504_6238301.1331528664378--