Support

Site Restoration

#12894 When running akeeba kickstart as direct, it extracts files as...

Posted in ‘Site restoration’
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
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by nicholas on Monday, 09 July 2012 02:14 CDT

livewire360
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)?
yes:
Troubleshooting instructions for akeeba kickstart
any other akeeba kickstart issue

Have I searched the tickets before posting? yes
Have I read the documentation before posting (which pages?)? yes (all)
Joomla! version: 2.5.6
PHP version: 5.3.3 (yes I upgraded from the stock that comes with koloxo)
MySQL version: 5.0.95
Host: (koloxo)
Akeeba Backup version which took the backup: (3.5.2 pro)
Kickstart version used to extract the backup: (3.5.2)

Description of my issue:
Upon extraction using akeeba kickstart, the owner is not the FTP owner, but it is changed to apache, which only root can change ownership back to their correct ownership. this works fine on my other hosts that use cpanel, but I would like to use this as a backup solution, so I need to figure out what is causing kickstart to make apache the owner of the files when it does not do that on any other hosting that I have seen thus far.

Thanks,

 

 

 

Thank you,
James Wilson
Internet Resource Solutions LLC

nicholas
Akeeba Staff
Manager
As I've written in the documentation, you have to use the "Use FTP" in the file writing selection method instead of the default "Write files directly" method. Full detailed instructions on using Kickstart's FTP mode can always be found in the documentation. Technically it's not a Kickstart limitation, it's the way PHP works when running as an Apache module (mod_php). The same problem exists with Joomla! itself, hence Joomla!'s own FTP layer in Global Configuration. And not just Joomla!, of course. The same holds true for any PHP-based script / application such as WordPress, Drupal, phpBB3, you-name-it.

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!

livewire360
what i was asking was if there was anything I could change on the server that you know that makes it preform this way to stop this behavior. I already know that I can use FTP layer, but it is soooo slllooowwww.

I have root access to the server so my ultimate question is "Do you know what causes this behavior that I can modify a setting to fix?"

Thanks,

 

 

 

Thank you,
James Wilson
Internet Resource Solutions LLC

livewire360
I think I understand, I am sorry for the problem
I do not have suPHP installed on the server,

Thanks,

 

 

 

Thank you,
James Wilson
Internet Resource Solutions LLC

nicholas
Akeeba Staff
Manager
There are three solutions: the good, the bad and the ugly.

The good. You have to either use suPHP or FastCGI Process Manager (Apache's mod_fpm) to run PHP. suPHP is slightly slower, FPM is blazing fast. I'd recommend asking/paying your host to do that for you.

The bad. If the dedicated server is only running one site, or sites owned by one user only, you can edit your httpd.conf and have Apache run under the same user and group as your FTP account. As I said, it's bad but it works.

The ugly. After you restore the site use chown and chmod to change ownership and permissions of files. However this will make stuff unwritable by PHP and by extension to Joomla!. This leads to a need for using the FTP mode or doing stupid things, like using 0777 permissions. Not recommended. It's ugly and can get you hacked eventually.

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!