Tripolis

Active Member
Sep 29, 2012
44
0
6
cPanel Access Level
Website Owner
Hey,
i create a cronjob and see after save a wrong address.
I delete the cronjob in Cpanel and it is delete.

But, the cronjob is working and cant delete because he is deleted.

Message:

Subject: Cron <wwwb...............
Content-Type: text/plain; charset=UTF-8
Auto-Submitted: auto-generated
X-Cron-Env: <LANG=en_US.UTF-8>
X-Cron-Env: <SHELL=/usr/local/cpanel/bin/jailshell>
X-Cron-Env: <HOME=/home/wwwo...>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=wwwb....>
X-Cron-Env: <USER=wwwb.....>

/usr/local/cpanel/bin/jailshell: .........................adress to file---

What can i do now?
I create a job every 30 minutes and you know how many mails i have until sunday evening :)

Regards
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,267
463
Hello :)

Do you have root access to this server? If not, please contact your web hosting provider to have them see why the cron job is not deleting properly. They will be able to manually remove the cron job directly from the command line.

Thank you.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,267
463
Please review the following file:

/var/spool/cron/$username

You can edit it with a text editor such as "vi" to delete the cron job in question.

Thank you.
 

Tripolis

Active Member
Sep 29, 2012
44
0
6
cPanel Access Level
Website Owner
Hm, i open it.
I only see:
MAILTO="pt..........ine.de"
SHELL="/usr/local/cpanel/bin/jailshell"

No cronjob set.

But, i dont be wrong or?
That is about the cronjob.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,880
2,267
463
Could you open a support ticket using the link in my signature so we can take a closer look and see why the cron job is still running if it's no longer created? You can post the ticket number here so we can update this thread with the outcome.

Thank you.
 

cPanelPeter

Senior Technical Analyst
Staff member
Sep 23, 2013
586
25
153
cPanel Access Level
Root Administrator
Hello,

To update, this appears to be that there are several frozen messages still in the Exim mail queue that were generated from
this cron job that now no longer exist. It was recommended that the Exim mail queue be cleared of those messages to see if the problem goes away. We are still waiting on confirmation on that.

Thank you.