A couple of weeks ago, I installed Graylog.  It was working fine but there 
were a lot of loose ends to take care of.  While I was tightening down 
iptables so the server could only talk to our LAN, I created a rule and 
broke the Graylog connection.  Even when I disabled the rule, Graylog still 
wouldn't start again because MongoDB was refusing the connection.  I 
thought that I would probably spend less time re-installing everything from 
scratch than to troubleshoot the issue.  So, I nuked and paved.

The new server has been running great for a week and has collected about 
65GB of logs.  Today, once again, I was tightening IPtables and now Graylog 
won't start because MongoDB is refusing the connection, even though it's 
listening for connections.  I reverted my IPtables config and even disabled 
rules that were working before.  So, the server is wide open now.  The 
MongoDB log shows no errors or warnings from the time it starts until it 
says it's up and waiting for connections.  Performing a netstat seems to 
confirm MongoDB is listening.

Neither of the times I've been creating IPtables rules should the rules 
have stopped anything from happening.  One of the times Graylog server 
stopped working, I created a rule to allow the localhost, restarted the 
server I was up and running again.  I have a two server Elasticsearch 
cluster with a third Graylog server acting as the Elasticsearch master. 
 The Elasticsearch cluster is green.

So, my questions are:

   1. Is it necessary to allow the localhost through IPtables or am I 
   missing something else?
   2. Has anyone else ran into this?
   3. Why would it still be broken?
   4. How can I fix it?

Any help you can give is greatly appreciated.

-- 
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/1865c8bd-8ff9-4865-8be4-dc8fd8df5961%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to