Re: [graylog2] my first syslog input is failing

2017-01-22 Thread Jason Fuller
the server and app. Thanks for all your help! Jason On Sun, Jan 22, 2017 at 9:51 PM, Jason Fuller <djasonful...@gmail.com> wrote: > Hi Jochen, > > Understand about the security implications. Thank you for pointing out ;) > > On the receipt issue, yes, I'm sure there is not a

Re: [graylog2] my first syslog input is failing

2017-01-22 Thread Jason Fuller
Hi Jochen, Understand about the security implications. Thank you for pointing out ;) On the receipt issue, yes, I'm sure there is not a network issue, on the graylog server I'm receiving the packet. It's just not showing up in Graylog: [root@server]# tcpdump -nnvvi ens32 port 514 tcpdump:

Re: [graylog2] my first syslog input is failing

2017-01-21 Thread Jason Fuller
Hi Jochen, Thanks! Changed user to root, restarted server, and the input is starting ok now. However, when I send test messages to the input, I don't see anything in input/search window. In the log, I see this: 2017-01-22T21:05:47.002+08:00 WARN [NettyTransport] receiveBufferSize (SO_RCVBUF)

Re: [graylog2] my first syslog input is failing

2017-01-20 Thread Jason Fuller
messages from this input. This is mostly an indication for a misconfiguration or an error. You can click here <http://10.208.0.64:9000/system/inputs> to solve this. On Fri, Jan 20, 2017 at 5:42 PM, Jason Fuller <djasonful...@gmail.com> wrote: > Hi Richard, > >- allow_ove

Re: [graylog2] my first syslog input is failing

2017-01-20 Thread Jason Fuller
Hi Richard, - allow_override_date: true - bind_address: 10.10.0.64 < I also tried 0.0.0.0 and 127.0.0.l - expand_structured_data: true - force_rdns: true - override_source: ** - port: 514 - recv_buffer_size: 262144 - store_full_message:

Re: [graylog2] Re: Can't open web console on host IP

2017-01-20 Thread Jason Fuller
On Fri, Jan 20, 2017 at 4:01 PM, Jochen Schalanda wrote: > - ip addr show > - hostname > - hostname -f > - hostname -a > - hostname -i Hi Jochen, You helped me find the problem. DNS resolution was going to internet before local server, so it was resolving to an incorrect

Re: [graylog2] Re: Can't open web console on host IP

2017-01-19 Thread Jason Fuller
Sorry - typo - the actual values are both matching IP's. rest_listen_uri = http://10.10.0.64:9000/api/ rest_transport_uri = http://10.10.0.64:9000/api/ <http://10.208.0.64:9000/api/> On Fri, Jan 20, 2017 at 9:49 AM, Jason Fuller <djasonful...@gmail.com> wrote: > Hi Jochen, &g

Re: [graylog2] Re: Can't open web console on host IP

2017-01-19 Thread Jason Fuller
Hi Jochen, Yes, I'm sure. I'm on a standard internal network with one external public IP. I'm in Asia, not Switzerland. No proxy. [root@server]# curl http://ipecho.net/plain; echo; 203.xxx.xxx.xxx Also: rest_listen_uri = http://10.10.0.64:9000/api/ rest_transport_uri =

Re: [graylog2] Re: Can't open web console on host IP

2017-01-19 Thread Jason Fuller
Hi Jochen, thank you for your reply. I'm past the logon issues now, however, when i go to setup an input, and tell it which node, it's only giving me an option for an externally connected IP - 141.8.225.xx But I only have this setup in an internal network, no external IP binding. Ad that IP is

Re: [graylog2] Re: Can't open web console on host IP

2017-01-19 Thread Jason Fuller
Hi Jochen, Thanks for the links. I did setup those variables, but let me explain what I found: When I tried to go to :9000 (as setup in the web_listen_uri) it would not respond. When I tried wrote: > Hi, > > On Thursday, 19 January 2017 03:33:26 UTC+1, JayJay wrote: >> >> So does that mean we

Re: [graylog2] Re: Can't open web console on host IP

2017-01-18 Thread Jason Fuller
Hi, thanks for your response. I installed it per the instructions on your setup page. So does that mean we can not access GrayLog from anywhere outside the localhost? It is a web services, after all... Thanks On Mon, Jan 16, 2017 at 5:26 PM, Jochen Schalanda wrote: > Hi,