[graylog2] Re: Graylog2 web 0.90.0 error API call failed to execute
Hi Jochen, I understand it is bound to local interface but I am only accessing this from the local node not from any other system. http://127.0.0.1:12900/api-browser using the drop down menu under Node menu API browser - and it comes back as not found. Also, if I change the rest_listen_uri and rest_transport_uri to physical interface - I can access the browser but I no longer access the graylog2-webserver on 9000 port using the physical address. Thanks Mukesh On Tuesday, October 14, 2014 5:33:25 AM UTC-4, Jochen Schalanda wrote: Hi, Am Freitag, 10. Oktober 2014 20:34:13 UTC+2 schrieb smgo...@gmail.com: Here are the outputs of my commands curl -i --user user:passwd -H 'Accept: application/json' http://x.x.x.x:12900/system/cluster/node curl: (7) Failed to connect to x.x.x.x port 12900: Connection refused root@01:/etc/init.d# netstat -tplen|grep :12900 tcp6 0 0 127.0.0.1:12900 :::* LISTEN 0 33562 3601/java root@01:/etc/init.d# lsof -i :12900 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java3601 root 44u IPv6 33562 0t0 TCP localhost:12900 (LISTEN) All things are running on a single node right now for me - mongodb, elastic search, graylog2-server and web The graylog2-server process is bound to the loopback interface (127.0.0.1), so it's only accessible from the same machine in this case. If you want to access the Graylog2 REST API from another system, you need to bind to an external network interface. Please refer to the rest_listen_uri (and rest_transport_uri) settings in your graylog2.conf. Cheers, Jochen -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] event correlation in graylog2
My need is to correlate two events for following purposes 1. find the duration from event 1 to event 2 like user logged in at time 1 and user logged out at time 2 - duration user was connected (t2-t1) 2. Secondly, event A has part of the information and part of the information is coming in event B - which the two together makes a full event. So in a nutshell is there some event correlation facility available in graylog2 - log analysis. Or how should I go about doing this with graylog2 0.90 version. I was looking into Drools Fusion for event processing - but not getting anywhere with that! Thanks -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[graylog2] Re: Graylog2 web 0.90.0 error API call failed to execute
Hi Jochen, Looks like I am hitting the same problem - but, I do get access to the web server properly. I just keep getting this API call failed to execute as well as I am not able to get to the API browser. Here are the outputs of my commands curl -i --user user:passwd -H 'Accept: application/json' http://x.x.x.x:12900/system/cluster/node curl: (7) Failed to connect to x.x.x.x port 12900: Connection refused root@01:/etc/init.d# netstat -tplen|grep :12900 tcp6 0 0 127.0.0.1:12900 :::*LISTEN 0 33562 3601/java root@01:/etc/init.d# lsof -i :12900 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME java3601 root 44u IPv6 33562 0t0 TCP localhost:12900 (LISTEN) All things are running on a single node right now for me - mongodb, elastic search, graylog2-server and web Thanks Mukesh Sharma On Thursday, October 9, 2014 4:09:54 AM UTC-4, Jochen Schalanda wrote: Hi Jeremy, Am Donnerstag, 9. Oktober 2014 06:12:59 UTC+2 schrieb Jeremy Farr: So, I'm not sure exactly why this connection is being refused. Most of my investigation reveals this a somewhat generic error message. Once I put the previously used graylog2 versions back in place (graylog2 0.20.6 server and web) and start both up it works fine. I didn't see anything that jumped out at me in the new config files that alluded to anything I needed to add that wasn't in the previous configs. After upgrading the binaries and starting the services, please check that graylog2-server is listening on the proper interface. You can check that by running `lsof -i :12900` or `netstat -tplen|grep :12900`. Please also check if you receive a proper reply for this cURL command (replace $GL2_USER and $GL2_PASSWORD with your admin user and its respective password): curl -i --user $GL2_USER:$GL2_PASSWORD -H 'Accept: application/json' http://172.20.56.41:12900/system/cluster/node Cheers, Jochen -- You received this message because you are subscribed to the Google Groups graylog2 group. To unsubscribe from this group and stop receiving emails from it, send an email to graylog2+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
