From: Jose P. <jos...@gm...> - 2012-04-22 01:49:10
|
Hi guys, Does anybody knows if something wrong with http://libusb.org/ ?? I got thi messages n my web browser 502 Bad Gateway ------------------------------ nginx/1.1.12 -- Saludos. Santiago 1:5 Y si alguno de vosotros tiene falta de sabiduría, pídala a Dios, el cual da a todos abundantemente y sin reproche, y le será dada. |
From: Xiaofan C. <xia...@gm...> - 2012-04-22 01:57:51
|
On Sun, Apr 22, 2012 at 9:49 AM, Jose Pablo <jos...@gm...> wrote: > Hi guys, > > Does anybody knows if something wrong with http://libusb.org/ ?? I got thi > messages n my web browser > > 502 Bad Gateway > > ________________________________ > nginx/1.1.12 > libusb.org has always been like this -- often down due to the (buggy? or bad? or just slow?) Trac git plugin. I would very much like to disable the Trac git plugin. However Peter mentioned to me that Trac git plugin is useful since it integrates closely with the Trac ticket system. In the mean time, you can see if libusbx MediaWiki can provide you similar information you want. If not, please let me know. I am an admin for both libusb Trac and libusbx Trac/MediaWiki. http://sourceforge.net/apps/mediawiki/libusbx/index.php?title=Main_Page -- Xiaofan |
From: Peter S. <pe...@st...> - 2012-04-22 14:09:08
|
Hi, Xiaofan Chen wrote: > > Does anybody knows if something wrong with http://libusb.org/ ?? > > I got thi messages n my web browser > > > > 502 Bad Gateway > > libusb.org has always been like this -- often down due to the > (buggy? or bad? or just slow?) Trac git plugin. Yes, all of the above. The problem is that the Trac Git plugin relies on executing many git processes on the server for every web page request to Trac, and the plugin doesn't always clean up correctly. This is not only horribly slow but of course leaks processes on the server. Previously there was no limit on the server for how many processes that could be running, and then the page would become unusably slow with 60 second timeouts after a while. I have more recently added a hard limit on processes, and when Trac has served sufficiently many requests this limit hits, and the web server directly responds with the 502 error, instead of the 60 second timeout. It's not good yet, but IMO it's better. For the immediate term I'm adding some monitoring on the server, to recover automatically from the error. Sorry I didn't think of doing that earlier. > I would very much like to disable the Trac git plugin. However > Peter mentioned to me that Trac git plugin is useful since it > integrates closely with the Trac ticket system. Yes, but at the same time I really like your idea to disable the plugin because it has such a bad impact on visiting the site. //Peter |