Crontab problem

[Das wheep]

Hello,

when i click on "Crontab" under "Server" i get the following error:

0: /usr/local/psa/admin/htdocs/sysuser/crontab.php:68 psaerror(string "Crontab() constructor failed: Unable to create Crontab entry: parse error")


crontab -l shows:

SHELL=/bin/sh
PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin
MAILTO=root
#
# check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly
#
-*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1



So where is the error?


Thank you,

Daniel

 

[Moore]

I got the same problem here. Fresh installation with no modifications.

Greetings,
Moore

 

[Syndic]

I have the same Problem.

Greetings,
Syndic

 

[squalo]

after upgrade crontab not work

to difference yours I do not receive error

 

[CoKo]

Can you please give some more informations?

What is the user name of the domain ftp account?

eg. the output of the following commands:

df -h
df -i
ls -al /var/spool/cron/

This will give us a base to find the problem (I hope)

 

[squalo]

[root@server2 root]# ls -al /var/spool/cron total 16
drwx------ 2 root root 4096 Oct 25 12:32 .
drwxr-xr-x 16 root root 4096 Dec 10 2004 ..
-rw------- 1 root root 0 Sep 27 05:31 dance_forum
-rw------- 1 root root 0 Sep 27 05:31 danceteam
-rw------- 1 root root 0 Oct 21 05:30 digitalcenter
-rw------- 1 root root 256 Oct 21 2004 drweb
-rw------- 1 root root 0 Sep 27 04:34 e1000
-rw------- 1 root root 741 Oct 25 12:32 root
-rw------- 1 root root 0 Sep 29 03:31 streghe
-rw------- 1 root root 0 Dec 29 2004 test
-rw------- 1 root root 0 Sep 27 04:34 upload
[root@server2 root]# df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hda3 7061504 326550 6734954 5% /
/dev/hda1 26104 35 26069 1% /boot
none 127551 1 127550 1% /dev/shm
[root@server2 root]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hda3 53G 15G 37G 29% /
/dev/hda1 99M 13M 82M 14% /boot
none 499M 0 499M 0% /dev/shm
[root@server2 root]#

 

[CoKo]

What is the user name of the domain ftp account you tried to setup a cron job for?

 

[squalo]

natuerlich root

 

[CoKo]

Sorry, that seems to be a way different problem to the one from the original poster.

Your problem is IMHO not related to Plesk anfd the frontend functionality of setting up cron jobs for each domain, but more a basic problem of cron jobs not getting executed at all.

In that case you should start searching at completly different locations, eg:

- is crond running?
- when restarting crond, is there anything in the logs?
- at the time a cron job should be executed - is there anything in /var/log/messages?


Huh - sorry. You're on server level - my fault.

But the above should help anyway...

 

[CoKo]

can you please also post the result of:

cat /var/spool/cron/root

ls -al /usr/local/psa/admin/sbin/wrapper

- just to be sure...

 

[squalo]

[root@server2 root]# cat /var/spool/cron/root
[email protected]
14 5 * * * /usr/local/psa/bin/mysqldump.sh >/dev/null 2>&1
7 4 * * * /usr/local/psa/admin/sbin/statistics >/dev/null 2>&1
30 * * * * /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1
30 12 * * * /usr/local/psa/admin/bin/php /usr/local/psa/admin/plib/report/autoreport.php --auto daily >/dev/null 2>&1
25 7 * * 1 /usr/local/psa/admin/bin/php /usr/local/psa/admin/plib/report/autoreport.php --auto weekly >/dev/null 2>&1
20 7 1 * * /usr/local/psa/admin/bin/php /usr/local/psa/admin/plib/report/autoreport.php --auto monthly >/dev/null 2>&1
0 * * * * /usr/sbin/ntpdate -b -s time.ien.it > /dev/null 2>&1
30 3 * * * /backup/backup.sh >/dev/null 2>&1
2 * * * * /opt/drweb/update/update.pl >/dev/null 2>&1
[root@server2 root]#


[root@server2 root]# ls -al /usr/local/psa/admin/sbin/wrapper
---s--x--- 1 root psaadm 14208 Aug 24 08:20 /usr/local/psa/admin/sbin/wrapper
[root@server2 root]#

 

[CoKo]

fine, so your base configuration is ok. What about the other questions:

- is crond running?
- when restarting crond, is there anything in the logs?
- at the time a cron job should be executed - is there anything in /var/log/messages?

Sorry for all the questions, but normally this is a support issue which needs hands on the server - then it should be solveable in some minutes. Without shell access I need to ask a lot...

 

[squalo]

yesssssssssss
thanks resolved the problem

service crond status = stop