Skip to main content

Cpanel install error

Comments

14 comments

  • cPanelLauren
    Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks!
    0
  • atkhosting
    Hi, A similar problem I follow the current issue. Centos 7.7 cPanel 84.0.17 (in cleanup) (in cleanup) at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/DNS/Unbound.pm line 536 during global destruction. cron message in active presentation : Cron /usr/local/cpanel/bin/autossl_check --all
    0
  • cPanelLauren
    Can you please open a ticket using the link in my signature? Once open please reply with the Ticket ID here so that we can update this thread with the resolution once the ticket is resolved. Thanks!
    0
  • MyLifeAsBK
    13970529 @cPanelLauren - this is my ticket number. Same issue.
    0
  • leoihtech
    Hey, Is there any update on this issue. We are also seeing the same message as email notification from CRON . (in cleanup) (in cleanup) at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/DNS/Unbound.pm line 541 during global destruction.
    0
  • cPanelLauren
    You could be receiving that error for a number of reasons, what is the cron running that is producing the error? In the instance of the OP it was a result of a firewall issue where root nameservers were unable to be reached. The ability to reach the root nameservers isn't specific to cPanel, but is expected in a normal webhosting environment. You can read more in the following resources: What are root name servers? | Netnod IANA " Root Servers
    0
  • bloatedstoat
    I am with @leoihtech on this @cPanelLauren and it only started recently. When cron runs this: /usr/local/cpanel/bin/autossl_check --all we receive an email with the same message: " (in cleanup) (in cleanup) at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/DNS/Unbound.pm line 541 during global destruction." CLOUDLINUX 6.10 v84.0.17 We know of no connectivity issues at all. When run manually from the cli no such error is generated. There are some warnings generated however; but these are instances where an expected text file cannot be retrieved from the user's directory purely because the domain owner's DNS points only an A record for www.domain to the server IP rather than a CNAME. If the check queried www.domainname.com.au the request would succeesd. I don't want to get away from the original thread here but here's an example of the error generated: Processing "account_username""s local DCV results " Local DNS DCV error (domainname.com.au): The DNS query to "_cpanel-dcv-test-record.domainname.com.au" for the DCV challenge returned no "TXT" record that matches the value "_cpanel-dcv-test-record=fgdfg....". Local DNS DCV error (mail.domainname.com.au): The DNS query to "_cpanel-dcv-test-record.domainname.com.au" for the DCV challenge returned no "TXT" record that matches the value "_cpanel-dcv-test-record=fgsdfgsfg...". Analyzing "domainname.com.au""s DCV results " Impediment: NO_UNSECURED_DOMAIN_PASSED_DCV: Every unsecured domain failed DCV. The system has completed "account_username""s AutoSSL check.
    0
  • LBJ
    G'day cPanel Team, Is there any update on this? We see the error each day on just one of our servers for the CRON /usr/local/cpanel/bin/autossl_check --all. (in cleanup) (in cleanup) at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/DNS/Unbound.pm line 541 during global destruction.
    DNS resolution is normal for all tests. Is there any chance you could update the Unbound.pm to script provide a more complete error message at... destroy_context( delete $[0]->{'_ub'} );
    That would help greatly. Thanks. Best regards, LBJ
    0
  • cPanelLauren
    We did release some changes for libunbound related items that would affect this (especially with error messages that are being returned) in v84.0.19 - they're noted in the changelogs here: Change Logs - Change Logs - cPanel Documentation CPANEL-30649 hasn't been resolved for this version of cPanel/WHM yet - though it was requested to be backported to this version. It is available in cPanel v86 which is currently in EDGE
    0
  • LBJ
    We did release some changes for libunbound related items that would affect this (especially with error messages that are being returned) in v84.0.19

    Thank you. We'll wait until that flows through to the stable stream. Best regards, LBJ
    0
  • HostXNow_Chris
    I noticed the same error a few times too (in cleanup) (in cleanup) at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/DNS/Unbound.pm line 581 during global destruction.
    Hopefully, it'll be fixed soon.
    0
  • PeteS
    Same error. Began 1/21/20. Not associated with a cPanel update, nor any change on server (unless it has to do with cert expiration dates). (in cleanup) (in cleanup) at /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int/DNS/Unbound.pm line 581 during global destruction.
    @cPanelLauren - You say it can be caused by several conditions, related to libunbound, and I see from the threads you referenced that it's been a issue for a couple months. IS the reason I am just now seeing it (the last two runs) is because certs are getting closer to expiring? (The closed expiration date is 25 days from now.) Elsewhere I'm seeing reports that it is not caused by ipv6 being enabled, nor any other specific, and that there is no current work-around. I believe you stated elsewhere that it is supposed to be fixed in v86 (and hopefully backported into v84). I have been on v84.0.20 for a while before this appeared. The information seems quite varied, and it is not clear what triggers the condition. Why did mine errors just start two days ago? Am I correct that the consequence of this is that certs will not renew? (If so, is it some, all, or only certain ones?) Are there other consequences and concerns? Will this be fixed in v86? Please clarify.
    0

Please sign in to leave a comment.