Error: Unable to export file as file: pmm-ras failed (Error code = 1): STDOUT: Transport error: unab

[ae9803]

Hi Guys,
I am receiving this error "Error: Unable to export file as file: pmm-ras failed (Error code = 1): STDOUT: Transport error: unable to read file backup_1509160104.tar: Curl error: Failed writing received data to disk/application STDERR:".
I am currently using Centos 7.0. I receive this error when I am trying to run a backup from a remote FTP. This error is related to this, http://kb.odin.com/en/118644

But I have no idea how to fix it. Any ideas?

 

[IgorG]

But I have no idea how to fix it. Any ideas?

Could you please explain why yo can't use solution from mentioned KB article?

 

[ae9803]

Could you please explain why yo can't use solution from mentioned KB article?

Thankyou for your reply IgorG,
The reason why I am having an issue is because the partition "/" maxes out at 100% when I try to restore using a backup, and the KB article doesnt really explain how I can fix it, I am not sure if I need to increase the partition or what I can do.

Thanks,
Jake

 

[IgorG]

Just remove all the unnecessary large files and directories to free more space on that partition.

 

[ae9803]

Just remove all the unnecessary large files and directories to free more space on that partition.

I did that but I quickly run out of space again, its in "/" and I only have 43% unused and the zipped folder is about 11gb, however, I literally just started with a clean slate dedicated server, installed 6.6 centos and plesk, and I cant run the backup. Because of the lack of space on that partitition. is there anyway I can put the ftp file on a different partition, if so, how?

 

[ae9803]

Just remove all the unnecessary large files and directories to free more space on that partition.

This is what I was looking for,
http://kb.odin.com/en/5816

 

[ae9803]

This is what I was looking for,
http://kb.odin.com/en/5816

I did follow the instructions, however, it will only down the file size to the desired folder but it still does something in "/" that causes it to reach 100%

 

[Dmitry Y.]

There are an issue in Plesk for Unix version (PPP-11017), that DUMP_TMP_D actually does not used for exporting dumps to FTP. Instead it uses /usr/local/psa/PMM/tmp
You can mount some storage to this path as workaround

 

[ae9803]

There are an issue in Plesk for Unix version (PPP-11017), that DUMP_TMP_D actually does not used for exporting dumps to FTP. Instead it uses /usr/local/psa/PMM/tmp
You can mount some storage to this path as workaround

Thanks for the reply, this is now where I am stuck

Error: Unable to import file as dump: The file you are trying to upload is not a valid backup file.
I have tried http://kb.odin.com/en/6080

but I get this error after I complete the last step

/usr/bin/xmllint --noout --schema /usr/local/psa/PMM/plesk.xsd backup_info_1509160104-formatted.xml

warning: failed to load external entity "backup_info_1509160104-formatted.xml"

 

[ae9803]

I was able to get it to work, not sure what I need to correct

 

[Dmitry Y.]

Never seen so many errors of such kind...
When you see "This element is not expected" it usualy means that element itself is correct, but placed wrong. According to XSD tags on this level of XML placed in wrong order.
E.g.

backup_info_1509160104-formatted.xml:141: element scheduled-tasks: Schemas validity error : Element 'scheduled-tasks': This element is not expected. Expected is one of ( pinfo, shared-ssl-base, cron, gapps-account, descriptions ).

You need to find element scheduled-tasks in plesk.xsd or pmm-common.xsd :

<xs:element name="preferences" minOccurs="0">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element ref="admin-password" minOccurs="0"/>
                            <xs:element ref="pinfo" minOccurs="0" maxOccurs="unbounded"/>
                            <xs:element ref="shared-ssl-base" minOccurs="0"/>
                            <xs:element ref="cron" minOccurs="0"/>
                            <xs:element ref="scheduled-tasks" minOccurs="0"/>
                            <xs:element ref="gapps-account" minOccurs="0"/>
                            <xs:element ref="descriptions" minOccurs="0"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>

Now check element scheduled-tasks in backup_info_1509160104-formatted.xml it must strongly follow after admin-password, pinfo, shared-ssl-base, cron if any of them present.

PS: How are you created XML with addition "-formatted" in the name. Suppose you use it for testing?

 

[ae9803]

Never seen so many errors of such kind...
When you see "This element is not expected" it usualy means that element itself is correct, but placed wrong. According to XSD tags on this level of XML placed in wrong order.
E.g.

backup_info_1509160104-formatted.xml:141: element scheduled-tasks: Schemas validity error : Element 'scheduled-tasks': This element is not expected. Expected is one of ( pinfo, shared-ssl-base, cron, gapps-account, descriptions ).

You need to find element scheduled-tasks in plesk.xsd or pmm-common.xsd :

<xs:element name="preferences" minOccurs="0">
                    <xs:complexType>
                        <xs:sequence>
                            <xs:element ref="admin-password" minOccurs="0"/>
                            <xs:element ref="pinfo" minOccurs="0" maxOccurs="unbounded"/>
                            <xs:element ref="shared-ssl-base" minOccurs="0"/>
                            <xs:element ref="cron" minOccurs="0"/>
                            <xs:element ref="scheduled-tasks" minOccurs="0"/>
                            <xs:element ref="gapps-account" minOccurs="0"/>
                            <xs:element ref="descriptions" minOccurs="0"/>
                        </xs:sequence>
                    </xs:complexType>
                </xs:element>

Now check element scheduled-tasks in backup_info_1509160104-formatted.xml it must strongly follow after admin-password, pinfo, shared-ssl-base, cron if any of them present.

PS: How are you created XML with addition "-formatted" in the name. Suppose you use it for testing?

Ugh, I was hoping running the backups would be easy, I was very wrong. All I did was move servers, I assumed I could redownload 6.6 centos, plesk, run the update and baam. This appears I am screwed, and I will have to do everything manually