Actually I tried the init sleep and it didn't solve it. At least not at the interval I set. What did fix it instantly was changing:
elasticsearch_discovery_zen_ping_unicast_hosts = foo.bar:9300 # FQDN:9300 to elasticsearch_discovery_zen_ping_unicast_hosts = 127.0.0.1:9300 Could be my firewall had something to do with it, but this fixed it. On Thursday, April 30, 2015 at 2:04:00 PM UTC-7, Mark Moorcroft wrote: > > > I have graylog/mongo/elastic installed via repo (RPM) on CentOS6. What I'm > seeing is any time I reboot the VM graylog-server fails to start. It seems > it tries to start up before elasticsearch has a chance to stabilize, > because if I service graylog-server restart later it will work. The problem > is this is a protected VM that I don't have root on, so I have to get the > system owner to restart the service for me. I'm not sure if elasticsearch > is taking too long to start, or if graylog-server needs a test so it waits > for the elasticsearch service to be running. As it is there seems to be no > wait loop, so graylog-server just dies, but it appears to leave the lock > file behind. None of this is good. > -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
