• Resolved mwarbinek

    (@mwarbinek)


    This error comes up for each job run,

    “WARNING: Database error Cannot load from mysql.proc. The table is probably corrupted for query SHOW FUNCTION STATUS”

    and

    “WARNING: Database error Cannot load from mysql.proc. The table is probably corrupted for query SHOW PROCEDURE STATUS”

    Questions
    1. Is there a fix to this?
    2. How does this effect using the backup to restore the website?

    Log Report
    Log Report below. I {removed} anything to do with identifying the website, reason is to avoid hackers.

    
    [INFO] BackWPup 3.3.7; A project of Inpsyde GmbH
    [INFO] WordPress 4.7.4 on {removed}
    [INFO] Log Level: Normal
    [INFO] BackWPup job: 2017 Build Backups
    [INFO] Logfile is: {removed}
    [INFO] Backup file is: {removed}
    [25-Apr-2017 11:55:22] 1. Try to backup database …
    [25-Apr-2017 11:55:23] Connected to database {removed} on {removed}
    [25-Apr-2017 11:55:25] WARNING: Database error Cannot load from mysql.proc. The table is probably corrupted for query SHOW FUNCTION STATUS
    [25-Apr-2017 11:55:25] WARNING: Database error Cannot load from mysql.proc. The table is probably corrupted for query SHOW PROCEDURE STATUS
    [25-Apr-2017 11:55:26] Added database dump "{removed}" with 19.73 MB to backup file list
    [25-Apr-2017 11:55:26] Database backup done!
    [25-Apr-2017 11:55:28] 1. Trying to make a list of folders to back up …
    [25-Apr-2017 11:55:47] Added "wp-config.php" to backup file list
    [25-Apr-2017 11:55:47] 981 folders to backup.
    [25-Apr-2017 11:55:49] 1. Trying to create a WordPress export to XML file …
    [25-Apr-2017 11:55:57] Check WP Export file …
    [25-Apr-2017 11:55:57] WP Export file is a valid WXR file.
    [25-Apr-2017 11:55:57] Added XML export "{removed}" with 4.85 MB to backup file list.
    [25-Apr-2017 11:56:00] 1. Trying to generate a file with installed plugin names …
    [25-Apr-2017 11:56:00] Added plugin list file "{removed}" with 3.20 KB to backup file list.
    [25-Apr-2017 11:56:00] 1. Trying to generate a manifest file …
    [25-Apr-2017 11:56:00] Added manifest.json file with 7.53 KB to backup file list.
    [25-Apr-2017 11:56:00] 1. Trying to create backup archive …
    [25-Apr-2017 11:56:00] Compressing files as TarGz. Please be patient, this may take a moment.
    [25-Apr-2017 12:00:30] ERROR: Aborted by user!
    
Viewing 15 replies - 1 through 15 (of 16 total)
  • Hi @mwarbinek,

    This is an issue with your database tables. Generally this happens when there is an incompatibility with schema changes between database versions.

    I’m assuming you don’t have root access. I’d report this error to your host and ask them if they can run the mysql_upgrade command on your database.

    If we were able to help with our answer, please mark this ticket as resolved. Otherwise, let us know if you need further support and we’ll be happy to help! ??

    If you are happy with our free plugin and support, please make us happy and take 30 seconds to leave a review. ?? We’d really appreciate that.

    Thread Starter mwarbinek

    (@mwarbinek)

    I did contact my website host and they claim, according to their database expert, this warning comes because there are no items or no content in those specific data base tables. – Does that makes sense to you? — because it doesn’t to me since this is the first time in the whole year I used the plugin at the same website.

    Also, If I have to restore a website that holds these 2 warnings, will there be a problem restoring?

    Hi @mwarbinek,

    No it does not make sense to me. If the table is empty, the plugin will detect that and you won’t get any warning messages. This message comes directly from MySQL.

    Please show them this link which describes this warning message: https://www.myguysolutions.com/2013/10/30/how-to-resolve-mysql-error-code-1548-cannot-load-from-mysql-proc-the-table-is-probably-corrupted/

    Also, your data will probably be okay, but I cannot be absolutely certain. I would suggest getting this warning message resolved.

    Thread Starter mwarbinek

    (@mwarbinek)

    Since your the author of this plugin,

    Can I ask for a confirmation with this because I am going to show the Website host this string.

    (1) If I understand what you are saying, the claim that the SQL tables being empty would generate the error is a false claim or “incorrect” or “not true”?

    (2) The “required” fix for this error is to do a “mysql_upgrade” command on the SQL database?

    @mwarbinek, yes both of those are true. Let me know if your host is able to resolve the issue.

    Thread Starter mwarbinek

    (@mwarbinek)

    Much thanks, especially for the link. ??

    Thread Starter mwarbinek

    (@mwarbinek)

    It is going to take a few days on this. I just sent the request to the hosting service and referenced this string and the link you gave above.

    @mwarbinek, no problem. Please let us know if anything else is needed.

    @mwarbinek, have you gotten any response from your host? Please let me know if there’s anything else I can help with. ??

    Thread Starter mwarbinek

    (@mwarbinek)

    Yes I did and I was not happy.

    Here is a little background, because I want Google to cache this.

    MY client wanted to have their business website hosted by Shaw Cable here in BC Canada. Shaw uses Hostopia to do the server end, Shaw does the hosting Admin end.

    According to Shaw/Hostopia, their mySQL server version is 5.1.73. It is already 6 versions out of date, as I understand the current version is 5.7.

    According to Shaw, Hostopia is really slow on doing any upgrades and it can be months or 2 years. I have no idea why a hosting service allows themselves to get so outdated.

    Unfortunately, it is what my client wanted, not what I recommended, so now I have to work within an outdated server environment.

    To anyone who finds this string and considers Hostopia or Shaw for hosting their website, please don’t and go with the bigger and more reliable hosting services.

    So any suggestions on how I can do a work around on this so the older database can work in the updates?

    @mwarbinek, I’m sorry to hear about the host. Yes that version is pretty old.

    I think you can likely ignore the warning then, if they won’t do anything about it.

    If you can access cron, you could also run mysqldump on a schedule and dump it into a folder that BackWPup will backup. I’m not sure if the same warning will appear in mysqldump or not.

    Thread Starter mwarbinek

    (@mwarbinek)

    What difference would the mysqldump provide?

    (PS: they finally agreed with your information that I gave them ?? )

    • This reply was modified 7 years, 11 months ago by mwarbinek.

    @mwarbinek, I don’t know unless you try it. It may circumvent the warning messages, but it may not. I’d try a mysqldump to see if you get the same message or not.

    I’m glad they agree with what the issue is at least.

    Thread Starter mwarbinek

    (@mwarbinek)

    Thanks Brandon.

    The posting of the error message in the Admin area is not my concern, I can ignore it if there is no other issues. My concern was any effect on the backup itself and whether the backup file is still usable to restore with, especially using the SQL database file included in the backup to restore the database.

    • This reply was modified 7 years, 11 months ago by mwarbinek.
    • This reply was modified 7 years, 11 months ago by mwarbinek.

    I understand. I believe the backup should still work fine despite the warning.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘Database error Cannot load from mysql.proc.’ is closed to new replies.