removed mysql in directadmin !

[He3am]

hi
mysqld service removed from server !!
when restart show this error
/etc/init.d/mysqld: line 260: my_print_defaults: command not found
/etc/init.d/mysqld: line 263: my_print_defaults: command not found
/etc/init.d/mysqld: line 260: my_print_defaults: command not found
/etc/init.d/mysqld: line 263: my_print_defaults: command not found
ERROR! MySQL manager or server PID file could not be found!
/etc/init.d/mysqld: line 260: my_print_defaults: command not found
/etc/init.d/mysqld: line 263: my_print_defaults: command not found
Starting MySQL ERROR! Couldn't find MySQL manager (/usr/bin/mysqlmanager) or server (/usr/bin/mysqld_safe)

 

[scsi]

cd /usr/local/directadmin/custombuild
./build update
./build clean
./build mysql d

 

[He3am]

cd /usr/local/directadmin/custombuild
./build update
./build clean
./build mysql d

hi
show this :

/etc/init.d/mysqld: line 263: my_print_defaults: command not found
/etc/init.d/mysqld: line 260: my_print_defaults: command not found
/etc/init.d/mysqld: line 263: my_print_defaults: command not found
ERROR! MySQL manager or server PID file could not be found!
/etc/init.d/mysqld: line 260: my_print_defaults: command not found
/etc/init.d/mysqld: line 263: my_print_defaults: command not found
Starting MySQL ERROR! Couldn't find MySQL manager (/usr/bin/mysqlmanager) or server (/usr/bin/mysqld_safe)
It is recommended to do "./build php n" after MySQL update.

 

[nobaloney]

Educated guess only...

CustomBuild and your OS package manager may put MySQL in different locations, and you may have still had a mysql configuration file installed (which CustomBuild probably wont touch if it exists.

Try finding and removing my.cnf and then rebuilding from CustomBuild.

Jeff

 

[JohnPal]

Lessons learned upgrading mysql 5.0 - 5.5

Just had to toss in a lessons learned on this thread...

I'm very much an app dev, not a sys admin...so I tend to fumble through linux admin tasks quite a bit. Hence my love for DA.
I just tried to perform a mysql upgrade from 5.0 to 5.5. I found the DA link http://help.directadmin.com/item.php?id=310 and updated the options.conf to 5.1 first...since everything I had read said go 5.0 to 5.1 to 5.5. Then I ran ./build mysql. It proceeded to blow up with the same issue He3am posted in this thread.

When that blew up, and I could no longer start mysqld, I tried to update the options.conf to 5.5, but that blew up similarly. Needless to say, I was a tad miffed.

Fortunately, after some searching, I read scsi's reply above, and that got me successfully through the upgrade to 5.5. THANKS SCSI!!!

I think the issue was that Custombuild was old because when I did ./build update, it pulled down a ton of updates.

I did get a bunch of 'Table upgrade required' errors, but it looks like the upgrade performed the repair automagically...cool.

Time for another cup of coffee...

---John Pal...