Hi Sean, those responses with HTTP status code 404 are fine, there's simply no handler defined for the root resource and it was merely meant to check the connectivity to the Graylog REST API in general.
Now that we have established that communications between the machine you're running the Graylog Collector on and the Graylog server is possible, it seems like either a bug in the Graylog Collector or a misconfiguration. Could you please upload your Graylog Collector configuration somewhere (e. g. https://gist.github.com/)? Maybe check server-url again and ensure that's it's really the correct host. Cheers, Jochen On Monday, 16 November 2015 17:56:33 UTC+1, Sean McGurk wrote: > > Hi Jochen, > > I'm using version 1.2.2 of graylog. > > Whenever I try your suggestion, I get the following message returned: > > ubuntu@ip-xxx-xxx-xxx-xxx:~$ curl -i http://xxx.xxx.xxx.xxx:12900/ > > HTTP/1.1 404 Not Found > > Content-Type: application/json > > X-Graylog-Node-ID: 35750f44-b78b-4bd4-8fb9-93ff9d3a5733 > > Transfer-Encoding: chunked > > > {"type":"ApiError","message":"HTTP 404 Not Found"} > > When I try and running the command on the graylog server itself, I get the > same message: > > ubuntu@graylog:~$ curl -i http://localhost:12900/ > > HTTP/1.1 404 Not Found > > Content-Type: application/json > > X-Graylog-Node-ID: 35750f44-b78b-4bd4-8fb9-93ff9d3a5733 > > Transfer-Encoding: chunked > > > {"type":"ApiError","message":"HTTP 404 Not Found"} > > So, based on this - do you think that it may be a problem on the graylog > server side (vs. with the connector)? > > Thanks again, > > Seán > > On Sunday, 15 November 2015 09:37:26 UTC, Sean McGurk wrote: >> >> Hi, >> >> I am trying to create a Graylog Server - Graylog Collector setup, where >> the graylog collector collects the syslog files on one machine and ships >> them to the server. >> >> I have used the AWS AMI to create the Graylog Server and it is working as >> expected. >> >> I installed a Graylog Collector on the same machine and I am able to see >> it in the list of sources for that instance. >> >> My problem is when I try and connect to a remote Graylog Collector. >> >> The Graylog Collector configuration file looks like this: >> >> server-url = "http://xxx.xxx.xxx.xxx:12900/"; >> >> inputs { >> syslog { >> type = "file" >> path = "/var/log/syslog" >> } >> } >> >> outputs { >> graylog-server { >> type = "gelf" >> host = "xxx.xxx.xxx.xxx" >> port = 12201 >> } >> } >> >> where xxx.xxx.xxx.xxx is the private IP address of the graylog server I >> am attempting to connect to. >> >> An extract from the configuration of the graylog server is: >> >> rest_listen_uri = http://0.0.0.0:12900/ >> >> And the security groups for both instances are as follows: >> >> Type Protocol Port Range Source >> Custom TCP Rule TCP 12201 0.0.0.0/0 >> Custom TCP Rule TCP 12900 0.0.0.0/0 >> >> When I look at the logs for the graylog collector, I get the following >> messages: >> >> 2015-11-14T23:41:33.948+0000 ERROR [gelfTcpTransport-1-1] >> gelfclient.transport.GelfTcpTransport - Connection failed: Connection >> refused: /xxx.xxx.xxx.xxx:12201 >> 2015-11-14T23:41:34.949+0000 ERROR [gelfTcpTransport-1-1] >> gelfclient.transport.GelfTcpTransport - Connection failed: Connection >> refused: /xxx.xxx.xxx.xxx:12201 >> 2015-11-14T23:41:35.951+0000 ERROR [gelfTcpTransport-1-1] >> gelfclient.transport.GelfTcpTransport - Connection failed: Connection >> refused: /xxx.xxx.xxx.xxx:12201 >> 2015-11-14T23:41:36.953+0000 ERROR [gelfTcpTransport-1-1] >> gelfclient.transport.GelfTcpTransport - Connection failed: Connection >> refused: /xxx.xxx.xxx.xxx:12201 >> 2015-11-14T23:41:37.956+0000 ERROR [gelfTcpTransport-1-1] >> gelfclient.transport.GelfTcpTransport - Connection failed: Connection >> refused: /xxx.xxx.xxx.xxx:12201 >> 2015-11-14T23:41:38.698+0000 WARN [HeartbeatService RUNNING] >> collector.heartbeat.HeartbeatService - Unable to send heartbeat to Graylog >> server: ConnectException: Connection refused >> >> (again xxx.xxx.xxx.xxx is the private IP address of the graylog server I >> am attempting to connect to) >> >> I have run a traceroute between the 2 machines on port 12201 and port >> 12900 without any problems. >> >> Can anyone tell me what I might be missing in my configuration to allow >> these 2 to connect? >> >> Both are running Ubuntu 14.04. >> >> Thanks, >> >> Seán >> >> -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/e12824ac-6413-4f4f-8626-3ae44626b8b7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
