Can't locate install/LegacyBackups.pm in @INC
Starting on May 30th, which coincides with the first day after 11.78.0.24 was upgraded to 11.80.0.9, the Cron Daemon has sent this message as it's running /scripts/cpbackup:
Can't locate install/LegacyBackups.pm in @INC (you may need to install the install::LegacyBackups module) (@INC contains: /usr/local/cpanel /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib/x86_64-linux-64int /usr/local/cpanel/3rdparty/perl/528/lib/perl5/cpanel_lib /usr/local/cpanel/3rdparty/perl/528/lib/perl5/5.28.0/x86_64-linux-64int /usr/local/cpanel/3rdparty/perl/528/lib/perl5/5.28.0 /opt/cpanel/perl5/528/site_lib/x86_64-linux-64int /opt/cpanel/perl5/528/site_lib) at /usr/local/cpanel/scripts/cpbackup line 38.
BEGIN failed--compilation aborted at /usr/local/cpanel/scripts/cpbackup line 38.
I followed CpanelMichael's advice found in a thread with similar subject - run /scripts/upcp and then try rebuilding the RPM database. Following those, /scripts/cpbackup yielded the same result (above).
What is the solution to this?
As an aside, Home " Backup " Backup Configuration is set to run backups - saving a few days worth on locally and remotely. Why do I need "this other" backup that is currently failing?
-
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 -
Same problem, what is the solution? OK, is this the issue; line 46, use install::LegacyBackups (); 0 -
A ticket for this issue has not yet been opened that I am aware of, if you're experiencing an issue with this I'd encourage you to please open a ticket with us and update here with the ticket ID once it's open. Thanks! 0 -
Nah, I am tired of tickets, every time new update new problems, aren't you guy even testing ? 0 -
Our QA team works diligently to test as thoroughly as possible, unfortunately, there are sometimes occurrences such as this one where the issue cannot be accounted for, in this case these are literally the only two reports of this occurring that I can find. While I believe that removing the /usr/local/cpanel/scripts/cpbackup cron job will resolve the issue temporarily, it will not be a permanent fix. We did remove the legacy backup module but understanding why it's occurring on these two systems is paramount to actually resolving the issue in the long run and for any others that may be affected. 0 -
Hello, The following case was included with cPanel & WHM version 80: Implemented case CPANEL-25650: Remove one time migration script install::LegacyBackups. With this change, we removed support for the legacy backups one-time migration task from /scripts/cpbackup (this was used to populate the cPanel user file correctly for accounts restored/transferred from legacy cPanel & WHM versions). While legacy backups are in-fact deprecated, I was unable to reproduce this error message on a test server running cPanel & WHM version 80.0.20 after manually enabling legacy backups. @David Colter and @Wabun, are either of you able to confirm if the cpbackup cron failure notification reports continue on cPanel & WHM version 80.0.18 or 80.0.20? Thank you. 0 -
I have been receiving the reported error notification as well starting on 5/30/2019. Although it appears backups are functioning correctly but I haven't had time to verify. Currently running WHM v80.0.20 on CENTOS 6.10 kvm 2.6.32-754.12.1.el6.x86_64 Daily compressed local backups, per account, w/ system files. Also backup to google drive. 0 -
I have been receiving the reported error notification as well starting on 5/30/2019. Although it appears backups are functioning correctly but I haven't had time to verify. Currently running WHM v80.0.20 on CENTOS 6.10 kvm 2.6.32-754.12.1.el6.x86_64 Daily compressed local backups, per account, w/ system files. Also backup to google drive.
Hello @kdub, Thank you for taking the time to let us know. Do you mind submitting this report as a0 -
Your Support Request ID is: 12751945 0 -
New Your Support Request ID is: 12751945
Thanks, I've added a note to the ticket and will update this thread with the outcome once it's closed.0 -
Hello Everyone, In ticket 12751945, we discovered that /usr/local/cpanel/scripts/cpbackup and /scripts/cpbackup were excluded from updates due to their inclusion in the /etc/cpanelsync.exclude file includes entries for the legacy backup scripts: cat /etc/cpanelsync.exclude
If you see entries for the "cpbackup" script; remove those lines, save the file, and update cPanel using the command below:/scripts/upcp --force
Thank you.0 -
I've cleared /etc/cpanelsync.exclude and run /scripts/upcp both manually and via nightly cron. I continue to receive the legacy notification. stat /usr/local/cpanel/scripts/cpbackup indicated the script is not updating automatically. Perhaps this won't update until a new cpanel version is installed? Where can I find the current cpbackup script so I can manually replace? Also, wanted to mention that I have no idea how cpbackups was added to the exclude file. cPanel support has stated that this could only have been done by manual user entry. However, the cpanelsync.exclude modify/change timestamp aligns perfectly with a daily cron updating cpanel from 11.68.0.37 to 11.68.0.38 that ran 2018-05-03 1:43 UTC. Unfortunately, the /root/.bash_history file doesn't go back that far so I suppose I'll never know the root cause. Anyway, much thanks to cPanel support's lightening fast response to my ticket. Top notch support. 0 -
I've cleared /etc/cpanelsync.exclude and run /scripts/upcp both manually and via nightly cron. I continue to receive the legacy notification. stat /usr/local/cpanel/scripts/cpbackup indicated the script is not updating automatically. Perhaps this won't update until a new cpanel version is installed? Where can I find the current cpbackup script so I can manually replace?
Hello @kdub, Try forcing a cPanel update using the command below:/scripts/upcp --force
If this doesn't replace the files, reply to the support ticket to let us know and we'll check to see why the file is not automatically replaced with the new version. Thank you.0 -
/scripts/upcp --force appears to have successfully updated cpbackup script and resolved the issue. Thanks for your help. 0 -
/scripts/upcp --force appears to have successfully updated cpbackup script and resolved the issue. Thanks for your help.
I'm glad to see that helped. Thanks for sharing the outcome.0 -
The following case was included with cPanel & WHM version 80: Implemented case CPANEL-25650: Remove one time migration script install::LegacyBackups. With this change, we removed support for the legacy backups one-time migration task from /scripts/cpbackup (this was used to populate the cPanel user file correctly for accounts restored/transferred from legacy cPanel & WHM versions). While legacy backups are in-fact deprecated, I was unable to reproduce this error message on a test server running cPanel & WHM version 80.0.20 after manually enabling legacy backups. @David Colter and @Wabun, are either of you able to confirm if the cpbackup cron failure notification reports continue on cPanel & WHM version 80.0.18 or 80.0.20?
@cPanelMichael Sorry to have been absent for all the discussion. I lost sight of this thread. I can confirm that the original error message continues thru 80.0.18, 80.0.20 and even 80.0.22. I had turned off the cPanel backup and then found this discussion. I found the suggestion made on July 3rd, ran thru those steps, turned cpbackup back on. Will post tomorrow's result...0
Please sign in to leave a comment.
Comments
20 comments