dandiodati

Members
 View Profile  See their activity

  • Posts

    25

  • Joined

  • Last visited

 Content Type 

Posts posted by dandiodati

    [Support] kilrah/nextcloud-ffmpeg

    in Docker Containers

    Posted · Edited by dandiodati

    Hmm it seems this container(Nextcloud-cronjob) is very basic it has the ability to run extra scripts (put into the cron-scripts directory) but they all run at the same global setting, where as I want to configure times for different scripts. 

    Sadly does not seem possible so I would have to make a custom version of this container or look at some other solution.

    [Support] kilrah/nextcloud-ffmpeg

    in Docker Containers

    Posted

    15 minutes ago, dandiodati said:

    I was trying to get nextcloud-cron installed in unraid, and I linked it to my existing nextCloud install but was not working. I tried mapping the directories from the nextcloud container over to the nextcloud-cron conntainer but found that it tries to run php which does not even exist on the the nextcloud-cron container so how does this even work ?

    Ok I see this container is supposed to do a docker exec into the other nextcloud one.

    [Support] kilrah/nextcloud-ffmpeg

    in Docker Containers

    Posted

    I was trying to get nextcloud-cron installed in unraid, and I linked it to my existing nextCloud install but was not working. I tried mapping the directories from the nextcloud container over to the nextcloud-cron conntainer but found that it tries to run php which does not even exist on the the nextcloud-cron container so how does this even work ?

    unraid server freezing up when doing a parity check

    in General Support

    Posted · Edited by dandiodati

    Thats what I heard before and I did change to a new PSU and (HBA)controller card. And I added more fans just incase for cooling and was monitoring temperatures which seem fine. 
    I ran memtest and even tried taking out some of the memory sticks. I dont have a spare motherboard and replacing that it more expensive and afraid it might not fix it.

    Like I said it is stable unless I run the parity check.

     

    Can someone please still look at the diagnostics since I saw one item that may be an error (like noted) but not an expert on all the other messages and on which ones might be a clue on the issue.

    unraid server freezing up when doing a parity check

    in General Support

    Posted · Edited by dandiodati
    Adding more info on lsi card

    I have a amd threadripper machine that keeps on freezing whenever the parity check runs. I am stuck on what else I can do.

    I followed all the threads on trying to disable any C-states within the bios(I found the C-states disabling makes no difference). I replaced the power supply, checked all the memory, and even replaced the sata controller with a new 16 port lsi 9300. I updated the motherboard bios to the latest F6 version.

    And I updated the LSI logic controller to the latest versions available.


    The machine is running with 14 disks( 6 disks are part of the main array a 62 TB) and a separate ssd cache pool, and about 15 active docker containers (like a mysql db) that have lots of disk access, but the machine is very stable for over a week if I turn off the parity check. As soon as the parity check runs it just freezing randomly (some times shortly after starting or could be half way or more)

     

    Specs:
    Gigabyte Technology Co., Ltd. TRX40 AORUS PRO WIFI , Version Default string
    American Megatrends International, LLC., Version FD
    BIOS dated: Wed 7 Sep 2022 12:00:00 AM PDT

    AMD Ryzen Threadripper 3960X 24-Core @ 3800 MHz

     LSI Logic Controller SAS 9300 16-port

    Memory: 128 GiB DDR4

     

     

    The versions of my LSI card is :

    root@media:~# lspci | grep LSI
    23:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)
    25:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02)

     

    dmesg | grep mpt3sas_cm0 

    ...

    [    9.488835] mpt3sas_cm0: LSISAS3008: FWVersion(16.00.10.00), ChipRevision(0x02), BiosVersion(18.00.00.00)

    ...

     

    I did notice this error in dmesg "overriding NVDATA EEDPTagMode setting" which maybe is related ?

    I also tried logging to a separate syslog server to try to capture any errors just as it froze but it just suddenly stops with not errors.

     

    Can someone take a look at me diagnostics and let me know if they see anything strange? 

    media-diagnostics-20230926-1230.zip

    server keeps freezing up when trying to do parity rebuild

    in General Support

    Posted · Edited by dandiodati

    Ok I finally figured it out the hardware issue that was causing it. I changed the cpu clock speed from 38 to 37.50 and that made the parity rebuild make it through without freezing.

    Strange the cpu (AMD Ryzen Threadripper 3960X 24-Core @ 3800 MHz) is rated at 3800mhz so should be able to run at 38 setting which as set to auto before and was not overclocking it, but it seems to cause issues on this gigabtye motherboard. 

     

    Dropping it down a bit seem to fix the issue. Plan to try 37.75 too.

     

     

    • Like 1

    server keeps freezing up when trying to do parity rebuild

    in General Support

    Posted

    Still struggling with getting the parity disk rebuild. I've tried to remove all the ram and only keep one stick, then tried moving drives to different to another controller card, changed all sas to sata cables, switch the PSU, and changed the icydock cage that I was using for the drives, removed all extra drives to only the 6 disks (with parity) that I have been trying to rebuild, updated to the latest bios, and Have been trying to change bios settings (turn off the global-C states, change memory speed to 3200.

     

    Any other settings on my board that may be a possible problem ?

    Gigabyte Technology Co., Ltd. TRX40 AORUS PRO WIFI , Version x.x

    American Megatrends Inc., Version FD

    AMD Ryzen Threadripper 3960X 24-Core @ 3800 MHz

     

    Anyone have any other ideas that I can try ? Or know about known issues with Ryzen threadripper and gigabtye board ?

    Kicked off another run and added diagnostics again

     

    media-diagnostics-20230404-2236.zip

    server keeps freezing up when trying to do parity rebuild

    in General Support

    Posted

    So I have been running this hardware setup for over a year so a bit surprising that some hardware is incompatible. 

    Could someone still take a look at my diagnostics quickly to see if there is some error or issue that I did not see ?

     

    I'm running on 

    Gigabyte Technology Co., Ltd. TRX40 AORUS PRO WIFI , Version x.x

    American Megatrends Inc., Version FA

    BIOS dated: Wed 01 Jul 2020 12:00:00 AM PDT

    AMD Ryzen Threadripper 3960X 24-Core @ 3800 MHz

     

    128 GB DDR4

     

    If there are any hints to help be figure out what the error is that would be great, I have not had my server started due to the parity being down.

    Attaching a new diagnostics just as I started the parity rebuild it case it helps.

     

    I'll also try jumping up to the latest rc version to see if it helps any.


    My system devices are the following: 

    IOMMU group 0:[1022:1482] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 1:[1022:1483] 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 2:[1022:1483] 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 3:[1022:1483] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 4:[1022:1482] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 5:[1022:1482] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 6:[1022:1482] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 7:[1022:1482] 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 8:[1022:1482] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 9:[1022:1484] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 10:[1022:1482] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 11:[1022:1484] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 12:[1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61)

