# Decommissioning a node **URL:** \ **Category:** Configuration\ **Created:** [January 23, 2017, 12:52am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786 "2017-01-23T00:52:50Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![AJVee](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJVee](https://discuss.aerospike.com/u/AJVee)\ **Post date:** [January 23, 2017, 12:52am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/1 "2017-01-23T00:52:50Z")
Hi, I have a 3 node cluster running on vagrant boxes all running on E 3.11.0.2 in mesh mode To decommission a node: 1. Stopped the node: SUCCESSFUL 2. Changed the config for the other 2 nodes to not include the stopped node in the mesh-seed-address-port list 3. Issued tip-clear on the other 2 nodes: SUCCESSFUL 4. Issued a service-alumni-reset on the other 2 nodes: SUCCESSFUL I am happy about restarting the 2 nodes already in the cluster to form a 2 node cluster but when I try to start the stopped node: I get the following error: > vagrant@vagrant-ubuntu-trusty-64:~$ sudo service aerospike start > > - Starting aerospike Jan 23 2017 00:38:40 GMT: FAILED ASSERTION (config): (cfg.c:1349) line 27 :: unknown config parameter name ‘mode’ Jan 23 2017 00:38:40 GMT: WARNING (as): (signal.c:153) SIGINT received, shutting down Jan 23 2017 00:38:40 GMT: WARNING (as): (signal.c:156) startup was not complete, exiting immediately The logs show this: > Jan 22 2017 23:58:42 GMT: INFO (as): (signal.c:193) SIGTERM received, starting normal shutdown Jan 22 2017 23:58:42 GMT: INFO (xdr): (xdr.c:5024) XDR is not running. Jan 22 2017 23:58:42 GMT: INFO (storage): (storage.c:797) initiating storage shutdown … Jan 22 2017 23:58:42 GMT: INFO (storage): (storage.c:808) flushing data to storage … Jan 22 2017 23:58:42 GMT: INFO (storage): (storage.c:825) completed flushing to storage Jan 22 2017 23:58:42 GMT: INFO (as): (as.c:546) finished clean shutdown - exiting please guide! Regards ---
**Author:** ![AJVee](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJVee](https://discuss.aerospike.com/u/AJVee)\ **Post date:** [January 23, 2017, 12:57am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/2 "2017-01-23T00:57:41Z")
okay found this [http://www.aerospike.com/docs/operations/troubleshoot/startup](http://www.aerospike.com/docs/operations/troubleshoot/startup) please allow me to get back Thanks ---
**Author:** ![AJVee](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJVee](https://discuss.aerospike.com/u/AJVee)\ **Post date:** [January 23, 2017, 1:02am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/3 "2017-01-23T01:02:00Z")
So any solution for this > [@Configuration documentation is a mess](https://discuss.aerospike.com/t/configuration-documentation-is-a-mess/3756): > > [http://www.aerospike.com/docs/operations/troubleshoot/startup](http://www.aerospike.com/docs/operations/troubleshoot/startup) network { service { ... node-id-interface p2p1 address any port 3000 } ... } \* Starting aerospike Jan 10 2017 15:08:47 GMT: FAILED ASSERTION (config): (cfg.c:1349) line 33 :: unknown config parameter name 'node-id-interface' Jan 10 2017 15:08:47 GMT: WARNING (as): (signal.c:153) SIGINT received, shutting down Jan 10 2017 15:08:47 GMT: WARNING (as): (sig… ---
**Author:** ![pgupta](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/pgupta/32/2351_2.png) [@pgupta](https://discuss.aerospike.com/u/pgupta)\ **Post date:** [January 23, 2017, 2:47am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/4 "2017-01-23T02:47:48Z")
> [@AJVee](#): > > unknown config parameter name ‘mode’ What does your config file look like? Editing error? ---
**Author:** ![AJVee](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJVee](https://discuss.aerospike.com/u/AJVee)\ **Post date:** [January 23, 2017, 2:50am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/5 "2017-01-23T02:50:45Z")
I don’t remember changing any thing > service { user root group root paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1. pidfile /var/run/aerospike/asd.pid service-threads 4 transaction-queues 4 transaction-threads-per-queue 4 proto-fd-max 15000 node-id-interface eth1 } > logging { # Log file must be an absolute path. file /var/log/aerospike/aerospike.log { context any info } } > network { service { address any access-address 172.31.99.128 port 3000 mode mesh port 3002 # Heartbeat port for this node. > ``` > # List one or more other nodes, one ip-address & port per line: > #mesh-seed-address-port 172.31.99.50 3002 > #mesh-seed-address-port 172.31.99.107 3002 > #mesh-seed-address-port 10.10.10.11 3002 > #mesh-seed-address-port 10.10.10.12 3002 > #mesh-seed-address-port 10.10.10.13 3002 > #mesh-seed-address-port 10.10.10.14 3002 > > ``` > ``` > interval 250 > timeout 10 > } > > ``` ---
**Author:** ![AJVee](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJVee](https://discuss.aerospike.com/u/AJVee)\ **Post date:** [January 23, 2017, 2:53am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/6 "2017-01-23T02:53:53Z")
172.31.99.50 3002 172.31.99.107 3002 are the 2 nodes that are still part of the cluster. ---
**Author:** ![pgupta](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/pgupta/32/2351_2.png) [@pgupta](https://discuss.aerospike.com/u/pgupta)\ **Post date:** [January 23, 2017, 2:56am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/7 "2017-01-23T02:56:51Z")
> [@AJVee](#): > > network { > service { > address any > access-address 172.31.99.128 > port 3000 > mode mesh > port 3002 # Heartbeat port for this node. # List one or more other nodes, one ip-address & port per line: #mesh-seed-address-port 172.31.99.50 3002 #mesh-seed-address-port 172.31.99.107 3002 #mesh-seed-address-port 10.10.10.11 3002 #mesh-seed-address-port 10.10.10.12 3002 #mesh-seed-address-port 10.10.10.13 3002 #mesh-seed-address-port 10.10.10.14 3002 > > ``` > interval 250 > timeout 10 > } > > ``` You are missing hearbeat context, assuming you cut and paste exactly what you have. network { service { address any port 3000 access-addres xxxxx } heartbeat { mode mesh … and so on. } fabric { port 3001 } info { port 3003 } } _service context does not have config parameter mode and that is what it is flagging_ ---
**Author:** ![AJVee](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AJVee](https://discuss.aerospike.com/u/AJVee)\ **Post date:** [January 23, 2017, 3:02am UTC](https://discuss.aerospike.com/t/decommissioning-a-node/3786/8 "2017-01-23T03:02:37Z")
oh yes how could I miss that 😮 thanks @pgupta