HTTP error: 500 read timeout
Chances are good that the new feature of logging errors with notification and TrackBack pings to the system Activity Log is showing you more HTTP error: 500 read timeout messages from weblogs.com than you would like, and worse yet, when you check weblogs.com it shows that your ping did work, because there it is, right there!
There are two different views of whether or not a ping worked, the pingee’s view and the pinger’s view. When your copy of Movable Type sends an update notification to weblogs.com, as far as weblogs.com is concerned the ping worked when it receives the notification, gets a copy of your page, verifies that it has changed since your last ping, and sends you a reply. It couldn’t care less whether you actually get the reply; if your server has melted into a pool of slag between the time it sent a copy of the page and the time weblogs.com sends its reply, it’s no skin off weblogs.com’s nose.
But as far as your copy of MT is concerned, the ping only succeeds if weblogs.com manages to send back a non-error reply before it gets tired of waiting. The time it’s willing to wait is where you can cut down on the number of (false) error messages you get, but only at the cost of having to sit around watching the “Pinging sites…” page longer when a ping isn’t going through. In {your MT directory}/mt.cfg, you can put in a PingTimeout value (or increase the value if you already have one), so that you have a longer setting than the default 15 seconds, which will cut down on the number of times you are told that a ping failed when it didn’t. Since the same value is used for TrackBack pings, it will also cut down on the number of times that you ping someone’s entry twice because your MT didn’t know that their MT got the ping. The downside is that when a ping isn’t going to go through, you have to wait through that timeout, but since I usually go do something in another tab while MT’s saving an entry anyway, I’m generally happy with
PingTimeout 30
and so far that’s only given me one read timeout error.
The pinger, the pingee, and the duplicate ping
Phil Ringnalda explains something that I’ve been wondering about ever since I enabled TrackBack: why does my Movable Type occasionally ping someone’s entry twice and, conversely, why do I sometimes get duplicate TrackBack pings for one of my posts? (I’…
Double looping
[via Jonathon Delacour:] Grâce à Phil Ringnalda, les utilisateurs de MT en savent un peu plus sur le pourquoi des doubles pings TrackBack que certains {ici même} ont eu le désagrément d’expérimenter. L’explication est en fait une extrapolation de ce qu…
Psst. You there?
Nope, I’m (I’s? I was) still at work. Now I’m home, but you’re probably snug in bed by now.
HTTP Timeout Answers
Phil Ringnalda explains HTTP error 500s that you may have in your MT activity log if you ping other sites.
Just Give Me The Ping, Vasili
Phil Ringnalda suggests an easy fix for MT users that will significantly reduce the number of timeout errors you get…
MT PING ERRORS
phil ringnalda has a fix for MT ping timeout problems. (Hat tip: Dodd Harris)…
Thanks! I was wondering why MT gave me that message almost every time I pought Weblogs.com.
thanks for finding it and simplifying the fix well enough that a technoidiot like me could understand it.
Sorry, I am just looking . . .
[linklylove] Andy at WWRant3 has a really good story about the intelligence of teachers and students in the current public educational system and even manages to reference Mary Kay Letourneau. This follows his important male health report: Pud Pulling …
’Net bits
The dark side of having your fridge connected to the web: ”and we’re going to need something like 100 IP addresses for each human being.” I’ve been getting timeout errors when pinging Weblogs; my MT activity log is growing exponentially….
Error 500 on MT Pings
Over at philringnalda, I found the answer to the time out error on MT trackback pings. The fix is to enable the PingTimeOut variable in the mt.cfg file. Thanks, Linkmeister….
Test
test… autodiscovery is on. and here is a link to an external mt blog entry….
HTTP error: 500 read timeout
I was getting this error: HTTP error: 500 read timeout, so I did a google search and the first result was this entry by Phil. Thanks for the advice Phil. Now I needed a place to test my new settings….
question:-
1:-
I have already load all file of rileted link in my server but It is avaliable in server but when i am start the my site and click on orderonline(as link) then it display error is pagecannot be
display and below display http500 internal server error
2:-
MY webpages names are small letter in my harddisk when i load this file on server through ftp then all webpages name are show on Capital letter on server
3:-
when i run asp page in my personalweb server in my pc then it display error header error and response object error ’ASP 0156 :80004005’
buon giorno ,senta ho dei problemi con il mio pc,non riesco piu a connettermi con dei siti di una certa importanza,mi dice che impossibile stabilire visualizzare pagina,impossibile tovsre server cosa devo fare ? grazie
Multiple trackback pings
Ugh again. When I edited my last post, duplicate trackback pings were sent to a couple of the sites I referenced. It’s happened before, and it’s embarassing, so I did a quick Google search and found Jonathon Delacour’s pointer to…
WHEN I SUBMITTED M Y ”FREELOTTO” GAMME’S PICK,I
RECEIVED THE MESSAGE AS”HTTP ERROR 500.AND I COULD NOT FIX IT SUCCESSFULLY ALL MY EFFERTS
Ummm. OK. This sounds simple enough, but, don’t we have to re-run the MTload.cgi after changing this MT.CFG file? Last time I tried this, i got a ”database exitsts” error, and had to drop/recreate my database for it to work. Is there a way around this? Like, is there a MySQL command I could execute against a database in the table to set the ping timeout to 30 seconds?
peeniewallie a_t wispertel.net
Nope, mt-load.cgi is a one-time thing, to create the database; as it tells you after you run it, you never want it to run again, and thus should delete it so you don’t accidently nuke your database. mt.cfg is read every single time you run any part of Movable Type. In this case, when you save an entry what you are actually doing is starting up a new instance of mt.cgi, sending it what you typed and some instructions about what to do with it, and before it does anything else it will read mt.cfg to see how it is supposed to behave. The PingTimeout isn’t saved in the database at all, only in mt.cfg, where it’s read every time before MT sends a ping (or does anything else).