cron running /usr/local/cpanel/cpkeyclt very frequently

[Skin]

Hello,
I've bought a vps from a few days and I receive every few hours this e-mail :

[Cron <root@host> /usr/local/cpanel/cpkeyclt
Updating cPanel license...Done. Update succeeded.
Building global cache for cpanel...Done/QUOTE]

is it normal or something is misconfigured?

Thanks
Alessio

 

[cPanelNick]

Hello,
I've bought a vps from a few days and I receive every few hours this e-mail :

[Cron <root@host> /usr/local/cpanel/cpkeyclt
Updating cPanel license...Done. Update succeeded.
Building global cache for cpanel...Done

is it normal or something is misconfigured?

Thanks
Alessio

Thats not normal and will likely result in your server being blocked from the cPanel license system.

 

[Skin]

Thanks for your reply,
can you please give me a hint on how to solve this problem?

Alessio

 

[cPanelNick]

We definitely need to investigate why it is configured in this manner. Please open a ticket using the link in my signature.

 

[ThinIce]

heh, sounds like someone is putting unncessary crons in their vps template :p be interested to see how the rest of it is setup if so...

 

[Skin]

Here is the output of crontab -e

0 */8 * * * /usr/local/cpanel/cpkeyclt
0 6 * * * /usr/local/cpanel/scripts/exim_tidydb > /dev/null 2>&1
30 5 * * * /usr/local/cpanel/scripts/optimize_eximstats > /dev/null 2>&1
2,58 * * * * /usr/local/bandmin/bandmin
0 0 * * * /usr/local/bandmin/ipaddrmap
32 4 * * * /usr/local/cpanel/scripts/upcp --cron
0 1 * * * /usr/local/cpanel/scripts/cpbackup
35 * * * * /usr/bin/test -x /usr/local/cpanel/bin/tail-check && /usr/local/cpan$
45 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_mailman_cache &&$
30 */4 * * * /usr/bin/test -x /usr/local/cpanel/scripts/update_db_cache && /usr$
45 */8 * * * /usr/bin/test -x /usr/local/cpanel/bin/optimizefs && /usr/local/cp$
30 */2 * * * /usr/local/cpanel/bin/mysqluserstore >/dev/null 2>&1
15 */2 * * * /usr/local/cpanel/bin/dbindex >/dev/null 2>&1
15 */6 * * * /usr/local/cpanel/scripts/autorepair recoverymgmt >/dev/null 2>&1
*/5 * * * * /usr/local/cpanel/bin/dcpumon >/dev/null 2>&1
52 0 * * * /usr/local/cpanel/whostmgr/docroot/cgi/cpaddons_report.pl --notify
13,28,43,58 * * * * /usr/local/cpanel/whostmgr/bin/dnsqueue > /dev/null 2>&1
21 2 * * * /usr/local/lp/apps/security/cronwrapper.sh

 

[Skin]

We definitely need to investigate why it is configured in this manner. Please open a ticket using the link in my signature.

Done, thanks.

Alessio

 

[JaredR.]

This is the problem:

0 */8 * * * /usr/local/cpanel/cpkeyclt

cPanel verifies its license information periodically without a cron job, so I am not sure why the cron job was configured. cPanel does not create that cron job by default. Have you asked your VPS provider if this is perhaps part of their VPS template?

 

[Skin]

Thanks, I've just removed the line.
I'm going to ask to my VPS provider, so if it is part of their VPS template may be the will remove this cron job.

 

[semseoymas]

Hello:

I have servers at HETZNER... frequently, although my cpanel license are auto-renewed and all is all right, when I try to access WHM I find out the cpanel screen telling something like "this server is not licensed, please run /usr/local/cpanel/cpkeyclt"...

Ok, I run "/usr/local/cpanel/cpkeyclt" as root and WHM is playing fine, but:

- what is the problem? Maybe an eventual communications problem between my server and cpanel licensing servers?
- How could auto-fix?

Sometimes, my clients could not access their WHM/cpanels because of this problem for hours, until I find out and run "/usr/local/cpanel/cpkeyclt" manually, and this is not a good solution.

This way, I think a cronjob running "/usr/local/cpanel/cpkeyclt" each 15 minutes is maybe a great idea.... if the problem appears, max "fall out" time is 15 minutes...

But now you say the cpanel servers are going to ban me... ¿?¿?

Do you have any suggestion for me? (is not a question of IPtables, or adding IPs to whitelisting, I am sure)

Thanks.

- - - Updated - - -

Ahm.... I am sorry... I am writting because:

• at 9am I have entered WHM without problems
• at 10:30am people tell me they couldnt enter whm/cpanel because server not licensed
• minutes later, I needed to run manually cpkeyclt for whm to be active again

Now have a look at the log:

Fri Jan 31 15:12:25 2014: Using full manual DNS resolution
Sat Feb 1 15:13:10 2014: License Update Request
Sat Feb 1 15:13:10 2014: Using full manual DNS resolution
Sun Feb 2 15:15:24 2014: License Update Request
Sun Feb 2 15:15:24 2014: Using full manual DNS resolution
Mon Feb 3 15:20:42 2014: License Update Request
Mon Feb 3 15:20:42 2014: Using full manual DNS resolution
Tue Feb 4 10:46:23 2014: License Update Request
Tue Feb 4 10:46:23 2014: Using full manual DNS resolution
Tue Feb 4 10:46:24 2014: Trying server 208.74.123.34
Tue Feb 4 10:46:24 2014: Server 208.74.123.34 on port 2089 returned:
cPanel License Service Version 29.9 on 'auth3' [AV+,ENCF]
Key Accepted
Key Follows
Tue Feb 4 10:46:24 2014: Obtained lock license file
Tue Feb 4 10:46:24 2014: Accepted license from server 208.74.123.34 on port 2089
Tue Feb 4 10:46:24 2014: License update succeeded after trying 1 server

Great: there is no fail at logs, before my "Tue Feb 4 10:46:23 2014: License Update Request"

Why then, this morning I have had this problem between 9am and 10:46am ?

Thanks.

 

[JaredR.]

If you find the need to run cpkeyclt every 15 minutes, something is wrong. That is not necessary with a normal network configuration.

Unfortunately, the log excerpt does not give enough information for us to tell exactly what is happening. Please submit a ticket so that we can look at this directly and securely. You can post the ticket number here so that we can follow up on it.

 

[semseoymas]

done...

 

[oswgarcia]

Hi,

This is my first post and since my problem is related to this thread and would like to continue the discussion here, if that is OK. I'm getting the same license issue which is fixed after run "/usr/local/cpanel/cpkeyclt" as it is well explained here, but the problem is that I need to do this in more than one hundred servers, so my question is, what is the best time to schedule a cron job that avoid be banned for cpanel servers , is once per month OK or maybe every 15 days?

Thanks,

 

[cPanelMichael]

I'm getting the same license issue which is fixed after run "/usr/local/cpanel/cpkeyclt" as it is well explained here

It's better to address the actual license issue you are experiencing so that you do not have to manually update the license file at set intervals. Could you elaborate on what error or issue you are experiencing?

Thank you.

 

[oswgarcia]

Thanks for your response, we finally discover the cause of our problem, there was a wrong script which changed the hostname of the servers, for that reason an update of the license was needed.

I have already notified this to my team, and there is not reason to have a cron job updating the license.

Thanks again,

 

[cliper]

I'm curious is the system was compromised?
I had the same line in my crontab:
0 */8 * * * /usr/local/cpanel/cpkeyclt

Not sure why.

stat /usr/local/cpanel/cpkeyclt
File: ‘/usr/local/cpanel/cpkeyclt’
Size: 14125899 Blocks: 27592 IO Block: 4096 regular file
Device: fd03h/64771d Inode: 553592 Links: 1
Access: (0700/-rwx------) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2016-04-29 00:00:01.718000000 -0400
Modify: 2016-04-26 22:32:23.013000000 -0400
Change: 2016-04-26 22:33:11.493000000 -0400
Birth: -

 

[Skin]

Hello cliper, in my case the system was not compromised, all the VPS i buy from my provider have this problem, so i think is part of their VPS template.

 

[cliper]

ah! :D thank you. So it must be a template then. thanks.

 

[cPanelMichael]

ah! :D thank you. So it must be a template then. thanks.

Hello,

You may want to report this to your VPS hosting provider so they can adjust their templates to address the problem.

Thank you.