[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openais/+bug/139062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: 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 received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 daemons: groupd fenced dlm_controld gfs_controld Joining fence domain: done Starting Quorum Disk daemon: done [EMAIL PROTECTED]:~# cman_tool status Version: 6.1.0 Config Version: 17 Cluster Name: hardy Cluster Id: 3217 Cluster Member: Yes Cluster Generation: 64 Membership state: Cluster-Member Nodes: 1 Expected votes: 1 Total votes: 1 Quorum: 1 Active subsystems: 7 Flags: 2node Dirty Ports Bound: 0 Node name: hagbard Node ID: 1 Multicast addresses: 225.0.0.11 Node addresses: 10.165.166.12 [EMAIL PROTECTED]:~# dpkg -l redhat-cluster-suite openais cman linux-image-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii cman 2.20071214-0ub cluster manager ii linux-image-ge 2.6.24.2.2 Generic Linux kernel image ii openais0.82-0ubuntu10 Standards-based cluster framework (daemon an ii redhat-cluster 2.20071214-0ub red hat cluster suite (meta package) -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 removed aisexec_tty_detach () in exec/main.c, then I can see all log entries in syslog and in /var/log/openais/aisexec.log. It looks like, that the logsys hangs after the fork in aisexec_tty_detach (). My versions: ii openais0.82-0ubuntu6 Standards-based cluster framework (daemon an ii redhat-cluster 2.20071022-0ub red hat cluster suite (meta package) and a X86_64 system. I see, the stable release o Openais is 0.80. Any ideas, how we can get the Openais logsys component working? Backstep to 0.80? Herbert -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 | LOG_MODE_OUTPUT_SYSLOG_THREADED | LOG_MODE_DISPLAY_DEBUG | LOG_MODE_BUFFER_BEFORE_CONFIG, NULL, LOG_DAEMON); */ to: LOGSYS_DECLARE_SYSTEM (openais, LOG_MODE_OUTPUT_FILE | LOG_MODE_DISPLAY_DEBUG , /var/log/openais/aisexec.log, LOG_DAEMON); LOGSYS_DECLARE_SUBSYS (MAIN, LOG_INFO); make copy aisexec to /usr/sbin and do /etc/init.d/cman start - with success: [EMAIL PROTECTED]:~# /etc/init.d/cman start Starting cluster manager: Loading kernel modules: done Mounting config filesystem: done Starting cluster configuration system:[ccsd.c:320] Entering parse_cli_args [ccsd.c:494] Exiting parse_cli_args [ccsd.c:705] Entering daemonize [ccsd.c:713] Entering daemon mode. [ccsd.c:623] Entering parent_exit_handler [ccsd.c:625] Exiting parent_exit_handler done Joining cluster:[libccs.c:319] Entering ccs_connect [libccs.c:235] Entering do_request [libccs.c:186] Entering setup_interface [libccs.c:140] Entering setup_interface_local [libccs.c:157] Exiting setup_interface_local [libccs.c:215] Exiting setup_interface [libccs.c:254] Protocol set to Local Domain. [libccs.c:298] Exiting do_request [libccs.c:356] Exiting ccs_connect [libccs.c:409] Entering ccs_disconnect [libccs.c:235] Entering do_request [libccs.c:186] Entering setup_interface [libccs.c:140] Entering setup_interface_local [libccs.c:157] Exiting setup_interface_local [libccs.c:215] Exiting setup_interface [libccs.c:298] Exiting do_request [libccs.c:428] Exiting ccs_disconnect Sehen wir das? argv[0]. aisexec envp[0]. OPENAIS_DEFAULT_CONFIG_IFACE=cmanconfig envp[1]. CMAN_PIPE=4 hier sind wir: done Starting daemons: groupd fenced dlm_controld gfs_controld Joining fence domain: done Starting Quorum Disk daemon: done [EMAIL PROTECTED]:~# cman_tool status Version: 6.1.0 Config Version: 17 Cluster Name: hardy Cluster Id: 3217 Cluster Member: Yes Cluster Generation: 64 Membership state: Cluster-Member Nodes: 1 Expected votes: 1 Total votes: 1 Quorum: 1 Active subsystems: 7 Flags: 2node Dirty Ports Bound: 0 Node name: hagbard Node ID: 1 Multicast addresses: 225.0.0.11 Node addresses: 10.165.166.12 ** Changed in: openais (Ubuntu) Status: New = Confirmed -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 +++--- ii openais 0.82-0ubuntu6Standards-based cluster framework (daemon and modules) ii redhat-cluster-suite 2.20071022-0ubuntu1 red hat cluster suite (meta package) -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 daemon didn't start This is after a fresh install of the redhat-cluster-suite from the original Ubuntu archive. ** Attachment added: cman startup - syslog http://launchpadlibrarian.net/10215664/syslog -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
** 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 /etc/defaults/opeanis to NOT start openais at boot and run only cman. 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, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 openais itself): /etc/init.d/openais stop /etc/init.d/cman start -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 options, but with a change gcc optimization configuration: -O0 instead of -O3. After the installation of the build packages sudo dpkg -i libopenais2_0.81-0ubuntu5_amd64.deb openais_0.81-0ubuntu5_amd64.deb, the /etc/init.d/cman start works without errors. I try this on an amd64 machine and on Xen with as x86_64 Gutsy Guest (installed via netinstaller). ** Attachment added: strace -f -o cman_tool_join-64.trace cman_tool -w -t 20 join http://launchpadlibrarian.net/9718971/cman_tool_join-64.trace.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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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}, {0x407320, [SEGV], SA_RESTORER|SA_RESTART
, 0x2b2da7e127d0}, 8) = 0
7335 tgkill(7335, 7335, SIGSEGV) = 0
7335 rt_sigreturn(0x1ca7) = 140733246875952
7335 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
7336 ... poll resumed 0, 0, -1) = -1 EINTR (Interrupted system call)
7333 ... select resumed )= 1 (in [3], left {0, 764000})
7336 +++ killed by SIGSEGV (core dumped) +++
created with strace -f -o /tmp/trace cman_tool -w -t 30 join. There are no
more aisexec in
futex_wait, but also no cluster infrastructure. Example start sh -x
/etc/init.d/cman start
+ echo -n Starting cluster configuration system:
Starting cluster configuration system:+ start-stop-daemon --start --quiet
--pidfile /var/run/cluster/ccsd.pid --exec /usr/sbin/ccsd --
+ sleep 1
+ echo done
done
+ echo -n Joining cluster:
Joining cluster:+ cman_tool -t 120 -w join
cman_tool: aisexec daemon didn't start
Versions:
[EMAIL PROTECTED]:~# dpkg -l redhat-cluster-suite openais
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-f/Unpacked/Failed-cfg/Half-inst/t-aWait/T-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii openais0.81-0ubuntu5 standards-based cluster framework (daemon an
ii redhat-cluster 2.20070823.1-0 red hat cluster suite (meta package)
--
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 for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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) Sourcepackagename: cman = redhat-cluster-suite -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 https://bugs.launchpad.net/bugs/139062 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: 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 notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 cman_tool -w -t 10 join increases the count of aisexec processes, example: [EMAIL PROTECTED]:~# ps axlw | egrep 'aise|ccsd' 1 0 3627 1 15 0 26392 1160 - Ssl ? 0:00 /usr/sbin/ccsd 1 0 3640 1 16 0 23956 1012 futex_ Sl ? 0:00 aisexec 1 0 6243 1 15 0 23960 1016 futex_ Sl ? 0:00 aisexec 1 0 6249 1 15 0 23956 1012 futex_ Sl ? 0:00 aisexec 1 0 6256 1 15 0 23956 1012 futex_ Sl ? 0:00 aisexec A Feisty system in normal cluster operation shows: [EMAIL PROTECTED]:~# ps axlw | egrep 'aise|ccs' 1 0 4452 1 15 0 24628 1552 - Ssl ? 3:12 /usr/sbin/ccsd 5 0 4457 1 -100 - 68520 27168 620133 SLl ? 0:11 aisexec -- 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 for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
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 this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
** 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 notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 139062] Re: Gutsy Tribe5: Startup reports: cman_tool: aisexec daemon didn't start
** 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 Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
