CiviCRM Community Forums (archive)

REcent update broke this, and it's not the password issue because I included it.  It's a multi-site Drupal set up, and it appears that the job tries to access civicrm.settings.php in the default directory, not in the proper site directory (and yes, I included -s 'nameofmydomain' at the end of the command).  Any ideas?

I don't but at least you shouldn't feel that no one is reading your posts. You may need to try to debug this yourself and see what's going wrong...

thanks folks, but i'm not qualified for that.  i'll keep trying to figure something out, and will report if I can solve it.  but if no one else experiences a similar problem, then I suppose the problem is probably on my end.  the entire sites folder is symlinked to the home directory, but this didn't cause a problem before so I can't see why it would now

just curious, what is the preferred (best practice) method for running scheduled jobs?  is it my server's cron process or should I try the url method?  I see there is even a drupal module that will do this, maybe I'll try that...

Hi,

If symlinks, you probably needs to add a settings_location.php files in the root of your civicrm that contains

<?php
define( 'CIVICRM_CONFDIR', '/var/www/yourdrupal/sites' );


and the cli cron should work fine.

This being said, I'm moving to using drush to call the api (so you don't need to provide any user info beside the id) and seems to work as well, but easier to maintain.

to be continued...

X+

Trial/error indicates this could be used to run all scheduled jobs:

drush example.org civicrm-api job.execute