Please fix this bug in the mini.iso - we're using it to provision
servers with foreman and had problems. It took us the better part of
yesterday until we discovered that it wasn't our setup but a broken
package.
Cudos to the other posters for pointing out the workaround with the FQDN
:)
--
You
** 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.
** 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327222
Title:
Segfault:
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.
** 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).
** 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).
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
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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
** 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
Bugs, which is subscribed to 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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327222
Title:
Segfault: corosync segfaults randomly on Ubuntu trusty
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:
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:
Binary package hint: open-vm-tools
Description:Ubuntu lucid (development branch)
Release:10.04
Package:open-vm-tools [2010.02.23-236320-1+ubuntu1]
The open-vm-tools are missing an option to enable the host-to-vm
timesync, which can be activated via the
** Attachment added: Init Script and default-file
http://launchpadlibrarian.net/41823025/open-vm-tools-files.tar.bz2
** Changed in: open-vm-tools (Ubuntu)
Assignee: (unassigned) = Ubuntu Virtualisation team (ubuntu-virt)
** Description changed:
Binary package hint: open-vm-tools
** 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
** 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
Bugs, which is subscribed to
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
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
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
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,
updated the forums posts too. binary packages ready for download now.
br,
David
--
Multiple tomcat instances
https://bugs.launchpad.net/bugs/207787
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
hi,
as a start i repackaged tomcat6 for 8.04 LTS, starting from the jaunty package
and using the apache source files from tomcat 6.0.20. Please consider this post
on the forums:
http://ubuntuforums.org/showpost.php?p=8066371postcount=4
also the new packages are up for grabs here:
Hi there,
seem to lots of use cases out there... here are my two cents to the
multi-instance tomcat5.5 thingy.
skel- files, little reworked init-script and a create-instance script
that accepts options for ports, ip and some java-opts. drop the contents
of the zipfile to /usr/local/bin, then
Hi again,
thx for your comments, greatly appreciated. At my company we mainly use
standard packages and this script builds upon them, however i was not
aware of neither the broken state of tomcat5.5 nor the thread you
pointed out above. Thanks for that.
No, it is no problem to rename the script
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 ]
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 ]
35 matches
Mail list logo
