# xinet.d crashes on cluster nodes

**URL:** <https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [March 14, 2014, 8:38am UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337 "2014-03-14T08:38:46Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![mandm](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@mandm](https://forums.percona.com/u/mandm)\
**Post date:** [March 14, 2014, 8:38am UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337/1 "2014-03-14T08:38:46Z")

</div>

I am running 3 node cluster on ubuntu 12.04 and recently i observed the xinetd process (which is a mechanism for cluster check to know if that node is active) crashes without much error in the syslog

has anyone faced this issue?

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [March 14, 2014, 9:31am UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337/2 "2014-03-14T09:31:55Z")

</div>

Can you paste what is exactly the message when xinetd dies? Also, is this a standard clustercheck script? Does it work when called manually?

---

<div class="post-metadata">

**Author:** ![mandm](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@mandm](https://forums.percona.com/u/mandm)\
**Post date:** [March 14, 2014, 10:47am UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337/3 "2014-03-14T10:47:41Z")

</div>

the error in the syslog file is

Mar 14 06:42:33 db-cluster1-node1 xinetd[2527]: Exiting…

similar on all the nodes

yes i am using the standard cluster check script along with and yes it works if i call it manually and that throws me off too…

---

<div class="post-metadata">

**Author:** ![KausitcRage](https://avatars.discourse-cdn.com/v4/letter/k/e480ec/32.png) [@KausitcRage](https://forums.percona.com/u/KausitcRage)\
**Post date:** [March 19, 2014, 9:21pm UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337/4 "2014-03-19T21:21:21Z")

</div>

mandm,

I am seeing the exact same activity on a cluster I built. What is weird is that on my home lab, I dont see the xinetd process restart itself. I am not even seeing any errors being logged. My cluster is setup on CentOS 6.5 all virtual machines.

---

<div class="post-metadata">

**Author:** ![mandm](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@mandm](https://forums.percona.com/u/mandm)\
**Post date:** [March 28, 2014, 3:37pm UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337/5 "2014-03-28T15:37:57Z")

</div>

It happened again today on my cluster where 2 nodes had their xinet.d process crash…any guidance here?

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [April 23, 2014, 3:05am UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337/6 "2014-04-23T03:05:23Z")

</div>

Is your xinetd enabled on system startup? The /etc/services, port 9200 is properly named? Any chance the service was just restarted by package update, automation software, etc?

---

<div class="post-metadata">

**Author:** ![mandm](https://avatars.discourse-cdn.com/v4/letter/m/ea5d25/32.png) [@mandm](https://forums.percona.com/u/mandm)\
**Post date:** [April 28, 2014, 3:30pm UTC](https://forums.percona.com/t/xinet-d-crashes-on-cluster-nodes/3337/7 "2014-04-28T15:30:19Z")

</div>

so these are the entries in the /etc/services file

xinetd 9098/tcp  
mysqlchk 9200/tcp # mysqlchk

even if the service is restarted it should have a log file ? the problem is there is a crash notice in the syslog for xinetd