misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
609537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mysql-server-5.1
Version: 5.1.49-3
Severity: serious
reassign 609537 mysql-server-5.5
thanks
As far as I can tell this bug doesn't exist in the init.d script shipped
with mysql-server-5.6 - I can see waiting code there similar to the code
proposed in the patches in this bug.
So presumably this should be tracked just in mysql-server-5.5 (which
will
Processing commands for cont...@bugs.debian.org:
> reassign 609537 mysql-server-5.5
Bug #609537 [mysql-server] /etc/init.d/mysql stop leaves a process but exits
with 0 status
Bug reassigned from package 'mysql-server' to 'mysql-server-5.5'.
No longer marked as found in ve
Hello!
In MariaDB the script has a section that waits for a long time so that
even the biggest and busiests databases will have enough time to shut
down:
for i in `seq 1 600`; do
sleep 1
if mysqld_status check_dead nowarn; then server_down=1; break; fi
done
if te
found 609537 5.5.38-0+wheezy1
thanks
I have found this bug happening even on wheezy, on a server that doesn't
exit immediately after a mysladmin shutdown.
I find that the expectation of the shutdown procedure of Debian's
initscript is a little unreasonable: it issues a shutdown command, and
if it
retitle 677222 log_slow_queries deprecated
reassign 609537 mysql-server
severity important
tag 609537 +patch
thanks
Are/Marko,
I am sorry that this has not been fixed (or even really looked at). I
see no reason why it should have been magically fixed in the migration
to 5.5 and 5.1 is goin
This RC bug is now unfixed for more than a year - the solution from
4dd128e8.1080...@gmail.com looks promising, but there was no action on it.
Is there any plan for a change?
cu
AW
--
[...] If you don't want to be restricted, don't agree to it. If you are
coerced, comply as much as you must to p
I could have made a patch to simply kill remaining process, but I
assumed it is wiser to leave that part to sysadmin. But I wanted to help
system admins easier to see that somthing is wrong. Normal exit in such
situations is misleading. People expect to be notified in such
situations. Severity
Hi,
Also as an opposite, the initscript could return 1 even if the daemon
has started successfully.
I see this on one of my server with innodb_buffer_pool_size = 33G and
memlock as the process take some time (more that the 14s allowed in the
init to start).
Should an other bug be opened for that
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was
jcris...@debian.org).
> usertag 609537 squeeze-can-defer
Bug#609537: /etc/init.d/mysql stop leaves a process but exits with 0 status
user release.debian@packages.debian.org
usertag 609537 squeeze-can-defer
tag 609537 squeeze-ignore
kthxbye
On Mon, Jan 10, 2011 at 14:09:58 +0100, Marko Randjelovic wrote:
> Package: mysql-server-5.1
> Version: 5.1.49-3
> Severity: serious
> Tags: squeeze
>
> >From Debian Policy Manual:
> ht
Package: mysql-server-5.1
Version: 5.1.49-3
Severity: serious
Tags: squeeze
>From Debian Policy Manual:
http://www.debian.org/doc/debian-policy/ch-opersys.html#s-writing-init
"The init.d scripts must ensure that they will behave sensibly (i.e.,
returning success and not starting multiple copies o
12 matches
Mail list logo
