cPanel Question posted in
The official documentation can be seen here.

Faulty cron job: safe to delete? – CPanel

One of the automatically generated cron jobs, namely:

2 0 * * * /usr/local/bin/perl /usr/local/cpanel/3rdparty/quickinstall/scripts/checkupdates.pl

outputs this:

    Bareword found where operator expected at /usr/local/cpanel/Cpanel/JS/Variations.pm line 20, near "$filename =~ s{/js2"
      (Might be a runaway multi-line // string starting on line 19)
            (Missing operator before js2?)
    syntax error at /usr/local/cpanel/Cpanel/JS/Variations.pm line 20, near "$filename =~ s{/js2"
    Global symbol "$filename" requires explicit package name at /usr/local/cpanel/Cpanel/JS/Variations.pm line 21.

and many other errors.

Would it be safe to delete this cron job? especially considering that:

  • it is faulty in the first place;
  • I don’t have access to the Perl script in question and can’t fix it;
  • quickinstall modules (such as WP and Moodle) properly check for updates themselves.

I’m using a shared hosting on HostGator and, as such, don’t have a shell access; all I can do is work thru cPanel.

Tags:

2

Answers


  1. 0

    As far as I know that cron entry is not a default cron entry added by cPanel. If the cron is faulty you can just delete it. I jave just checked on my cPanel/WHM server, I do not have such a cron job, I do not have that quickinstall folder. Most probably you are using some 3rd party apps (like softaculous for example) so that’s why the cron is there. You could also open a support request to HostGator and see what they say.

    Login or Signup to reply.
  2. 0

    I’m not familiar with cPanel, so I can’t address that aspect of the question, but, from the Perl side, I can tell you that deleting the cron job will do no (additional?) harm. Because there’s a syntax error in the Perl code, the checkupdates program is already not running (and, indeed, can’t run).

    Checking with any appropriate vendor to see whether they can provide a fixed copy of Cpanel::JS::Variations (the source library which contains the actual error) would likely be a good idea, as it may be used by other pieces of Cpanel which actually are important, but the cron job isn’t doing anything other than generating email to tell you it failed.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search