Hi,
Did this ever get resolved. I have almost the exact same issue:
Dec 14 15:57:13 elk-esnode03 systemd[1]: elasticsearch-es01.service: main process exited, code=killed, status=6/ABRT
Dec 14 15:57:13 elk-esnode03 systemd[1]: Unit elasticsearch-es01.service entered failed state.
This too is a puppet setup box but it does not control the Elasticsearch setup.
I am also getting the same NotSerializableExceptionWrapper error on my logs:
[2015-12-15 10:24:55,852][DEBUG][action.admin.cluster.node.info] [elk-esnode03-b] failed to execute on node [hSQKljERQdWucsEMCL-p8g]
RemoteTransportException[[elk-esnode01-a][10.218.38.120:9300][cluster:monitor/nodes/info[n]]]; nested: NotSerializableExceptionWrapper;
Caused by: NotSerializableExceptionWrapper[null]
This is Elasticsearch 2.1.0 with same versions of shield and marvel-agent.
In my elasticsearch.yaml i have:
shield.transport.filter.allow: "10.218.38.0/24"
to allow intercluster transport communication but it seems strange that all the errors in my logs are transport connections and only with the action.admin.cluster.node.info action.
Thanks.