The free forums are no longer in use. It remains available as read-only archive.
5:54 pm
December 15, 2013
I have been trying for over a year to get XCloner working using cron on my client's Joomla installation on Amazon EC2 with a Bitnami LAMP stack. You can see the problem spelled out at this website. http://community.bit.....n/8342/5 Please read it thorougly.
I think that the Bitnami folks have done everything they can to help me; I'm convinced that there is something wrong with your cron implementation.
- The script (custom config or not) runs perfectly when I manually start it from the web browser
- Whether I specify a user or not in the cron instructions, the job refuses to run.
- Since the instance doesn't have CPanel installed, I tried using Webmin, and the job still does not run.
Environment:
- Apache 2.4 installation (bitnami-lampstack-5.4.23-0-linux-ubuntu-12.04.3-x86_64-ebs)
- Joomla 2.5.19, manually installed.
I directly edited the crontab, but neither of these worked:
0 0 * * * bitnami /opt/bitnami/php/bin/php /opt/bitnami/apache2/htdocs/administrator/components/com_xcloner-backupandrestore/cloner.cron.php
0 0 * * * su - bitnami -c "php /opt/bitnami/apache2/htdocs/administrator/components/com_xcloner-backupandrestore/cloner.cron.php"
What else can I try?
Toolie
7:00 pm
December 15, 2013
I am confused, Ovidiu, am I supposed to put that command in a Linux command line or use that in the crontab file? On the Bitnami stacks, I have been told that PHP will be invoked correctly if I use:
/opt/bitnami/php/bin/php
Which makes me wonder why I would need to add the "php" in front of that path. Can you explain further?
Here is my current crontab command, based on the input from the Community over at Bitnami.com. I am not trying to use the custom config at this point.
0 23 * * * su - daemon -c "/opt/bitnami/php/bin/php /opt/bitnami/apache2/htdocs/administrator/components/com_xcloner-backupandrestore/cloner.cron.php"
After I added your latest version for v2.5, I am no longer able to run the command unless I am logged in to the Admin area, even though I have specified that my individual static IP address should be authorized.
Here is what the manually executed files look like when I list them:
$ ls -la
-rw-r--r-- 1 daemon daemon 1527622656 Apr 7 10:16 backup_2014-04-07_09-12_www.websitenamechanged.com-sql-nodrop.tar
-rw-r--r-- 1 daemon daemon 1300480000 Apr 15 20:34 backup_2014-04-15_19-31_www.websitenamechanged.com-sql-nodrop.tar
-rw-r--r-- 1 daemon daemon 1300480000 Apr 15 20:40 backup_2014-04-15_19-37_www.websitenamechanged.com-sql-nodrop.tar
-rw-r--r-- 1 daemon daemon 1306172928 Apr 20 19:15 backup_2014-04-20_18-13_www.websitenamechanged.com-sql-nodrop.tar
When manually executed, the daemon user owns the files.
You can see the latest discussion of this issue over at http://community.bit.....ron/8342/5.
Toolie
The cron command format changed, so now you are forced to save the cron config as a custom config, and you would need to adjust your cron command like this(the rest can stay the same)
0 23 * * * su - daemon -c "/opt/bitnami/php/bin/php /opt/bitnami/apache2/htdocs/administrator/components/com_xcloner-backupandrestore/cloner.cron.php mycustomcorn.php"
Hope it helps! Ovidiu
5:54 am
December 15, 2013
Ovidiu, the folks over at Bitnami came to the same conclusion:
http://community.bit.....on/8342/17
except without the custom configuration tacked on at the end. It FINALLY worked. I have been working on this since January of 2013, so having this solved is a HUGE relief.
Toolie
1 Guest(s)