When you look at your database configuration where does it say the socket is located?
On Fri, Oct 26, 2012 at 1:12 PM, Stormont, Stephen (IMS) < stormo...@imsweb.com> wrote: > I followed those steps which is what led us to the > creation of the symbolic link, but I was attempting to find out why we > would even need to do that. Was there some option that we missed at build > time for PHP that would have bypassed this issue? > > > > *From:* Jonathan Sundquist [mailto:jsundqu...@gmail.com] > *Sent:* Friday, October 26, 2012 2:11 PM > *To:* Stormont, Stephen (IMS) > *Cc:* php-install@lists.php.net > *Subject:* Re: [PHP-INSTALL] Symbolic link needed with mysql and PHP? > > > > A quick google search turned up a few answers that might help you, > > > > http://docs.cacti.net/manual:087:4_help.1_faq#database_setup_seems_to_fail > > On Fri, Oct 26, 2012 at 1:03 PM, Stormont, Stephen (IMS) < > stormo...@imsweb.com> wrote: > > We have a new CentOS installation using PHP5 and MySQL. We were having an > issue getting Cacti running, but the problem appears to boil down to a PHP > issue. > > When attempting to access Cacti via the web, we got this error: > > FATAL: Cannot connect to MySQL server on 'localhost'. Please make sure you > have specified a valid MySQL database name in 'include/config.php' > > We checked config.php and everything is configured correctly. > > We then looked at "my.cnf" and saw this line: > socket=/var/lib/mysql/mysql.sock > > Running "netstat -an | grep mysql" says the following: > unix 2 [ ACC ] STREAM LISTENING 11035 > /var/lib/mysql/mysql.sock > > However, we have to create a symbolic link in /tmp in order to be able to > get to the Cacti config screen: > ln -s /var/lib/mysql/mysql.sock mysql.sock > > Why do we have to do this though? > > ________________________________ > > Information in this e-mail may be confidential. It is intended only for > the addressee(s) identified above. If you are not the addressee(s), or an > employee or agent of the addressee(s), please note that any dissemination, > distribution, or copying of this communication is strictly prohibited. If > you have received this e-mail in error, please notify the sender of the > error. > > > > ------------------------------ > > Information in this e-mail may be confidential. It is intended only for > the addressee(s) identified above. If you are not the addressee(s), or an > employee or agent of the addressee(s), please note that any dissemination, > distribution, or copying of this communication is strictly prohibited. If > you have received this e-mail in error, please notify the sender of the > error. >
