Wrong mysql installed on new install?

[Richard G]

I just installed a new server and transfered some accounts to test.
Now some mysql troubles came up.
This is in my options.conf of custombuild:

#Possible values - 5.0, 5.1, 5.5
mysql=5.0
mysql_inst=no
mysql_backup=yes

So I thought mysql 5.0 was installed and forgot to check.
The mysql -V is giving me this:

mysql Ver 14.14 Distrib 5.1.57, for unknown-linux-gnu (x86_64) using readline 5.1

So 5.1.57 is installed.

How can this be happening while 5.0 should be installed by custombuild?

 

[smtalk]

You have "mysql_inst=no" set, so CustomBuild does not touch the MySQL installation at all. Please do the following to reinstall MySQL:

cd /usr/local/directadmin/custombuild
./build update
./build set mysql_inst yes
./build mysql
./build php n

 

[Richard G]

You have "mysql_inst=no"

I did not set it up that way, this is automatically done by setup.sh from DA when installing custombuild.

So thank you for the answer but I have Mysql already installed again. Maybe my question was not clear enough.

What I'm wondering about is, why in a plain custombuild setup, the setup.sh put's the configuration like that, but installes 5.1.
Otherwise said, the other server was almost a year old, and there the DA setup automatically installed 5.0.
So one could expect that when it is mentioned in the options.conf this way, also today on new installes, the newest 5.0.x version is installed, and not 5.1.

So why wasn't the newest 5.0.x version installed by DA?
And when it was time to head up to the next version, why is it default not set to 5.1 in the options.conf, because this works confusing.

 

[SeLLeRoNe]

Cause DA setup doenst use custombuild for install mysql, it use a script apart as far as i remember.

Regards

 

[Richard G]

I understand that, but I thought the script would install the default values of the custombuild options. Seems it does not.

Maybe it's a good idea then to put the default values of the options.conf to the version that will be installed automatically. I could try to put that in the suggestion section.

One last question. I got the same in the options.conf for Exim.
#Mail options
exim=no

What if i put this to yes. Exim is already installed, what's the benefit? Or is this option only ment for Custombuild 1.2 so exim will update automatically?

 

[SeLLeRoNe]

if you set exim to yes then you will be able to update your exim version using custombuild and not just using source (there is a guide in help.directadmin.com to update exim from source)

 

[Richard G]

But this updating using custombuild for exim, only works for custombuild 1.2 or does it these days also work for custombuild 1.1?

 

[SeLLeRoNe]

It work just for 1.2 yes is correct. But unless you are using php 4 i dont see any reason for keep using 1.1

Regards

 

[Richard G]

The only reason was that with a new installation you can not directly choose for version 1.2 and I wanted both DA versions between the servers that should be transfered as much the same as possible.
After the work is done now, I can change to 1.2.

Thanks for the explanations!!

 

[smtalk]

It work just for 1.2 yes is correct. But unless you are using php 4 i dont see any reason for keep using 1.1

Regards

It works with 1.1 too We backported the code a few months ago.

 

[SeLLeRoNe]

Oh ok Didnt know, thanks ^^

 

[Richard G]

I knew it was in the planning, but did not know when.
Now i do, thanks!