Okay, so we just got dug, and DSource has been down for more than a week. Does anyone else see the problem here? People will be turning away as I write this because the main repository of open source development in D has a "FATAL: connection limit exceeded for non-superusers" message on the front page.

While I appreciate the work done to create and maintain dsource.org, a week is not acceptable. I would be happy to help in any capacity to get even a mirror up asap.

Kyle Furlong wrote:
> Okay, so we just got dug, and DSource has been down for more than a week. Does anyone else see the problem here? People will be turning away as I write this because the main repository of open source development in D has a "FATAL: connection limit exceeded for non-superusers" message on the front page.
> 
> While I appreciate the work done to create and maintain dsource.org, a week is not acceptable. I would be happy to help in any capacity to get even a mirror up asap.

digitalmars.com saw roughly a 6 fold increase in traffic yesterday.

Walter Bright wrote:
> Kyle Furlong wrote:
>> Okay, so we just got dug, and DSource has been down for more than a week. Does anyone else see the problem here? People will be turning away as I write this because the main repository of open source development in D has a "FATAL: connection limit exceeded for non-superusers" message on the front page.
>>
>> While I appreciate the work done to create and maintain dsource.org, a week is not acceptable. I would be happy to help in any capacity to get even a mirror up asap.
> 
> digitalmars.com saw roughly a 6 fold increase in traffic yesterday.

Thats exciting, but what does that have to do with the fact that dsource has been down for much longer than just yesterday? It would have been nice to have some of that increased traffic funneled to a working dsource. What we got is in essence a PR disaster.

Kyle Furlong wrote:

> Walter Bright wrote:
>> Kyle Furlong wrote:
>>> Okay, so we just got dug, and DSource has been down for more than a week. Does anyone else see the problem here? People will be turning away as I write this because the main repository of open source development in D has a "FATAL: connection limit exceeded for non-superusers" message on the front page.
>>>
>>> While I appreciate the work done to create and maintain dsource.org, a week is not acceptable. I would be happy to help in any capacity to get even a mirror up asap.
>> 
>> digitalmars.com saw roughly a 6 fold increase in traffic yesterday.
> 
> Thats exciting, but what does that have to do with the fact that dsource has been down for much longer than just yesterday? It would have been nice to have some of that increased traffic funneled to a working dsource. What we got is in essence a PR disaster.

The problems Dsource is having is not really traffic related (although high traffic don't help), it is a technical problem in Trac wherein it don't release it's db connections the way it should. You might help resolve the problem by finding out where in the Trac/Python code the problem is, I know Brad would be very happy to find it.

Lars Ivar Igesund wrote:

> The problems Dsource is having is not really traffic related (although high traffic don't help), it is a technical problem in Trac wherein it don't release it's db connections the way it should. You might help resolve the problem by finding out where in the Trac/Python code the problem is, I know Brad would be very happy to find it.

Has this already been fixed in the 0.10dev version of trac?

-- 
Jari-Matti

Kyle Furlong wrote:
> Okay, so we just got dug, and DSource has been down for more than a week. Does anyone else see the problem here? People will be turning away as I write this because the main repository of open source development in D has a "FATAL: connection limit exceeded for non-superusers" message on the front page.
> 
> While I appreciate the work done to create and maintain dsource.org, a week is not acceptable. I would be happy to help in any capacity to get even a mirror up asap.

Has it been down for a week? I remember navigating dsource a few days ago and it was working!

Hasan Aljudy wrote:

> Kyle Furlong wrote:
>> Okay, so we just got dug, and DSource has been down for more than a week. Does anyone else see the problem here? People will be turning away as I write this because the main repository of open source development in D has a "FATAL: connection limit exceeded for non-superusers" message on the front page.
>> 
>> While I appreciate the work done to create and maintain dsource.org, a week is not acceptable. I would be happy to help in any capacity to get even a mirror up asap.
> 
> Has it been down for a week? I remember navigating dsource a few days ago and it was working!

No, it hasn't been down at all, in the correct way of speech, but the Trac part of the site that use the underlying database, causes connection leaks that makes those pages inaccesible until they are cleaned up. At that point it also affects the forums. The connections also cause some thrashing, meaning that svn may or may not be somewhat accesible too, but in general, svn has been mostly unaffected.

Jari-Matti Mäkelä wrote:

> Lars Ivar Igesund wrote:
> 
>> The problems Dsource is having is not really traffic related (although high traffic don't help), it is a technical problem in Trac wherein it don't release it's db connections the way it should. You might help resolve the problem by finding out where in the Trac/Python code the problem is, I know Brad would be very happy to find it.
> 
> Has this already been fixed in the 0.10dev version of trac?
> 

AFAIK, DSource is one of very few Trac enabled sites using Postgres as it's DB backend. Apparently there are no similar problems with the default SQLite backend. Therefore it has been somewhat difficult getting those who know the code best to look at it.

Lars Ivar Igesund says...
>
>No, it hasn't been down at all, in the correct way of speech, but the Trac part of the site that use the underlying database, causes connection leaks that makes those pages inaccesible until they are cleaned up. At that point it also affects the forums. The connections also cause some thrashing, meaning that svn may or may not be somewhat accesible too, but in general, svn has been mostly unaffected.

May be this can be temporary solved by setting low connection timeout...?

lightoze wrote:
> Lars Ivar Igesund says...
>> No, it hasn't been down at all, in the correct way of speech, but the Trac
>> part of the site that use the underlying database, causes connection leaks
>> that makes those pages inaccesible until they are cleaned up. At that point
>> it also affects the forums. The connections also cause some thrashing,
>> meaning that svn may or may not be somewhat accesible too, but in general,
>> svn has been mostly unaffected.
> 
> May be this can be temporary solved by setting low connection timeout...?
> 
> 

or use the SQLite backend?