** Changed in: openais (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/139062
Title:
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
I also have trouble with openais under gutsy amd64. The only way to get
it going is to download the source package and rebuild with -O1 in
CFLAGS instead of the default of -O3.
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You
Status Update
I tried the cluster startup with Hardy Alpha 2 on amd64 with success:
[EMAIL PROTECTED]:~# /etc/init.d/cman start
Starting cluster manager:
Loading kernel modules: done
Mounting config filesystem: done
Starting cluster configuration system: done
Joining cluster: done
Starting
I'm missing the Openais log entries. I should find always the start
message: Dec 3 10:29:59 rh openais[6460]: MAIN ] AIS Executive
Service RELEASE 's ubrev 1358 version 0.80.3'. Ubuntu using the 0.82.0
(trunk), which is using the new logsys system. I think, the logsys
system is the problem. If i
Test with Hardy Alpha1: same situation on x86_64. I try to
OPENAIS_BUILD=debug, but i got: cman_tool: aisexec daemon didn't start.
Next I try to modify the logging in
openais-0.82/debian/build/build/exec/main.c from:
/*
LOGSYS_DECLARE_SYSTEM (openais,
LOG_MODE_OUTPUT_STDERR |
I tested the situation on Hardy (2007-11-05) on i686 and x86_86 with the
result: working on i686 and doesn't working on x86_86. My workaround
with -O0 doesn't work anymore. I used this versions (on both platforms):
||/ Name Version Description
The same problem here with the same output and syslog messages. My
machine: Dell PE2950.
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
Guys could somebody be so kind to attach /var/log/syslog and messages
from a failing amd64?
Thanks
Fabio
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received this bug notification because you are a member of Ubuntu
Bugs,
Fabio, I attached the cman startup syslog section. The command and the
output:
[EMAIL PROTECTED]:~# /etc/init.d/cman start
Starting cluster manager:
Loading kernel modules: done
Mounting config filesystem: done
Starting cluster configuration system: done
Joining cluster:cman_tool: aisexec
** Changed in: openais (Ubuntu)
Sourcepackagename: redhat-cluster-suite = openais
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I will need to get somebody to look at the amd64 fault.
openais can be executed standalone (hence the openais init script) or
via cman but they shouldn't be executed together on the same machine. I
don't know what kind of behaviour that will have.
Make absolutely sure to have
I confirm the bug is still here on amd64.
I've process the way Herbert describes changing 'CFLAGS += -O3 -Wall
to CFLAGS += -O0 -Wall in the Makefile.inc and then rebuilding the
package.
I don't know if it's a normal behavior but openais must remain shutdown before
starting cman (cman runs
I do some further tests on amd64 platfom and see the old error: aisexec
daemon didn't start. See the attached strace output. This output
contains a Segmentation fault. I try to build the openais package with
DEB_BUILD_OPTIONS=debug and see the error is gone. Next I try to build
this without debug
I do a fresh installation of Gutsy on another machine and now it is
working. I have a two node cluster with one active member. Thanks.
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received this bug notification because you
The behavior ist different, but there is still a segmentation fault:
24, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr(10.2.1.30)},
[16]) = 52
7335 close(5) = 0
7335 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
7335 rt_sigaction(SIGSEGV, {SIG_DFL},
I was able to reproduce the problem and it should be fixed in the latest
upload I did one hour ago with openais 0.81-0ubuntu5 and redhat-cluster-
suite_2.20070823.1-0ubuntu1.
Please let me know if this fixes the problem for you.
Cheers
Fabio
** Changed in: redhat-cluster-suite (Ubuntu)
In the strace output I posted yesterday, we can see that aisexec fork,
then the child segfault (line 679). No idea what is caused the
segfault, but it may be related.
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received
Same situation, also after a apt-get dist-upgrade (2007-09-28). I see
also a segfault (line 771).
** Attachment added: strace of cman_tool -t 30 -w join
http://launchpadlibrarian.net/9544402/join.trace.txt
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
Attached the output of strace -f cman_tool -d join
** Attachment added: strace of cman_tool -d join
http://launchpadlibrarian.net/9523264/cman_tool.strace
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received this bug
This processes are active after a reboot and startup of /etc/init.d/cman
start:
[EMAIL PROTECTED]:~# ps axlw | egrep 'aise|ccsd'
1 0 3627 1 15 0 26392 1152 - Ssl ? 0:00
/usr/sbin/ccsd
1 0 3640 1 16 0 23956 1012 futex_ Sl ? 0:00 aisexec
Every
I can confirm the bug. The same configuration file (hostname have been
changed but that's all) work out-of-the-box in 7.04, but fail with the
exact same error in 7.10.
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received
** Attachment added: The /etc/cluster/cluster.conf configuration file (simple
single node cluster)
http://launchpadlibrarian.net/9251208/cluster.conf
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received this bug
** Attachment added: Same configuration file with .txt suffix
http://launchpadlibrarian.net/9251252/cluster.conf.txt
--
Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
https://bugs.launchpad.net/bugs/139062
You received this bug notification because you are a member of
23 matches
Mail list logo
