"Unable to execute SQL: MySQL server has gone away" Backup-Error

[_sarbc]

hi guys!
all my clients without backups!
as it turned out, backup don't work almost a month ... I am very afraid of their clients )


I ran backup manually for some domain and have the following:

/opt/psa/bin/pleskbackup domains-name -v --output-file=- etks.info
Domains [0/1]
Domains [1/1]
-------------- Start print backup log hire --------------
<?xml version="1.0" encoding="UTF-8"?>
  <execution-result status="error" log-location="/opt/psa/PMM/sessions/2013-09-17-101809.677/migration.result">
    <object name="etks.info" type="domain">
      <message id="a571e90f-9234-4c1f-8cc9-62f7967f2310" severity="warning" code="msgtext">
        <description>Timeout occured during mysql query. Reconnecting.</description>
      </message>
      <message id="1b6d215e-f1aa-403e-8fd7-e1adc42fe3b3" severity="error" code="msgtext">
        <description>Unable to execute SQL: MySQL server has gone away</description>
      </message>
      <object name="etks" type="mysql">
        <message id="7df897b7-6169-4cb5-86cf-f8ba3da5e60a" severity="error" code="msgtext">
          <description>Failed to execute backup database</description>
        </message>
        <message id="2a609af0-aa8b-47a7-88db-26b280b1f150" severity="error" code="msgtext">
          <description>Failed to pack files backup_etks_1_1309171018 in /backup/domains/etks.info/databases/etks_1 [ 875758411776 bytes free of 1969009598464 bytes total on mount point /backup]</description>
        </message>
      </object>
    </object>
  </execution-result>
-------------- End print backup log hire --------------

You can view additional information in the log file located in /opt/psa/PMM/sessions/2013-09-17-101809.677 directory. This directory will be removed automatically after 30 days

Runtime error: The backup failed with errors!

look what the last MU:

cat /root/.autoinstaller/microupdates.xml
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<patches>
    <product id="plesk" version="10.4.4" installed-at="20120716T153408">
        <patch version="55" timestamp="" installed-at="20130826T130806" />
    </product>
</patches>

