Wrong my.cnf location?

Arieh

Arieh

Verified User
Joined
May 27, 2008
Messages
1,236
Location
The Netherlands
I've installed a fresh box with CB 2.0 and latest MySQL (5.6) on Debian.

As it turns out, it is using /usr/local/mysql-5.6.12-linux-x86_64/my.cnf instead of /etc/my.cnf

I found that out as strict mode is enabled in it (which is the new default since 5.6 I believe), which causes all sorts of errors if sites aren't using strictly coded SQL.

Maybe there needs to be a symlink to /etc/my.cnf or something else?
 
you need to do symbol link .
mysql service read only the file /etc/my.cnf
 
By default as far as I know CB does not either touch /etc/my.cnf or do anything to it.
That's the only what I found in the code:

Code: 
                if [ -d /etc/mysql ]; then
                    if [ ! -L /etc/mysql/my.cnf ]; then
                            mv -f /etc/mysql/my.cnf /etc/mysql/my.cnf.back
                                ln -s /etc/my.cnf /etc/mysql/my.cnf
                        fi
                fi

So currently it's up to you to have /etc/my.cnf
If you need another you may post a feature request.
 
Not too sure whether or not it is a bug, but you might want to post a feature request and see what they will say.
Probably CustomBuild could install /etc/my.cnf with the smallest set of options in it, but it should not overwrite existing one.
 
Hello,

If you find:
/usr/local/mysql-5.6.12-linux-x86_64/my.cnf

Delete it. We only want mysqld to use /etc/my.cnf.

It's possible that mysql is creating it on it's own.. which would be something we'd have to investigate.

John
 
I've deleted the one in /usr/local/mysql- etc and moved my modifications to /etc/my.cnf. It seems to just pick up that one now.

It was put there after installation and it was using it, and contained a few lines (don't have the original anymore), but it had STRICT_TRANS_TABLES in sql_mode= which was causing trouble for me.

Debian 7.6, MySQL 5.6, CB 2.0.
 
You must log in or register to reply here.
Back
Top