[1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)

IOMMU group 13:[1022:1490] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 0

[1022:1491] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 1

[1022:1492] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 2

[1022:1493] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 3

[1022:1494] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 4

[1022:1495] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 5

[1022:1496] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 6

[1022:1497] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship Device 24; Function 7

IOMMU group 14:[144d:a80a] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO

[N:0:6:1] disk Samsung SSD 980 PRO 2TB__1 /dev/nvme0n1 2.00TB

IOMMU group 15:[1987:5012] 02:00.0 Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller (rev 01)

[N:1:1:1] disk Corsair MP400__1 /dev/nvme1n1 8.00TB

IOMMU group 16:[1000:0072] 03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

[3:0:0:0] disk ATA ST6000VN0033-2EE SC60 /dev/sdc 6.00TB

[3:0:1:0] disk ATA ST14000NM001G-2K SN03 /dev/sdd 14.0TB

[3:0:2:0] disk ATA ST14000NM001G-2K SN03 /dev/sde 14.0TB

[3:0:3:0] disk ATA ST6000VN0033-2EE SC60 /dev/sdf 6.00TB

[3:0:4:0] disk ATA ST14000NM001G-2K SN03 /dev/sdg 14.0TB

[3:0:5:0] disk ATA ST14000NM001G-2K SN03 /dev/sdh 14.0TB

[3:0:6:0] disk ATA ST14000NM001G-2K SN03 /dev/sdi 14.0TB

IOMMU group 17:[1022:148a] 04:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

IOMMU group 18:[1022:1485] 05:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

IOMMU group 19:[1022:148c] 05:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller

Bus 001 Device 001 Port 1-0 ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001 Port 2-0 ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 002 Port 2-2 ID 21c4:0cd1 Lexar USB Flash Drive

IOMMU group 20:[1022:1482] 20:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 21:[1022:1482] 20:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 22:[1022:1482] 20:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 23:[1022:1483] 20:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 24:[1022:1482] 20:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 25:[1022:1482] 20:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 26:[1022:1482] 20:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 27:[1022:1484] 20:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 28:[1022:1482] 20:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 29:[1022:1484] 20:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 30:[10de:128b] 21:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 710] (rev a1)

[10de:0e0f] 21:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1)

IOMMU group 31:[1022:148a] 22:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

IOMMU group 32:[1022:1485] 23:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

IOMMU group 33:[1022:1486] 23:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP

IOMMU group 34:[1022:148c] 23:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller

Bus 003 Device 001 Port 3-0 ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001 Port 4-0 ID 1d6b:0003 Linux Foundation 3.0 root hub

