no etc/mycnf file

[dmacleo]

fresh install of DA and mysql 5.5.31 is running, sites/databases working.
but there is no etc/mycnf file.
where would it be?
in /usr/local/directadmin/conf there is a mysql.conf but thats not the same iirc and was only used for dumps or something.

 

[dmacleo]

DUH I forgot it does not exist by default on DA.
been so used to having it there I forgot I need to make it first.
sorry about that.

 

[Richard G]

DUH I forgot it does not exist by default on DA.

Sorry? On which Linux system is that?

On a default DA installation on Centos with MySql installed, there always is a /etc/my.cnf present by default, you never have to create one.
It only contains this:

[mysqld]
local-infile=0

or something like it, but it exists by default on a DA installation.

 

[Arieh]

Got those same 2 lines on default DA Debian.

 

[dmacleo]

centos 6.4 fresh install of DA and no /etc.mycnf
only thing in /etc was a my.cnf.old with the following

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
user=mysql
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid

made one based on the example cnf fles and restarted sql

 

[Richard G]

only thing in /etc was a my.cnf.old with the following

Ah oke, I had that once on a newly installed server, but that was the case after downgrading and/or upgrading to a different version of mysql.

I read you upgraded to mysql 5.6 in another post, it might be caused by that upgrade, that's also the reason why it's called ".old". So it was an existing my.cnf before.

 

[dmacleo]

the 5.6 upgrade was done after this, so I am not sure why this happened.
I had not done anything to mysql prior to this (fresh installs) so it puzzled me.
I checked and system is using the my.cnf I built now so there is no real issue, maybe if someone with a way to test could test fresh cent 6.4 and DA installs with immediate swap to CB2 ?
the only thing I did after server was running was swap to CB2, maybe a build-update/all affected it somehow?

 

[Richard G]

the only thing I did after server was running was swap to CB2, maybe a build-update/all affected it somehow?

Wasn't mysql rebuild when swapping to CB2? Anyway, I think this will have affected it, can't imagine anything else.
I did a fresh Centos 6.4 installation 2 weeks ago and a /etc/my.cnf was present then.

 

[dmacleo]

I am not sure, I started with mysql 5.5 even before swapping to CB2 and did not look to see.
so its very possible.