Colecção de Erros nos comentários dos Weblog.com.pt
Amigos, tenho para troca! Ja tenho 3 diferentes, quem encontrar mais avise! Vamos trocando, porque mais cedo ou mais tarde a AEIOU vai ter de fazer uma caderneta!!
Erro na submissão de comentário
O seu comentário falhou pelas seguintes razões:
In an effort to curb malicious comment posting by abusive users, I've enabled a feature that requires a weblog commenter to wait a short amount of time before being able to post again. Please try to post your comment again in a short while. Thanks for your patience.
Got an error: Bad ObjectDriver config: Connection error: Too many connections
An error occurred
Rebuild failed: Renaming tempfile '/blog/populo.weblog.com.pt/arquivo/2006/06/index.html.new' failed: Renaming '/blog/populo.weblog.com.pt/arquivo/2006/06/index.html.new' to '/blog/populo.weblog.com.pt/arquivo/2006/06/index.html' failed: No such file or directory
2 comentários:
O problema é estares a tentar comentar a horas em que o tráfego é grande. Às 1:44, hora em que escreveste este post de alerta, também eu tentava comentar algures na weblog. Já eramos dois! Too many connections! Ai Farpas, agora sou eu que tenho de te ensinar estas coisas!?!??!?
500 INTERNAL SERVER ERROR: procuram-se alternativas ao weblog
500 Internal Server Error
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, ptd@xpto.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Apache Server at lua.weblog.com.pt Port 80
--------------------------------------------------------------------------------
Tendo em conta que o Lua já tem 3 anos, qual será a alternativa mais viável?
Quando mudei do Blogspot para o Weblog trouxe os arquivos todos.
Procuro plataformas onde tenha total controle de templates. O ideal seria continuar no Movable Type...
--------------------------------------------------------------------------------
500 Internal Server Error
HTTP Error 500 - Internal server error
Introduction
Your Web server encountered an unexpected condition that prevented it from fulfilling the request by the client (e.g. your Web browser or our CheckUpDown robot) for access to the requested URL.
This is a 'catch-all' error generated by your Web server. Basically something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of your Web server site to locate and analyse these logs.
500 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:
* Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
* Open an IP socket connection to that IP address.
* Write an HTTP data stream through that socket.
* Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '500'.
Resolving 500 errors - general
This error can only be resolved by fixes to the Web server software. It is not a client-side problem. It is up to the operators of your Web server site to locate and analyse the logs which should give further information about the error.
http://lua.weblog.com.pt/arquivo/174955.html
Enviar um comentário