# Graylog - Error **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [June 15, 2019, 12:13pm UTC](https://community.graylog.org/t/graylog-error/10800 "2019-06-15T12:13:52Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![zeus76](https://avatars.discourse-cdn.com/v4/letter/z/848f3c/32.png) [@zeus76](https://community.graylog.org/u/zeus76)\ **Post date:** [June 15, 2019, 12:13pm UTC](https://community.graylog.org/t/graylog-error/10800/1 "2019-06-15T12:13:52Z")
Hello, I set up a new Graylog server yesterday. My experiences with Linux and Graylog are not very high, because I come from the Windows world. Now I have set up the Graylog according to these instructions: > **[How To Install Graylog 3.0 on Ubuntu 18.04 / Ubuntu 16.04](https://www.itzgeek.com/how-tos/linux/ubuntu-how-tos/how-to-install-graylog-on-ubuntu-16-04.html)** > > Graylog is an open-source log management tool that helps you to collect, index and analyze any machine logs centrally. This guide So far everything runs fine with the server, but if I activate the rsyslog with the specify IP of the graylog, I get the following error message from the graylog: - Deflector exists as an index and is not an alias On the other hand, I did the following: 1. input configured incl. Extractors of Sophos UTM \-=https://github.com/habibmbacfou/graylogzeus/blob/master/Graylog=- Proudly Presents 2. syslog enabled on Sophos UTM -\> The data comes in - but cannot be interpreted. Section of the log: 2019-06-15T13:56:41.152+02:00 ERROR [AbstractRotationStrategy] Could not find current deflector target of index set . Aborting. org.graylog2.indexer.NoTargetIndexException: Couldn’t get newest index number for indices [graylog\_deflector] at org.graylog2.indexer.MongoIndexSet.getNewestIndexNumber(MongoIndexSet.java:170) ~[graylog.jar:?] at org.graylog2.indexer.MongoIndexSet.getNewestIndex(MongoIndexSet.java:146) ~[graylog.jar:?] at org.graylog2.indexer.rotation.strategies.AbstractRotationStrategy.rotate(AbstractRotationStrategy.java:61) ~[graylog.jar:?] at org.graylog2.periodical.IndexRotationThread.checkForRotation(IndexRotationThread.java:113) ~[graylog.jar:?] at org.graylog2.periodical.IndexRotationThread.lambda$doRun$0(IndexRotationThread.java:77) ~[graylog.jar:?] at java.lang.Iterable.forEach(Iterable.java:75) [?:1.8.0\_212] at org.graylog2.periodical.IndexRotationThread.doRun(IndexRotationThread.java:73) [graylog.jar:?] at org.graylog2.plugin.periodical.Periodical.run(Periodical.java:77) [graylog.jar:?] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0\_212] at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) [?:1.8.0\_212] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) [?:1.8.0\_212] at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) [?:1.8.0\_212] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0\_212] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0\_212] at java.lang.Thread.run(Thread.java:748) [?:1.8.0\_212] 2019-06-15T13:56:41.447+02:00 WARN [IndexFieldTypePollerPeriodical] Active write index for index set “Default index set” (5d0394653e02981bf218c7f6) doesn’t exist yet 2019-06-15T13:56:41.878+02:00 ERROR [DecodingProcessor] Unable to decode raw message RawMessage{id=a3c77450-8f64-11e9-b6d1-5a16cebbffb5, journalOffset=3753, codec=syslog, payloadSize=890, timestamp=2019-06-15T11:56:41.877Z, remoteAddress=/192.168.20.1:59968} on input \<5d040f613e0298045a49bf88\>. 2019-06-15T13:56:41.878+02:00 ERROR [DecodingProcessor] Error processing message RawMessage{id=a3c77450-8f64-11e9-b6d1-5a16cebbffb5, journalOffset=3753, codec=syslog, payloadSize=890, timestamp=2019-06-15T11:56:41.877Z, remoteAddress=/192.168.20.1:59968} Two questions: 1. why do I get this error message “Deflector exists as an index and is not an alias”? How can I solve the problem? Please a little instruction, because I am absolutely no Linux professional, thank you very much. 2. why are the logs not interpreted? Thank you very much for your help. Best regards ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [June 17, 2019, 7:37am UTC](https://community.graylog.org/t/graylog-error/10800/2 "2019-06-17T07:37:52Z")
@zeus76 I’m sorry that you have that issues. But the guide you had followed left some important steps out … Your error can be fixed with the information found in our documentation: [http://docs.graylog.org/en/3.0/pages/faq.html#how-do-i-fix-the-deflector-exists-as-an-index-and-is-not-an-alias-error-message](http://docs.graylog.org/en/3.0/pages/faq.html#how-do-i-fix-the-deflector-exists-as-an-index-and-is-not-an-alias-error-message) ---
**Author:** ![zeus76](https://avatars.discourse-cdn.com/v4/letter/z/848f3c/32.png) [@zeus76](https://community.graylog.org/u/zeus76)\ **Post date:** [June 17, 2019, 6:50pm UTC](https://community.graylog.org/t/graylog-error/10800/3 "2019-06-17T18:50:14Z")
Hallo Jan, Thank you for your feedback. I was able to find and solve the problem in the meantime. Wish you a nice evening – best regards ---
**Author:** ![jan](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/jan/32/11_2.png) [@jan](https://community.graylog.org/u/jan)\ **Post date:** [June 18, 2019, 6:45am UTC](https://community.graylog.org/t/graylog-error/10800/4 "2019-06-18T06:45:14Z")
He @zeus76 sharing is caring - it might be helpful for others if you write your solution or point to the guide that solved your issue. thx ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [July 2, 2019, 6:45am UTC](https://community.graylog.org/t/graylog-error/10800/5 "2019-07-02T06:45:17Z")
Closed on July 2, 2019, 6:45am UTC This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.