Hi Sikender,

I'm not sure what you want to know. Could you please try to rephrase your 
questions or add more details?


Cheers,
Jochen

On Thursday, 14 April 2016 07:29:52 UTC+2, sikender...@acesred.com wrote:
>
> Hi JOchen,
>
>
>
> I dont know what might be the reason But I cant able to access REST API. 
>  And one more thing is like, If i provide more nodes to server ad access 
> graylog? What are the defects I will be facing ? 
> For example; 
>
> I have 10 environments, Can I access 5 environments in 1 node and other 5 
> in another node ? IS it fine If i do that ? 
>
> Thank you Jochen. 
>
> Regards
> Sikender
>
> On Monday, April 11, 2016 at 3:36:22 AM UTC-7, Jochen Schalanda wrote:
>>
>> Hi Sikender,
>>
>> if you're using Graylog 1.3.x, the Graylog REST API must be accessible by 
>> the Graylog web interface. If you're using Graylog 2.x, the Graylog REST 
>> API must additionally be accessible by your web browser (since the web 
>> interface is now a single-page application directly communicating with the 
>> Graylog REST API from your browser).
>>
>> Cheers,
>> Jochen
>>
>> On Thursday, 7 April 2016 10:36:53 UTC+2, sikender...@acesred.com wrote:
>>>
>>> HI Jochen,
>>>
>>>
>>> My graylog server is different server compare to client server.  my 
>>> graylog server is x.x.x.x:9000 and client server is on x.x.x.x:port.   DO 
>>> we need this API access to perform well? I have mu graylog server up and 
>>> able to receive logs though?
>>>
>>> When I run lsof -l :12900;
>>> It gives me output like:
>>>
>>> COMMAND   PID    USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
>>> java    12450 graylog  137u  IPv6 877480      0t0  TCP localhost:12900 
>>> (LISTEN)
>>>
>>>
>>>
>>>
>>> On Thursday, April 7, 2016 at 1:01:07 AM UTC-7, Jochen Schalanda wrote:
>>>>
>>>> Hi Sikender,
>>>>
>>>> the loopback interface <https://en.wikipedia.org/wiki/Localhost> is 
>>>> always only accessible from the very same machine, so your client or 
>>>> browser also needs to run on that machine in order to access the Graylog 
>>>> REST API at http://127.0.0.1:12900/.
>>>>
>>>> If that's already the case, then you need to check the logs of your 
>>>> Graylog server for error messages. Checking that the actual process is 
>>>> running (e. g. sudo lsof -i :12900 or sudo netstat -tplen | grep 
>>>> :12900) would also help.
>>>>
>>>> Cheers,
>>>> Jochen
>>>>
>>>> On Thursday, 7 April 2016 09:37:36 UTC+2, sikender...@acesred.com 
>>>> wrote:
>>>>>
>>>>> Hi Jochen,
>>>>>
>>>>>
>>>>> The graylog-server is running. 
>>>>>
>>>>> Status is "graylog-server (pid  24233) is running..."  But I can't 
>>>>> able to access http://127.0.0.1:12900/ . Even graylog server and 
>>>>> server web are on the same server. ?? CAn you please tell me where am I 
>>>>> going wrong. 
>>>>>
>>>>>
>>>>> Thank you 
>>>>> Sikender
>>>>>
>>>>>
>>>>> On Thursday, March 31, 2016 at 2:54:27 AM UTC-7, Jochen Schalanda 
>>>>> wrote:
>>>>>>
>>>>>> Hi Sikender,
>>>>>>
>>>>>> make sure that your Graylog server is running and that the web 
>>>>>> interface can reach it at http://127.0.0.1:12900/ (which will only 
>>>>>> work if it's running on the same machine).
>>>>>>
>>>>>> Cheers,
>>>>>> Jochen
>>>>>>
>>>>>> On Thursday, 31 March 2016 01:45:07 UTC+2, sikender...@acesred.com 
>>>>>> wrote:
>>>>>>>
>>>>>>> H Jochen, 
>>>>>>>
>>>>>>>
>>>>>>> Awesome. That works for me. Now I am able to send logs so easily :) 
>>>>>>>
>>>>>>> Seems everything is fine , but when I see the logs of graylog-web 
>>>>>>> server after restart, I see something like ; 
>>>>>>>
>>>>>>>
>>>>>>> 2016-03-30T02:14:25.471-04:00 - [INFO] - from play in main
>>>>>>> Application started (Prod)
>>>>>>>
>>>>>>> 2016-03-30T02:14:25.614-04:00 - [INFO] - from play in main
>>>>>>> Listening for HTTP on /0:0:0:0:0:0:0:0:9000
>>>>>>>
>>>>>>> 2016-03-30T02:15:55.038-04:00 - [INFO] - from play in New I/O worker 
>>>>>>> #13
>>>>>>> Starting application default Akka system.
>>>>>>>
>>>>>>> 2016-03-30T17:12:42.253-04:00 - [ERROR] - from 
>>>>>>> org.graylog2.restclient.lib.ApiClient in pool-22-thread-1
>>>>>>> Connection refused: /127.0.0.1:12900 to 
>>>>>>> http://127.0.0.1:12900/system/metrics/multiple
>>>>>>>
>>>>>>> 2016-03-30T17:12:46.427-04:00 - [ERROR] - from 
>>>>>>> org.graylog2.restclient.lib.ApiClient in servernodes-refresh-0
>>>>>>> Connection refused: /127.0.0.1:12900 to 
>>>>>>> http://127.0.0.1:12900/system/cluster/node
>>>>>>> "application.log" 145L, 7809C
>>>>>>>
>>>>>>>
>>>>>>> Can you please tell me where exactly it is pointing to ! 
>>>>>>>
>>>>>>>
>>>>>>> Thank you 
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, March 30, 2016 at 2:10:03 AM UTC-7, Jochen Schalanda 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Hi Sikender,
>>>>>>>>
>>>>>>>> you cannot bind two inputs to the same network interface (in this 
>>>>>>>> case 0.0.0.0:12201). One of those GELF TCP inputs has to use 
>>>>>>>> another port (e. g. 12201 or anything above 1024).
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Jochen
>>>>>>>>
>>>>>>>> On Wednesday, 30 March 2016 00:22:22 UTC+2, sikender...@acesred.com 
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> HI Jochen,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Sure. Below are the snapshots of GELF-TCP input running and the 
>>>>>>>>> other one saying "Address already in use" 
>>>>>>>>>
>>>>>>>>> Can you please go through it and let me know where am I going 
>>>>>>>>> wrong. I have also attached the config files for reference. 
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thank you
>>>>>>>>>
>>>>>>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Graylog Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to graylog2+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/graylog2/f151545b-6426-4d1f-9ae0-96543429b71f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to