The mysql_pconnect() problem

[difficultcms]

Well, I think I've read everything on the above mentioned problem, but it's still not solved for me.

Did install successfully (as was the message), then click on "here's your cms page" and getting the pconnect error.
So, I have set persistent_db_conn to false in my config.php
Now I'm getting a connect error (instead of pconnect):

Warning: mysql_connect(): Access denied for user: '*****@localhost' (Using password: YES) in ********************/lib/adodb/drivers/adodb-mysql.inc.php on line 340

Warning: Smarty error: unable to read resource: "db:-1" in **********/lib/smarty/Smarty.class.php on line 1088

When I try to login as admin I get this:

Warning: mysql_connect(): Access denied for user: '******@localhost' (Using password: YES) in *********/lib/adodb/drivers/adodb-mysql.inc.php on line 340

Warning: Smarty error: unable to read resource: "db:-1" in **********/lib/smarty/Smarty.class.php on line 1088

Sigh....well, after days of struggling with Mambo I hoped I had finally found a simple CMS. When the message "install successful" appeared I was happy. Only to find a second afterwards again it is not working. Quite frustrating really.

[Ted]

I modified the installer a bit.  Can you do me a favor and try installing the daily and see if that fairs better for you?

http://cmsmadesimple.org/cms-daily.tar.gz

Thanks!

[Pozican]

Same issue -- Didn't help.

[Jeremy]

did this issue ever get dorted out? I am running into the same issue

[earlten]

If you do a dmesg, you get some insight into this.  I had checked everything but dmesg, and to my amusement, someone suggested this and I figured, why the heck not.  In my case, as is, I'm guessing with others here, SELinux was preventing access to the sql socket.  The dmesg notice was this:

avc:  denied  { connectto } for  pid=2963 comm=httpd path=/var/lib/mysql/mysql.sock scontext=root:system_r:httpd_t tcontext=root:system_r:unconfined_t tclass=unix_stream_socket

So far, I have completely DISABLED SELinux, and everything started working again.  I switched back to SELINUX=enforcing (in /etc/selinux/config, this re-enables SELinux) and I get the same problems.  I will be working on a solution for this, when I have one , I will try to remember to post!  In the meantime, do not DISABLE SELinux, just set it to permissive.  You will need the security reports it is generating!

Cheers!  -Bill