Hi Peter, 

no , not one single line in any of the /var/log/mysql/* files, only when i start
mysql manually with the parameters in the init script i see
########
mysqld: ready for connections.
Version: '4.1.21-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  
Gentoo Linux mysql-4.1.21
060807 16:46:20 [Note] mysqld: Normal shutdown

060807 16:46:21 [Note] mysqld: Shutdown complete

mysqld: ready for connections.
Version: '4.1.21'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Gentoo 
Linux mysql-4.1.21
060823 14:09:54 [Note] mysqld: Normal shutdown

060823 14:09:54 [Note] mysqld: Shutdown complete

mysqld: ready for connections.
Version: '4.1.21'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Gentoo 
Linux mysql-4.1.21
060831  1:26:31 [Note] mysqld: Normal shutdown

060831  1:26:31 [Note] mysqld: Shutdown complete

mysqld: ready for connections.
Version: '4.1.21'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Gentoo 
Linux mysql-4.1.21
060905 15:18:15 [Note] mysqld: Normal shutdown

060905 15:18:16 [Note] mysqld: Shutdown complete

mysqld: ready for connections.
Version: '4.1.21'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Gentoo 
Linux mysql-4.1.21
#########

in /var/log/mysql/mysqld.err

mysql.err and mysql.log are empty

when i try the init script i get:
#####
# /etc/init.d/mysql start
dbg:  >>> start()
 *  ...
dbg:  >>> get_slot_config()
dbg:  srv                0
dbg:  srv_slot           0
dbg:  srv_num
dbg:  tmp_eval           [EMAIL PROTECTED]
dbg:  conf_d_parameters
dbg:  MY_SUFFIX
dbg:  chroot dir =>
dbg:  niceness   =>
dbg:  basedir    => /usr
dbg:  datadir    => /var/lib/mysql
dbg:  pidfile    => /var/run/mysqld/mysqld.pid
dbg:  socket     => /var/run/mysqld/mysqld.sock
dbg:  Unamanged  =>
dbg:  <<< get_slot_config() ok
dbg:  >>> checkconfig("/var/lib/mysql")
dbg:  <<< checkconfig() ok
 * Starting mysql (/etc/mysql/my.cnf)
dbg:  starting mysqld with: --defaults-file=/etc/mysql/my.cnf   --basedir=/usr 
--datadir=/var/lib/mysql --pid-file=/var/run/mysqld/mysqld.pid 
--socket=/var/run/mysqld/mysqld.sock
dbg:
49,48,47,46,45,44,43,42,41,40,39,38,37,36,35,34,33,32,31,30,29,28,27,26,25,24,23,22,21,20,19,18,17,16,15,14,13,12,11,10,9,8,7,6,5,4,3,2,1,0,dbg:
 * MySQL NOT started (0)
dbg:  <<< start()             
######

*shrug*

On Wed, 13 Sep 2006 18:51:44 -0700
"Peter Abrahamsen" <[EMAIL PROTECTED]> wrote:

> 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
> 


-- 
Darko Luketic
[EMAIL PROTECTED]
-- 
[email protected] mailing list

Reply via email to