ERROR: S3 Service API: String could not be parsed as XML
-
Get the following error with S3 Google cloud service.
ERROR: S3 Service API: String could not be parsed as XML
Regard,
JeeS
Viewing 6 replies - 1 through 6 (of 6 total)
-
[ Moderator Note: Please post code, markup snippet, or log data between backticks or use the code button. ]
[INFO] BackWPup version 3.0.10; WordPress version 3.5.1; A project of Inpsyde GmbH developed by Daniel Hüsken [INFO] This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions. [INFO] BackWPup job: Backup Villa2Go Test; DBCHECK+DBDUMP+DBOPTIMIZE+FILE [INFO] BackWPup cron: 30 3 * * *; ma, 6 mei 2013 @ 07:00 [INFO] BackWPup job started from wp-cron [INFO] PHP ver.: 5.3.22; apache2handler; Linux [INFO] Maximum script execution time is 30 seconds [INFO] MySQL ver.: 5.1.60-log [INFO] curl ver.: 7.23.1; OpenSSL/1.0.0 [INFO] Temp folder is: /home/id02723/domains/villa2go.nl/public_html/test/media/backwpup-98372-temp/ [INFO] Logfile folder is: /home/id02723/domains/villa2go.nl/public_html/test/wp-content/backwpup-98372-logs/ [INFO] Backup type is: archive [INFO] Backup file is: /home/id02723/domains/villa2go.nl/public_html/test/media/backwpup-98372-temp/Backup_Villa2Go_Test_Alles_2013-05-06_07-00-33.zip [06-mei-2013 07:00:33] 1. Try to dump database … [06-mei-2013 07:00:33] Connected to database id02723_wp-test-villa2go on localhost [06-mei-2013 07:00:33] Dump database table "wp_commentmeta" [06-mei-2013 07:00:33] Dump database table "wp_comments" [06-mei-2013 07:00:33] Dump database table "wp_cp_ad_fields" [06-mei-2013 07:00:33] Dump database table "wp_cp_ad_forms" [06-mei-2013 07:00:33] Dump database table "wp_cp_ad_geocodes" [06-mei-2013 07:00:33] Dump database table "wp_cp_ad_meta" [06-mei-2013 07:00:33] Dump database table "wp_cp_ad_packs" [06-mei-2013 07:00:33] Dump database table "wp_cp_ad_pop_daily" [06-mei-2013 07:00:33] Dump database table "wp_cp_ad_pop_total" [06-mei-2013 07:00:33] Dump database table "wp_cp_coupons" [06-mei-2013 07:00:33] Dump database table "wp_cp_order_info" [06-mei-2013 07:00:33] Dump database table "wp_gsom_subscribers" [06-mei-2013 07:00:33] Dump database table "wp_links" [06-mei-2013 07:00:33] Dump database table "wp_ngg_album" [06-mei-2013 07:00:33] Dump database table "wp_ngg_gallery" [06-mei-2013 07:00:33] Dump database table "wp_ngg_pictures" [06-mei-2013 07:00:33] Dump database table "wp_options" [06-mei-2013 07:00:33] Dump database table "wp_postmeta" [06-mei-2013 07:00:33] Dump database table "wp_posts" [06-mei-2013 07:00:33] Dump database table "wp_slp_rep_query" [06-mei-2013 07:00:33] Dump database table "wp_slp_rep_query_results" [06-mei-2013 07:00:33] Dump database table "wp_store_locator" [06-mei-2013 07:00:33] Dump database table "wp_term_relationships" [06-mei-2013 07:00:33] Dump database table "wp_term_taxonomy" [06-mei-2013 07:00:33] Dump database table "wp_terms" [06-mei-2013 07:00:33] Dump database table "wp_usermeta" [06-mei-2013 07:00:33] Dump database table "wp_users" [06-mei-2013 07:00:33] Added database dump "id02723_wp-test-villa2go.sql" with 1.44 MB to backup file list [06-mei-2013 07:00:33] Database dump done! [06-mei-2013 07:00:33] 1. Trying to make a list of folders to back up … [06-mei-2013 07:00:34] 525 folders to back up. [06-mei-2013 07:00:34] 1. Trying to create backup archive … [06-mei-2013 07:00:34] Compression method is ZipArchive [06-mei-2013 07:02:20] Backup archive created. [06-mei-2013 07:02:20] Archive size is 27.03 MB. [06-mei-2013 07:02:20] 4106 Files with 51.61 MB in Archive. [06-mei-2013 07:02:20] 1. Trying to send backup file to S3 Service … [06-mei-2013 07:02:22] Connected to S3 Bucket "backupwebsites" in US [06-mei-2013 07:02:22] Starting upload to S3 Service … [06-mei-2013 07:02:22] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: Entity: line 1: parser error : Start tag expected, '<' not found [06-mei-2013 07:02:22] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: The request's content type is not accepted on this URL. [06-mei-2013 07:02:22] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: ^ [06-mei-2013 07:02:22] ERROR: S3 Service API: String could not be parsed as XML [06-mei-2013 07:02:22] 2. Trying to send backup file to S3 Service … [06-mei-2013 07:02:22] Connected to S3 Bucket "backupwebsites" in US [06-mei-2013 07:02:22] Starting upload to S3 Service … [06-mei-2013 07:02:22] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: Entity: line 1: parser error : Start tag expected, '<' not found [06-mei-2013 07:02:22] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: The request's content type is not accepted on this URL. [06-mei-2013 07:02:22] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: ^ [06-mei-2013 07:02:22] ERROR: S3 Service API: String could not be parsed as XML [06-mei-2013 07:02:22] 3. Trying to send backup file to S3 Service … [06-mei-2013 07:02:23] Connected to S3 Bucket "backupwebsites" in US [06-mei-2013 07:02:23] Starting upload to S3 Service … [06-mei-2013 07:02:23] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: Entity: line 1: parser error : Start tag expected, '<' not found [06-mei-2013 07:02:23] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: The request's content type is not accepted on this URL. [06-mei-2013 07:02:23] WARNING: SimpleXMLElement::__construct() [<a href='simplexmlelement.--construct'>simplexmlelement.--construct</a>]: ^ [06-mei-2013 07:02:23] ERROR: S3 Service API: String could not be parsed as XML [06-mei-2013 07:02:23] 1. Trying to optimize database … [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_commentmeta is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_comments is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_ad_fields is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_ad_forms is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_ad_geocodes is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_ad_meta is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_ad_packs is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_ad_pop_daily is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_ad_pop_total is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_coupons is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_cp_order_info is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_gsom_subscribers is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_links is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_ngg_album is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_ngg_gallery is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_ngg_pictures is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_options is: OK [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_postmeta is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_posts is: OK [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_slp_rep_query is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_slp_rep_query_results is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_store_locator is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_term_relationships is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_term_taxonomy is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_terms is: Table is already up to date [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_usermeta is: OK [06-mei-2013 07:02:23] Result of MyISAM table optimize for wp_users is: Table is already up to date [06-mei-2013 07:02:23] Database optimization done! [06-mei-2013 07:02:23] 1. Trying to check database … [06-mei-2013 07:02:23] Result of table check for wp_commentmeta is: OK [06-mei-2013 07:02:23] Result of table check for wp_comments is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_ad_fields is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_ad_forms is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_ad_geocodes is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_ad_meta is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_ad_packs is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_ad_pop_daily is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_ad_pop_total is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_coupons is: OK [06-mei-2013 07:02:23] Result of table check for wp_cp_order_info is: OK [06-mei-2013 07:02:23] Result of table check for wp_gsom_subscribers is: OK [06-mei-2013 07:02:23] Result of table check for wp_links is: OK [06-mei-2013 07:02:23] Result of table check for wp_ngg_album is: OK [06-mei-2013 07:02:23] Result of table check for wp_ngg_gallery is: OK [06-mei-2013 07:02:23] Result of table check for wp_ngg_pictures is: OK [06-mei-2013 07:02:23] Result of table check for wp_options is: OK [06-mei-2013 07:02:23] Result of table check for wp_postmeta is: OK [06-mei-2013 07:02:23] Result of table check for wp_posts is: OK [06-mei-2013 07:02:23] Result of table check for wp_slp_rep_query is: OK [06-mei-2013 07:02:23] Result of table check for wp_slp_rep_query_results is: OK [06-mei-2013 07:02:23] Result of table check for wp_store_locator is: OK [06-mei-2013 07:02:23] Result of table check for wp_term_relationships is: OK [06-mei-2013 07:02:23] Result of table check for wp_term_taxonomy is: OK [06-mei-2013 07:02:23] Result of table check for wp_terms is: OK [06-mei-2013 07:02:23] Result of table check for wp_usermeta is: OK [06-mei-2013 07:02:23] Result of table check for wp_users is: OK [06-mei-2013 07:02:23] Database check done! [06-mei-2013 07:02:23] One old log deleted [06-mei-2013 07:02:23] Job has ended with errors in 110 seconds. You must resolve the errors for correct execution.
I’d say this is the problem in your case: http://wordpress.org/support/topic/again-problems-backing-up-to-google-storage?replies=4
Hello dhunink and Casper.
I tried it last night ant it seens to work, Thanks.
Jan
Hello @jees, that is great news. If your issue is resolved would you be able to close it as resolved.
Thank you.
Kind and warm regards
Viewing 6 replies - 1 through 6 (of 6 total)
- The topic ‘ERROR: S3 Service API: String could not be parsed as XML’ is closed to new replies.