# XtraDB Cluster one node boot error: Segmentation fault

**URL:** https://forums.percona.com/t/xtradb-cluster-one-node-boot-error-segmentation-fault/1758
**Category:** Other MySQL® Questions
**Created:** [February 13, 2012, 4:58am UTC](https://forums.percona.com/t/xtradb-cluster-one-node-boot-error-segmentation-fault/1758 "2012-02-13T04:58:31Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![seagen](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@seagen](https://forums.percona.com/u/seagen)
#### Post date: [February 13, 2012, 4:58am UTC](https://forums.percona.com/t/xtradb-cluster-one-node-boot-error-segmentation-fault/1758/1 "2012-02-13T04:58:31Z")

</div>

Now I am testing XtraDB Cluster following the URL: [http://www.percona.com/doc/percona-xtradb-cluster/singlebox](http://www.percona.com/doc/percona-xtradb-cluster/singlebox). html

The first one node is working well.  
When I tried to start the second node,I met the above error mentioned: Segmentation fault. And I also logged the error information. Please see more as follow:  
++++++  
120213 18:03:11 [Note] WSREP: wsrep\_load(): loading provider library ‘/usr/local/xtradbcluster/lib/libgalera\_smm.so’  
120213 18:03:11 [Note] WSREP: wsrep\_load(): Galera 2.0beta(rXXXX) by Codership Oy \<[info&#64;codership.com](mailto:info&#64;codership.com)\> loaded succesfully.  
120213 18:03:11 [Note] WSREP: Reusing existing ‘/data/db/xtradbcluster2//galera.cache’.  
120213 18:03:11 [Note] WSREP: Passing config to GCS: gcache.dir = /data/db/xtradbcluster2/; gcache.keep\_pages\_size = 0; gcache.mem\_size = 0; gcache.name = /data/db/xtradbcluster2//galera.cache; gcache.page\_size = 128M; gcache.size = 128M; gcs.fc\_debug = 0; gcs.fc\_factor = 0.5; gcs.fc\_limit = 16; gcs.fc\_master\_slave = NO; gcs.max\_packet\_size = 64500; gcs.max\_throttle = 0.25; gcs.recv\_q\_hard\_limit = 9223372036854775807; gcs.recv\_q\_soft\_limit = 0.25; gmcast.listen\_addr = tcp://0.0.0.0:5010; replicator.commit\_order = 3  
120213 18:03:11 [Note] WSREP: wsrep\_sst\_grab()  
120213 18:03:11 [Note] WSREP: Start replication

120213 18:03:11 [Note] WSREP: Assign initial position for certification: -1, protocol version: -1  
120213 18:03:11 [Note] WSREP: Setting initial position to 00000000-0000-0000-0000-000000000000:-1  
120213 18:03:11 [Note] WSREP: protonet asio version 0  
120213 18:03:11 [Note] WSREP: backend: asio  
120213 18:03:11 [Note] WSREP: GMCast version 0  
120213 18:03:11 [Note] WSREP: (f00b117c-5629-11e1-0800-e389f3198479, ‘tcp://0.0.0.0:5010’) listening at tcp://0.0.0.0:5010  
120213 18:03:11 [Note] WSREP: (f00b117c-5629-11e1-0800-e389f3198479, ‘tcp://0.0.0.0:5010’) multicast: , ttl: 1  
120213 18:03:11 [Note] WSREP: EVS version 0  
120213 18:03:11 [Note] WSREP: PC version 0  
120213 18:03:11 [Note] WSREP: gcomm: connecting to group ‘trimethylxanthine’, peer ‘192.168.109.6:4010’

You could find that there is one warning prompting as above,which is highlighted by myself. I don’t why this file was not created by itself and why there is the additional slash behind the path /data/db/xtradbcluster2/.  
Finally back to my puzzle: what could result in “Segmentation fault”?

Thanks and Regards,  
Zhang

---

<div class="post-metadata">

### Author: ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)
#### Post date: [February 17, 2012, 3:48pm UTC](https://forums.percona.com/t/xtradb-cluster-one-node-boot-error-segmentation-fault/1758/2 "2012-02-17T15:48:37Z")

</div>

This might be two different problems. Please file a bug report on Launchpad and paste the URL here so other interested users can find it.

---

<div class="post-metadata">

### Author: ![seagen](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@seagen](https://forums.percona.com/u/seagen)
#### Post date: [February 18, 2012, 7:27am UTC](https://forums.percona.com/t/xtradb-cluster-one-node-boot-error-segmentation-fault/1758/3 "2012-02-18T07:27:19Z")

</div>

Thank you,Baron.  
I already reported a bug on the Launchpad. But I am not sure whether the issue I mentioned here is a real bug and before I got stuck on my process and configuration with more suspicion.
