CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site
This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • CiviMail installation and configuration (Moderator: Donald Lobo) »
  • civimail.cronjob.php and EmailProcessor.php fail silently and send a HTTP 301
Pages: [1]

Author Topic: civimail.cronjob.php and EmailProcessor.php fail silently and send a HTTP 301  (Read 998 times)

jun

  • I’m new here
  • *
  • Posts: 3
  • Karma: 0
civimail.cronjob.php and EmailProcessor.php fail silently and send a HTTP 301
January 11, 2011, 08:40:01 am
Hi,

Since I upgraded from CiviCRM 3.2 to 3.3.1 (and now to 3.3.2) both the civimail.cron.php and the EmailProcessor.php scripts fail silently. Here's few details:
 - I've tried to trigger them both from the web and from the CLI with the "cd $CIVI_ROOT;$PHP bin/civimail.cronjob.php $PARAMS" and the "wget --no-check-certificate 'httpourdomain/sites/all/modules/civicrm/bin/civimail.cronjob.php?name=xxxx&pass=xxxx&key=$KEY'
 - Passing them incorrect login / password or key from wget does raise an error message so they do get call.
 - Passing them correct information leads to a 301 Moved Permanently HTTP message (called from both wget on the server or a browser).

Our installation has been upgraded several times and used to be, some time ago, a version 2. Drupal is version 6.17 and the site is in a multi-site config on Aegir.
 
I have tried to apply the patch recommended here http://forum.civicrm.org/index.php/topic,16569.msg72549.html but to no avail. I've also tried to remove any ACL query bits to no avail. Next on my list would be to start putting debug messages to find where the scripts fails but I'm turning over to real professionals hoping you can support us.

If someone is available to work for hire on this, please PM me.

Thanks!

Jun.
Internews Europe

xavier

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4453
  • Karma: 161
    • Tech To The People
  • CiviCRM version: yes probably
  • CMS version: drupal
cronjob isn't compatible with destination_user and possibly with aegir
January 12, 2011, 07:28:55 am
Full disclaimer: been working on Jun server. For what I could see after a couple of hours:

The difference between 3.2 and 3.3 is that now the cron are bootstrapping drupal, including loading all the modules you have on your particular configuration.

In Jun's case, it seems that one of the drupal module exit(); in the login hook, hence stopping the bootstrapping and the cron process: destination_user

plus it seems that the default config on aegir isn't compatible with running the cron from php cli. More specifically, configuring the db access form within the vhost doesn't work when you run it from the cli, obviously.

X+

-Hackathon and data journalism about the European parliament 24-26 jan. Watch out the result
Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • CiviMail installation and configuration (Moderator: Donald Lobo) »
  • civimail.cronjob.php and EmailProcessor.php fail silently and send a HTTP 301

This forum was archived on 2017-11-26.