I also have problems with this initscript (mostly with wrong return
codes in scripted shutdowns), however i think that the author overlooked
an 'else' statement:
@142ff: instead of:
142 if [ $r -ne 0 ]; then
143 log_end_msg 1
144 [ $VERBOSE != no ]
Patch for the mysql init script attached. Reworked the 'stop'-section
some more, removed unused / old variables etc...
br,
David
** Attachment added: Patch for the mysql-server-5.0 init script.
http://launchpadlibrarian.net/35750472/mysql.patch
--
Strange or obsolete code in mysql
Hi Alexey,
true, killing all mysqld-procs isn't the best choice, however i tried
to stick to the original initscript which also killed the processes
after some time. Its no problem to change this behaviour if wanted, only
the 'kill -9' and 'log_msg' lines have to be altered. Who is up to
** Changed in: mysql-dfsg-5.0 (Ubuntu)
Assignee: (unassigned) = Patch for MySQL team (mysql-patch-team)
--
Strange or obsolete code in mysql initscript
https://bugs.launchpad.net/bugs/359177
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
The haproxy initscript misses a configtest option, which haproxy natively
supports. It also does not warn the user, if haproxy has been disabled in the
default file, but exits silently.
Also, it has become a de-facto standard for daemons to include conf.d
configuration
I filed a bug with debian, perhaps it will get included in one of the next
releases:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750459
** Bug watch added: Debian Bug tracker #750459
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750459
--
You received this bug notification because
Public bug reported:
I'm running a two node HA Cluster with pacemaker/corosync and a pretty
simple configuration - only an IP address, one service and two clone
sets of resources are managed (see below). however i run into constant
crashes of corosync on both nodes. At the moment this behaviour
** Attachment added: pacemaker crashdump
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1327222/+attachment/4126486/+files/_usr_lib_pacemaker_crmd.111.crash
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in
** Attachment added: corosync crashdump
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1327222/+attachment/4126487/+files/_usr_sbin_corosync.0.crash
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
** Attachment added: Cluster Information Base XML
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1327222/+attachment/4126485/+files/cib.xml
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
At the moment I'm running corosync in debug mode, so I should get more
logs soon.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1327222
Title:
Segfault: corosync segfaults
** Also affects: pacemaker (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
I'm running a two node HA Cluster with pacemaker/corosync and a pretty
simple configuration - only an IP address, one service and two clone
sets of resources are managed (see below).
** Changed in: corosync (Ubuntu)
Status: New = Invalid
** Changed in: pacemaker (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1327222
I found out that not the cluster stack itself was causing the issues but
the tool that I used to configure the cluster: LCMC. Although LCMC has
been working flawlessly for me on older versions of corosync/pacemaker,
it seems as it hasn't been updated to work with corosync 2.3.x and
pacemaker 1.1x.
14 matches
Mail list logo
