What if you can't run cron

By charlener on 26 Feb 2006 at 07:38 UTC

Hi. Due to my setup (authentication upon going to the URL via pubcookie using .htaccess), when I run the cronjob (cron.php) via lynx, it never "gets through" due to the instance of lynx not getting authenticated. The other option listed on this site, using wget, doesn't work at all. (I know lynx works if the site's not secured).

Is there a way that I can run cron.php directly from a command line? like, through an absolute path to it with php? Or through moving the cron.php file to another directory with a different .htaccess file?

Hope that made sense,
Charlene

Comments

No ideas..

sangamreddi commented 26 February 2006 at 07:47

as of now no ideas. will test/try and let you know possible solutions..
Sunny
www.gleez.com | www.sandeepone.com

Not Sure if This Helps

erikhanson commented 26 February 2006 at 07:53

Not sure if this module (Poormanscron) helps, but it sounds like it could solve (band-aid) your issue a least until you figure out to get past the lynx issue.

Poormanscron.module should solve your problem

sprite commented 26 February 2006 at 09:38

Poormanscron.module should solve your problem for cron job dependent features within drupal.

I use Poormanscron.module on my drupal sites and it works fabulously.

spritefully yours

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

having installed poormanscron...

charlener commented 27 February 2006 at 19:41

Thanks for the advice - I've installed it and reading over its docs it seems promising.

However, I get an oddity I think I shouldn't get in its settings.

On its Home >> administer >> settings page, all I see is the word 'Array' and then the 'Save configuration' and 'Reset to defaults' button. Not too much to change, I'd think. Any ideas as to what is happening?

Thanks,
Charlene

poormanscron - installation should be straightforward ...

sprite commented 28 February 2006 at 08:58

The [ Home » administer » settings ] page should include:

-----------------------------

[ Time intervals ]
Cron runs interval:
Minimum number of minutes between cron runs. Cron will actually execute during the first page request after the interval has elapsed.
Retry interval:
The number of minutes to wait after a cron run error before retrying.

[ Logging ]
Log successful cron runs:
If you want to log successful cron runs to the Drupal watchdog, say Yes here. If those messages annoy you, disable them by selecting No.

----------------------------

I have installed this module dozens of times in various projects without problem. It should be straightforward.

spritefully yours

spritefully yours
Technical assistance provided to the Drupal community on my own time ...
Thank yous appreciated ...

wrong version, just my guess

guckie commented 28 February 2006 at 09:12

It sounds like you may have installed the 4.7 or current cvs version of the poormanscron.module onto a prior drupal version (i.e. 4.6.5), or something similar. give that a check?

poormans cron version

heine commented 28 February 2006 at 09:15

What version of poormanscron did you install? You will need to use the 4.6 version on Drupal 4.6 and the 4.7 version on Drupal 4.7.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.