Problem loading imagick.so in MacOS X Server

Antw1 · Post by **Antw1** » Wed Mar 12, 2008 3:43 pm

The log is fine and logs the startup of MySQL and location of the socket.
MySQL does actually run (ps -ax | grep my).

There just are no mysql.sock in the designated directory for clients to connect to.
I tried to chmod 777 the whole directory. No luck.

Post by **pacsone** » Wed Mar 12, 2008 5:21 pm

Did you check the /etc/my.cnf file for the location of the MySQL socket?

Stephan · Post by **Stephan** » Wed Mar 12, 2008 5:38 pm

What's the error message you get when you try to connect to mysql?

Go to the directory you installed XAMPP in and switch to the /bin directory:

Code: Select all

cd .../xampp/xamppfiles/bin

then try to connect to mysql:

Code: Select all

./mysql -u root -p

Once you entered your password there should be an error message telling you there is no mysql.sock file in a directory. You need the file in that directory.

Now, mysql.sock should be there, just not in the directory it should be in. Most likely "/private/var/mysql/"
XAMPP usually has mysql.sock in .../xampp/xamppfiles/var/mysql/.

Since you can't copy sock-files, you'll have to create a symbolic link from the directory (see error message from above) that should have the mysql.sock file to the location where the file is actually located.
You can do this by using the

Code: Select all

ln -s

command.

You also have to change the default path to mysql.sock during the installation of PacsOne. I believe PacsOne has a default location for mysql.sock in /tmp/ or /var.

In the end, you're dealing with three problems here.

1. XAMPP has the mysql.sock file in .../xampp/xamppfiles/var/mysql/
2. The OS is looking for it in another directory /private/var/mysql/ or somethign silimar.
3. PacsOne is expecting the file in yet another directory.

Easiest way to fix it is, create a symbolic link for the OS and .../bin/mysql to the directory that has the file and manually enter the location of the file during the installation of PacsOne.

Antw1 · Post by **Antw1** » Thu Mar 13, 2008 11:01 am

It seems that MySQL 5.0.51a has stability issues on 10.5.

The points you bring up are all good and valid and are covered.
My XAMPP-installed MySQL actually starts up fine, with the socket created in the right directory etc, and initially I had a fully functional PacsOne/XAMPP system.

But lately the socket seem to vanish shortly after startup making client connections impossible.
A post from the MySQL platform notes recommended enabling the "sticky" bit on /Applications/xampp/xamppfiles/var/mysql which didn't fix anything.

I'll take any good advice, or a link to a MySQL 5.0.45 download!

Post by **pacsone** » Thu Mar 13, 2008 4:25 pm

Here's a link to the MySQL 5.0.45 release:

http://downloads.mysql.com/archives.php ... 0&v=5.0.45

Stephan · Post by **Stephan** » Fri Mar 14, 2008 10:27 pm

There's definitely a stability issue with MySQL here. I have the exact same problem now. After I copied over the full PacsOne licese and restarted the server, mysql.sock is gone and there's no way to bring it back and log into MySQL. Very annoying problem.

So on monday, I will use the xampp package without MySQL, install a seperate MySQL release and re-install PacsOne so I can use it with the stand alone MySQL version. And so the neverending story continues...

Stephan · Post by **Stephan** » Mon Mar 17, 2008 2:54 pm

Ok, next problem. After dumping the MySQL release that comes with XAMPP and switching to the MySQL server in Leopard, everything seems fine so far, but I can't log into PacsOne via the web interface.

I've re-installed PacsOne, database is there. I can log into the MySQL server using

Code: Select all

mysql -u root -p

but it won't let me log in via the web interface.

Given that it created the database and tables during the installation it seems strange that I can't log in now. The error message I'm getting is "Could not connect to MySQL database as User: root", "Please check your username and password".

Using the the same username and password via mysql command works like a charm. Any advice?

Post by **pacsone** » Mon Mar 17, 2008 4:34 pm

This usually means there is a problem with the mysql/mysqli PHP extension, if you can not login from the web page but can from a command shell.

Check if you see if the mysql/mysqli php extension loaded successfully from the output of the test page:

http://localhost/pacsone/Hello.php

Stephan · Post by **Stephan** » Mon Mar 17, 2008 9:49 pm

Thanks for the quick reply. That was indeed the problem. Everything still pointed to the mysql.sock and mysql server that's coming with XAMPP. I had a symbolic link in /Applications/xampp/xamppfiles/var/mysql/ which pointed to /tmp/mysql.sock, of course that old file had the sticky bit set and served no real purpose. So I deleted the symbolic link and added a new one which points to /var/mysql/mysql.sock where the actual file is put every time the internal MySQL server is started.

Guess all the playing with different installation of Apache/PHP/MySQL left some garbage in the system. I can log in now. I'll continue the configuration with AEs and RemotEye on wednesday and see if it runs stable. I'll report back if I run into more trouble. At this point I'm not sure if I should just re-install the whole server and use the build-in versions of Apache/PHP/MySQL or leave it running with the current configuration. Guess we'll see. Thanks for the help.