IOMMU group 35:[1022:1487] 23:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller

IOMMU group 36:[1022:1482] 40:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 37:[1022:1483] 40:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 38:[1022:1483] 40:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 39:[1022:1482] 40:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 40:[1022:1482] 40:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 41:[1022:1483] 40:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 42:[1022:1483] 40:03.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 43:[1022:1483] 40:03.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 44:[1022:1483] 40:03.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge

IOMMU group 45:[1022:1482] 40:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 46:[1022:1482] 40:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 47:[1022:1482] 40:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 48:[1022:1484] 40:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 49:[1022:1482] 40:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 50:[1022:1484] 40:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 51:[1022:57ad] 41:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse Switch Upstream

IOMMU group 52:[1022:57a3] 42:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

IOMMU group 53:[1022:57a3] 42:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

IOMMU group 54:[1022:57a3] 42:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

IOMMU group 55:[1022:57a4] 42:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

[1022:1485] 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

[1022:149c] 46:00.1 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

Bus 005 Device 001 Port 5-0 ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 005 Device 002 Port 5-4 ID 05e3:0608 Genesys Logic, Inc. Hub

Bus 005 Device 003 Port 5-5 ID 0414:a002 Giga-Byte Technology Co., Ltd USB Audio

Bus 005 Device 004 Port 5-4.1 ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard

Bus 005 Device 005 Port 5-4.2 ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

Bus 005 Device 006 Port 5-4.3 ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio

Bus 005 Device 007 Port 5-6 ID 048d:8297 Integrated Technology Express, Inc. IT8297 RGB LED Controller

Bus 006 Device 001 Port 6-0 ID 1d6b:0003 Linux Foundation 3.0 root hub

[1022:149c] 46:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller

Bus 007 Device 001 Port 7-0 ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 007 Device 002 Port 7-5 ID 8087:0029 Intel Corp. AX200 Bluetooth

Bus 007 Device 003 Port 7-6 ID 05e3:0608 Genesys Logic, Inc. Hub

Bus 008 Device 001 Port 8-0 ID 1d6b:0003 Linux Foundation 3.0 root hub

IOMMU group 56:[1022:57a4] 42:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

[1022:7901] 47:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

IOMMU group 57:[1022:57a4] 42:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Matisse PCIe GPP Bridge

[1022:7901] 48:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51)

[2:0:0:0] disk ATA Samsung SSD 870 1B6Q /dev/sdb 1.00TB

IOMMU group 58:[144d:a80a] 43:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO

[N:2:6:1] disk Samsung SSD 980 PRO 2TB__1 /dev/nvme2n1 2.00TB

IOMMU group 59:[8086:1539] 44:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

IOMMU group 60:[8086:2723] 45:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)

IOMMU group 61:[1000:0072] 49:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)

[4:0:0:0] disk ATA ST6000VN0033-2EE SC60 /dev/sdj 6.00TB

[4:0:1:0] disk ATA ST6000VN0041-2EL SC61 /dev/sdk 6.00TB

[4:0:2:0] disk ATA ST6000VN0033-2EE SC60 /dev/sdl 6.00TB

[4:0:3:0] disk ATA ST6000VN0033-2EE SC60 /dev/sdm 6.00TB

[4:0:4:0] disk ATA ST6000VN0041-2EL SC61 /dev/sdn 6.00TB

[4:0:5:0] disk ATA ST14000NM001G-2K SN03 /dev/sdo 14.0TB

[4:0:6:0] disk ATA ST14000NM001G-2K SN03 /dev/sdp 14.0TB

[4:0:7:0] disk ATA ST6000VN0033-2EE SC60 /dev/sdq 6.00TB

IOMMU group 62:[1987:5016] 4a:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)

[N:3:1:1] disk Viper M.2 VP4100__1 /dev/nvme3n1 2.00TB

IOMMU group 63:[1987:5016] 4b:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)

[N:4:1:1] disk Viper M.2 VP4100__1 /dev/nvme4n1 2.00TB

IOMMU group 64:[1987:5016] 4c:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)

[N:5:1:1] disk Viper M.2 VP4100__1 /dev/nvme5n1 2.00TB

IOMMU group 65:[1987:5016] 4d:00.0 Non-Volatile memory controller: Phison Electronics Corporation E16 PCIe4 NVMe Controller (rev 01)

[N:6:1:1] disk Viper M.2 VP4100__1 /dev/nvme6n1 2.00TB

IOMMU group 66:[1022:148a] 4e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

IOMMU group 67:[1022:1485] 4f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP

