Jump to content

Tom Sealey

Members
  • Posts

    15
  • Joined

Posts posted by Tom Sealey

  1. Hi,
    I noticed that Influxdb was offline this morning.
    after investigating, I'm seeing this error in the logs:
     

    Executable /usr/bin/influxd does not exist!

    Sure enough, if I go into the container and check, that file is missing.

    Not sure what caused this, I pulled the previous container, same issue.
    I then pulled the newest one again, same.

    any help appreciated.

  2. Hi,
    I've been using GUS for a while. 

    However, since updating to UnRAID 6.11, whenever the docker restarts, the services crash.

    If I manually console into the docker and restart them, they will run fine, but they don't run when the container starts.

    Any ideas?

  3. Hi all,

    we use the Grafana-Unraid-Stack container.

    it keeps crashing, which we believe is due to a permissions issue.

    running:

    chown -R 99:100 

    on the config directory caused the terminal to hang for hours. 

    I narrowed it down to the loki/data/chunks directory.

    If I try to list or remove this directory, the terminal hangs. 

     

    We've also realized that this is possibly crashing mover, so that the shares disappear until we restart the server.

     

    Can any one explain why this is happening?

    I would just delete the dir and start again, but it's impossible to do anything to it.

     

    Thanks in advance

  4. 1 minute ago, Tom Sealey said:

    Hi all,

    I'm having an issue with Graylog.

    It was working fine, then I upgraded Unraid from 6.8 to 6.10.

    Since then Graylog stops after a short time.

    It stopped processing messages and the journal fills up.

    If I restart the container, it will process the journal for a time, then stop again.

    When it stops, I get this error:

    2022-06-17 11:21:57,189 ERROR: com.google.common.util.concurrent.ServiceManager - Service LocalKafkaMessageQueueReader [FAILED] has failed in the RUNNING state.
    java.lang.IllegalStateException: Invalid message size: 0
            at org.graylog.shaded.kafka09.log.FileMessageSet.searchFor(FileMessageSet.scala:141) ~[graylog.jar:?]
            at org.graylog.shaded.kafka09.log.LogSegment.translateOffset(LogSegment.scala:105) ~[graylog.jar:?]
            at org.graylog.shaded.kafka09.log.LogSegment.read(LogSegment.scala:148) ~[graylog.jar:?]
            at org.graylog.shaded.kafka09.log.Log.read(Log.scala:506) ~[graylog.jar:?]
            at org.graylog2.shared.journal.LocalKafkaJournal.read(LocalKafkaJournal.java:677) ~[graylog.jar:?]
            at org.graylog2.shared.journal.LocalKafkaJournal.readNext(LocalKafkaJournal.java:617) ~[graylog.jar:?]
            at org.graylog2.shared.journal.LocalKafkaJournal.read(LocalKafkaJournal.java:599) ~[graylog.jar:?]
            at org.graylog2.shared.messageq.localkafka.LocalKafkaMessageQueueReader.run(LocalKafkaMessageQueueReader.java:110) ~[graylog.jar:?]
            at com.google.common.util.concurrent.AbstractExecutionThreadService$1$2.run(AbstractExecutionThreadService.java:67) [graylog.jar:?]
            at com.google.common.util.concurrent.Callables$4.run(Callables.java:121) [graylog.jar:?]
            at java.lang.Thread.run(Thread.java:750) [?:1.8.0_332]

     

    I cannot work out why.

    Elasticsearch is fine, according to it's logs.

    I have no pipelines and I tried removing all extractors, same error.

    Also,

    I have tried several different versions of the Graylog Docker, currently sat on 4.2.8

  5. Hi all,

    I'm having an issue with Graylog.

    It was working fine, then I upgraded Unraid from 6.8 to 6.10.

    Since then Graylog stops after a short time.

    It stopped processing messages and the journal fills up.

    If I restart the container, it will process the journal for a time, then stop again.

    When it stops, I get this error:

    2022-06-17 11:21:57,189 ERROR: com.google.common.util.concurrent.ServiceManager - Service LocalKafkaMessageQueueReader [FAILED] has failed in the RUNNING state.
    java.lang.IllegalStateException: Invalid message size: 0
            at org.graylog.shaded.kafka09.log.FileMessageSet.searchFor(FileMessageSet.scala:141) ~[graylog.jar:?]
            at org.graylog.shaded.kafka09.log.LogSegment.translateOffset(LogSegment.scala:105) ~[graylog.jar:?]
            at org.graylog.shaded.kafka09.log.LogSegment.read(LogSegment.scala:148) ~[graylog.jar:?]
            at org.graylog.shaded.kafka09.log.Log.read(Log.scala:506) ~[graylog.jar:?]
            at org.graylog2.shared.journal.LocalKafkaJournal.read(LocalKafkaJournal.java:677) ~[graylog.jar:?]
            at org.graylog2.shared.journal.LocalKafkaJournal.readNext(LocalKafkaJournal.java:617) ~[graylog.jar:?]
            at org.graylog2.shared.journal.LocalKafkaJournal.read(LocalKafkaJournal.java:599) ~[graylog.jar:?]
            at org.graylog2.shared.messageq.localkafka.LocalKafkaMessageQueueReader.run(LocalKafkaMessageQueueReader.java:110) ~[graylog.jar:?]
            at com.google.common.util.concurrent.AbstractExecutionThreadService$1$2.run(AbstractExecutionThreadService.java:67) [graylog.jar:?]
            at com.google.common.util.concurrent.Callables$4.run(Callables.java:121) [graylog.jar:?]
            at java.lang.Thread.run(Thread.java:750) [?:1.8.0_332]

     

    I cannot work out why.

    Elasticsearch is fine, according to it's logs.

    I have no pipelines and I tried removing all extractors, same error.

  6. 16 minutes ago, AlainF said:

    Good day everyone,

     

    Running latest unRAID OS "Plus", and latest version of ts-dnsserver.

     

    I have recently starting experimenting with ts-dnsserver, and have come accross a problem I can't properly debug or explain. Every so often I notice that when the ts-dnsserver docker is stopped, and try to start it, the start process exits with an "execution error". Checking the logfiles, I find an error message that it cannot bind to port 53 (which is indeed bad for a DNS server 😁 ). Opening a terminal on the unRAID box and listing processes attached to port 53, I see a "dnsmasq" process. Once I kill this process, the ts-dnsserver docker starts again and all works fine.

     

    Any ideas? Sorry to not be clearer or more explicit ; if it helps to provide additional data, please let me know which.

     

    Thanks in advance,

     

    Alain

     

    Hi @AlainF,

    this is because unRAID runs its own DNS server using dnsmasq.

    I believe it's used for VMs.

     

    Details here of how to disable it:

     

    • Thanks 1
  7. 1 hour ago, trurl said:

    The title you have given this thread says you want to add HDD to this pool? Not recommended to mix HDD and SSD.

    Ah good point, I'm planning on adding a matching NVMe SSD.

    But thanks for the heads up.

  8. 1 hour ago, itimpi said:

    What file system is in use for the current cache drive?    If it is BTRFS then yes you can add a drive at any time.    If it is XFS then you would first need to back it up elsewhere as a multi-drive pool HAS to use a BTRFS file system.

    Thansk, it is BTRFS. 

     

    Is there any docs on adding an additional drive?

     

  9. Hi all,

    I hope you can help.

     

     

    I have an existing cache drive, and NVMe SSD.

    I use it as a cache and also the appdata drive for docker containers.

    It's backed up nightly to the main array.

     

    I would like to add a second to create a cache pool for redundancy.

    Is this possible since it has data on it already?

     

    Thanks

     

     

     

×
×
  • Create New...