[12:05] Our graylog instance won't
start. /var/log/graylog/server/current shows the following failures...
[12:05] 2016-08-10_16:56:49.58726 Caused by:
kafka.common.KafkaException: Failed to acquire lock on file .lock in
/var/opt/graylog/data/journal. A Kafka instance in another process or
I discovered what my problem was. I was selecting (from the drop down
CST6CDT. This is apparently not a valid time zone. I changed it to
'Chicago' and that appears to stick.
On Friday, August 5, 2016 at 1:09:39 PM UTC-5, Ralph @GM wrote:
>
> We have an AD integrated instance (late
We have an AD integrated instance (latest OVA) of graylog. For some reason
the time zone for all AD users reverts back to UTC when they log off. It's
like the first thing that needs to be set on their profile when they log in
or the times are all wrong. Anyone else experienced this?
