Package: mysql-server
Version: 5.5.9999+default
Severity: important

Dear Maintainer,

   When i call 'sudo service mysql restart' it sometimes fails with a log like :
Mar  8 16:20:22 localhost systemd[1]: Stopping LSB: Start and stop the mysql 
database server daemon...
Mar  8 16:20:22 localhost mysql[1847]: Stopping MySQL database server: mysqld.
Mar  8 16:20:22 localhost systemd[1]: Stopped LSB: Start and stop the mysql 
database server daemon.
Mar  8 16:20:22 localhost systemd[1]: Starting LSB: Start and stop the mysql 
database server daemon...
Mar  8 16:20:54 localhost /etc/init.d/mysql[2492]: 0 processes alive and 
'/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Mar  8 16:20:54 localhost /etc/init.d/mysql[2492]: #007/usr/bin/mysqladmin: 
connect to server at 'localhost' failed
Mar  8 16:20:54 localhost /etc/init.d/mysql[2492]: error: 'Can't connect to 
local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Mar  8 16:20:54 localhost /etc/init.d/mysql[2492]: Check that mysqld is running 
and that the socket: '/var/run/mysqld/mysqld.sock' exists!


   i made some tests and it appears that after the 'stop' step the mysql server 
is sometimes not really 'dead' yet. I can sometimes see it  still running when 
i use the following command li$
                sudo  systemctl stop  mysql; ps -ef | grep -i sql; sudo  
systemctl start mysql

 Of course, when it happens, the start treatment of  /etc/init.d/mysql will 
assume that a server is already running, it will to start this service and 
directly go to the part where it tries$
 And of course the service is not started.

 I 'think' that this beahavior could be caused by a massive select query 
running on the mysql database at the moment the stop step of the init script is 
called.

i submit this bug from my corporate computer (duno how to configure Debian to 
use my Ms Office email) but it occurs on my debian8 servers.
Best Regards,
Marc

Ce message et toutes les pièces jointes (ci-après le "message") sont établis à 
l’intention exclusive des destinataires désignés. Il contient des informations 
confidentielles et pouvant être protégé par le secret professionnel. Si vous 
recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et 
de détruire le message. Toute utilisation de ce message non conforme à sa 
destination, toute diffusion ou toute publication, totale ou partielle, est 
interdite, sauf autorisation expresse de l’émetteur. L'internet ne garantissant 
pas l'intégrité de ce message lors de son acheminement, Atos (et ses filiales) 
décline(nt) toute responsabilité au titre de son contenu. Bien que ce message 
ait fait l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne 
peut garantir l’absence totale de logiciels malveillants dans son contenu et ne 
pourrait être tenu pour responsable des dommages engendrés par la transmission 
de l’un d’eux.

This message and any attachments (the "message") are intended solely for the 
addressee(s). It contains confidential information, that may be privileged. If 
you receive this message in error, please notify the sender immediately and 
delete the message. Any use of the message in violation of its purpose, any 
dissemination or disclosure, either wholly or partially is strictly prohibited, 
unless it has been explicitly authorized by the sender. As its integrity cannot 
be secured on the internet, Atos and its subsidiaries decline any liability for 
the content of this message. Although the sender endeavors to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Reply via email to