Weird. The missing info is standard ES and should be there independent of the OS (and solaris is supported, but not relevant here :)).
Double checking - do you access the marvel ui through es-mon-1? On Thursday, February 6, 2014 1:56:06 PM UTC+1, Paweł Krzaczkowski wrote: > > OK i don;t know how .. but after 10 min of error it connected but it looks > like it's not sending all the information - maybe Marvel is not able to > collect system information from Solaris (smartOS) > > > https://picasaweb.google.com/lh/photo/L9Jptbfzxmh4JL6yVditfsi8TTKXUxXi6TYOgY7UZe8 > > W dniu czwartek, 6 lutego 2014 13:40:42 UTC+1 użytkownik Paweł > Krzaczkowski napisał: >> >> [root@es-mon-1 /opt/es]# uname -a >> SunOS es-mon-1 5.11 joyent_20130508T120818Z i86pc i386 i86pc Solaris >> >> >> W dniu czwartek, 6 lutego 2014 13:40:00 UTC+1 użytkownik Paweł >> Krzaczkowski napisał: >>> >>> Ok it looks like it has something to do with the system it's running on. >>> >>> Both es-d-1 and es-mon-1 run on smartos Solaris - and it doesn't work. >>> But I just started another data node on linux -> and this node connects to >>> es-mon-1.z - well it gives one 'connect timed out' error - but then it >>> establishes a working connection. >>> >>> W dniu czwartek, 6 lutego 2014 13:28:29 UTC+1 użytkownik Paweł >>> Krzaczkowski napisał: >>>> >>>> Sorry wrong node ;) >>>> >>>> [root@es-d-2 ~]# curl -XPOST es-mon-1.z:9200/_bulk -d'test body' >>>> {"error":"Failed to derive xcontent from >>>> org.elasticsearch.common.bytes.ChannelBufferBytesReference@b628f070"}[root@es-d-2 >>>> >>>> ~]# >>>> [root@es-d-2 ~]# >>>> >>>> >>>> W dniu czwartek, 6 lutego 2014 13:24:16 UTC+1 użytkownik Paweł >>>> Krzaczkowski napisał: >>>>> >>>>> [root@es-mon-1 ~]# curl -XPOST es-mon-1.z:9200/_bulk -d'test body' >>>>> {"error":"Failed to derive xcontent from >>>>> org.elasticsearch.common.bytes.ChannelBufferBytesReference@b628f070"} >>>>> [root@es-mon-1 ~]# >>>>> >>>>> W dniu czwartek, 6 lutego 2014 13:23:03 UTC+1 użytkownik Boaz Leskes >>>>> napisał: >>>>>> >>>>>> Looks good. Can you run the following? (running out of ideas here): >>>>>> >>>>>> [root@es-d-2 /opt/es/bin]# curl -XPOST es-mon-1.z:9200/_bulk -d'test >>>>>> body' >>>>>> >>>>>> Note that ES will fail this request as it is not valid but I want to >>>>>> double check we get an ES specific error (i.e., it connected). >>>>>> >>>>>> >>>>>> On Thursday, February 6, 2014 1:05:42 PM UTC+1, Paweł Krzaczkowski >>>>>> wrote: >>>>>>> >>>>>>> [root@es-d-2 ~]# env >>>>>>> >>>>>>> MANPATH=/opt/local/man:/usr/share/man:/opt/local/gcc47/man:/opt/local/java/sun6/man:/opt/local/lib/perl5/man:/opt/local/lib/perl5/vendor_perl/man >>>>>>> HZ=100 >>>>>>> SHELL=/usr/bin/bash >>>>>>> TERM=xterm >>>>>>> ES_HEAP_SIZE=8192M >>>>>>> ES_JAVA_OPTS=-d64 -server -Des.processors=4 -Des.node.name=es-d-2 >>>>>>> -Des.node.machine=44454c4c-5200-1038-8030-c2c04f365931 >>>>>>> COLUMNS=238 >>>>>>> PAGER=less >>>>>>> MAIL=/var/mail/root >>>>>>> >>>>>>> PATH=/usr/local/sbin:/usr/local/bin:/opt/local/sbin:/opt/local/bin:/usr/sbin:/usr/bin:/sbin >>>>>>> PWD=/root >>>>>>> JAVA_HOME=/opt/jdk1.7.0_25/ >>>>>>> LINES=74 >>>>>>> SHLVL=1 >>>>>>> HOME=/root >>>>>>> TERMINFO=/opt/local/share/lib/terminfo >>>>>>> LOGNAME=root >>>>>>> FTPMODE=auto >>>>>>> >>>>>>> Start command: >>>>>>> /opt/es/bin/elasticsearch -d -p /export/es/logs/elasticsearch.pid >>>>>>> >>>>>>> >>>>>>> W dniu czwartek, 6 lutego 2014 13:02:37 UTC+1 użytkownik Boaz Leskes >>>>>>> napisał: >>>>>>>> >>>>>>>> Hi Pawel, >>>>>>>> >>>>>>>> The only thing I can think of is that potentially some java system >>>>>>>> properties or ENV variables get in the way - things like forcing it >>>>>>>> use a >>>>>>>> proxy which I mentioned earlier. Can you list the ENV variables and >>>>>>>> the >>>>>>>> exact command line that is used to start elastic search? >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Boaz >>>>>>>> >>>>>>>> On Wednesday, February 5, 2014 3:36:23 PM UTC+1, Paweł Krzaczkowski >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Even better .. if I set cluster name on none 192.168.0.202 to my >>>>>>>>> default cluster name - the node will join the cluster and the >>>>>>>>> connection is >>>>>>>>> working fine. The only thing that is not working is if i change the >>>>>>>>> cluster >>>>>>>>> name to "monitoring" and try to send Marvel data to this cluster node. >>>>>>>>> >>>>>>>>> Paweł >>>>>>>>> >>>>>>>>> W dniu środa, 5 lutego 2014 14:51:59 UTC+1 użytkownik Boaz Leskes >>>>>>>>> napisał: >>>>>>>>>> >>>>>>>>>> Perhaps you have a proxy configured? >>>>>>>>>> >>>>>>>>>> curl listens to a couple of environment variables by default: see >>>>>>>>>> http://curl.haxx.se/docs/manpage.html >>>>>>>>>> >>>>>>>>>> If so, you can tell ES to use the same by adding the following >>>>>>>>>> properties upon startup: -Dhttp.proxyHost=webcache.example.com >>>>>>>>>> >>>>>>>>>> -Dhttp.proxyPort=8080 >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Wednesday, February 5, 2014 2:26:06 PM UTC+1, Paweł >>>>>>>>>> Krzaczkowski wrote: >>>>>>>>>>> >>>>>>>>>>> Same error >>>>>>>>>>> >>>>>>>>>>> [2014-02-05 14:25:17,254][ERROR][marvel.agent.exporter ]could >>>>>>>>>>> not connect to any configured elasticsearch instances: [192.168. >>>>>>>>>>> 0.202:9200] >>>>>>>>>>> [2014-02-05 14:25:18,204][ERROR][marvel.agent.exporter ]error >>>>>>>>>>> connecting to >>>>>>>>>>> [192.168.0.202:9200] >>>>>>>>>>> java.net.SocketTimeoutException: connect timed out >>>>>>>>>>> at java.net.PlainSocketImpl.socketConnect(Native Method) >>>>>>>>>>> at java.net.AbstractPlainSocketImpl.doConnect( >>>>>>>>>>> AbstractPlainSocketImpl.java:339) >>>>>>>>>>> at java.net.AbstractPlainSocketImpl.connectToAddress( >>>>>>>>>>> AbstractPlainSocketImpl.java:200) >>>>>>>>>>> at java.net.AbstractPlainSocketImpl.connect( >>>>>>>>>>> AbstractPlainSocketImpl.java:182) >>>>>>>>>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java >>>>>>>>>>> :392) >>>>>>>>>>> at java.net.Socket.connect(Socket.java:579) >>>>>>>>>>> at sun.net.NetworkClient.doConnect(NetworkClient.java: >>>>>>>>>>> 175) >>>>>>>>>>> at sun.net.www.http.HttpClient.openServer(HttpClient. >>>>>>>>>>> java:378) >>>>>>>>>>> at sun.net.www.http.HttpClient.openServer(HttpClient. >>>>>>>>>>> java:473) >>>>>>>>>>> at sun.net.www.http.HttpClient.<init>(HttpClient.java: >>>>>>>>>>> 203) >>>>>>>>>>> at sun.net.www.http.HttpClient.New(HttpClient.java:290) >>>>>>>>>>> at sun.net.www.http.HttpClient.New(HttpClient.java:306) >>>>>>>>>>> at sun.net.www.protocol.http.HttpURLConnection. >>>>>>>>>>> getNewHttpClient(HttpURLConnection.java:995) >>>>>>>>>>> at sun.net.www.protocol.http.HttpURLConnection. >>>>>>>>>>> plainConnect(HttpURLConnection.java:931) >>>>>>>>>>> at sun.net.www.protocol.http.HttpURLConnection.connect( >>>>>>>>>>> HttpURLConnection.java:849) >>>>>>>>>>> at org.elasticsearch.marvel.agent.exporter.ESExporter. >>>>>>>>>>> openConnection(ESExporter.java:317) >>>>>>>>>>> at org.elasticsearch.marvel.agent.exporter.ESExporter. >>>>>>>>>>> openConnection(ESExporter.java:293) >>>>>>>>>>> at org.elasticsearch.marvel.agent.exporter.ESExporter. >>>>>>>>>>> access$200(ESExporter.java:56) >>>>>>>>>>> at org.elasticsearch.marvel.agent.exporter. >>>>>>>>>>> ESExporter$ConnectionKeepAliveWorker.run(ESExporter.java:734) >>>>>>>>>>> at java.lang.Thread.run(Thread.java:724) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/43c91e89-cabb-4874-bf0f-8cb5212f8c5c%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
