Tom Sealey

Thanks. T400 should be good, it's 2 4k CCTV cameras. Should be perfect and power efficient.

Thanks for the suggestion. It's for transcoding cctv streams for Frigate. I'll look for a T400... a genuine one.

Thanks @ich777. I bought it on Ebay as new but unused... I did wonder if it was fake, but the pci id seemed right, and the line above says GP107, so I thought it was legit. Missed checking the audio driver line. I'll complain to ebay, I might get my money back... Thanks for the help.

Hi, Hope you can help. I have an Nvidia 1050 TI, but none of the drivers work, even though it is listed as supported. Here is an extract from my logs: Jul 9 21:23:58 Lofty kernel: nvidia: loading out-of-tree module taints kernel. Jul 9 21:23:58 Lofty kernel: nvidia: module license 'NVIDIA' taints kernel. Jul 9 21:23:58 Lofty kernel: Disabling lock debugging due to kernel taint Jul 9 21:23:58 Lofty kernel: AES CTR mode by8 optimization enabled Jul 9 21:23:58 Lofty kernel: [drm] Initialized mgag200 1.0.0 20110418 for 0000:01:00.1 on minor 0 Jul 9 21:23:58 Lofty kernel: fbcon: mgag200drmfb (fb0) is primary device Jul 9 21:23:58 Lofty kernel: BTRFS: device fsid ab17ef47-9a14-4f2a-975b-53afb10fcaf5 devid 1 transid 15717 /dev/sdd1 scanned by udevd (888) Jul 9 21:23:58 Lofty kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 244 Jul 9 21:23:58 Lofty kernel: Jul 9 21:23:58 Lofty kernel: nvidia 0000:04:00.0: enabling device (0040 -> 0043) Jul 9 21:23:58 Lofty kernel: nvidia 0000:04:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none Jul 9 21:23:58 Lofty kernel: NVRM: The NVIDIA GPU 0000:04:00.0 (PCI ID: 10de:1c82) Jul 9 21:23:58 Lofty kernel: NVRM: installed in this system is not supported by the Jul 9 21:23:58 Lofty kernel: NVRM: NVIDIA 470.239.06 driver release. Jul 9 21:23:58 Lofty kernel: NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products' Jul 9 21:23:58 Lofty kernel: NVRM: in this release's README, available on the operating system Jul 9 21:23:58 Lofty kernel: NVRM: specific graphics driver download page at www.nvidia.com. Jul 9 21:23:58 Lofty kernel: nvidia: probe of 0000:04:00.0 failed with error -1 Jul 9 21:23:58 Lofty kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Jul 9 21:23:58 Lofty kernel: NVRM: None of the NVIDIA devices were initialized. Jul 9 21:23:58 Lofty kernel: nvidia-nvlink: Unregistered the Nvlink Core, major device number 244 Jul 9 21:23:58 Lofty kernel: Console: switching to colour frame buffer device 128x48 Jul 9 21:23:58 Lofty kernel: mgag200 0000:01:00.1: [drm] fb0: mgag200drmfb frame buffer device Jul 9 21:23:58 Lofty kernel: sr 5:0:0:0: [sr0] scsi3-mmc drive: 40x/12x writer dvd-ram cd/rw xa/form2 cdda tray Jul 9 21:23:58 Lofty kernel: cdrom: Uniform CD-ROM driver Revision: 3.20 Jul 9 21:23:58 Lofty kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 244 Jul 9 21:23:58 Lofty kernel: Jul 9 21:23:58 Lofty kernel: nvidia 0000:04:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=none Jul 9 21:23:58 Lofty kernel: NVRM: The NVIDIA GPU 0000:04:00.0 (PCI ID: 10de:1c82) Jul 9 21:23:58 Lofty kernel: NVRM: installed in this system is not supported by the Jul 9 21:23:58 Lofty kernel: NVRM: NVIDIA 470.239.06 driver release. Jul 9 21:23:58 Lofty kernel: NVRM: Please see 'Appendix A - Supported NVIDIA GPU Products' Jul 9 21:23:58 Lofty kernel: NVRM: in this release's README, available on the operating system Jul 9 21:23:58 Lofty kernel: NVRM: specific graphics driver download page at www.nvidia.com. Jul 9 21:23:58 Lofty kernel: sr 5:0:0:0: Attached scsi CD-ROM sr0 Jul 9 21:23:58 Lofty kernel: nvidia: probe of 0000:04:00.0 failed with error -1 Jul 9 21:23:58 Lofty kernel: NVRM: The NVIDIA probe routine failed for 1 device(s). Jul 9 21:23:58 Lofty kernel: NVRM: None of the NVIDIA devices were initialized. 04:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) Kernel modules: nvidia_drm, nvidia 04:00.1 Audio device: NVIDIA Corporation GF116 High Definition Audio Controller (rev a1) The logs indicated that the GPU is not supported, but from what I can see the 1050 TI is supported still by these drivers? Ive tried the latest Production and earliest drivers available in the plugin. Any suggestions? Thanks in advance

Hi all, Anyone have any thoughts on how I can resolve this? It's becoming an issue again. If I try to list or delete the Loki dir, the shell hangs. It seems to cause shfs CPU usage to go up as well. I'm really not sure how to diagnose and resolve the issue.

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.

Thanks @Squid. I have tried it with the docker shutdown, same result.

Anybody have any thoughts? I cannot even remove this directory.

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?

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

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

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.

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 itimpi!

Ah good point, I'm planning on adding a matching NVMe SSD. But thanks for the heads up.