Hi,
Today, while accessing GDAL Trac, I've been experiencing random
errors about:
- database is locked
- Internal Server Error
Sometimes I can not even load Trac frontpage.
Are we suffering services overload?
Regards
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Mateusz Łoskot wrote:
Hi,
Today, while accessing GDAL Trac, I've been experiencing random
errors about:
- database is locked
- Internal Server ErrorSometimes I can not even load Trac frontpage.
Are we suffering services overload?
Mateusz,
I ran into the same, and logged into www.osgeo.org right afterwards. There was
little sign of system overload.
I *suspect* some robot did a huge request of some sort against Trac and
this locked the database for an extended period of time.
Generally speaking osgeo1 is not overly busy.
Best regards,
--
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
Frank Warmerdam pisze:
Mateusz Łoskot wrote:
Hi,
Today, while accessing GDAL Trac, I've been experiencing random
errors about:
- database is locked
- Internal Server ErrorSometimes I can not even load Trac frontpage.
Are we suffering services overload?
Mateusz,
I ran into the same, and logged into www.osgeo.org right afterwards. There was
little sign of system overload.I *suspect* some robot did a huge request of some sort against Trac and
this locked the database for an extended period of time.Generally speaking osgeo1 is not overly busy.
Frank,
Thanks for the info.
I will report only if I observe services unavailability for an hour or more. But if its randomly down for only a few minutes, then I should ignore it.
Greetings
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Hi Mateusz,
On Mon, Jul 21, 2008 at 10:23:11PM +0200, Mateusz Å?oskot wrote:
I will report only if I observe services unavailability for an hour or
more. But if its randomly down for only a few minutes, then I should
ignore it.
Well, if you see a pretty obvious hang or lock that would be related to
the HTTP or database service, I might be interested in getting a notice
that contains an exact timestamp (preferrably UTC).
Well, I won't make any promises wether I'd be capable of fixing, but I
might have a look to see if there's any related notice on the server.
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
Martin Spott pisze:
Hi Mateusz,
On Mon, Jul 21, 2008 at 10:23:11PM +0200, Mateusz Å?oskot wrote:
I will report only if I observe services unavailability for an hour or more. But if its randomly down for only a few minutes, then I should ignore it.
Well, if you see a pretty obvious hang or lock that would be related to
the HTTP or database service, I might be interested in getting a notice
that contains an exact timestamp (preferrably UTC).
Well, I won't make any promises wether I'd be capable of fixing, but I
might have a look to see if there's any related notice on the server.
Martin,
Understood. I will keep that in mind.
Gretings
--
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org