On 06/13/2012 09:29 AM, Florian Effenberger wrote:
Hello,
webmaster-Kracked_P_P wrote on 2012-06-13 15:16:
When I wanted to see if there was any more new chapters for 3.4 or 3.5,
I got the server error 503.
http://wiki.documentfoundation.org/Documentation/Publications
this seems to be a load-related problem. When the script takes too
long to process due to high server load, the wiki puts out a 5xx error
code.
I forwarded it to the admins - I myself am buried in work and don't
know when I will find time to investigate, so maybe someone is faster
than me...
Florian
For past month or so, every so often I have been getting the 500 or 503
errors when I go to most of the wiki pages. This almost never happened
before May. But now it seems it happen at least once a week.
I just seems strange. A few minutes after I get these server errors, I
try to load the pages again, and there is not errors.
I just hope some new user or business user does not come across a server
error and does not try back or figures it is a reflection on TDF/LO as a
"company" or organization. It is just a "technology gremlin" and can
happen to any business.
.
--
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.