Thanks, Jochen! That worked. Sincerely, Dilip M.
On Thursday, May 19, 2016 at 8:19:53 AM UTC-4, Jochen Schalanda wrote: > > Hi Dilip, > > please try deleting the files in the message_journal_dir ( > https://github.com/Graylog2/graylog2-server/blob/2.0.1/misc/graylog.conf#L328-L330) > > and restart Graylog. > > Cheers, > Jochen > > On Wednesday, 18 May 2016 19:15:53 UTC+2, Dilip Muthukrishnan wrote: >> >> I should mention that I'm trying to setup Graylog 2.0.1 with >> Elasticsearch 2.3.2. However, I've not been able to get any of my inputs >> to work so far. >> >> Here is my Elasticsearch configuration: >> >> cluster.name: graylog2 >> network.host: vtor-lx-tomcat-d01 >> discovery.zen.ping.unicast.hosts: ["vtor-lx-tomcat-d01:9300"] >> script.inline: false >> script.indexed: false >> script.file: false >> >> Here is my Graylog server configuration: >> >> is_master = true >> node_id_file = /bns/home/tomcat/graylog/graylog-2.0.1/server/node-ID >> password_secret = december >> root_password_sha2 = >> 8745f86640ad2ed6b8a2fd428845df3daa1cfcdba9ef74c0cfaa57cacec34f5b >> plugin_dir = plugin >> rest_listen_uri = http://vtor-lx-tomcat-d01:12900/ >> web_listen_uri = http://vtor-lx-tomcat-d01:9000/ >> rotation_strategy = count >> elasticsearch_max_docs_per_index = 20000000 >> elasticsearch_max_number_of_indices = 20 >> retention_strategy = delete >> elasticsearch_shards = 4 >> elasticsearch_replicas = 0 >> elasticsearch_index_prefix = graylog2 >> allow_leading_wildcard_searches = true >> allow_highlighting = true >> elasticsearch_cluster_name = graylog2 >> elasticsearch_discovery_zen_ping_unicast_hosts = vtor-lx-tomcat-d01:9300 >> elasticsearch_analyzer = whitespace >> output_batch_size = 500 >> output_flush_interval = 1 >> output_fault_count_threshold = 5 >> output_fault_penalty_seconds = 30 >> processbuffer_processors = 5 >> outputbuffer_processors = 3 >> processor_wait_strategy = blocking >> ring_size = 65536 >> inputbuffer_ring_size = 65536 >> inputbuffer_processors = 2 >> inputbuffer_wait_strategy = blocking >> message_journal_enabled = true >> message_journal_dir = data/journal >> lb_recognition_period_seconds = 3 >> mongodb_uri = mongodb://vtor-lx-tomcat-d01:27017/graylog2 >> mongodb_max_connections = 1000 >> mongodb_threads_allowed_to_block_multiplier = 5 >> transport_email_enabled = true >> transport_email_hostname = TORACCHUB01.accounts.dundeecorp.com >> transport_email_port = 25 >> transport_email_use_auth = false >> transport_email_use_tls = false >> transport_email_use_ssl = false >> transport_email_subject_prefix = [graylog] >> transport_email_from_email = [email protected] <javascript:> >> content_packs_auto_load = grok-patterns.json >> >> >> On Tuesday, May 17, 2016 at 1:35:19 PM UTC-4, Dilip Muthukrishnan wrote: >>> >>> Hi, >>> >>> I keep seeing the following error my logs whenever I start the server. >>> What's causing it and how can it be resolved? >>> >>> 2016-05-17 13:12:14,740 ERROR: org.graylog2.shared.journal.KafkaJournal >>> - Read offset 0 before start of log at 2523, starting to read from the >>> beginning of the journal. >>> >>> Sincerely, >>> >>> Dilip M. >>> >> -- 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/ab9cfb68-ac31-40eb-acf1-8398191d6671%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