IOMMU group 68:[1022:1482] 60:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 69:[1022:1482] 60:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 70:[1022:1482] 60:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 71:[1022:1482] 60:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 72:[1022:1482] 60:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 73:[1022:1482] 60:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 74:[1022:1484] 60:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 75:[1022:1482] 60:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge

IOMMU group 76:[1022:1484] 60:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]

IOMMU group 77:[1022:148a] 61:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function

IOMMU group 78:[1022:1485] 62:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP





CPU Thread Pairings

Pair 1:cpu 0 / cpu 24

Pair 2:cpu 1 / cpu 25

Pair 3:cpu 2 / cpu 26

Pair 4:cpu 3 / cpu 27

Pair 5:cpu 4 / cpu 28

Pair 6:cpu 5 / cpu 29

Pair 7:cpu 6 / cpu 30

Pair 8:cpu 7 / cpu 31

Pair 9:cpu 8 / cpu 32

Pair 10:cpu 9 / cpu 33

Pair 11:cpu 10 / cpu 34

Pair 12:cpu 11 / cpu 35

Pair 13:cpu 12 / cpu 36

Pair 14:cpu 13 / cpu 37

Pair 15:cpu 14 / cpu 38

Pair 16:cpu 15 / cpu 39

Pair 17:cpu 16 / cpu 40

Pair 18:cpu 17 / cpu 41

Pair 19:cpu 18 / cpu 42

Pair 20:cpu 19 / cpu 43

Pair 21:cpu 20 / cpu 44

Pair 22:cpu 21 / cpu 45

Pair 23:cpu 22 / cpu 46

Pair 24:cpu 23 / cpu 47



USB Devices

Bus 001 Device 001 Port 1-0ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 002 Device 001 Port 2-0ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 002 Device 002 Port 2-2ID 21c4:0cd1 Lexar USB Flash Drive

Bus 003 Device 001 Port 3-0ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 004 Device 001 Port 4-0ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 005 Device 001 Port 5-0ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 005 Device 002 Port 5-4ID 05e3:0608 Genesys Logic, Inc. Hub

Bus 005 Device 003 Port 5-5ID 0414:a002 Giga-Byte Technology Co., Ltd USB Audio

Bus 005 Device 004 Port 5-4.1ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard

Bus 005 Device 005 Port 5-4.2ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS

Bus 005 Device 006 Port 5-4.3ID 0bda:8771 Realtek Semiconductor Corp. Bluetooth Radio

Bus 005 Device 007 Port 5-6ID 048d:8297 Integrated Technology Express, Inc. IT8297 RGB LED Controller

Bus 006 Device 001 Port 6-0ID 1d6b:0003 Linux Foundation 3.0 root hub

Bus 007 Device 001 Port 7-0ID 1d6b:0002 Linux Foundation 2.0 root hub

Bus 007 Device 002 Port 7-5ID 8087:0029 Intel Corp. AX200 Bluetooth

Bus 007 Device 003 Port 7-6ID 05e3:0608 Genesys Logic, Inc. Hub

Bus 008 Device 001 Port 8-0ID 1d6b:0003 Linux Foundation 3.0 root hub



SCSI Devices

[0:0:0:0]disk Lexar USB Flash Drive 1100 /dev/sda 61.8GB

[2:0:0:0]disk ATA Samsung SSD 870 1B6Q /dev/sdb 1.00TB

[3:0:0:0]disk ATA ST6000VN0033-2EE SC60 /dev/sdc 6.00TB

[3:0:1:0]disk ATA ST14000NM001G-2K SN03 /dev/sdd 14.0TB

[3:0:2:0]disk ATA ST14000NM001G-2K SN03 /dev/sde 14.0TB

[3:0:3:0]disk ATA ST6000VN0033-2EE SC60 /dev/sdf 6.00TB

[3:0:4:0]disk ATA ST14000NM001G-2K SN03 /dev/sdg 14.0TB

[3:0:5:0]disk ATA ST14000NM001G-2K SN03 /dev/sdh 14.0TB

[3:0:6:0]disk ATA ST14000NM001G-2K SN03 /dev/sdi 14.0TB

[4:0:0:0]disk ATA ST6000VN0033-2EE SC60 /dev/sdj 6.00TB

[4:0:1:0]disk ATA ST6000VN0041-2EL SC61 /dev/sdk 6.00TB

[4:0:2:0]disk ATA ST6000VN0033-2EE SC60 /dev/sdl 6.00TB

[4:0:3:0]disk ATA ST6000VN0033-2EE SC60 /dev/sdm 6.00TB

[4:0:4:0]disk ATA ST6000VN0041-2EL SC61 /dev/sdn 6.00TB

[4:0:5:0]disk ATA ST14000NM001G-2K SN03 /dev/sdo 14.0TB

[4:0:6:0]disk ATA ST14000NM001G-2K SN03 /dev/sdp 14.0TB

