Hello Darko, Are you saying that turning up the debug puts nothing in the logs? I don't use mysql, but something ought to be logged. If not, what I often do is start the daemon manually, and if that isn't enough, strace it.
As to the vhosts thing, please read the documentation here: http://httpd.apache.org/docs/2.0/vhosts/mass.html Good luck, Peter On 9/13/06, Darko Luketic <[EMAIL PROTECTED]> wrote:
Hello, i upgraded mysql a few months ago. i remember that this upgrade was that one that added the file server-running to /etc/init.d/mysql i've been running mysql 4 since 08/2005, 1st install. current installed version is 4.1.21. in this version the check for the server-running file was removed. the problem appeared 2 upgrades ago. (4.0.x) last version was 4.0.27 , previous 4.0.26 . when i upgraded to 4.1.21 from 4.0.27 i created a db dump, but not from 4.0.26->4.0.27. i'm using a nptl-enabled compilation. problem is i can't start the mysql server through the init script. i set debug to max possible, but the output is just a counter to 40 and starting mysql failed. when i'm starting the mysql server by hand with the parameters in the init script, it runs fine, however as soon as i want to restart daemons depending upon mysql, the mysql server stops, and i have to start it manually, which is annoying as e.g. i would like to restart apache or other daemons daily through cron. i know a reboot would very likely solve the problem, but thats not an option. (366 days uptime ruined, nooo :) ). it's not because of ibdata or similar files, it has to be something in the init script or in the content of some file that drives the start-stop-daemon crazy. any help appreciated i hope my english wasn't too bad. p.s.: does anyone know of a namebased virtualhosting module or similar for apache2 that doesn't require a graceful apache2 restart? -- Darko Luketic [EMAIL PROTECTED] -- [email protected] mailing list
-- [email protected] mailing list
