• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Plesk Backup Error

Boindil

New Pleskian
Hi,
today I received like 20 mails for the last 20 backups (were sent today according to pmmcli_daemon.log).

Code:
[2015-04-17 22:42:02] Action param: session_id:/opt/psa/PMM/sessions/2015-04-17-221202.885
[2015-04-17 22:42:02] Action param: session_id:/opt/psa/PMM/sessions/2015-04-16-221202.335

.. and so on

In these mails I get the following message (with different IDs)
Code:
<?xml version="1.0" encoding="UTF-8"?>
  <execution-result status="warnings" log-location="/opt/psa/PMM/sessions/2015-04-17-221202.885/migration.result">
    <object name="server" type="server">
      <object name="hob_plesk_admin" type="client" uuid="client#hob_plesk_admin">
        <object name="mydomain.de" type="domain" uuid="domain#mydomain.de">
          <object name="mydomain.de" type="hosting">
            <message id="5a3a06ac-d816-44df-85c9-d2bd6d2220b5" severity="warning" code="msgtext">
              <description>Encoding::encode: source UTF-8 encoding declared, but invalid UTF-8 sequence occured. Falling back to ISO-8859-1</description>
            </message>
            <message id="a5f841d4-0656-4157-87fc-1b37e9012141" severity="warning" code="msgtext">
                <description>Encoding::encode: source UTF-8 encoding declared, but invalid UTF-8 sequence occured. Falling back to ISO-8859-1</description>
            </message>
            <message id="a9289c20-c1a0-45ff-8602-7312596861ce" severity="warning" code="msgtext">
              <description>Encoding::encode: source UTF-8 encoding declared, but invalid UTF-8 sequence occured. Falling back to ISO-8859-1</description>
            </message>
            <message id="6dad4419-1542-4b4c-86b1-0ccc5660e921" severity="warning" code="msgtext">
               <description>Encoding::encode: source UTF-8 encoding declared, but invalid UTF-8 sequence occured. Falling back to ISO-8859-1</description>
            </message>
          </object>
        </object>
      </object>
    </object>
  </execution-result>

How to fix the error described in the mails? I see no indication of where the error occured (specific file/folder).

Thanks in advance
 
Hi, your post in a different thread helped identifying the files.

Go to /var/www/vhosts/ and run two commands:

# find . -print | sed 's;[^/]*/;|___;g;s;___|; |;g' > files1.txt
# grep --color='auto' -P -n "[\x80-\xFF]" files1.txt

With first command file files1.txt with all directories structure will be created.
Second command will highlight by red all non-usual symbols in files1.txt

There were a few files with german characters but also one with russian chars (language file).

I changed the filenames and hope its working now. Maybe it would be a good thing to add this to KB124608.

Still i think its interesting, that the following occured:
1. Me getting about 20 mails for different backups at once, now every day - other mails were sending fine the whole time.
2. That error taking place out of a sudden. It was working fine about 12 months now.

Greetings
 
Last edited:
Well the solution worked.

But I noticed, that yesterday the backup threw an error:
Unable to rotate dump: The dump rotation is failed with code '126' at /opt/psa/admin/bin/plesk_agent_manager line 1038

Greetings
 
The last error;
Unable to rotate dump: The dump rotation is failed with code '127' at /opt/psa/admin/bin/plesk_agent_manager line 1038 any ideas what that might be? How to fix that.
 
Back
Top