ERROR - Exception error connecting to database!

fredericc · Post by **fredericc** » Sat Feb 06, 2010 5:36 pm

Hi all!
I'am working on debian lenny, mysql an php are working for another applications.
I can connect to the web interface. I have got the last version.
I set up an AETitle for Kpacs.
I can't connect with kpacs.
I don't know where to start.
Thanks for your help.....
Fred
PS: I have got a Trial license two days old.

Post by **pacsone** » Sat Feb 06, 2010 9:56 pm

1. Did you make any recent change to the MySQL username assigned to PacsOne Server during its installation? e.g., changing the password, etc.

2. Can you trying logging into MySQL using the above username/password from a local command shell? e.g.,

$ mysql -u $username -p

where $username is the MySQL usrname you assigned to PacsOne Server during its installation.

3. Can you the ${AeTilte} configuration file under the directory where PacsOne is installed to mailto:pacsone@pacsone.net?

flaurent · Post by **flaurent** » Mon Feb 08, 2010 8:08 am

pacsone wrote:1. Did you make any recent change to the MySQL username assigned to PacsOne Server during its installation? e.g., changing the password, etc.

Yes, I do! I tried to resolve this issue.

2. Can you trying logging into MySQL using the above username/password from a local command shell? e.g.,
$ mysql -u $username -p
where $username is the MySQL usrname you assigned to PacsOne Server during its installation.

That's working properly.

3. Can you the ${AeTilte} configuration file under the directory where PacsOne is installed to mailto:pacsone@pacsone.net?

Yes, I do. Thanks
PS: Following the error message on web interface.
Mon Feb 8 08:58:59 2010 ERROR - Exception error connecting to database!
Mon Feb 8 08:58:59 2010 ERROR - Exception error connecting to database!
Mon Feb 8 08:58:59 2010 ERROR - Exception error connecting to database!
Mon Feb 8 08:58:59 2010 ERROR - Exception error connecting to database!
Mon Feb 8 08:58:59 2010 ERROR - Exception error connecting to database!
Mon Feb 8 08:58:59 2010 ERROR - Exception error connecting to database!
Mon Feb 8 08:58:59 2010 ERROR - Exception error connecting to database!

Post by **pacsone** » Mon Feb 08, 2010 4:35 pm

Can you check if the MySQL socket name configured in your ${AeTitle} file matches with the one that MySQL daemon is currently listening to?

# ps -e | grep mysqld

fredericc · Post by **fredericc** » Mon Feb 08, 2010 7:17 pm

Find following.
~# ps -ef | grep mysqld
root 2359 1 0 Feb07 ? 00:00:00 /bin/sh /usr/bin/mysqld_safe
mysql 2396 2359 0 Feb07 ? 00:00:27 /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql --pid-file=/var/run/mysqld/mysqld.pid --skip-external-locking --port=3306 --socket=/var/run/mysqld/mysqld.sock
root 2397 2359 0 Feb07 ? 00:00:00 logger -p daemon.err -t mysqld_safe -i -t mysqld
root 8288 8279 0 20:16 pts/1 00:00:00 grep mysqld

Thanks!

Post by **pacsone** » Mon Feb 08, 2010 7:51 pm

Looks like MySQL is running with a non-default socket name of /var/run/mysqld/mysqld.sock on your server, so you should edit your ${AeTitle} configuration file, and edit the MysqlPort setting to match with the current MySQL socket name:

Code: Select all

MysqlPort = /var/run/mysqld/mysqld.sock

Save the change and restart PacsOne Server, then check if you still get the MySQL exception errors or not.

fredericc · Post by **fredericc** » Mon Feb 08, 2010 10:33 pm

thanks and great for your help!
Finally the problem was with sock file.
it was in /var/run/mysqld/mysqld.sock
I modified two files $aetitle $aetitle.ini

tburba · Post by **tburba** » Fri Sep 16, 2011 8:09 pm

I was just hit by the same problem. (Debian here, too.) As this was an upgrade to the newest 6.3.1-Linux-x86_64 and I paranoidally backed up the existing installation tree, later I was able to pinpoint the cause by comparing $aetitle.ini with the old one.

Code: Select all

/home/PacsOne# diff -EbB PACSONE.ini ~/1/PACSONE.ini
7c7
< MysqlSocket = /var/lib/mysql/mysql.sock
---
> MysqlSocket = /var/run/mysqld/mysqld.sock
18d18
< DatabaseHost = localhost

I think the installer should not be that dumb. In case of upgrade, certain existing entries are by definition working and are to be preserved. This will really save some time for customers and support staff.

Post by **pacsone** » Sat Sep 17, 2011 8:27 pm

Thank you for reporting this bug in the Installer for PacsOne Server, and we'll fix it for the next upcoming release (6.3.2) of PacsOne.