# Missing OS statistics on data nodes **URL:** \ **Category:** Elasticsearch\ **Created:** [May 12, 2015, 8:28am UTC](https://discuss.elastic.co/t/missing-os-statistics-on-data-nodes/536 "2015-05-12T08:28:55Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Alexander\_Vassilevsk](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@Alexander\_Vassilevsk](https://discuss.elastic.co/u/Alexander_Vassilevsk)\ **Post date:** [May 12, 2015, 8:28am UTC](https://discuss.elastic.co/t/missing-os-statistics-on-data-nodes/536/1 "2015-05-12T08:28:56Z")
Hey guys, I'm sorry if this is a duplicate post - I did in fact do various searches in the group prior to writing this, but I'd be more than glad to use a URL if someone has already solved this exact problem. Here's a short description of the problem: I have a cluster with 5 data nodes ( all eligible masters, with minimum 3 ). I also have a no data no master node which I use for load balancing search and indexing requests ( its the REST endpoint ). The problem is that for data nodes 4 and 5 I am getting no OS statistics ( the ones provided by the sigar lib ). The only difference between nodes 1-3 and 4,5 are that the last two were installed via puppet. There are no significant ( meaning nothing more nothing less, just different values for IP's and hostnames) elasticsearch.yml config differences and I haven't set anything unique on the last two nodes via cluster permanent/transient, node or index settings. I have tried restarting both all the individual nodes one by one and the cluster as a whole and neither of these resolved the issue. I am willing to provide config files, program output, anything, etc, so that we can get this issue resolved - just let me know! The elasticsearch version I'm using on all the nodes is 1.5.0, java is oracle 1.7.0\_75. -Alex V ---
**Author:** ![nellicus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nellicus/32/51566_2.png) [@nellicus](https://discuss.elastic.co/u/nellicus)\ **Post date:** [May 12, 2015, 12:47pm UTC](https://discuss.elastic.co/t/missing-os-statistics-on-data-nodes/536/2 "2015-05-12T12:47:38Z")
can you check if any differences between kernel versions between the nodes? sigar is not supporting newest kernels. ---
**Author:** ![Alexander\_Vassilevsk](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@Alexander\_Vassilevsk](https://discuss.elastic.co/u/Alexander_Vassilevsk)\ **Post date:** [May 12, 2015, 12:55pm UTC](https://discuss.elastic.co/t/missing-os-statistics-on-data-nodes/536/3 "2015-05-12T12:55:15Z")
Actually, there are some differences between the kernel versions ( they are all CentOS 7 machines): On the working nodes, the kernel version is like this: ``` 3.10.0-123.20.1.el7.x86_64 ``` On the broken nodes, the kernel version is: ``` 3.10.0-123.el7.x86_64 ``` Can you point me to the source you are referring to? Is there a version of sigar lib jar which is immune to this problem? ---
**Author:** ![Alexander\_Vassilevsk](https://avatars.discourse-cdn.com/v4/letter/a/c37758/32.png) [@Alexander\_Vassilevsk](https://discuss.elastic.co/u/Alexander_Vassilevsk)\ **Post date:** [May 12, 2015, 1:18pm UTC](https://discuss.elastic.co/t/missing-os-statistics-on-data-nodes/536/4 "2015-05-12T13:18:24Z")
Actually - your post got me thinking and I saw this page: [https://support.hyperic.com/display/SIGAR/Home](https://support.hyperic.com/display/SIGAR/Home) After testing out: ``` [root@esdata-003 lib]# java -Djava.library.path='/usr/share/elasticsearch/lib/sigar/' -jar sigar/sigar-1.6.4.jar sigar> ``` on the working node and ``` [root@esdata-004 sigar]# java -Djava.library.path='/usr/share/elasticsearch/lib/sigar/' -jar sigar-1.6.4.jar no libsigar-amd64-linux.so in java.library.path org.hyperic.sigar.SigarException: no libsigar-amd64-linux.so in java.library.path at org.hyperic.sigar.Sigar.loadLibrary(Sigar.java:172) at org.hyperic.sigar.Sigar.(Sigar.java:100) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:191) at org.hyperic.sigar.SigarLoader.class$(SigarLoader.java:77) at org.hyperic.sigar.SigarLoader.getLocation(SigarLoader.java:77) at org.hyperic.sigar.cmd.Runner.main(Runner.java:176) java.lang.UnsatisfiedLinkError: org.hyperic.sigar.util.Getline.isatty()Z at org.hyperic.sigar.util.Getline.isatty(Native Method) at org.hyperic.sigar.util.Getline.(Getline.java:34) at org.hyperic.sigar.shell.ShellBase.init(ShellBase.java:91) at org.hyperic.sigar.cmd. [root@esdata-004 sigar]# java -Djava.library.path='/usr/share/elasticsearch/lib/sigar/' -jar sigar-1.6.4.jar no libsigar-amd64-linux.so in java.library.path org.hyperic.sigar.SigarException: no libsigar-amd64-linux.so in java.library.path at org.hyperic.sigar.Sigar.loadLibrary(Sigar.java:172) at org.hyperic.sigar.Sigar.(Sigar.java:100) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:191) at org.hyperic.sigar.SigarLoader.class$(SigarLoader.java:77) at org.hyperic.sigar.SigarLoader.getLocation(SigarLoader.java:77) at org.hyperic.sigar.cmd.Runner.main(Runner.java:176) java.lang.UnsatisfiedLinkError: org.hyperic.sigar.util.Getline.isatty()Z at org.hyperic.sigar.util.Getline.isatty(Native Method) at org.hyperic.sigar.util.Getline.(Getline.java:34) at org.hyperic.sigar.shell.ShellBase.init(ShellBase.java:91) at org.hyperic.sigar.cmd.Shell.main(Shell.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.hyperic.sigar.cmd.Runner.main(Runner.java:236)Shell.main(Shell.java:225) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.hyperic.sigar.cmd.Runner.main(Runner.java:236) ``` on one of the failing nodes I realized that I was missing some libraries in the files directory of my puppet module. Most likely this is what was causing the problem with operating system stats! Thanks for the idea. ---
**Author:** ![nellicus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nellicus/32/51566_2.png) [@nellicus](https://discuss.elastic.co/u/nellicus)\ **Post date:** [May 12, 2015, 2:43pm UTC](https://discuss.elastic.co/t/missing-os-statistics-on-data-nodes/536/5 "2015-05-12T14:43:14Z")
sorry got sidetracked by busy day 🙂 but looks like you've found your way! you're welcome ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:26pm UTC](https://discuss.elastic.co/t/missing-os-statistics-on-data-nodes/536/8 "2017-07-05T23:26:34Z")