Joomla 1.7 installation problem

[xuannghi]

Hi,
I am new with DA. After installing DA I created reseller then user.. then I try to install a joomla 1.7 website but I always have problem with this error:

JFolder::create: Could not create directory
Component Install: Failed to create site directory: /home/xxx/domains/xxx.com/public_html/components/com_xxx

I even try to set public_html, tmp directories to 777. But none is working so far.
This seems to have problem with the DA's permissions?
Thanks for sharing your experience.

 

[xuannghi]

Hi,
I am new with DA. After installing DA I created reseller then user.. then I try to install a joomla 1.7 website but I always have problem with this error:

JFolder::create: Could not create directory
Component Install: Failed to create site directory: /home/xxx/domains/xxx.com/public_html/components/com_xxx

I even try to set public_html, tmp directories to 777. But none is working so far.
This seems to have problem with the DA's permissions?
Thanks for sharing your experience.

Would like to add that my server is CentOs 6.2

 

[zEitEr]

Hello,

The most simple would be for you to install PHP as suPHP (PHP-CGI) and then re-try installation (note in this case, you will need fix owner of directories and files in your public_html, or empty it). The other way you can go is to use mod_ruid2.

Search the forums to find detailed help and How-To on both subjects. Note, you should choose between mod_suphp and mod_ruid2, as they mostly do the same thing, and I would not recommend to try use them both, unless you've got enough experience.

Please feel free to contact me by PM, if you need a qualified hands to do the job for you, I'm ready to give you a commerce service as well as some others members of these forums.

 

[xuannghi]

Thank you zEitEr. I'll follow your guide.
To be honest, I have thought that installing joomla with DA was as simple as with cPanel!

 

[zEitEr]

It's still as simple as it can be, but since you've got a fresh installed server with directadmin you might need to reconfigure PHP.
Next time you will install directadmin, select PHP-CGI as default PHP and everything would go smoother.

 

[NoBaloney2]

Note we find that using PHP-CGI uses much more resources when running PHP scripts than mod_ruid2, so we use mod_ruid2 on all new installations. We've also been converting previous CGI installs to mod_ruid2.

Jeff

 

[zEitEr]

@Jeff,

mod_ruid2 is still available neither from installation script nor custombuild, isn't it?!

Note we find that using PHP-CGI uses much more resources when running PHP scripts than mod_ruid2

Do you have any graphs to share? I'd like to see differences, as I've never compared them in this way.

 

[NoBaloney2]

mod_ruid2 is still available neither from installation script nor custombuild, isn't it?!

You're correct, but it's an easy and fast conversion using the How-To on these forums. One issue is we've run into situations where we'd have to install mod_ruid2 over again after an update, but we schedule our updates so for us it's not a problem. Nevertheless, I'd like to see mod_ruid2 installed into CustomBuild and the original installation.

Do you have any graphs to share? I'd like to see differences, as I've never compared them in this way.

Only anecdotal and our own experience; CGI sets up an entirely new instance of PHP for each call. That's more resource intensive.

In our own situation we had an admittedly underpowered server brought to it's knees when we switched from mod_php to CGI; it had only a few WordPress sites on it. We converted it to mod_ruid2 and it's still usable now with over double the WordPress sites.

Jeff

 

[xuannghi]

Thank you all for the support. I have managed to install mod_ruid2. It looks ok now.