Remove cronjob haulting server booting
Hey,
I am a new user of a dedicated server and have not had any issues with it in the last 9 months. I was making some changes to the Cron in Cpanel for one account, and now have caused the server to get stuck in a boot loop. It will not boot to the normal drives, but I can get into the CENTOS Rescue Drive.
What I am trying to do is firgure out how to find/remove the cron script that was added under that Username, in Cpanel. I am falling short on this though.
I can get into SSH and mount the drives, but am unable to find the data.
My drives are setup as follows:
Number Size File System Name Flags
/dev/sda1 1029Kb Primary bios_grub
/dev/sda2 52.4gb ext3 Primary raid
/dev/sda3 1947gb ext4 Primary raid
/dev/sda4 536mb linux_swap(v1) Primary
Number Size File System Name Flags
/dev/sdb1 1029Kb Primary bios_grub
/dev/sdb2 52.4gb ext3 Primary raid
/dev/sdb3 1947gb ext4 Primary raid
/dev/sdb4 536mb linux_swap(v1) Primary
I then have these 2 RAID Array's:
/dev/md2 52.4gb Partition Table: Loop File System Ext3
/dev/md3 1947gb Partition Table:LOoop File System Ext4
I have tried checking cronttab, and find it to be empty in all the locations that I check the file. The scripts that I added into Cpanel/Cron Jobs were the following
* * * * * /usr/bin/php /home/mtukaraoke/public_html/store/bin/magento cron:run | grep -v "Ran jobs by schedule" >> /home/mtukaraoke/public_html/store/var/log/magento.cron.log
* * * * * /usr/bin/php /home/mtukaraoke/public_html/store/update/cron.php >> /home/mtukaraoke/public_html/store/log/update.cron.log
* * * * * /usr/bin/php /home/mtukaraoke/public_html/store/bin/magento setup:cron:run >> /home/mtukaraoke/public_html/store/var/log/setup.cron.log
So if anyone can help me get my server back up and running, I would be very greatful. The hosting company, only handles hardware issues, they do not help out with software. So this is why I am reaching out, no way to contact them for help.
Thanks,
Bryan
-
Hello, Cron jobs are added to the following location when setup through cPanel: /var/spool/cron/$username
However, note that if your system is unable to boot, I don't believe the cron job is the likely culprit. Do you notice any specific output to /var/log/messages or /var/log/dmesg? Thank you.0 -
So what I found in /Var/log/Messages is root@rescue:/var/log# cd messages -bash: cd: messages: Not a directory root@rescue:/var/log# tail messages Oct 5 13:17:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 13:27:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 13:37:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 13:47:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 13:57:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 14:07:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 14:17:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 14:27:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 14:37:27 rescue mpt-statusd: detected non-optimal RAID status Oct 5 14:40:19 rescue kernel: EXT4-fs (md3): mounted filesystem with ordered data mode. Opts: (null) I have attached the DMESG in a notepad text file, as it is very long. If you wish to take a look at that, and see if you see anything that sticks out. I am still stuck :( But thank you for your help! Bryan 0 -
Hello, It's showing output related to the rescue mode boot option. The output is only helpful if it's from when you attempted to boot the server normally. If you are unable to boot using the normal mode, and your provider is unable to help, then you may need to consult with a system administrator. We provide a list of companies offering system administration services at: System Administration Services | cPanel Forums Thank you. 0 -
Thank you. I have sent an email to one of them on your list. Thanks, Bryan 0
Please sign in to leave a comment.
Comments
4 comments