Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I enable MultiPing on the Ping on Cron Run and I can not run Cron manually anymore. Disabling Ping on Cron and Enabling Ping after blog post seems to eliminate this problem.
Can't wait for the finished product!!! Multi-Ping keeps my pages way high up in the search ranks. Thanks!!!
Comments
Comment #1
Hotlikecold CreditAttribution: Hotlikecold commentedMore info on Multiping. First here is a great Ping list! These all work.
http://rpc.pingomatic.com/
http://api.my.yahoo.com/RPC2
http://bblog.com/ping.php
http://blog.goo.ne.jp/XMLRPC
http://rpc.technorati.com/rpc/ping
http://rpc.weblogs.com/RPC2
http://xping.pubsub.com/ping/
http://api.moreover.com/RPC2
http://ping.bloggers.jp/rpc/
http://ping.feedburner.com/
Second, I find that if I turn off, uninstall and delete the stock Drupal Ping module then all is well. If not MultiPing certainly does interfere somehow in Cron runs. Also I set it to ping after post and not cron run.
http://globalamericanmedia.com/
Comment #2
voxpelli CreditAttribution: voxpelli commentedWhat do you mean by it not running anymore? Is it running for too long? With so many ping services we might need to add a system for just pinging a few of them each time.
Can you test if this is still a problem with the new beta?
Comment #3
Treidge CreditAttribution: Treidge commentedJust ran into the same problem with latest 6.x-1.x-dev version of Multiping. After I enabled this module Cron can't be triggered anymore.
What I did:
1. Enabled Multiping.
2. Checked if Cron can be triggered - right after module was enabled it's still works properly.
3. Waited for scheduled Cron Job - right after that time Watchdog log says that "Cron run exceeded the time limit and was aborted."
4. From this moment manual request to /cron.php throws 404 error and Cron can't be triggered manually or by server on scheduled job.
Cache clearing did not take any effect. If disable Multiping - Cron starts to work properly without any additional actions. Also I didn't see any dependence on Multiping settings.
Comment #4
dgtlmoon CreditAttribution: dgtlmoon commentedMy guess is that what ever service you are hitting is timing out and causing everything to wait for that call.
drupal_http_request which does the XMLRPC heavy work does not have support for timeouts in 6, but does in 7.
http://api.drupal.org/api/drupal/includes--common.inc/function/drupal_ht...
Please check all your services are responsive (you may have to go through them by hand)
Comment #5
voxpelli CreditAttribution: voxpelli commentedThis should be fixed in the new 7.x-2.x version as that uses the queue system that was introduced in Drupal 7 to avoid trying to do too much in a single cron run.