crontab command not allowed issue after

kam

Verified User
Joined
Jan 4, 2009
Messages
56
crontab command not allowed issue after Roundcube 0.2 update [custombuild]

Hello,

I found that after I run the Roundcube 0.2 update [custombuild]

Ref: http://www.directadmin.com/forum/showthread.php?t=29240

I unable to add any new cron,

and I found below error message in /var/log/cron

Jan 15 22:30:02 server crontab[7820]: (apache) AUTH (crontab command not allowed)

Also, the cron log showed that other crons are run by crond instead of crontab

Jan 15 22:36:01 server crond[11396]: (root) CMD (/usr/local/directadmin/dataskq)

I don't know how to fix this issue,

please help,

Thanks,

Kam
 
Last edited:
Problem solved.

I have no idea why apache has been added to /etc/cron.deny after custom build update.

Also, the name is changed [from crond to crontab]

Now, it's
Jan 16 00:47:18 server crontab[31336]: (apache) LIST (apache)
Jan 16 00:47:18 server crontab[31337]: (apache) REPLACE (apache)
Jan 16 00:47:25 server crontab[31380]: (apache) LIST (apache)
Jan 16 00:47:25 server crontab[31381]: (apache) REPLACE (apache)

Before update, it's something liked

Jan 10 01:27:15 server crond [21211]: (apache) REPLACE (apache)

Kam
 
Last edited:
I have no idea why apache has been added to /etc/cron.deny after custom build update.

Because apache should never be allowed to add a cron job.
 
Why should we never run cron as apache and any alternatives?

Sorry to revive an old thread, but facing this problem currently.

I am running PHP as CLI so web requests run as apache. As such I change ownership of tmp, cache, image and upload folders to apache:apache.

Problem is when you run a cron job as the user it cant write to the cache folders. If you run the cron as root it creates files/folders as root and stops apache being able to write to them.

The easiest solution would be to run the cron as apache, but that is denied (why is this bad)?

I've been advised to use suPHP/PHP CGI, but that's a big change to make on a server with lots of client sites.

Is there an alternative way to get a user cron to run as it would when a normal web request?

Thanks, Paul.
 
Back
Top