Link on #3 is dead now.
http://logstash.openstack.org/#dashboard/file/logstash.json?query=message%3A%5C%22pstree%5C%22%20AND%20message%3A%5C%22segfault%5C%22
shows several messages such as:
pstree[8267]: segfault at 0 ip 00007f93355b4264 sp 00007ffceaaf6370 error 4 in libc-2.23.so[7f9335547000+1bf000]
The OS is ubuntu xenial and it might be possible to find the offending libc function from ip. IMO, pstree segfaulting is no good.
Link on #3 is dead now.
http:// logstash. openstack. org/#dashboard/ file/logstash. json?query= message% 3A%5C%22pstree% 5C%22%20AND% 20message% 3A%5C%22segfaul t%5C%22
shows several messages such as:
pstree[8267]: segfault at 0 ip 00007f93355b4264 sp 00007ffceaaf6370 error 4 in libc-2. 23.so[7f9335547 000+1bf000]
The OS is ubuntu xenial and it might be possible to find the offending libc function from ip.
IMO, pstree segfaulting is no good.