link on update (http://kb.parallels.com/116338) - rejected!

look what further ...

cat /opt/psa/PMM/sessions/2013-09-17-101809.677/migration.log 
[10:18:19|INFO: 9053:p.log] pmm-ras started : /opt/psa/admin/bin/pmm-ras --get-dump-info --dump-file-specification=domains/etks.info/backup_etks.info_info_1309171018.xml --with-feedback --session-path=/opt/psa/PMM/sessions/2013-09-17-101809.677 --verbose
[10:18:19|INFO: 9053:p.log] Repository '/backup' initialising...
[10:18:19|INFO: 9053:p.log] Repository '/backup': Initialized
[10:18:19|INFO: 9053:p.log] Repository '/backup': Get backup info from domains/etks.info/backup_etks.info_info_1309171018.xml
[10:18:19|INFO: 9053:p.log] Repository '/backup': Get initial backup info from dir domains/etks.info/.discovered/backup_etks.info_info_1309171018
[10:18:19|INFO: 9053:p.log] Get backup params from listing of domains/etks.info/.discovered/backup_etks.info_info_1309171018
[10:18:19|INFO: 9053:p.log] Read properties from xml domains/etks.info/backup_etks.info_info_1309171018.xml
[10:18:19|INFO: 9053:p.log] Repository '/backup': Validate backup domains/etks.info/backup_etks.info_info_1309171018.xml
[10:18:19|INFO: 9053:p.log] Repository '/backup': Validate backup (common phase) domains/etks.info/backup_etks.info_info_1309171018.xml
[10:18:19|INFO: 9053:p.log] Repository '/backup': Get items 'status' for discovered 'backup_etks.info_info_1309171018' at path domains/etks.info
[10:18:19|INFO: 9053:p.log] Executing utility: /opt/psa/admin/sbin/backup_sign verify /backup//domains/etks.info/backup_etks.info_info_1309171018.xml
[10:18:19|INFO: 9053:p.log] The utility executed with the return code 0
[10:18:19|INFO: 9053:p.log] Validate content files backup_statistics_1309171018.tgz at dir domains/etks.info/phosting
[10:18:19|INFO: 9053:p.log] Validate content files backup_statistics_1309171018.tgz at dir domains/etks.info/phosting
[10:18:19|INFO: 9053:p.log] Validate content files backup_statistics_1309171018.tgz at dir domains/etks.info/phosting
[10:18:19|INFO: 9053:p.log] Validate content files backup_statistics_1309171018.tgz at dir domains/etks.info/phosting
[10:18:19|INFO: 9053:p.log] Validate content files backup_statistics_1309171018.tgz at dir domains/etks.info/phosting
[10:18:19|INFO: 9053:p.log] Validate content files backup_statistics_1309171018.tgz at dir domains/etks.info/phosting
[10:18:19|INFO: 9053:p.log] Validate content files backup_conf_1309171018.tgz at dir domains/etks.info/phosting
[10:18:19|INFO: 9053:p.log] Repository '/backup': Create item 'status_OK' for discovered 'backup_etks.info_info_1309171018' at path domains/etks.info
[10:18:19|INFO: 9053:p.log] Repository '/backup': Put info to domains/etks.info/.discovered/backup_etks.info_info_1309171018/status_OK
[10:18:19|INFO: 9053:p.log] pmm-ras finished. Exit code: 0

cat /opt/psa/PMM/sessions/2013-09-17-101809.677/psadump.log
[8944]: 06:18:10 INFO ------------------------------------------------------------
[8944]: 06:18:10 INFO Migration status reporting initialized.
[8944]: 06:18:10 INFO Status file: /opt/psa/PMM/sessions/2013-09-17-101809.677/dump-status.xml
[8944]: 06:18:10 INFO ------------------------------------------------------------
[8966]: 06:18:13 ERROR fbc7d2e8-dd91-4c02-80f0-7bd90a1983b5 Unable to create dump: 
 at /opt/psa/PMM/agents/shared/Logging.pm line 84
        Logging::error('Unable to create dump', 'fatal') called at /opt/psa/admin/bin/plesk_agent_manager line 648
        main::__ANON__('Error::Simple=HASH(0x36e7640)', 'SCALAR(0x3045ee8)') called at /usr/share/perl5/Error.pm line 340
        eval {...} called at /usr/share/perl5/Error.pm line 330
        Error::subs::run_clauses('HASH(0x36ca820)', 'Can\'t locate object method "_setFileToRemove" via package "D...', undef, 'ARRAY(0x36caa60)') called at /usr/share/perl5/Error.pm line 427
        Error::subs::try('CODE(0x36d0048)', 'HASH(0x36ca820)') called at /opt/psa/admin/bin/plesk_agent_manager line 650
        main::perform('owner-uid', '00000000-0000-0000-0000-000000000000', 'verbose', 1, 'owner-type', 'server', 'domains-name', 'ARRAY(0x1dde8f8)', 'output-file', ...) called at /opt/psa/admin/bin/plesk_agent_manager line 1217
        main::__ANON__() called at /usr/share/perl5/Error.pm line 409
        eval {...} called at /usr/share/perl5/Error.pm line 408
        Error::subs::try('CODE(0x233b838)', 'HASH(0x233b910)') called at /opt/psa/admin/bin/plesk_agent_manager line 1226
        main::main() called at /opt/psa/admin/bin/plesk_agent_manager line 1228

full in attached file

can be cause is next string:
Error::subs::run_clauses('HASH(0x36ca820)', 'Can\'t locate object method "_setFileToRemove" via package "D...', undef, 'ARRAY(0x36caa60)') called at /usr/share/perl5/Error.pm line 427

what happened to the method _setFileToRemove ?

the same for the other domains ... =(

how can I now sleep peacefully?!

Igor help me and other good guys who use your product!

ps/ tried to attach a file but the form has not earned

 

[_sarbc]

sorry, forgot to specify the version of the product

cat /opt/psa/version
Panel 10.4.4 Debian 6.0 1013111102.18

 

[_sarbc]

Up ............

 

[_sarbc]

Igor, or somebody of the support!!!
This is not funny!!!

Give me a body function _setFileToRemove of a package MysqlShellBackend.pm !

it is not be in directory /opt/psa/PMM/agents/

grep -R _setFileToRemove /opt/psa/PMM/agents/
/opt/psa/PMM/agents/shared/Db/MysqlShellBackend.pm: $self->_setFileToRemove($fileName);

If I remember rightly, a function _setFileToRemove is not declared!

 

[_sarbc]

the duplicate ..

 

[_sarbc]

your silence does you credit!
your silence

I was very lucky
I found an old snapshot of the system and what I see!
there is a body of functions:

cat /opt/psa/PMM/agents/shared/Db/ShellBackend.pm

...

sub _setFileToRemove {
** my ($ self, $ file) = @ _;
** push @ {$ self-> {fileToRemove}}, $ file;
}

sub getFileToRemove {
** my ($ self) = @ _;
** return @ {$ self-> {fileToRemove}};
}

1;

in the original, these two functions are not available!
they are simply not there.

I them added, it worked!

Questions.
1) Why do they have to clean up?
2) If they were removed on purpose, why were calls to them?