Le 22/09/2012 13:51, Avi Greenbury a écrit :
rudu wrote:
Hi,
Running wheezy on my laptop.
I can glimpse while booting a message :
Starting MySQL database server: mysqld ...... Failed!

Indeed  a command "ps aux | grep mysql " at the end of the boot
returns nothing.
But I can start it with "service mysql start" ok.

/var/log/mysql.err and mysql.log are empty.
dmesg | grep -i mysql    returns nothing

I'm at a loss here.
Anybody sees how I could get mysql to be fired up at boot time ?

You want to be checking syslog, since that's where MySQL's startup
messages go. Does it fail on *every* boot, and succeed on *every*
manual start?


Hi Avi, thanks.(Posting back on the list)

Well it seems a little bit clearer now.

# cat /var/log/syslog | grep -i mysql | tail -n 30
Sep 22 15:06:12 ubajm mysqld:
Sep 22 15:06:12 ubajm mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Sep 22 15:07:22 ubajm mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 [Note] Plugin 'FEDERATED' is disabled. Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 InnoDB: The InnoDB memory heap is disabled Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 InnoDB: Mutexes and rw_locks use GCC atomic builtins Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 InnoDB: Compressed tables use zlib 1.2.3
Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 InnoDB: Using Linux native AIO
Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 InnoDB: Initializing buffer pool, size = 128.0M Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 InnoDB: Completed initialization of buffer pool Sep 22 15:07:22 ubajm mysqld: 120922 15:07:22 InnoDB: highest supported file format is Barracuda. Sep 22 15:07:23 ubajm mysqld: 120922 15:07:23 InnoDB: Waiting for the background threads to start Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24 InnoDB: 1.1.8 started; log sequence number 33023319 Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24 [Note] Server hostname (bind-address): '192.168.1.60'; port: 3306 Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24 [Note] - '192.168.1.60' resolves to '192.168.1.60'; Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24 [Note] Server socket created on IP: '192.168.1.60'. Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24 [ERROR] Do you already have another mysqld server running on port: 3306 ?
Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24 [ERROR] Aborting
Sep 22 15:07:24 ubajm mysqld:
Sep 22 15:07:24 ubajm mysqld: 120922 15:07:24  InnoDB: Starting shutdown...
Sep 22 15:07:25 ubajm mysqld: 120922 15:07:25 InnoDB: Shutdown completed; log sequence number 33023319 Sep 22 15:07:25 ubajm mysqld: 120922 15:07:25 [Note] /usr/sbin/mysqld: Shutdown complete
Sep 22 15:07:25 ubajm mysqld:
Sep 22 15:07:25 ubajm mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended Sep 22 15:07:35 ubajm /etc/init.d/mysql[3333]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in Sep 22 15:07:35 ubajm /etc/init.d/mysql[3333]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed Sep 22 15:07:35 ubajm /etc/init.d/mysql[3333]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)' Sep 22 15:07:35 ubajm /etc/init.d/mysql[3333]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Sep 22 15:07:35 ubajm /etc/init.d/mysql[3333]:

What I'm understanding here is that my laptop hasn't got his IP address yet when mysqld tries to initialize itself ...
Am I right ?
If so, what should I do ?

Jean-Marc


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/505dbbc2.5070...@cegetel.net

Reply via email to