Skip to main content

Webserver: Cron problem

After setting-up some cron jobs in my webserver, after checking the logs, I realised a Permission denied message.

The first thing that came to my mind, was that the user running the cron job with the error didn't have access to the file. This would awkward since the user cron job and the web-server user were the same.

I didn't find any solutions in the forums of the php framework I use, so I just googled it and stepped into this.

I read all the comments, and finally the solution came to me through glued2(10-15-2005, 09:08 PM) saying:
"call the php script with the same command as the cron script does (probably php -q /var/www/script.php)".
It was then that I undestood what was going on. I am mostly(if not completely) using debian-based linux OS, apache and php. By saying that, I falsely assumed that cron was going to "understand" that I was using a php file as a command and it should run php by its own.

To conclude, let's say I have cron file in /var/www:
CorrectFalse
* * * * * wget http://www.example.com/cron.php
* * * * * /var/www/cron.php


Cron is a program used for general purposes. It's not mathematics. It's just general knowledge. Many of the programs I use, even in my home pc, have been running cron jobs. For some reason, I forgot. :-P

Comments

Popular posts from this blog

Configure drupal_http_request() on the fly

The drupal_http_request() function supports connections using a proxy. You can configure a global proxy to use for all drupal_http_request() callbacks from the settings.php file of your website/installation by filling the following lines with the proper information:For those of you preferring a UI, then HTTP proxy module is for you.But what if you only want to use a proxy in some cases; like a custom module? In that case you will need the following function(modify accordingly):Now all you have to do is Call <?php _MYMODULE_change_proxy(); ?>.Do your drupal_http_request() calls.Call <?php _MYMODULE_change_proxy(TRUE); ?> to reset your previous settings.

Drupal: Allow registrations through Invite or Referral modules only

The Invite module provides invitations from existing users to their contacts. The Referral module, in contrary, creates a special URL for each existing user, which can be found in each user's profile, and allows new user registration. Even though, these two modules seem to provide the same functionality, they don't (and they shouldn't). Invite module, provides a mechanism for a site administrator to limit new registrations to "Invitations only". Referral module doesn't provide any of this functionality. Some users have requested the Invite module and Referral module to join in one module. Until now, there isn't anything to that direction. Wouldn't it be great though if there was a solution to limit drupal registration to referral or invitation only? Copy the functions below to a refinvite.module file in your sites→all→modules→refinvite folder and enable the module. Then go to http://<your-address-here>/admin/user/settings and enable the new …

Send mass email to certain users using VBO

Views Bulk Operations uses the built-in actions to act upon nodes, users, entities etc. Among these actions is our ability to send emails to users. If you try to use this action though you will encounter a small but serious problem. You are asked for an email address to send your message. You might say "but I have selected the users I want this message to reach. Why should I input an address again?". Don't get overwhelmed. What this field expects is not an address but a token. Specially this token [user-email]. If the website is intended for you, then you might say that's not such a problem to write this token down again and again. But if the manager of the website is bound to be the client or if you just want to spend less time writing things down, you might prefer to use a custom hook_form_alter() callback to set a default value. It could be done in both theme and module environment so suit yourself. Just add the following in your module or theme.