Problem "solved" partially. graylog seems to rely on an old directory as mentioned earlier. (/etc/graylog2/server/ and coping the node-id into there.)
Removed everything in the journal directory an I am running fine again. hth On Friday, February 20, 2015 at 1:44:42 PM UTC+1, Arie wrote: > > Solverd the problem partially bij creating > > /etc/graylog2/server/ and coping the node-id into there. > > Now only the kafaka exeption remains > > On Friday, February 20, 2015 at 1:36:33 PM UTC+1, Arie wrote: >> >> Hi All >> >> After succesfully updating to 1.0 from the latest 0.9 and starting up >> after a reboot all was fine in our test environment. >> >> Now after a resatrt of the graylog-server service we have the following >> error: >> >> 2015-02-20T13:26:25.572+01:00 ERROR [CmdLineTool] Guice error (more >> detail on log level debug): Error injecting constructor, >> java.lang.RuntimeException: kafka.common.KafkaException: Failed to acquire >> lock on file .lock in /var/lib/graylog-server/journal. A Kafka instance in >> another process or thread is using this directory. >> >> Cleaning up the directory does not solve this startup error. >> >> What can be wrong/ >> >> running on centos 6.6 >> latest java >> es 1.4.3 >> >> >> -- 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.
