Details
-
Bug
-
Resolution: Fixed
-
Major
-
5.0.0
-
Untriaged
-
-
No
Description
Seeing "Service 'ns_server' exited with status 137" in centos longevity logs - Spock RC6 build - servers are healthy and rebalance succeeded without any issues - from .103:
connection_closed}]
|
2017-09-21T12:51:13.829-07:00, ns_node_disco:5:warning:node down(ns_1@172.23.99.21) - Node 'ns_1@172.23.99.21' saw that node 'ns_1@172.23.99.22' went down. Details: [{nodedown_reason,
|
connection_closed}]
|
2017-09-21T12:51:28.636-07:00, ns_log:0:info:message(ns_1@172.23.99.22) - Service 'ns_server' exited with status 137. Restarting. Messages:
|
working as port
|
32242: Booted. Waiting for shutdown request
|
working as port
|
working as port
|
2017-09-21T12:51:29.276-07:00, ns_cookie_manager:2:info:cookie update(ns_1@172.23.99.22) - Node 'ns_1@172.23.99.22' synchronized otp cookie {sanitized,
|
<<"6wmkQdduqsJyY12Ofys59YHF20RtPWkrfHOEogG1lkU=">>} from cluster
|
2017-09-21T12:51:29.314-07:00, ns_node_disco:4:info:node up(ns_1@172.23.106.188) - Node 'ns_1@172.23.106.188' saw that node 'ns_1@172.23.99.22' came up. Tag
|
