[Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
Hello Andrew et al,
few days ago, I asked about pacemaker + corosync + clvmd etc. With Your advice,
I got this working well.
It was in testing virtual machines, I'm now trying to install similar setup on
raw hardware but for some
reasong attrd and cib seem to be crashing.
here's snippet from corosync log:
Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync Cluster Engine
('1.1.2'): started and ready to provide service.
Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync built-in features:
nss rdma
Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Successfully read main
configuration file '/etc/corosync/corosync.conf'.
Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing transport
(UDP/IP).
Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing transmit/receive
security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Compatibility mode set to
whitetank. Using V1 and V2 of the synchronization engine.
Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] The network interface
[10.58.0.1] is now up.
Nov 10 14:12:21 vbox3 corosync[4299]: [pcmk ] info: process_ais_conf:
Reading configure
Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync Cluster Engine
('1.1.2'): started and ready to provide service.
Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync built-in features:
nss rdma
Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Successfully read main
configuration file '/etc/corosync/corosync.conf'.
Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing transport
(UDP/IP).
Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing transmit/receive
security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Compatibility mode set to
whitetank. Using V1 and V2 of the synchronization engine.
Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] The network interface
[10.58.0.1] is now up.
Nov 10 14:13:16 vbox3 corosync[4348]: [pcmk ] info: process_ais_conf:
Reading configure
Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync Cluster Engine
('1.1.2'): started and ready to provide service.
Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync built-in features:
nss rdma
Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Successfully read main
configuration file '/etc/corosync/corosync.conf'.
Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing transport
(UDP/IP).
Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing transmit/receive
security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Compatibility mode set to
whitetank. Using V1 and V2 of the synchronization engine.
Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] The network interface
[10.58.0.1] is now up.
Nov 10 14:13:24 vbox3 corosync[4357]: [pcmk ] info: process_ais_conf:
Reading configure
Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync Cluster Engine
('1.1.2'): started and ready to provide service.
Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync built-in features:
nss rdma
Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Successfully read main
configuration file '/etc/corosync/corosync.conf'.
Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing transport
(UDP/IP).
Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing transmit/receive
security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Compatibility mode set to
whitetank. Using V1 and V2 of the synchronization engine.
Nov 10 14:13:58 vbox3 corosync[4380]: [TOTEM ] The network interface
[10.58.0.1] is now up.
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: process_ais_conf:
Reading configure
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_init: Local
handle: 9213452461992312833 for logging
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_next:
Processing additional logging options...
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt: Found
'off' for option: debug
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt:
Defaulting to 'off' for option: to_file
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt:
Defaulting to 'daemon' for option: syslog_facility
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_init: Local
handle: 2013064636357672962 for service
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_next:
Processing additional service options...
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt:
Defaulting to 'no' for option: use_logd
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt: Found
'no' for option: use_mgmtd
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: pcmk_startup: CRM:
Initialized
Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] Logging: Initialized
pcmk_startup
Nov 10 14:13:58 vbox3
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
On Tue, November 10, 2009 10:28 am, Nikola Ciprich wrote: > Nov 10 14:13:59 vbox3 cib: [4391]: WARN: retrieveCib: Cluster > configuration not found: /var/lib/heartbeat/crm/cib.xml Nov 10 14:13:59 > vbox3 cib: [4391]: WARN: readCibXmlFile: Primary configuration corrupt or > unusable, trying backup... Nov 10 14:13:59 vbox3 cib: [4391]: WARN: > readCibXmlFile: Continuing with an empty configuration. > Nov 10 14:13:59 vbox3 cib: [4391]: info: startCib: CIB Initialization > completed successfully Nov 10 14:13:59 vbox3 cib: [4391]: info: I think cib is stopping not crashing. Can you check permissions of /var/lib/heartbeat/crm and also if it belongs to the hacluster user etc? Rasto -- : Dipl-Ing Rastislav Levrinc : DRBD-MC http://www.drbd.org/mc/management-console/ : DRBD/HA support and consulting http://www.linbit.com/ DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria. ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
nope, it really is crashing, it's visible in log: Nov 10 14:13:58 vbox3 stonithd: [4384]: info: G_main_add_SignalHandler: Added signal handler for signal 17 Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process cib terminated with signal 11 (pid=4385, +core=false) Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] notice: pcmk_wait_dispatch: Respawning failed child process: cib Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] info: spawn_child: Forked child 4391 for process cib Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] ERROR: pcmk_wait_dispatch: Child process attrd terminated with signal 11 (pid=4387, +core=false) Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] notice: pcmk_wait_dispatch: Respawning failed child process: attrd I've checked permissions already, and it seems OK to me (hacluster:haclient, 750) On Tue, Nov 10, 2009 at 11:37:31AM +0100, Rasto Levrinc wrote: > > On Tue, November 10, 2009 10:28 am, Nikola Ciprich wrote: > > > Nov 10 14:13:59 vbox3 cib: [4391]: WARN: retrieveCib: Cluster > > configuration not found: /var/lib/heartbeat/crm/cib.xml Nov 10 14:13:59 > > vbox3 cib: [4391]: WARN: readCibXmlFile: Primary configuration corrupt or > > unusable, trying backup... Nov 10 14:13:59 vbox3 cib: [4391]: WARN: > > readCibXmlFile: Continuing with an empty configuration. > > Nov 10 14:13:59 vbox3 cib: [4391]: info: startCib: CIB Initialization > > completed successfully Nov 10 14:13:59 vbox3 cib: [4391]: info: > > I think cib is stopping not crashing. Can you check permissions of > /var/lib/heartbeat/crm and also if it belongs to the hacluster user etc? > > Rasto > > -- > : Dipl-Ing Rastislav Levrinc > : DRBD-MC http://www.drbd.org/mc/management-console/ > : DRBD/HA support and consulting http://www.linbit.com/ > DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria. > > > > ___ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > -- - Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax:+420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: ser...@linuxbox.cz - ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
On Tue, November 10, 2009 11:54 am, Nikola Ciprich wrote: > nope, it really is crashing, it's visible in log: Nov 10 14:13:58 vbox3 > stonithd: [4384]: info: G_main_add_SignalHandler: Added signal handler > for signal 17 Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] ERROR: > pcmk_wait_dispatch: Child process cib terminated with signal 11 > (pid=4385, > +core=false) > Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] notice: > pcmk_wait_dispatch: Respawning failed child process: cib > Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] info: spawn_child: Forked > child 4391 for process cib Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk > ] ERROR: pcmk_wait_dispatch: Child process attrd terminated with signal > 11 (pid=4387, > +core=false) > Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] notice: > pcmk_wait_dispatch: Respawning failed child process: attrd > > > I've checked permissions already, and it seems OK to me > (hacluster:haclient, 750) > Oops, sorry. It looks like they died while connecting to the corosync. What distro do you have? Rasto -- : Dipl-Ing Rastislav Levrinc : DRBD-MC http://www.drbd.org/mc/management-console/ : DRBD/HA support and consulting http://www.linbit.com/ DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria. ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
Hi, On Tue, Nov 10, 2009 at 12:47:50PM +0100, Rasto Levrinc wrote: > > On Tue, November 10, 2009 11:54 am, Nikola Ciprich wrote: > > nope, it really is crashing, it's visible in log: Nov 10 14:13:58 vbox3 > > stonithd: [4384]: info: G_main_add_SignalHandler: Added signal handler > > for signal 17 Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] ERROR: > > pcmk_wait_dispatch: Child process cib terminated with signal 11 > > (pid=4385, > > +core=false) > > Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] notice: > > pcmk_wait_dispatch: Respawning failed child process: cib > > Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] info: spawn_child: Forked > > child 4391 for process cib Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk > > ] ERROR: pcmk_wait_dispatch: Child process attrd terminated with signal > > 11 (pid=4387, > > +core=false) > > Nov 10 14:13:59 vbox3 corosync[4380]: [pcmk ] notice: > > pcmk_wait_dispatch: Respawning failed child process: attrd > > > > > > I've checked permissions already, and it seems OK to me > > (hacluster:haclient, 750) > > > > Oops, sorry. It looks like they died while connecting to the corosync. > What distro do you have? Probably best to enable coredumps and to post the output of gdb. Thanks, Dejan > > Rasto > > -- > : Dipl-Ing Rastislav Levrinc > : DRBD-MC http://www.drbd.org/mc/management-console/ > : DRBD/HA support and consulting http://www.linbit.com/ > DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria. > > > > ___ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
Nikola,
Sorry, I don't have a solution, but I'm curious about your setup.
Which version of DLM are you using? Did you have to compile it
yourself?
Regards,
Mark
On Tue, Nov 10, 2009 at 7:28 AM, Nikola Ciprich wrote:
> Hello Andrew et al,
> few days ago, I asked about pacemaker + corosync + clvmd etc. With Your
> advice, I got this working well.
> It was in testing virtual machines, I'm now trying to install similar setup
> on raw hardware but for some
> reasong attrd and cib seem to be crashing.
>
> here's snippet from corosync log:
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:12:21 vbox3 corosync[4299]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:13:16 vbox3 corosync[4348]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:13:24 vbox3 corosync[4357]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:13:58 vbox3 corosync[4380]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_init:
> Local handle: 9213452461992312833 for logging
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_next:
> Processing additional logging options...
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt: Found
> 'off' for option: debug
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt:
> Defaulting to 'off' for option: to_file
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt:
> Defaulting to 'daemon' for option: syslog_facility
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_init:
> Local handle: 2013064636357672962 for service
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_next:
> Processing additional service options...
> Nov 10 14:13:58 v
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
One possibility is selinux is enabled and your selinux policies are out
dated.
Another possibility is you have improper coroipcc libraries (duplicates)
installed on your system.
Check your installed lib dir for coroipcc.so.4 and 4.0.0 and
coroipcc.so. They should all link to the same file.
Another possibility is your compiling on a libc which does not support
posix semaphores.
Could you explain more of your platform?
regards
-steve
On Tue, 2009-11-10 at 21:48 -0200, Mark Horton wrote:
> Nikola,
> Sorry, I don't have a solution, but I'm curious about your setup.
> Which version of DLM are you using? Did you have to compile it
> yourself?
>
> Regards,
> Mark
>
> On Tue, Nov 10, 2009 at 7:28 AM, Nikola Ciprich
> wrote:
> > Hello Andrew et al,
> > few days ago, I asked about pacemaker + corosync + clvmd etc. With Your
> > advice, I got this working well.
> > It was in testing virtual machines, I'm now trying to install similar setup
> > on raw hardware but for some
> > reasong attrd and cib seem to be crashing.
> >
> > here's snippet from corosync log:
> > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync Cluster Engine
> > ('1.1.2'): started and ready to provide service.
> > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync built-in
> > features: nss rdma
> > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Successfully read main
> > configuration file '/etc/corosync/corosync.conf'.
> > Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing transport
> > (UDP/IP).
> > Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing
> > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Compatibility mode set to
> > whitetank. Using V1 and V2 of the synchronization engine.
> > Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] The network interface
> > [10.58.0.1] is now up.
> > Nov 10 14:12:21 vbox3 corosync[4299]: [pcmk ] info: process_ais_conf:
> > Reading configure
> > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync Cluster Engine
> > ('1.1.2'): started and ready to provide service.
> > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync built-in
> > features: nss rdma
> > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Successfully read main
> > configuration file '/etc/corosync/corosync.conf'.
> > Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing transport
> > (UDP/IP).
> > Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing
> > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Compatibility mode set to
> > whitetank. Using V1 and V2 of the synchronization engine.
> > Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] The network interface
> > [10.58.0.1] is now up.
> > Nov 10 14:13:16 vbox3 corosync[4348]: [pcmk ] info: process_ais_conf:
> > Reading configure
> > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync Cluster Engine
> > ('1.1.2'): started and ready to provide service.
> > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync built-in
> > features: nss rdma
> > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Successfully read main
> > configuration file '/etc/corosync/corosync.conf'.
> > Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing transport
> > (UDP/IP).
> > Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing
> > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Compatibility mode set to
> > whitetank. Using V1 and V2 of the synchronization engine.
> > Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] The network interface
> > [10.58.0.1] is now up.
> > Nov 10 14:13:24 vbox3 corosync[4357]: [pcmk ] info: process_ais_conf:
> > Reading configure
> > Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync Cluster Engine
> > ('1.1.2'): started and ready to provide service.
> > Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync built-in
> > features: nss rdma
> > Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Successfully read main
> > configuration file '/etc/corosync/corosync.conf'.
> > Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing transport
> > (UDP/IP).
> > Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing
> > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> > Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Compatibility mode set to
> > whitetank. Using V1 and V2 of the synchronization engine.
> > Nov 10 14:13:58 vbox3 corosync[4380]: [TOTEM ] The network interface
> > [10.58.0.1] is now up.
> > Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: process_ais_conf:
> > Reading configure
> > Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_init:
> > Local handle: 9213452461992312833 for logging
> > Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: confi
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
Nikola,
yet another possibility is your box doesn't have any/enough shared
memory available. Usually this is in the directory /dev/shm.
Unfortunately bad things happen and error handling around this condition
needs some work. Its hard to tell because the signal delivered to the
application on failure is not shown in your backtrace.
For example I have plenty of shared memory available (command is from
df).
tmpfs 1027020 3560 1023460 1% /dev/shm
Regards
-steve
On Tue, 2009-11-10 at 10:28 +0100, Nikola Ciprich wrote:
> Hello Andrew et al,
> few days ago, I asked about pacemaker + corosync + clvmd etc. With Your
> advice, I got this working well.
> It was in testing virtual machines, I'm now trying to install similar setup
> on raw hardware but for some
> reasong attrd and cib seem to be crashing.
>
> here's snippet from corosync log:
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:12:21 vbox3 corosync[4299]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:13:16 vbox3 corosync[4348]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:13:24 vbox3 corosync[4357]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync Cluster Engine
> ('1.1.2'): started and ready to provide service.
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync built-in features:
> nss rdma
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Successfully read main
> configuration file '/etc/corosync/corosync.conf'.
> Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing transport
> (UDP/IP).
> Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing
> transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Compatibility mode set to
> whitetank. Using V1 and V2 of the synchronization engine.
> Nov 10 14:13:58 vbox3 corosync[4380]: [TOTEM ] The network interface
> [10.58.0.1] is now up.
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: process_ais_conf:
> Reading configure
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_init:
> Local handle: 9213452461992312833 for logging
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: config_find_next:
> Processing additional logging options...
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt: Found
> 'off' for option: debug
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info: get_config_opt:
> Defaulting to 'off' for option: to_file
> Nov 10 14:13:58 vbox3 corosync[4380]: [pcmk ] info:
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
> Probably best to enable coredumps and to post the output of gdb. Hi, well, but that's exactly what I did... It's all in first post ;-) regards nik > > Thanks, > > Dejan > > > > > Rasto > > > > -- > > : Dipl-Ing Rastislav Levrinc > > : DRBD-MC http://www.drbd.org/mc/management-console/ > > : DRBD/HA support and consulting http://www.linbit.com/ > > DRBD(R) and LINBIT(R) are registered trademarks of LINBIT, Austria. > > > > > > > > ___ > > Pacemaker mailing list > > Pacemaker@oss.clusterlabs.org > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > ___ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > -- - Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax:+420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: ser...@linuxbox.cz - ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
Hi Steve,
I'm running CentOS5 based x86_64 system, 2.6.31.6 kernel, selinux is disabled,
corosync libraries seem to be properly installed, and I've got big enough
/dev/shm
ramdisk. libc should be OK as well.
I just tried rebuilding all packages from scratch and the problem persists :(
regards
nik
On Tue, Nov 10, 2009 at 05:21:32PM -0700, Steven Dake wrote:
> One possibility is selinux is enabled and your selinux policies are out
> dated.
>
> Another possibility is you have improper coroipcc libraries (duplicates)
> installed on your system.
>
> Check your installed lib dir for coroipcc.so.4 and 4.0.0 and
> coroipcc.so. They should all link to the same file.
>
> Another possibility is your compiling on a libc which does not support
> posix semaphores.
>
> Could you explain more of your platform?
>
> regards
> -steve
>
> On Tue, 2009-11-10 at 21:48 -0200, Mark Horton wrote:
> > Nikola,
> > Sorry, I don't have a solution, but I'm curious about your setup.
> > Which version of DLM are you using? Did you have to compile it
> > yourself?
> >
> > Regards,
> > Mark
> >
> > On Tue, Nov 10, 2009 at 7:28 AM, Nikola Ciprich
> > wrote:
> > > Hello Andrew et al,
> > > few days ago, I asked about pacemaker + corosync + clvmd etc. With Your
> > > advice, I got this working well.
> > > It was in testing virtual machines, I'm now trying to install similar
> > > setup on raw hardware but for some
> > > reasong attrd and cib seem to be crashing.
> > >
> > > here's snippet from corosync log:
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync Cluster Engine
> > > ('1.1.2'): started and ready to provide service.
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Corosync built-in
> > > features: nss rdma
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Successfully read main
> > > configuration file '/etc/corosync/corosync.conf'.
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing transport
> > > (UDP/IP).
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] Initializing
> > > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [MAIN ] Compatibility mode set
> > > to whitetank. Using V1 and V2 of the synchronization engine.
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [TOTEM ] The network interface
> > > [10.58.0.1] is now up.
> > > Nov 10 14:12:21 vbox3 corosync[4299]: [pcmk ] info: process_ais_conf:
> > > Reading configure
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync Cluster Engine
> > > ('1.1.2'): started and ready to provide service.
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Corosync built-in
> > > features: nss rdma
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Successfully read main
> > > configuration file '/etc/corosync/corosync.conf'.
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing transport
> > > (UDP/IP).
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] Initializing
> > > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [MAIN ] Compatibility mode set
> > > to whitetank. Using V1 and V2 of the synchronization engine.
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [TOTEM ] The network interface
> > > [10.58.0.1] is now up.
> > > Nov 10 14:13:16 vbox3 corosync[4348]: [pcmk ] info: process_ais_conf:
> > > Reading configure
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync Cluster Engine
> > > ('1.1.2'): started and ready to provide service.
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Corosync built-in
> > > features: nss rdma
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Successfully read main
> > > configuration file '/etc/corosync/corosync.conf'.
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing transport
> > > (UDP/IP).
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] Initializing
> > > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [MAIN ] Compatibility mode set
> > > to whitetank. Using V1 and V2 of the synchronization engine.
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [TOTEM ] The network interface
> > > [10.58.0.1] is now up.
> > > Nov 10 14:13:24 vbox3 corosync[4357]: [pcmk ] info: process_ais_conf:
> > > Reading configure
> > > Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync Cluster Engine
> > > ('1.1.2'): started and ready to provide service.
> > > Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Corosync built-in
> > > features: nss rdma
> > > Nov 10 14:13:57 vbox3 corosync[4380]: [MAIN ] Successfully read main
> > > configuration file '/etc/corosync/corosync.conf'.
> > > Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing transport
> > > (UDP/IP).
> > > Nov 10 14:13:57 vbox3 corosync[4380]: [TOTEM ] Initializing
> > > transmit/receive security: libtomcrypt SOBER128/SHA1HMAC
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
On Tue, Nov 10, 2009 at 10:28 AM, Nikola Ciprich wrote: > Hello Andrew et al, > few days ago, I asked about pacemaker + corosync + clvmd etc. With Your > advice, I got this working well. > It was in testing virtual machines, I'm now trying to install similar setup > on raw hardware but for some > reasong attrd and cib seem to be crashing. Can we see your corosync.conf ? (Oh, and please use attachments for log files) ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
Hi,
sure, here it is. I also tried setting compatibility to none, but it did't help.
cheers
n.
On Mon, Nov 16, 2009 at 03:08:23PM +0100, Andrew Beekhof wrote:
> On Tue, Nov 10, 2009 at 10:28 AM, Nikola Ciprich
> wrote:
> > Hello Andrew et al,
> > few days ago, I asked about pacemaker + corosync + clvmd etc. With Your
> > advice, I got this working well.
> > It was in testing virtual machines, I'm now trying to install similar setup
> > on raw hardware but for some
> > reasong attrd and cib seem to be crashing.
>
> Can we see your corosync.conf ?
> (Oh, and please use attachments for log files)
>
> ___
> Pacemaker mailing list
> Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
--
-
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax:+420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: ser...@linuxbox.cz
-
# Please read the corosync.conf.5 manual page
compatibility: none
totem {
version: 2
secauth: off
threads: 0
interface {
ringnumber: 0
bindnetaddr: 10.58.0.0
mcastaddr: 226.94.1.1
mcastport: 5405
}
}
logging {
fileline: off
to_stderr: yes
to_logfile: yes
to_syslog: yes
logfile: /tmp/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: AMF
debug: off
}
}
amf {
mode: disabled
}
service {
# Load the Pacemaker Cluster Resource Manager
ver: 0
name: pacemaker
use_mgmtd: no
}
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
On Wed, Nov 18, 2009 at 8:22 AM, Nikola Ciprich wrote: > Hi, > sure, here it is. I also tried setting compatibility to none, but it did't > help. > cheers > n. I had a feeling that might be the problem. You skipped a step :-) Check out example D.3 of http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-install-enable.html#s-install-enable-ais and the text that follows it ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
Hi, well, I'm a bit confused now :) I have identical configuration working on my testing virtual machines, so it doesn't seem to be problem there. Furthermore, corosync.conf manpage doesn't mention any directives for setting user/group and "aisexec" directive is not mentioned there either. I tried it anyways, but it didn't help :( Is this really needed for corosync based cluster? n. On Wed, Nov 18, 2009 at 08:40:32AM +0100, Andrew Beekhof wrote: > On Wed, Nov 18, 2009 at 8:22 AM, Nikola Ciprich > wrote: > > Hi, > > sure, here it is. I also tried setting compatibility to none, but it did't > > help. > > cheers > > n. > > > I had a feeling that might be the problem. > You skipped a step :-) > > Check out example D.3 of > http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-install-enable.html#s-install-enable-ais > and the text that follows it > > ___ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > -- - Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax:+420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: ser...@linuxbox.cz - ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
On Wed, Nov 18, 2009 at 9:16 AM, Nikola Ciprich wrote: > Hi, > well, I'm a bit confused now :) > I have identical configuration working on my testing virtual machines, so it > doesn't seem to be problem there. Furthermore, corosync.conf manpage doesn't > mention any directives for setting user/group and "aisexec" directive is not > mentioned there either. > I tried it anyways, but it didn't help :( > Is this really needed for corosync based cluster? Its needed for if you're running pacemaker on top. > n. > > On Wed, Nov 18, 2009 at 08:40:32AM +0100, Andrew Beekhof wrote: >> On Wed, Nov 18, 2009 at 8:22 AM, Nikola Ciprich >> wrote: >> > Hi, >> > sure, here it is. I also tried setting compatibility to none, but it did't >> > help. >> > cheers >> > n. >> >> >> I had a feeling that might be the problem. >> You skipped a step :-) >> >> Check out example D.3 of >> http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-install-enable.html#s-install-enable-ais >> and the text that follows it >> >> ___ >> Pacemaker mailing list >> Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> > > -- > - > Nikola CIPRICH > LinuxBox.cz, s.r.o. > 28. rijna 168, 709 01 Ostrava > > tel.: +420 596 603 142 > fax: +420 596 621 273 > mobil: +420 777 093 799 > www.linuxbox.cz > > mobil servis: +420 737 238 656 > email servis: ser...@linuxbox.cz > - > > ___ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync 1.1.2 crashing
On Nov 18, 2009, at 10:32 AM, Nikola Ciprich wrote:
ok, but then how do I set it for corosync?
just adding
aisexec {
user: root
group: root
}
The above is what I have.
if you run:
ps axfu | grep coro
do you get something like this:
root 29024 0.3 0.1 465000 4348 ?Ssl 11:04 0:00 /
usr/sbin/corosync
or
corosync {
user: root
group: root
}
to my corosync.conf didn't help and there's no mention about setting
user/group in corosync documentation. I'm sorry if I'm too anoying,
I coudn't find any information about the topic anywhere :(
On Wed, Nov 18, 2009 at 10:02:14AM +0100, Andrew Beekhof wrote:
Its needed for if you're running pacemaker on top.
n.
On Wed, Nov 18, 2009 at 08:40:32AM +0100, Andrew Beekhof wrote:
On Wed, Nov 18, 2009 at 8:22 AM, Nikola Ciprich > wrote:
Hi,
sure, here it is. I also tried setting compatibility to none,
but it did't help.
cheers
n.
I had a feeling that might be the problem.
You skipped a step :-)
Check out example D.3 of
http://clusterlabs.org/doc/en-US/Pacemaker/1.0/html/Pacemaker_Explained/s-install-enable.html#s-install-enable-ais
and the text that follows it
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
--
-
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax:+420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: ser...@linuxbox.cz
-
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
--
-
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava
tel.: +420 596 603 142
fax:+420 596 621 273
mobil: +420 777 093 799
www.linuxbox.cz
mobil servis: +420 737 238 656
email servis: ser...@linuxbox.cz
-
-- Andrew
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
[Pacemaker] pacemaker-1.0.6 + corosync-1.1.2 crashing - SOLVED
Hi Guys, Finally I've found where the problem was! On my testing machines, the system was lacking separate /dev/shm tmpfs mount. While the /dev directory is also mounted as tmpfs, so it seemingly doesn't make any difference, there IS one: /dev is mounted with mode=755 parameter, while /dev/shm should be mounted without it. So after I mounted it, everything starts working like a charm! :) While it's certainly unusual that systems lack separate /dev/shm mount, it still might be mentioned in documentation. anyways, thanks to all of You for Your time. have a nice day. nik -- - Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax:+420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: ser...@linuxbox.cz - ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Re: [Pacemaker] pacemaker-1.0.6 + corosync-1.1.2 crashing - SOLVED
On Sat, 2009-11-21 at 20:00 +0100, Nikola Ciprich wrote: > Hi Guys, > Finally I've found where the problem was! On my testing machines, > the system was lacking separate /dev/shm tmpfs mount. While the /dev > directory is also mounted as tmpfs, so it seemingly doesn't make any > difference, there IS one: /dev is mounted with mode=755 parameter, > while /dev/shm should be mounted without it. So after I mounted it, > everything starts working like a charm! :) > While it's certainly unusual that systems lack separate /dev/shm > mount, > it still might be mentioned in documentation. > anyways, thanks to all of You for Your time. > have a nice day. > nik thanks for the bug report. corosync should use /var/lib/corosync if /dev/shm is unavailable. This is also what the code does. Probably needs a bit of testing around that case. Regards -steve ___ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
