Support

UNiTE, Remote CLI, eXtract Wizard

#3799 Remote CLI seems to require log file for download of backup file to work

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 Monday, 07 November 2011 01:59 CST

davidascher
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the forum before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! : 1.5.23
PHP version: php6 (on client) php 5.2.17 on Joomla server
MySQL version: (unknown)
Host: 1and1
Akeeba eXtract Wizard / Remote Control / SiteDiff version: REMOTE CLI 1.0

EXTREMELY IMPORTANT: Please attach the Remote Control and Akeeba Backup log files if you are reporting an Akeeba Remote Control issue, othrewise we can not help you

Description of my issue:

I was very happy that I had been able to successfully perform backups from a different (linux) host than the one where my Joomla is running. I put all the necessary commands into a shell script and could run the backups and have them downloaded to my other (client) host just fine.

At some point I decided to simply invoke the shell script from crontab to perform daily backups. Foolishly I did not think to verify that the whole process still worked as it should once I ran the script from crontab.

The backups still run but the backup file does not get downloaded to my client machine.

I then tried copying the command line from the script into cron - that changed nothing. The backups are still created on the server machine but not downloaded to the client machine.

Here is the command line (with secret word, ftp userid, and ftp password hidden) :

/usr/bin/php6 /kunden/homepages/26/d218031710/htdocs/JoomlaBackups/FWLive/remote.phar --action=backup --description="Remote CLI BACKUP for FWLive - saved at infong604 in /JoomlaBackups/FWLive " --download --dlmode=curl --host=http://folkworks.org --secret=secretxxx --dlurl="ftp://useridxxx:[email protected]:21/administrator/backups" --comment="this is a backup" --dlpath="/kunden/homepages/26/d218031710/htdocs/JoomlaBackups/FWLive"


I keep going 'round in circles thinking that there must be a problem with the command line but then realize that the command line can be run successfully if it is not run in crontab.

Desperate to find a solution I decided to try crontab again with the shell script and specifying a log file for the crontab output... Oddly, now the backup runs and the file is downloaded successfully.

This doesn't make a lot of sense to me. Can you explain why adding the log file for output would allow the download to run? and not having would prevent the download from working successfully?

I'm very puzzled.

nicholas
Akeeba Staff
Manager
PHP 6 is still alpha quality software. It's not stable, it's not supposed to use in the real world and Remote CLI has NOT been tested with it. The only non-beta PHP version family at the time of this writing is PHP 5.3. Please use PHP 5.3 instead.

That said, I have tested over here, but I couldn't replicate your issue with PHP 5.3.8. Remote CLI was able to download the backup archive with or without a standard output (it's not a log file, it's a standard output redirection ;) )

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!