Hi Steven,
> continually use the cpu 100% or only doing startup?
yes.
> Which VM technology are you using?
I use VMWare Esxi.
> With pacemaker, or only with corosync?
When it combined Pacemaker, the problem seems to happen.
The problem does not happen by the start only in corosync.
--- corosync.conf----
# Please read the corosync.conf.5 manual page
compatibility: whitetank
service {
# Load the Pacemaker Cluster Resource Manager
name: pacemaker
ver: 0
}
totem {
version: 2
secauth: off
join: 1000
token: 24000
threads: 0
rrp_mode: none
interface {
ringnumber: 0
bindnetaddr: 192.168.10.0
mcastaddr: 226.94.1.1
mcastport: 5405]
}
# interface {
# ringnumber: 1
# bindnetaddr: 192.168.20.0
# mcastaddr: 226.94.1.1
# mcastport: 5405
# }
}
logging {
fileline: on
to_stderr: no
to_logfile: no
to_syslog: yes
# logfile: /tmp/corosync.log
debug: on
syslog_facility: local1
timestamp: on
logger_subsys {
subsys: AMF
debug: off
}
}
amf { mode: disabled
}
Best Regards,
Hideo Yamauchi.
--- Steven Dake <sd...@redhat.com> wrote:
> On 06/30/2010 06:38 PM, renayama19661...@ybb.ne.jp wrote:
> > Hi Steven,
> >
> > In addition, a problem is taking place with the virtual guest whom I
> > assigned one CPU to.
> > It did not occur with version 1.2.5.
> >
> > When I start corosync, this problem occurs.
> > Some guests use the CPU 100%.
> >
>
> continually use the cpu 100% or only doing startup?
>
> Which VM technology are you using?
>
> With pacemaker, or only with corosync?
>
> Regards
> -steve
> > I think that there is a problem in 1.2.6 revisions.
> >
> > Best Regards,
> > Hideo Yamacuhi.
> >
> > --- Steven Dake<sd...@redhat.com> wrote:
> >
> >> Hello,
> >>
> >> It is with great pleasure I announce the release of the Corosync Cluster
> >> Engine 1.2.6.
> >>
> >> This update resolves the following defects:
> >>
> >> * Fix problem where glibc's fork() implementation may cause segfaults in
> >> Pacemaker's use of the fork() system call.
> >> * Fix problem where a cman configuration reload while statistics are
> >> being gathered leads to mutex deadlock.
> >> * Fix problem where a full /dev/shm would result in client segfault -
> >> instead an error is returned in this situation.
> >> * Have corosync.spec.in own /var/log/cluster and have makefiles create
> >> this directory. Modified example configuration file to default to
> >> logging to /var/log/cluster to match upstream selinux defaults.
> >> * Fix problem where flight recorder leaks files in shared memory
> >> filesystem. Also clean up the error handling of the shared memory
> >> allocation code of the flight recorder.
> >> * Fix problem where a failure in glibc's pathconf API would result in
> >> segfault.
> >> * Add corosync and corosync-blackbox man pages.
> >>
> >> This release is immediately available from our website:
> >>
> >> http://www.corosync.org
> >>
> >> Regards
> >> -steve
> >> _______________________________________________
> >> Openais mailing list
> >> Openais@lists.linux-foundation.org
> >> https://lists.linux-foundation.org/mailman/listinfo/openais
> >>
> >
>
>
_______________________________________________
Openais mailing list
Openais@lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/openais
