Mailing List Archive

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Changes (by anonymous):

* cc: jouvin@lal.in2p3.fr (added)
* milestone: => 0.10
* version: 0.9.6 => devel

Comment:

Sorry for entering the wrong version... In fact this issue already
happened in the source browser in 0.9.x...

--
Ticket URL: <http://projects.edgewall.com/trac/ticket/3369>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
Trac-Tickets@lists.edgewall.com
http://lists.edgewall.com/mailman/listinfo/trac-tickets

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by mgood):

Can you retest this since r3677 and r3678? There were a couple updates to
the FastCGI stuff there which may have fixed this.

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:2>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Changes (by Russell Hind <rhind@mac.com>):

* cc: rhind@mac.com (added)

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:3>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by jouvin@lal.in2p3.fr):

I just retested with r3692. The problem is still there... First time after
starting the fcgi (Apache restart). Retrying one minute later it works.
The same for every potentially long operation (e.g. repository browsing in
a branch with many child). The associated error in Apache log file is :

{{{
[Wed Sep 06 10:53:19 2006] [error] [client 134.158.88.66] FastCGI: comm
with server "/htdocs/tractest/bin/trac.fcgi" aborted: idle timeout (30
sec)
[Wed Sep 06 10:53:19 2006] [error] [client 134.158.88.66] FastCGI:
incomplete headers (0 bytes) received from server
"/htdocs/tractest/bin/trac.fcgi"
}}}

I didn't find any way to increase the timeout.

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:4>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by jouvin@lal.in2p3.fr):

Previously, I missed that there was a traceback in the Apache main error
log file. Here it is :

{{{
Unhandled exception in thread started by <bound method Connection.run of
<trac.web._fcgi.Connection object at 0x1404c9d90>>
Traceback (most recent call last):
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 654, in run
self.process_input()
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 690, in process_input
self._do_params(rec)
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 789, in _do_params
self._start_request(req)
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 773, in _start_request
req.run()
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 582, in run
self._flush()
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 589, in _flush
self.stdout.close()
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 348, in close
self._conn.writeRecord(rec)
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 705, in writeRecord
rec.write(self._sock)
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 542, in write
self._sendall(sock, header)
File "/www/Web/servers/trac/0.10b1-3692/lib/python2.4/site-
packages/trac/web/_fcgi.py", line 519, in _sendall
sent = sock.send(data)
socket.error: (32, 'Broken pipe')

}}}

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:5>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by mgood):

Replying to [comment:5 jouvin@lal.in2p3.fr]:
> Previously, I missed that there was a traceback in the Apache main error
log file. Here it is :
...snip...
> socket.error: (32, 'Broken pipe')

This just means that Apache killed the socket, so when Trac is trying to
respond it can't. When this happens, there's nothing to be done on the
Trac side.

You can set the timeout in the
[http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html#FastCgiConfig
FastCgiConfig] or
[http://www.fastcgi.com/mod_fastcgi/docs/mod_fastcgi.html#FastCgiServer
FastCgiServer] directives with the option `-appConfigTimeout`.

Try increasing the timeout to give the process some more time to start up.

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:6>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by jouvin@lal.in2p3.fr):

Thanks for the advice. In fact, the FastCgiServer option is `-idle-
timeout` instead of `-appConfigTimeout` (this one doesn't exist and
`-appConnTimeout`is not recommended).

I had to increase the timeout from 30s to 180s to have the project index
working properly (120s was not enough). This looks surprising to me. The
server running Trac is quite heavily loaded but still seems quite
excessive.

I would say the main last changes are that quite a significant number of
users started to use RSS reader... I have the impression this leads to
Trac being being much less responsive... Does this make sense ?

BTW, what happens to other requests if trac.fcgi is busy during 3 minutes
building the process index. Are other requests processed in parallel or
are they waiting for the index to finish ?

Michel

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:7>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by mgood):

Replying to [comment:7 jouvin@lal.in2p3.fr]:
> I had to increase the timeout from 30s to 180s to have the project index
working properly (120s was not enough). This looks surprising to me. The
server running Trac is quite heavily loaded but still seems quite
excessive.

Yes, this does seem quite long. I'm running Trac on a shared host and
have not had problems with the startup time. There may be a way to trace
the Trac process to see if there's some operation in the startup that's
hanging, but I don't have any good advice on how to do that.

> I would say the main last changes are that quite a significant number of
users started to use RSS reader... I have the impression this leads to
Trac being being much less responsive... Does this make sense ?

"Good" RSS readers should default to only refreshing the feed once an
hour. Unfortunately there are some that default to
[http://roland.entierement.nu/blog/2006/01/15/rss-aggregators-again.html
refreshing extremely frequently]. So you may want to check the server log
to see if there are some RSS readers overloading the site.

> BTW, what happens to other requests if trac.fcgi is busy during 3
minutes building the process index. Are other requests processed in
parallel or are they waiting for the index to finish ?

It shouldn't affect other requests.

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:8>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by anonymous):

Replying to [comment:8 mgood]:
> Yes, this does seem quite long. I'm running Trac on a shared host and
have not had problems with the startup time. There may be a way to trace
the Trac process to see if there's some operation in the startup that's
hanging, but I don't have any good advice on how to do that.

In fact we have 2 Trac "instances" running on the same host with separate
project areas. One instance has around 25 projects, the other one 3. And
the time to get the project index seems roughly proportional to the number
of project (at least it is much quicker to get the index for the 3
projects instance).

I upgraded to the last version of sqlite and pysql but it didn't change
anything.

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:9>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by mgood):

I'm going to push back the milestone since I don't think this will be
fixed for [milestone:0.10].

Replying to [comment:9 anonymous]:
> In fact we have 2 Trac "instances" running on the same host with
separate project areas. One instance has around 25 projects, the other one
3. And the time to get the project index seems roughly proportional to the
number of project (at least it is much quicker to get the index for the 3
projects instance).

Ok, that's helpful. Trac itself should be able to handle loading 25
projects fairly quickly. I just tested a directory here with 40 projects
and it loaded within a few seconds. However, you may have a plugin that
is slow doing the `environment_needs_upgrade` check. Can you provide a
list of the plugins you have installed?

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:10>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10.1
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Changes (by mgood):

* milestone: 0.10 => 0.10.1

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:11>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---

#3369: FastCGI : timeout during project index the first time after starting Trac
---------------------------------+------------------------------------------
Reporter: jouvin@lal.in2p3.fr | Owner: jonas
Type: defect | Status: new
Priority: normal | Milestone: 0.10.1
Component: general | Version: devel
Severity: normal | Resolution:
Keywords: |
---------------------------------+------------------------------------------
Comment (by anonymous):

I've also experienced this issue with just running "tracd", with Trac v
0.10

--
Ticket URL: <http://trac.edgewall.org/ticket/3369#comment:12>
The Trac Project <http://trac.edgewall.org/>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---