after applying #23 pleskbackup fails on some domains with "Unable to create dump".
in verbose mode the psa_dump.log shows an XML Parser Error
the xml-line (141) it complains about contains garbage, but it is special character data (in my case umlauts in some comments) from ANSI-encoded(!) custom config files (vhost.conf, etc)
QUICK FIX: all *conf files eventually containing special chars must be properly encoded (utf-8 without BOM)
SUGGESTED PLESK FIX: there is no need to parse these fields , backup_restore_helper should mark their content as unparsed character data CDATA,
(i guess this was the case before MU#23 since the error occured suddenly)
in verbose mode the psa_dump.log shows an XML Parser Error
Code:
[25284]: 13:32:52 DEBUG Exec: /usr/local/psa/bin/sw-engine-pleskrun /usr/local/psa/admin/sbin/backup_restore_helper --backup-subscription domain.tld
[25284]: 13:32:54 DEBUG Unable to create dump:
not well-formed (invalid token) at line 141, column 17, byte 7313 at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/XML/Parser.pm line 187
the xml-line (141) it complains about contains garbage, but it is special character data (in my case umlauts in some comments) from ANSI-encoded(!) custom config files (vhost.conf, etc)
Code:
# stark genutzter host (da mehrere sites gehosted, FcgidMaxProcessesPerClass h�� setzen)
FcgidMaxProcessesPerClass 4
# test: extralanges timout f��ultiple file uploads.
QUICK FIX: all *conf files eventually containing special chars must be properly encoded (utf-8 without BOM)
SUGGESTED PLESK FIX: there is no need to parse these fields , backup_restore_helper should mark their content as unparsed character data CDATA,
(i guess this was the case before MU#23 since the error occured suddenly)
Last edited: