Skip to main content

Total Noob here - Cron issue

Comments

22 comments

  • cPanelLauren
    Hello, Is the issue that the cron is still running after fantastico was removed? You can check for cron jobs associated with the root user through the command line interface (can be accessed through WHM>>Server Configuration>>Terminal) with the command: crontab -u root -l
    You can edit the crontab with the following: crontab -u root -e
    If you see the fantastico cron present there you can just remove it which will stop it from running.
    0
  • cerion
    Thank you for your reply. When I go to WHM>Server Configuration I do not see a Terminal option. Any thoughts? This is what I found in the kb. Is this what I need to look at?
    0
  • cPanelLauren
    I believe I misunderstood your access level, my apologies. If you don't have access to WHM you wouldn't be able to access the terminal for WHM. Your cPanel account may not allow this access. This makes it a bit easier though. If you go to cPanel>>Advanced>>Cron Jobs you should be able to remove that cron job from the list right from your cPanel account.
    0
  • cerion
    I can log into WHM as root. Is there a way to access cPanel via WHM? No one seems to know what our cPanel login would be or what email address it is tied to... Thank you for your patience.
    0
  • cPanelLauren
    You can definitely access cPanel from WHM if you go to WHM>>Account Information>>List Accounts -> click the cP logo next to the account to access it.
    0
  • cerion
    I got to the Cron Jobs portal. There are no jobs - How do I stop the error messages?
    0
  • cPanelLauren
    Hello, Ok it looks like the easy mode is going to be out for this issue, I'm sorry. In order to remove this you'll need to log in to the server as the root user over CLI, or access terminal from WHM - but it sounded like you didn't have that available in your WHM earlier. Once logged in the original commands I provided would allow us to see if the cron is in the root user's crontab: To view: crontab -u root -l
    You can edit the crontab with the following: To edit: crontab -u root -e
    If you see the fantastico cron present there you can just remove it which will stop it from running.
    0
  • cerion
    Ok. Now I'm feeling very ignorant. I'm assuming CLI is command line interface? I'm assuming that is the Windows command prompt. This is what I tried to get loggedin. I"m guessing I did something wrong. For what it's worth, I tried it in PowerShell as well.
    0
  • cPanelLauren
    Hello, I'm so sorry, yes this would be command line and to access from windows you'd need to use a program like
    0
  • cerion
    I'll eventually go away.
    0
  • cPanelLauren
    What if you go directly to the IP address, do you still get a timed out error? Are you sure that the SSH port is 22? You can find this out by restarting the SSH service in WHM>>Restart Services>>SSH Server when it restarts you'll get some output like "server listening on port 22"
    0
  • cerion
    Here are the results of the SSH restart: Waiting for "sshd" to restart "waiting for "sshd" to initialize "finished. Service Status sshd (/usr/sbin/sshd -D) is running as root with PID 26018 (systemd+/proc check method). Startup Log May 01 14:51:46 host.allianceprinting.net systemd[1]: Starting OpenSSH server daemon... May 01 14:51:46 host.allianceprinting.net sshd[26018]: Could not load host key: /etc/ssh/ssh_host_dsa_key May 01 14:51:46 host.allianceprinting.net systemd[1]: Started OpenSSH server daemon. Log Messages May 1 10:51:46 host sshd: Could not load host key: /etc/ssh/ssh_host_dsa_key May 1 10:51:46 host sshd[26018]: Server listening on :: port 2200. May 1 10:51:46 host sshd[26018]: Server listening on 0.0.0.0 port 2200. May 1 10:51:46 host sshd[26019]: Server listening on 0.0.0.0 port 56696. May 1 10:51:46 host sshd[31346]: Received signal 15; terminating. May 1 10:51:46 host sshd[31334]: Received signal 15; terminating. sshd restarted successfully. Would the port be 22 or 2200? There is also 56696. Thoughts?
    0
  • cerion
    I tried port 2200 and it prompted me to login. Attached are the results. FWIW, the 56696 wouldn't connect.
    0
  • cPanelLauren
    It looks like based on that last screenshot the password is incorrect or password authentication is disabled - did it ask you for a password or just tell you access denied? What is set at WHM>>Security Center>>SSH Password Authorization Tweak?
    0
  • cerion
    Ok. We're getting somewhere! This is what I see when I run: crontab -u root -l It may as well be in Chinese as far as I'm concerned. Thoughts?
    0
  • cPanelLauren
    Oh, you got in! I see there, it's the 10th line up from the bottom. To edit the crontab you can do: crontab -u root -e
    Just remove the associated entry (the full entry is as follows): 59 12 * * * cd /usr/local/cpanel/whostmgr/docroot/cgi/fantastico/scripts/ ; /usr/local/cpanel/3rdparty/bin/php cron.php > /dev/null 2>&1
    0
  • cerion
    Please review:
    0
  • cPanelLauren
    Hello, You need to do this through the crontab interface which I showed you how to do: To edit the crontab: crontab -u root -e
    Just entering in the command as listed in the cron through the SSH interface will not make any changes
    0
  • cerion
    After I enter it and remove the offending line, when I exit and choose to save, there are a number of options: What is the next move?
    0
  • cPanelLauren
    When you're in this UI and you've removed it already - hit enter then save it. The text editor being used here is nano, this should be helpful: Linux Nano Editor Explained for Beginners (10 Examples)
    0
  • cerion
    Awesome. It's done. Thank you for your patience. I know this took a lot longer than it should have!
    0
  • cPanelLauren
    No worries, I'm glad you were able to get it resolved and you learned something new :)
    0

Please sign in to leave a comment.