• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Server backup is completed, but some errors occured during backup.

B

bsysbvba

Guest
Can't locate XML/Parser/Style/Dom.pm in @INC

Hi there,

Is there anybody who van help me with this one. My backup script doesn't work any more (new server FC2 with Plesk 7..5.4). Look what I get when I run psadump :

/usr/local/psa/bin/psadump -f /backup/$(date +%F) --force --nostop --nostop-domain --no-internal-zip --do-not-dump-logs

==================================================

Attempt to connect to MySQL server ... done
==================================================


Checking packages installation ... done
Postgres is not configured (unable to define pg admin login and password).
Postgres is not configured: all postgres databases will not be dumped.

==================================================


Making backup to file '/backup/2006-02-12'

[Sun Feb 12 21:37:39 2006] dumping directory '/var/www/vhosts/.skel/0/.' ... error!
sh: line 1: -c: command not found
An error was occured during execution: " -c -f - -C '/var/www/vhosts/.skel/0' '.' "

==================================================


**************************************************
********************
* ATTENTION: DUMP PROCEDURE HAS BEEN ABORTED, BECAUSE AN ERROR OCCURED! *
* *
* Using the dump file for restoration is dangerous !!! *
**************************************************
********************


Server backup is completed, but some errors occured during backup.

PS: Removing .skel does not work.
 
Hi,

As there is nobody who can solve my problem I was wandering if folowing questions could give us clue:
- Is there a way of doing the psadump in a more verbose manner?
- Or should a YUM upgrade of whatever PERL library solve my problem?
- What libary is used for doing PSADUMP?

E.
 
Can't locate XML/Parser/Style/Dom.pm in @INC

I found something in my psadump log file. But I really don't know how to fix this.

Any ideas?

psadump: Can't locate XML/Parser/Style/Dom.pm in @INC (@INC contains: /usr/local/psa/lib/perl5 . /usr/local/psa/lib/perl5/5.8.3
/usr/local/psa/lib/perl5/5.8.3/i386-linux-thread-multi /usr/local/psa/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/local/psa/lib/perl5/site_perl/5.
8.3 /usr/lib/perl5/5.8.3/i386-linux-thread-multi /usr/lib/perl5/5.8.3 /usr/lib/perl5/site_perl/5.8.3/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.3 /
usr/lib/perl5/site_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread
-multi /usr/lib/perl5/site_perl/5.8.2 /usr/lib/perl5/site_perl/5.8.1 /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.3
/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.2/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.1/i386-linux-thread-multi /usr/lib/perl5/ven
dor_perl/5.8.0/i386-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.3 /usr/lib/perl5/vendor_perl/5.8.2 /usr/lib/perl5/vendor_perl/5.8.1 /usr/lib/perl5/vend
or_perl/5.8.0 /usr/lib/perl5/vendor_perl) at /usr/lib/perl5/vendor_perl/5.8.3/i386-linux-thread-multi/XML/Parser.pm line 55.
 
Back
Top