On Wed, Sep 20, 2000 at 12:15:55PM -0700, Account for Debian group mail wrote: > > New mySQL install (3.22.32-3) on Debian 2.2 (kernel 2.2.17). I can easily > issue a /etc/init.d/mysql start|reload|stop okay, but once it's running I > try a simple "mysqladmin version" and the tty hangs. > > This is what I see in mysql.err: > > mysqld started on Tue Sep 19 14:02:07 PDT 2000 > /usr/sbin/mysqld: Can't create/write to file '/var/log/mysql.log' > (Errcode: 13) > /usr/sbin/mysqld: ready for connections > > Number of processes running now: 0 > mysqld restarted on Tue Sep 19 14:02:14 PDT 2000 > 000919 14:02:14 Can't start server: Bind on TCP/IP port: Address already > in use000919 14:02:14 Do you already have another mysqld server running > on port: 3306 ? > 000919 14:02:14 Aborting > > mysqld ended on Tue Sep 19 14:02:14 PDT 2000 > > I've already tried giving the mysql.log file 777 perms and changed the > ownership from root to mysql and back, but no luck on getting rid of the > initial "Can't create/write" error. When doing a ps, there are no other > mysqld processes listed.
occasionally it helps to remove the socket file "mysql.sock" (if you have one), which is by default created in /tmp. I don't know why sometimes mySQL cannot do this by itself (permissions?), and also I don't really know, what this is created for, but I assume it is supposed to allow local clients to connect via a unix domain socket instead of the usual inet socket on port 3306. Maybe that helps, Erdmut -- Erdmut Pfeifer science+computing gmbh Hagellocher Weg 71 phone: +49 (0)7071-9457-255 D-72070 Tuebingen email: [EMAIL PROTECTED] -- Bugs come in through open windows. Keep Windows shut! --
