Aerospike single node getting stop automatically

Hi I have installed aerospike server in the slave node of the ambari setup, server is getting started but its getting stop with out any reason, no clues found in the logs /var/log/aerospike/aerospike.log I was using below mesh configuration as the instance is AWS EC2, kindly help as it is a critical need

ubuntu@slave2:/etc/aerospike$ asinfo -v service
10.0.0.3:3000
ubuntu@slave2:/etc/aerospike$ asinfo -v services

ubuntu@slave2:/etc/aerospike$ asinfo -v  'get-config:context=network.heartbeat' -l
heartbeat-mode=mesh
heartbeat-protocol=v2
heartbeat-address=10.0.0.3:3000
heartbeat-port=3002
heartbeat-interval=150
heartbeat-timeout=20
ubuntu@slave2:/etc/aerospike$

network {
        service {
                address any
                port 3000
        }

    heartbeat { 
            mode mesh
            port 3002
            mesh-seed-address-port 10.0.0.3 3002
            # To use unicast-mesh heartbeats, remove the 3 lines above, and see
            # aerospike_mesh.conf for alternative.

            interval 150
            timeout 20
    }

    fabric {
            port 3001
    }

    info {
            port 3003
    }

}

Can you please paste last few lines in the log file before the server terminates ? And which version of the server are you using ?

– R