[graylog2] Re: Graylog2 web 0.90.0 error "API call failed to execute"

Jochen, Here you go: [root@graylog2-server graylog2]# curl -i -H 'Accept: application/json' 'http://172.20.56.41:12900/system/cluster/node?pretty=true' HTTP/1.1 404 Not Found Transfer-Encoding: chunked {"type":"ApiError","message":"HTTP 404 Not Found"} [root@graylog2-server graylog2]# curl -

[graylog2] AD auth issues when matching on a CN

I'm trying to set up AD auth in Graylog2 and I have it *mostly* working. When my Search Base DN looks like this: OU=ITS-NS,OU=ITS,DC=ad,DC=example,DC=edu My test user (in the ITS-NS OU) can log in. However, I want to match on membership within a CN: CN=ITS-NSMonTeamWebTest,OU=ITS-NS,OU=ITS,DC=a

[graylog2] Re: graylog2 v0.90.0 MessageBodyWriter not found for media type=text/csv

Jochen, thank you so much! Consider this issue resolved. Again, we appreciate the help! On Tuesday, October 14, 2014 10:45:11 AM UTC-5, Jochen Schalanda wrote: > > Hi, > > Am Dienstag, 14. Oktober 2014 16:29:47 UTC+2 schrieb Mave Zero: >> >> When I do >> request: >> http://{graylog2ip}:12900/se

[graylog2] Re: graylog2 v0.90.0 MessageBodyWriter not found for media type=text/csv

Hi, Am Dienstag, 14. Oktober 2014 16:29:47 UTC+2 schrieb Mave Zero: > > When I do > request: > http://{graylog2ip}:12900/search/universal/keyword?query=cluster%3Abugatti&keyword=1%20week%20ago > […] > But 150 is not enough, how can I change query to have more that 150? This > one even shows the

[graylog2] Re: graylog2 v0.90.0 MessageBodyWriter not found for media type=text/csv

Hi Jochen, appreciate your help with the matter. It appears as though a reindex has solved the problem as I am now able to get a response. I have one quick question I am hoping you can assist with: When I do request: http://{graylog2ip}:12900/search/universal/keyword?query=cluster%3Abugatti&ke

[graylog2] Re: Graylog2 web 0.90.0 error "API call failed to execute"

Hi, Am Dienstag, 14. Oktober 2014 15:14:32 UTC+2 schrieb Jeremy Farr: > > Everything seems good from a mongodb point-of-view: > Yes, it looks fine. Please post the output of the following commands: - curl -i -H 'Accept: application/json' 'http://172.20.56.41:12900/system/cluster/node?pret

[graylog2] Re: Graylog2 web 0.90.0 error "API call failed to execute"

Hi, Am Dienstag, 14. Oktober 2014 14:52:11 UTC+2 schrieb smgo...@gmail.com: > > 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 -

[graylog2] What is the difference between normal input vs transport input.

Hi, In graylog2 v 0.92 some new "transport" inputs are added. What is the purpose of transport input? How it differs with normal input? regards, -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emai

[graylog2] Re: Graylog2 web 0.90.0 error "API call failed to execute"

Everything seems good from a mongodb point-of-view: [root@graylog2-server ~]# mongo graylog2 MongoDB shell version: 2.6.4 connecting to: graylog2 Welcome to the MongoDB shell. For interactive help, type "help". For more comprehensive documentation, see http://docs.mongodb.org/ Questions?

[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

[graylog2] Rewrite timestamp on incoming logs?

Hello, Is it possible to rewrite the timestamp on incoming logs to the local system time of the Graylog server? I'm asking because we have some machines all across the world where the timezones don't match up so the timestamps get fairly large offsets. I've looked into using a Drools rule for t

[graylog2] Re: graylog2 v0.90.0 MessageBodyWriter not found for media type=text/csv

Hi, unfortunately I still can't reproduce your problem on recent Graylog2 versions. One thing: You should use an Accept header instead of Content-Type in your HTTP request. Please also run the following query against your Elasticsearch cluster directly and check if it returns any errors: {"f

[graylog2] Re: -java-home not working

Hi Cédric, Am Freitag, 10. Oktober 2014 09:46:30 UTC+2 schrieb Cédric Madörin: > > Our envireonement requires java 6 so I installed 7 in addition to get > graylog2 to run. > I saw that there is the parameter -java-home so I tried using it but > always got the error: > java_cmd can't be redeclare

[graylog2] Re: Graylog2 web 0.90.0 error "API call failed to execute"

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 > >

[graylog2] Re: Graylog2 web 0.90.0 error "API call failed to execute"

Hi Jeremy, Am Freitag, 10. Oktober 2014 05:17:14 UTC+2 schrieb Jeremy Farr: > > Ok, so all looks good there. Now trying with the curl command for the > proper reply: > > [root@graylog2-server graylog2]# curl -i --user admin:mypassword -H > 'Accept: application/json' http://172.20.56.41:12900/sys