[4:0:7:0]disk ATA ST6000VN0033-2EE SC60 /dev/sdq 6.00TB

[N:0:6:1]disk Samsung SSD 980 PRO 2TB__1 /dev/nvme0n1 2.00TB

[N:1:1:1]disk Corsair MP400__1 /dev/nvme1n1 8.00TB

[N:2:6:1]disk Samsung SSD 980 PRO 2TB__1 /dev/nvme2n1 2.00TB

[N:3:1:1]disk Viper M.2 VP4100__1 /dev/nvme3n1 2.00TB

[N:4:1:1]disk Viper M.2 VP4100__1 /dev/nvme4n1 2.00TB

[N:5:1:1]disk Viper M.2 VP4100__1 /dev/nvme5n1 2.00TB

[N:6:1:1]disk Viper M.2 VP4100__1 /dev/nvme6n1 2.00TB

     

    media-diagnostics-20230329-0934.zip

    server keeps freezing up when trying to do parity rebuild

    in General Support

    Posted · Edited by dandiodati

    I had an error on my parity disk so I changed it to another drive and have been trying to rebuild it and my server just keep freezing up (requires a hard reboot) when the parity is rebuild is running. 

    I had the array started in maintenance mode too. I was also mirroring the syslog into the flash drive but don't see any errors in the syslog.

     

    Here is my diagnostics from a couple days ago.

     

    I have two mini sas controller cards in the machine: LSI Logic SAS9211-8I 8PORT Int 6GB Sata+SAS Pcie 2.0 & SAS9211-8I 8PORT Int 6GB Sata+SAS Pcie 2.0 and tried replacing sata cables and moving cables to different cards but still the same result.

     

    Been trying since last week and very frustrated.

    media-diagnostics-20230325-2255.zip

    [Support] for atribe's repo Docker images

    in Docker Containers

    Posted

    SpeedTestForInfluxDB seems to no longer work. I downgraded from influx 2 back to 1.8.6 since it broke too many things.

     

    But the speed test is no longer working (was working before) and

    get the following in the logs:

     

    Loading Configuration File config.ini
    Configuration Successfully Loaded
    2021-06-09 20:32:17,631 - DEBUG: Testing connection to InfluxDb using provided credentials
    2021-06-09 20:32:17,634 - DEBUG: Successful connection to InfluxDb
    2021-06-09 20:32:17,634 - INFO: Starting Speed Test For Server None
    2021-06-09 20:32:17,664 - DEBUG: Setting up SpeedTest.net client
    Traceback (most recent call last):
    File "/src/influxspeedtest.py", line 8, in <module>
    collector.run()
    File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 173, in run
    self.run_speed_test()
    File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 121, in run_speed_test
    self.setup_speedtest(server)
    File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 71, in setup_speedtest
    self.speedtest = speedtest.Speedtest()
    File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1091, in __init__
    self.get_config()
    File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1174, in get_config
    map(int, server_config['ignoreids'].split(','))
    ValueError: invalid literal for int() with base 10: ''
    Loading Configuration File config.ini
    Configuration Successfully Loaded
    2021-06-09 20:50:45,047 - DEBUG: Testing connection to InfluxDb using provided credentials
    2021-06-09 20:50:45,050 - DEBUG: Successful connection to InfluxDb
    2021-06-09 20:50:45,050 - INFO: Starting Speed Test For Server None
    2021-06-09 20:50:45,058 - DEBUG: Setting up SpeedTest.net client
    Traceback (most recent call last):
    File "/src/influxspeedtest.py", line 8, in <module>
    collector.run()
    File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 173, in run
    self.run_speed_test()
    File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 121, in run_speed_test
    self.setup_speedtest(server)
    File "/src/influxspeedtest/InfluxdbSpeedtest.py", line 71, in setup_speedtest
    self.speedtest = speedtest.Speedtest()
    File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1091, in __init__
    self.get_config()
    File "/usr/local/lib/python3.7/site-packages/speedtest.py", line 1174, in get_config
    map(int, server_config['ignoreids'].split(','))
    ValueError: invalid literal for int() with base 10: ''

    [Support] Partition Pixel - Chia

    in Docker Containers

    Posted

    On 5/7/2021 at 8:27 AM, burgess22 said:

    Nice work boss...I nutted out how to build the docker from reddit the other day and then fix common problems popped up tonight and found an issue because you have put a template up...winning now I can plot away happily and and get auto updates in CA 🍻

     

     

    one thing you might want to add is a how to start plotting once docker is up and running I assume from the console it will be 

    venv/bin/chia plots create -b 5000 -r 2 -n 1 -t /plotting/plot1 -d /plots 

     

    I've always started my from the terminal window using 

     

    docker exec -it chia venv/bin/chia plots create -b 5000 -r 2 -n 1 -t /plotting/plot1 -d /plots

     

    -b is amount of ram you want to give

    -r is the amount of threads 

    -n is the number of plots you want to queue

    -t is temp dir

    -d is the completed directory

     

    and if you want to run in Parallel just run the command in another terminal window as many times as your rig will allow

    Thanks for the details just one thing I'm not clear on is that with this command line how to you chose your plotting sizes ? Basically I saw in the UI the ability to choose different plotting sizes but with this command line tool does not seem to indicate it. I need to determine how many I can run on a SSD and not run out of space?

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    On 11/27/2019 at 10:20 AM, dandiodati said:

    Still have not been able to get letsencrypt to reverse proxy for unms. MothyTim sent me his configuration on a previous post but still did not work. 

    The regular login redirects me fine just the websocket does not work therefore unms device discovery etc dont work correctly.

     

    Anyone else have luch with unms ? 

     

    I'm using the nico640/docker-unms docker container which starts find and works correctly (websockets included) when I connect directly to it.

    I attached my letsencrypt nginx/proxy-confs/unms.subdomain.conf configuration. 

    I have a custom network bridge step up for the letsencypt container and unms (also have nextcloud in there which works correctly).

    My DNS is setup correct at cloudflare with A name for main ip address and C names for unms and nextcloud pointing to it.

     

    Any ideas or help for solving this issue ? Been fighting with it for a long time with no solution.

     

    Dan

     

     

    unms.subdomain.conf 1.42 kB · 0 downloads

    Has anyone else gotten unms working behind swag ? Still have issues with the websocket failing to passthrough.

    I tried again using the pages https://help.ui.com/hc/en-us/articles/115015690207-UNMS-Reverse-Proxy and testing with https://help.ui.com/hc/en-us/articles/115015690147 but no luck. The external curl with websockets just causes swag to show its default web page instead of forward to the unms container.

     

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted

    5 minutes ago, dandiodati said:

    Still have not been able to get letsencrypt to reverse proxy for unms. MothyTim sent me his configuration on a previous post but still did not work. 

    The regular login redirects me fine just the websocket does not work therefore unms device discovery etc dont work correctly.

     

    Anyone else have luch with unms ? 

     

    I'm using the nico640/docker-unms docker container which starts find and works correctly (websockets included) when I connect directly to it.

    I attached my letsencrypt nginx/proxy-confs/unms.subdomain.conf configuration. 

    I have a custom network bridge step up for the letsencypt container and unms (also have nextcloud in there which works correctly).

    My DNS is setup correct at cloudflare with A name for main ip address and C names for unms and nextcloud pointing to it.

    On i did notice this error in letsencypt log but does not see to cause any issues:

    nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
    nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

     

    Any ideas or help for solving this issue ? Been fighting with it for a long time with no solution.

     

    Dan

     

     

    unms.subdomain.conf

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by dandiodati

    On 10/8/2019 at 12:06 PM, dandiodati said:

    Anyone else have luck setting up letsencrypt and unms ? I have both services running in docker containers. If I send a websocket request (curl --insecure --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host: example.com:80" --header "Origin: http://example.com:80" --header "Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==" --header "Sec-WebSocket-Version: 13" https://192.168.x.x:443/)  then the nginx service within letsencrypt container just redirects me to its default home page instead of the unms container. If I use a regular https request then I do get redirected to the unms container(The login page). So something is weird with trying to connect as a websocket container which is needed for discovery. I tried the setting above too but no luck.  

    Still have not been able to get letsencrypt to reverse proxy for unms. MothyTim sent me his configuration on a previous post but still did not work. 

    The regular login redirects me fine just the websocket does not work therefore unms device discovery etc dont work correctly.

     

    Anyone else have luch with unms ? 

     

    I'm using the nico640/docker-unms docker container which starts find and works correctly (websockets included) when I connect directly to it.

    I attached my letsencrypt nginx/proxy-confs/unms.subdomain.conf configuration. 

    I have a custom network bridge step up for the letsencypt container and unms (also have nextcloud in there which works correctly).

    My DNS is setup correct at cloudflare with A name for main ip address and C names for unms and nextcloud pointing to it.

     

    Any ideas or help for solving this issue ? Been fighting with it for a long time with no solution.

     

    Dan

     

     

    unms.subdomain.conf

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by dandiodati

    On 9/28/2019 at 8:20 AM, MothyTim said:

    This is the config I've ended up with after much eperimentation! Devices show up and I'm able to add them and manage them!

    Cheers,

    Tim 

    
# make sure that your dns has a cname set for unms and that your unms container is not using a base url

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name unms.YOURDOMAIN.com;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_unms unms;
        proxy_pass https://$upstream_unms:443;
        proxy_cache off;
    	proxy_store off;
    	proxy_buffering off;
        
        proxy_set_header Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_set_header X-Real-IP $remote_addr;
    	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    	proxy_set_header X-Forwarded-Proto $scheme;
    	proxy_set_header Referer "";

    	client_max_body_size 0;
    }

}

     

    Anyone else have luck setting up letsencrypt and unms ? I have both services running in docker containers. If I send a websocket request (curl --insecure --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host: example.com:80" --header "Origin: http://example.com:80" --header "Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==" --header "Sec-WebSocket-Version: 13" https://192.168.x.x:443/)  then the nginx service within letsencrypt container just redirects me to its default home page instead of the unms container. If I use a regular https request then I do get redirected to the unms container(The login page). So something is weird with trying to connect as a websocket container which is needed for discovery. I tried the setting above too but no luck.  

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by dandiodati

    On 9/28/2019 at 8:20 AM, MothyTim said:

    This is the config I've ended up with after much eperimentation! Devices show up and I'm able to add them and manage them!

    Cheers,

    Tim 

    
# make sure that your dns has a cname set for unms and that your unms container is not using a base url

server {
    listen 443 ssl;
    listen [::]:443 ssl;

    server_name unms.YOURDOMAIN.com;

    include /config/nginx/ssl.conf;

    client_max_body_size 0;

    # enable for ldap auth, fill in ldap details in ldap.conf
    #include /config/nginx/ldap.conf;

    location / {
        # enable the next two lines for http auth
        #auth_basic "Restricted";
        #auth_basic_user_file /config/nginx/.htpasswd;

        # enable the next two lines for ldap auth
        #auth_request /auth;
        #error_page 401 =200 /login;

        include /config/nginx/proxy.conf;
        resolver 127.0.0.11 valid=30s;
        set $upstream_unms unms;
        proxy_pass https://$upstream_unms:443;
        proxy_cache off;
    	proxy_store off;
    	proxy_buffering off;
        
        proxy_set_header Host $http_host;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "Upgrade";
        proxy_set_header X-Real-IP $remote_addr;
    	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    	proxy_set_header X-Forwarded-Proto $scheme;
    	proxy_set_header Referer "";

    	client_max_body_size 0;
    }

}

     

    HI Tim thanks for the response, I just got a chance to try it and did not work for me. When I make the websocket CURL request the letsencrypt nginx server just gives me the default page. Getting very frustrated since i can hit the unms port directly and it works just not through this reverse proxy.

     

    If you do this call does it work for you ?

     

    curl --insecure --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host: example.com:80" --header "Origin: http://example.com:80" --header "Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==" --header "Sec-WebSocket-Version: 13" https://unms.yourserver.com

    (Change the unms.yourserver.com to yours, reset does not matter)

     

    [Support] Linuxserver.io - SWAG - Secure Web Application Gateway (Nginx/PHP/Certbot/Fail2ban)

    in Docker Containers

    Posted · Edited by dandiodati

    On 9/5/2019 at 10:39 AM, MothyTim said:

    I found this on Ubiquity’s website, not sure what I need from it to make UNMS work? Like I said previously I can get the GUI page but can’t see my devices, that was by editing the UniFi template!

     

    Hoping that someone with mor knowledge can help? 

    
map $http_upgrade $connection_upgrade {
  default upgrade;
  ''      close;
}

server {
  listen 80;
  server_name unms.example.com;

  client_max_body_size 4G;

  location / {
    proxy_redirect off;
    proxy_set_header Host $host;
    proxy_pass http://127.0.0.1:8080/;
  }
}

server {
  listen 443 ssl http2;
  server_name unms.example.com;

  ssl_certificate     /etc/letsencrypt/live/unms.example.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/unms.example.com/privkey.pem;

  ssl on;

  set $upstream 127.0.0.1:8443;

  location / {
    proxy_pass     https://$upstream;
    proxy_redirect https://$upstream https://$server_name;

    proxy_cache off;
    proxy_store off;
    proxy_buffering off;
    proxy_http_version 1.1;
    proxy_read_timeout 36000s;

    proxy_set_header Host $http_host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $connection_upgrade;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Referer "";

    client_max_body_size 0;
  }
}

     

    Have you found a solution for this I also have been trying to solve it and tried these options without luck. One thing I found out is that you can manually test the websocket call via this command: curl --insecure --include --no-buffer --header "Connection: Upgrade" --header "Upgrade: websocket" --header "Host: example.com:80" --header "Origin: http://example.com:80" --header "Sec-WebSocket-Key: dGhlIHNhbXBsZSBub25jZQ==" --header "Sec-WebSocket-Version: 13" https://192.168.x.x:443/

     

    (Found it on this page https://help.ubnt.com/hc/en-us/articles/115015690147-UNMS-Device-Discovery#blocking discover)

     

    And I noticed that the websocket call does not work going through the nginx proxy. I can make it work if I go directly to the unms server and port. And I also can access the UI, just the registry does not work due to the websocket calls not going though the nginx/letsencrypt reverse proxy. 

    Any one else have any luck with unms ?

    [support] digiblur's Docker Template Repository

    in Docker Containers

    Posted

    On 3/25/2019 at 4:20 PM, dandiodati said:

    I tried out the UNMS but when I tried to start it up the web ui fails and gave a posgres error in the logs, did you have to make any changes or did it just startup fine ?

    Tried with the latest version after removing the container and image anyone else get it working recently ?

     

    ...
    /var/run/postgresql:5432 - no response
    Waiting for postgres to come up...
    Starting postgres...
    {"name":"netflow","hostname":"9668b2b4b120","pid":323,"level":50,"msg":"Failed to get DB schema version: connect ECONNREFUSED 127.0.0.1:5432","time":"2019-03-27T07:33:32.105Z","v":0}
    /var/run/postgresql:5432 - no response
    Waiting for postgres to come up...
    Starting postgres...
    /var/run/postgresql:5432 - no response
    ...
    Starting postgres...
    {"name":"netflow","hostname":"9668b2b4b120","pid":323,"level":50,"msg":"Failed to get DB schema version: connect ECONNREFUSED 127.0.0.1:5432","time":"2019-03-27T07:35:02.156Z","v":0}

    ...

    It seems like the docker image is not able to create all the configuration files on start up. Under the /config directory its supposed to create a postgres directory with a bunch of configuration files but not able to do so when I point it to a /mnt/users/... volume on a unraid share. Thinking it could be a permission issue but tried changing permissions but still does not create the needed files. Anyone else seen this ?

    [support] digiblur's Docker Template Repository

    in Docker Containers

    Posted · Edited by dandiodati

    I tried out the UNMS but when I tried to start it up the web ui fails and gave a posgres error in the logs, did you have to make any changes or did it just startup fine ?

    Tried with the latest version after removing the container and image anyone else get it working recently ?

     

    ...
    /var/run/postgresql:5432 - no response
    Waiting for postgres to come up...
    Starting postgres...
    {"name":"netflow","hostname":"9668b2b4b120","pid":323,"level":50,"msg":"Failed to get DB schema version: connect ECONNREFUSED 127.0.0.1:5432","time":"2019-03-27T07:33:32.105Z","v":0}
    /var/run/postgresql:5432 - no response
    Waiting for postgres to come up...
    Starting postgres...
    /var/run/postgresql:5432 - no response
    ...
    Starting postgres...
    {"name":"netflow","hostname":"9668b2b4b120","pid":323,"level":50,"msg":"Failed to get DB schema version: connect ECONNREFUSED 127.0.0.1:5432","time":"2019-03-27T07:35:02.156Z","v":0}

    ...

    Can't install plugins from github

    in General Support (V5 and Older)

    Posted

    I have been trying to install tvheadend plugin and it keeps failing when trying to connect to download it.

     

    So I put the tvheadend_mod.plg file into the config/plugins directory

    and then I ran installplg tvheadend_mod.plg and got and ssl certificate authtentication error:

    root@Media:/boot/config/plugins# installplg tvheadend_mod.plg

    installing plugin: tvheadend_mod

    file /boot/config/plugins/tvheadend/tv_grab_file: downloading from http://dl.dropbox.com/u/19960175/unRAID/tv_grab_file ... Cookie coming from dl.dropboxusercontent.com attempted to set domain to dl.dropboxusercontent.com

    Cookie coming from dl.dropboxusercontent.com attempted to set domain to dl.dropboxusercontent.com

    ERROR: cannot verify dl.dropboxusercontent.com's certificate, issued by `/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert SHA2 High Assurance Server CA':

      Unable to locally verify the issuer's authority.

    To connect to dl.dropboxusercontent.com insecurely, use `--no-check-certificate'.

    bad download, deleting

     

    I found out that this is occuring during the wget command within the installplg script, and can produce the same error

    by running wget https://github.com/downloads/W-W/unRAID/tvheadend.png

     

    I tried it in both cases to add the --no-check-certificate but that still fails with this error:

    OpenSSL: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure

    Unable to establish SSL connection.

     

    It seems like ssl handshaking is always failing.

     

    I tried upgrading from unraid 5.0.0 to latest 5.0.5, but still the same error. :(

     

    Anyone know how to solve this issue ?

     

    Dan