07 March 2005

Ping, Ping-O-Matic 7-Mar-05 UTC 19:15:46

Error message:

Something went wrong - -32300 : transport error - HTTP status code was not 200
Transitory

This error message may occur using Ping-O-Matic. The error message does not necessarily mean that the system is blocked.

If you re-ping, the same services creating this message may produce an "all clear" message.

You could also get this message on "new services on the next ping" that were not generating this message on the first ping.

As confused as I am? Another way of saying this: The error message does not consistently occur on the same services from the same blog.

If you ping once, some services may report this error; then if you re-ping the same services may not report this error, but other services, that did not previously report an error, may then report the error in the second ping.

Services

Saw this on the following services, but did not occur again on other pings: Yahoo, FeedBurner, NewsGator.

This is a transitory issue. Appears to be outside user-control.

Resolution

1. De-select the services that worked.

2. Wait a couple of minutes and reping the services that didn't get a ping.

3. Subsequent pings could go through the next time. Maybe not.

Other research

It remains unclear what percentage of the incoming data does not get adequately handled.

A. Sometimes a reping doesn't generate a new-different message. I have seen multiple days where the same error message occurred. Unknown whether content correctly reported.

B. Even services that do not produce this message may have problems. For example have seen Technoraiti, PubSub, and Feedster not reporting data, although the service has been pinged.

Error message:

Something went wrong - -32300 : transport error - HTTP status code was not 200
Transitory

This error message may occur using Ping-O-Matic. The error message does not necessarily mean that the system is blocked.

If you re-ping, the same services creating this message may produce an "all clear" message.

You could also get this message on "new services on the next ping" that were not generating this message on the first ping.

As confused as I am? Another way of saying this: The error message does not consistently occur on the same services from the same blog.

If you ping once, some services may report this error; then if you re-ping the same services may not report this error, but other services, that did not previously report an error, may then report the error in the second ping.

Services

Saw this on the following services, but did not occur again on other pings: Yahoo, FeedBurner, NewsGator.

This is a transitory issue. Appears to be outside user-control.

Resolution

1. De-select the services that worked.

2. Wait a couple of minutes and reping the services that didn't get a ping.

3. Subsequent pings could go through the next time. Maybe not.

Other research

It remains unclear what percentage of the incoming data does not get adequately handled.

A. Sometimes a reping doesn't generate a new-different message. I have seen multiple days where the same error message occurred. Unknown whether content correctly reported.

B. Even services that do not produce this message may have problems. For example have seen Technoraiti, PubSub, and Feedster not reporting data, although the service has been pinged.

" />