tlsolutions
Sep 24th 2007, 10:19 pm
Hi,
I am using the Smart Update Pinger Plug in for my wordpress blogs and it is set to ping my ping list after every new post, however when I check my ping logs after a new post I get a bunch of error messages like these:
============================
These are the lastest actions performed by the plugin.
09/14/07 12:57:54 - http://www.a2b.cc/setloc/bp.a2b could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:57:54 - http://www.bitacoles.net/ping.php could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:57:54 - http://www.blogdigger.com/RPC2 was successfully pinged
09/14/07 12:57:55 - http://www.blogoole.com/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:57:56 - http://www.blogoon.net/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:57:56 - http://www.blogpeople.net/servlet/weblogUpdates was successfully pinged (extended format)
09/14/07 12:57:56 - http://www.blogroots.com/tb_populi.blog?id=1 could not be pinged. Error message: “transport error - could not open socket: 111 Connection refused”
09/14/07 12:57:56 - http://www.blogroots.com/tbpopuli.blog?id=1 could not be pinged. Error message: “transport error - could not open socket: 111 Connection refused”
09/14/07 12:57:56 - http://www.blogshares.com/rpc.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:57:56 - http://www.blogsnow.com/ping could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:57:58 - http://www.blogstreet.com/xrbin/xmlrpc.cgi could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:00 - http://www.lasermemory.com/lsrpc could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:00 - http://www.mod-pubsub.org/kn_apps/blogchatter/ping.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:00 - http://www.mod-pubsub.org/knapps/blogchatter/ping.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:02 - http://www.newsisfree.com/xmlrpctest.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:02 - http://www.popdex.com/addsite.php could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:58:02 - http://www.snipsnap.org/RPC2 could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:03 - http://www.weblogues.com/RPC could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:03 - http://xmlrpc.blogg.de could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:09 - http://xping.pubsub.com/ping could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”
=============================
What is causing this? is my plugin corrupt or do I need a new ping list? Or is it something else entirely?
Thanks in advance.
I am using the Smart Update Pinger Plug in for my wordpress blogs and it is set to ping my ping list after every new post, however when I check my ping logs after a new post I get a bunch of error messages like these:
============================
These are the lastest actions performed by the plugin.
09/14/07 12:57:54 - http://www.a2b.cc/setloc/bp.a2b could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:57:54 - http://www.bitacoles.net/ping.php could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:57:54 - http://www.blogdigger.com/RPC2 was successfully pinged
09/14/07 12:57:55 - http://www.blogoole.com/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:57:56 - http://www.blogoon.net/ping could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:57:56 - http://www.blogpeople.net/servlet/weblogUpdates was successfully pinged (extended format)
09/14/07 12:57:56 - http://www.blogroots.com/tb_populi.blog?id=1 could not be pinged. Error message: “transport error - could not open socket: 111 Connection refused”
09/14/07 12:57:56 - http://www.blogroots.com/tbpopuli.blog?id=1 could not be pinged. Error message: “transport error - could not open socket: 111 Connection refused”
09/14/07 12:57:56 - http://www.blogshares.com/rpc.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:57:56 - http://www.blogsnow.com/ping could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:57:58 - http://www.blogstreet.com/xrbin/xmlrpc.cgi could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:00 - http://www.lasermemory.com/lsrpc could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:00 - http://www.mod-pubsub.org/kn_apps/blogchatter/ping.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:00 - http://www.mod-pubsub.org/knapps/blogchatter/ping.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:02 - http://www.newsisfree.com/xmlrpctest.php could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:02 - http://www.popdex.com/addsite.php could not be pinged. Error message: “parse error. not well formed”
09/14/07 12:58:02 - http://www.snipsnap.org/RPC2 could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:03 - http://www.weblogues.com/RPC could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:03 - http://xmlrpc.blogg.de could not be pinged. Error message: “transport error - HTTP status code was not 200”
09/14/07 12:58:09 - http://xping.pubsub.com/ping could not be pinged. Error message: “transport error - could not open socket: 110 Connection timed out”
=============================
What is causing this? is my plugin corrupt or do I need a new ping list? Or is it something else entirely?
Thanks in advance.