Skip to main content Help Control Panel

Login   A+   A-

Community «   Discussion forum «   Installation support «  

Installation problem

Jiji -- on Dec. 30 2005
mysql version higher than requiered?
Hi,

I just uploaded the directory structure and chmoded all directories to 777 to make sure. I go to the yasc directory, click the "installation" link and keep getting the following error:

Warning: mysql_get_server_info(): Access denied for user 'root'@'localhost' (using password: NO) in /usr/local/psa/home/vhosts/animasia.net/httpdocs/yacs/setup.php on line 111

Warning: mysql_get_server_info(): A link to the server could not be established in /usr/local/psa/home/vhosts/animasia.net/httpdocs/yacs/setup.php on line 111 First installation

ERROR: YACS requires at least MySQL version 4.0. The server runs version 4.3.10.

Could you please help?
Fernand
avatar
from Paris
1287 posts

on Dec. 31 2005


I use not to intervene here but I asked exactlectly the same question on the forum in french, and Bernard answered to me that this message indicates simply that YACS could not, temporarily, get the access to the MySQL server. This is happening from time to time because of the separation of web services and data bases on different physical machines, explained Bernard.
In that case, the problem should not last.
The problem can happen too, if you not correctly adressed the name of your data base when you were configurating YACS just after you installed it. I already met this problem because I forgot one letter and did not reproduce correctly the name of my data base.
Hope this could be helpfull to you.
Jiji
4 posts

on Dec. 31 2005


Thanks Fernand, I'll give it some time an try again. Hopefully it will fix the problem - I really want to try YACS out. If it doesn't, I'll be back here
>The problem can happen too, if you not correctly adressed the name of your data base when you were configurating YACS just after you installed it.

I don't think that was the reason because I never got to install it - I got this error message at the very first step of the setup process.
Bernard
avatar
from nearby-an-airport
Associate, 6674 posts

on Jan. 1 2006


Actually, I have added this additional check just before the release 5.12, and this is a buggy one.

Tomorrow I will provide an updated version of setup.php that should fix this.

Thank you for your interest in YACS.
Bernard
avatar
from nearby-an-airport
Associate, 6674 posts

inspired from Bernard on Jan. 3 2006


An updated release 5.12.1 has been uploaded today, which should fix this issue, among others.

Can you check YACS version 8.6beta30.31.12 (zip) and provide (supposedly positive) feed-back?

I wish you a very Happy 2006 Year with YACS.
Jiji
4 posts

inspired from Bernard on Jan. 3 2006


" Can you check YACS version 8.6beta30.31.12 (zip) and provide (supposedly positive) feed-back? "


I would have loved to, but it still fails to install. This time I get

First installation Unable to write to file ./switch.on

ERROR: YACS cannot write to files. If you are running some Unix, please chmod all files under the YACS installation directory to at least 755.

although I had chmoded every dir and every file to 755, and then to 777 to make sure.
Bernard
avatar
from nearby-an-airport
Associate, 6674 posts

on Jan. 4 2006


Jiji: ok, maybe some light would come from going back to the roots.

YACS has to write to any PHP script (for example, during the update process), and to other places as well (for example, to write configuration files).

As you may know, every directory and file on a Unix system has an owner, and also an associated group. It also has a set of permission flags which specify separate read, write and execute permissions for the 'user' (owner), 'group', and 'other' (everyone else with an account on the computer). The 'ls' command shows the permissions and group associated with files when used with the -l option.

To understand permissions set by the 'chmod' command, remind that these are numerically equivalent to those reported by the 'ls' command, namely:
  • 7 means "may read, write, and execute"
  • 6 means "may read and write"
  • 4 means "may read"
  • 0 means "forbidden access"


Normally, user/group information is set based on the FTP account used to upload YACS files to the web server, for example foobar/users.

Ideally, a properly configured web server should impersonate you when executing your scripts, for example with user/group information set to foobar/nobody. In this case the server has exactly the same rights that you have through FTP, and you can 'chmod' everything to 700 if you like.

Sometimes, and this is probably where you are, the web daemon uses dedicated accounts, such as apache/www-data.

In that case the web daemon effectively has no rights to your files. How to overcome this?

Solution 1- Ask your system administrator to run your scripts with your account information, as explained before. See www.suphp.org if he is looking for an adequate solution.

Solution 2- You can attempt to 'chmod' everything to 707, to give maximum permissions to the world, including the web daemon. Check actual results with 'ls -l', since your account may be prevented to do this. For example:
cd your_home_directory
chmod -R 707 .
ls -l


Solution 3- Another option is to change group information of all files, to re-use the one of the web daemon. Then you will have to give maximum permissions to the group. For example:
cd your_home_directory
chgrp -R www-data .
chmod -R 770 .


Solution 4- Lastly, you can ask your system administrator to put the web user account in your own group, and then to give maximum permissions to the group. For example:
cd your_home_directory
chmod -R 770 .
Jiji
4 posts

inspired from Bernard on Jan. 4 2006


Thank you, solution 2 worked like a charm. I'm still in the process of getting to know the backend but I'm already impressed. Yacs IS different and I'm looking forward to exploring it.
Bernard
avatar
from nearby-an-airport
Associate, 6674 posts

inspired from Jiji on Jan. 4 2006


Jiji: Many thanks for the positive feedback.

Rate this page
Posted by Jiji on Dec. 30 2005, commented by Bernard on Dec. 30 2005, (popular)