Support

UNiTE, Remote CLI, eXtract Wizard

#3526 JPRemote: XML-RPC Layer Error

Posted in ‘UNiTE and Remote CLI’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
Tool
UNiTE
Tool version
n/a

Latest post by nicholas on Thursday, 20 August 2009 11:37 CDT

Neilz
I searched the forum, and tried the recommended fixes, but none helped.

Background:

JPRemote starts the backup successfully, it goes on for a few minutes, then the error pops up. This occurs on two different subdomains, under the same domain on a GoDaddy Linux hosting account.

Here's the last few lines of the log:

[10/08 21:06:49] Ticking remote backup engine

[10/08 21:06:49] POST: joomlapack.continueBackup **** **** 1

[10/08 21:06:50] GOT:









IsFinished

0



Domain

Packing



Step

/home/content/n/z/a/nzampella/html/churchwebsites/administrator/language/en-GB



Substep

[NULL]



Error

[NULL]



Warnings

[NULL]











[10/08 21:06:50] Got backup progress signal

[10/08 21:06:50] Ticking remote backup engine

[10/08 21:06:50] POST: joomlapack.continueBackup **** **** 1

[10/08 21:06:53] Backup error: XML-RPC layer error:HTTP/1.1 500 Internal Server Error



Thanks in advance.

UPDATE
Went to the site to check the backup files and remove the JPRemote created one that (I thought) errored out. Saw the backup with the system showin g a big, green OK next to it.

So, I performed a backup from the backend, and then looked at the sizes of the files, exactly the same!! :?:

dlb
That makes me very nervous. The error at the end of the Remote log is a 500 error from the server. It is possible that the backup was done and the 500 came during cleanup or the ftp download of the backup, which would mean the backup is good. Please check the backup log on the back end to make sure that you have a "completed" message near the end of the log.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Neilz
Did not have the system setup to download the file, just do the backup.

There was no completed message, just the error message in the log as the final log entry.

dlb
I'm sorry, I didn't state that very well. I was interested in the backup log in JoomlaPack in the back end of your site. The version of the log for the Remote session would have been overwritten by your back end backup. Please try the Remote backup again, when it fails, download, zip and post the backup log from the JoomlaPack Control Panel.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Neilz
dlb wrote:
I'm sorry, I didn't state that very well. I was interested in the backup log in JoomlaPack in the back end of your site. The version of the log for the Remote session would have been overwritten by your back end backup. Please try the Remote backup again, when it fails, download, zip and post the backup log from the JoomlaPack Control Panel.


Urp, sorry. Here's the log, from what I can tell, it completed fine on the back end !!

NZlog.zip

dlb
I agree that the backup finished successfully. But there is a clue in the log - you're still using the beta version. There were a lot of changes in 2.3, so the beta was a little rough in spots. You should update both JoomlaPack and Remote to the stable release. It was posted last Friday.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Neilz
Sheesh ... behind the times again ;)

Thanks for your help.

dlb
You gotta be really quick to keep up with Nicholas. :lol:


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Neilz
Dale,

problem:

Same error on two sites, both hosted on GoDaddy, a third site hosted elsewhere completed without errors.

Attached logfile is from one of the GoDaddy sites, the archive was created OK. nzlogfile.zip

dlb
Once again, the backup log says the backup completed.

With GoDaddy you can access the server error log, but you have to "turn on" that function, then it times out after a maximum of 24 hours. I don't remember exactly how to turn it on, I probably found it in the frequently asked questions on their site. The server error log will contain more information about the 500 error. The only reason that we're getting any message about that error is because the Remote log is based on your local machine. The 500 kills the backup log instantly.

Please see if you can turn on the server log and redo the Remote backup to trigger the error, then see what the log says.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Neilz
Here's the error on the server log:

[Wed Aug 12 23:20:09 2009] [error] [client 98.236.6.35] malformed header from script. Bad header=/home/content/x/y/z/nxxx/: /var/chroot/home/content/x/y/z/zzzzz/html/zzz/xmlrpc/index.php


From the looks of the error, I fully expect that I missed some configuration setting I was supposed to make !!

Of course, the path has been disguised ;)

dlb
I'm sorry, I just don't know the answer on this one. :oops: I would recommend that you do your backup through the back end until Nicholas returns and has a chance to figure out what is going on with this. The backup logs say the backup is complete, but "pretty sure" is not good enough here.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
I am damn sure that the backup is complete. However, it looks like the XML-RPC server built in Joomla! couldn't run the part which reports the archive name back to JoomlaPack Remote. I suspect this is a host-related error, but I can't tell for sure.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Neilz
nicholas wrote:
I am damn sure that the backup is complete. However, it looks like the XML-RPC server built in Joomla! couldn't run the part which reports the archive name back to JoomlaPack Remote. I suspect this is a host-related error, but I can't tell for sure.


Nicholas,

I thinks so too as I have another site I admin on a different hosting company, and it completes the backup without an error.

This may be confined to GoDaddy. That said, I'd like to know if anyone else using GoDaddy has this issue, but for now, I can live with it.

Thanks for the assistance!!

user6795
Hey buddy. I have the same 500 when using remote tools and Godaddy with Linux. I also admin Godaddy on Windows platform and it completes with no errors.

nicholas
Akeeba Staff
Manager
As I said, this one looks like a host firewall intercepting the call. It is too consistent and confined on a single hosting platform, so it doesn't look like a generic bug...

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!