Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
The specific reason should have shown up in your daemon log in /var/log, or in your mysql specific error logs.
If it's not obvious there (typically that sort of thing happens because the log or ibdata files are in the wrong place or the permissions are off), post the relevant log portions.
Jan 29 08:46:32 shells mysqld: 110129 8:46:32 InnoDB: Starting shutdown...
Jan 29 08:46:37 shells mysqld: 110129 8:46:37 InnoDB: Shutdown completed; log sequence number 0 44233
Jan 29 08:46:37 shells mysqld: 110129 8:46:37 [Note] /usr/sbin/mysqld: Shutdown complete
Jan 29 08:46:37 shells mysqld:
Jan 29 08:46:37 shells mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Jan 29 08:46:46 shells /etc/init.d/mysql[3401]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Jan 29 08:46:46 shells /etc/init.d/mysql[3401]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed
Jan 29 08:46:46 shells /etc/init.d/mysql[3401]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Jan 29 08:46:46 shells /etc/init.d/mysql[3401]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Jan 29 08:46:46 shells /etc/init.d/mysql[3401]:
$ cat /etc/mysql/debian.cnf | grep password
$ mysql -u root -p
mysql> GRANT ALL PRIVILEGES ON *.* TO 'debian-sys-maint'@'localhost' IDENTIFIED BY 'password' WITH GRANT OPTION
where password is the output from the first command.
MsLinux-
forums.debian.net - where facepalm is the default answer
Hi,
I had the same problem after upgrade to squeeze.
I have a solution:
- rename the /etc/mysql/my.cnf to /etc/mysql/my.cnf.squeeze
- rename the /etc/mysql/my.cnf.dpkg-dist to /etc/mysql/my.cnf
- start the mysql daemon: /etc/init.d/mysql start.
I am having the same issue but I made an additional mistake. When I've removed the mysql and all the mysql dependencies I noticed the init.d scripts and settings were still there, so I've removed them manually to make sure everything will be installed from scratch. For my greatest surpise the init.d scripts were not reinstalled.
I tried to find it by "apt-file search mysql", I found nothing as /etc/init.d/mysql. I had no clue how to continue so just to be sure I've reinstalled lsb-base as well. Still no init.d script.
Could somebody point me how to find the mentioned file or which package contains it?
check for loopback-interface with "ifconfig".
In my case the loopback interface was missing, and since mysql is configured as per default to bind to that, it could not start...
just edit /etc/network/interfaces:
add "lo" to the line with auto
in my case
before:
auto eth0
after:
auto lo eth0
and add the line:
iface lo inet loopback
then reboot.
If all went good, and it should then the loopback interface will be up and running as well as mysqld.
thofmann wrote:check for loopback-interface with "ifconfig".
In my case the loopback interface was missing, and since mysql is configured as per default to bind to that, it could not start...
just edit /etc/network/interfaces:
add "lo" to the line with auto
in my case
before:
auto eth0
after:
auto lo eth0
and add the line:
iface lo inet loopback
then reboot.
If all went good, and it should then the loopback interface will be up and running as well as mysqld.
I had this issue. In my case it was because skip-bdb was in my my.cnf and I kept my custom my.cnf instead of installing the distributed version.
Removing it allows the server to start.
Berkeley DB is no longer in 5.1x, so the option doesn't apply any more, but why the mysql developers halt startup upon seeing this now deprecated option instead of just logging and ignoring is beyond me.