rjorgenson

Members
  • Posts

    37
  • Joined

  • Last visited

Posts posted by rjorgenson

  1. 4 hours ago, Rysz said:

     

    MODBUS is an APC protocol that needs to be specifically activated on the UPS:

     

    Note that you will have to enable Modbus communication. In the front panel of

    the UPS, go to Advanced Menu mode, under Configuration and enable Modbus.

     

    If you don't have this/want this activated you should use the driver usbhid-ups instead.

    The old version of NUT didn't include the MODBUS driver, so you were using usbhid-ups there.

     

    You will need to click "Reset Config" first to remove the configuration by the auto-config tool.

    Then set the NUT settings up as follows:

     

    grafik.thumb.png.c266407a992fa6de7066acc567d957a3.png

     

    Please let me know if that works for you! 🙂

     

     

    Thanks! I dug around in the menu on the device but couldn't find an option to enable modbus anywhere, there was an NMC setting that was network based but I decided not to mess with that and just set it up as usbhid-ups and everything worked as before =]

    • Like 1
  2. Trying to get this plugin setup to replace the outdated NUT plugin. I used the auto-config and it detected my UPS but the service wont start. When trying to start it manually form the command line it gives a timeout error.

     

    Writing NUT configuration...
    Updating permissions for NUT...
    Checking if the NUT Runtime Statistics Module should be enabled...
    Disabling the NUT Runtime Statistics Module...
    Network UPS Tools - UPS driver controller 2.8.0.1
    Network UPS Tools - NUT APC Modbus driver 0.01 (2.8.0.1)
    _apc_modbus_read_registers: Read of 516:604 failed: Connection timed out (auto)
    Can't read inventory information from the UPS
    upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
    Driver failed to start (exit status=1)
    

     

    The autoconfig sees the device plugged in over USB and says it's writing the config

     

    NUT Scanner is now searching for UPS devices...
    #####################################################
    
    [nutdev1]
    driver = "apc_modbus"
    port = "auto"
    vendorid = "051D"
    productid = "0003"
    product = "Smart-UPS 1500 FW:UPS 08.8 / ID=18"
    serial = "__REDACTED__"
    vendor = "American Power Conversion"
    bus = "005"
    device = "003"
    busport = "001"
    ###NOTMATCHED-YET###bcdDevice = "0106"
    
    #####################################################

     

    I'm not sure what could be the issue here, is this config actually written? It looks like it's trying to connect to a busport other than what is detected.

  3. 14 minutes ago, ljm42 said:

     

    Would you run these two commands please?

    openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p'
    
    openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g'

     

    Is this is an official cert provided by a certificate provider or one you generated?

     

    This is a wildacard cert provided by letsencrypt. Here is the output of those two commands.

    root@mnemos:~# openssl x509 -noout -subject -nameopt multiline -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | sed -n 's/ *commonName *= //p'
    *.rendezvous.agffa.net
    root@mnemos:~# openssl x509 -noout -ext subjectAltName -in /boot/config/ssl/certs/mnemos_unraid_bundle.pem | grep -Eo 'DNS:[a-zA-Z 0-9.*-]*' | sed 's/DNS://g'
    *.rendezvous.agffa.net
    agffa.net
    rendezvous.agffa.net
    root@mnemos:~#

     

    • Like 1
  4. FCP recently started warning me that 

    Quote

    Your mnemos_unraid_bundle.pem certificate is not valid for your system's hostname 'mnemos.rendezvous.agffa.net'. Either adjust the system name and local TLD to match the certificate, or get a certificate that matches your settings.

     

    But my subject CN appears to be set correct for a wildcard

    root@mnemos:/boot/config/ssl/certs# openssl x509 -noout -text -in mnemos_unraid_bundle.pem | grep "Subject: CN"
            Subject: CN = *.rendezvous.agffa.net
    root@mnemos:/boot/config/ssl/certs#

     and my local TLD also appears to be correct

    image.thumb.png.da526507bb62f4e068ec7b9a639d432b.png

     

    I am still on unRAID 6.9.2 if that matters.

     

  5. On 3/12/2021 at 4:49 PM, loond said:

    I would not call that a resolution, more a workaround.  The values are retained in the smart-one.cfg file, and in the top 3 browsers; chrome, firefox, and edge.  Seems like the new file isn't being read.  Any idea how to get this issue into limetech bug queue?  I've found half a dozen different threads across several forums all reporting the same thing.

    Any luck with this? It'd be nice if there was a bug thread somewhere we could follow to know when this is resolved.

  6. This same thing just happened to me last night. I am not able to SSH into the host or get to the GUI to attempt to troubleshoot/reboot but the VM's are still running and everything else seems okay. I have no idea what to do other than just do a hard reset, which seems like a not so great idea.

     

    *edit* - Also I am stubbing my GPU to a VM so my unRAID console is not available, no idea what is in there =/

  7. I have an Asus Prime x370 Pro(latest BIOS, 5603) with a Ryzen 1700X, GTX 1080, and a Samsung 960 Pro NVMe SSD that I am currently running windows on. I am attempting to run unRAID on this system and virtualize my windows system(for gaming) so I can consolidate my computers down a bit. I am also currently acquiring parts to upgrade this host to a Ryzen 3900XT on x570 a bit down the line (or maybe Ryzen 4000, or 5000? who knows).

     

    I put unRAID 6.9 beta25 on a thumb drive and am giving this a go to see how well it might or might not work before migrating all my unRAID stuff from my actual server to this new one. So far I am having terrible lag and stuttering on the VM when gaming, though it seems to run pretty much okay for normal desktop stuff(web browser, video playback, etc). Here is how I have my VM setup.

     

    • Host passthrough on the last 4 CPU cores and their threads(8 total, all isolated in unraid settings)
    • emulatorpin set to the first core and it's thread
    • 8G of memory for initial and max (I initially tried 16G as I have it to spare but read that more can cause issues so I tried with less)
    • i440fx-5.0
    • OVMF
    • hyper-v off (nvidia card)
    • passing in my game storage drive via /dev/disk/by-id with SATA driver
    • passing through my GTX 1080 with ROM BIOS from techpowerup and hex edited (only GPU in system)
    • bother motherboard and GPU sound cards being passed through
    • bridged networking
    • stubbed (via vfio plugin) NVMe samsung 960 pro (it's in it's own IOMMU group)
    • USB mouse dongle (wireless)
    • USB keyboard  (wired)

     

    Here is a list of the things I have tried, all with no success.

     

    • cpu isolation/pinning (with 4 core and their threads[8 total] as well as 3 cores and their threads)
    • emulatorpin setting
    • motherbaord audio only
    • graphics card audio only
    • no audio at all
    • passing just the NVMe drive and not the storage drive
    • rebuilt the machine using q35-5.0 instead of i440fx-5.0
    • installed a completely new instance of windows 10 to a vdisk not passing through any drives
    • various permutations of CPU cores/pinning/isolation

     

    I am at a complete loss as to what to try next. I am hoping someone can point me in the right direction every thread i've found so far has been a dead end =/ Any help would be greatly appreciated! As far as testing goes i've been using latencymon(seeing interrupt to process latency up to 71416 microseconds and DPC routine execution time as high as 30911 microseconds) as well as just firing up a game and seeing how it plays. Here is my current XML

     

    <?xml version='1.0' encoding='UTF-8'?>
    <domain type='kvm'>
      <name>Windows 10</name>
      <uuid>67a99274-6d55-5348-5429-af9ea7a40d9b</uuid>
      <metadata>
        <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/>
      </metadata>
      <memory unit='KiB'>8388608</memory>
      <currentMemory unit='KiB'>8388608</currentMemory>
      <memoryBacking>
        <nosharepages/>
      </memoryBacking>
      <vcpu placement='static'>8</vcpu>
      <cputune>
        <vcpupin vcpu='0' cpuset='4'/>
        <vcpupin vcpu='1' cpuset='12'/>
        <vcpupin vcpu='2' cpuset='5'/>
        <vcpupin vcpu='3' cpuset='13'/>
        <vcpupin vcpu='4' cpuset='6'/>
        <vcpupin vcpu='5' cpuset='14'/>
        <vcpupin vcpu='6' cpuset='7'/>
        <vcpupin vcpu='7' cpuset='15'/>
        <emulatorpin cpuset='0,8'/>
      </cputune>
      <os>
        <type arch='x86_64' machine='pc-i440fx-5.0'>hvm</type>
        <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader>
        <nvram>/etc/libvirt/qemu/nvram/67a99274-6d55-5348-5429-af9ea7a40d9b_VARS-pure-efi.fd</nvram>
      </os>
      <features>
        <acpi/>
        <apic/>
      </features>
      <cpu mode='host-passthrough' check='none'>
        <topology sockets='1' dies='1' cores='4' threads='2'/>
        <cache mode='passthrough'/>
        <feature policy='require' name='topoext'/>
      </cpu>
      <clock offset='localtime'>
        <timer name='rtc' tickpolicy='catchup'/>
        <timer name='pit' tickpolicy='delay'/>
        <timer name='hpet' present='no'/>
      </clock>
      <on_poweroff>destroy</on_poweroff>
      <on_reboot>restart</on_reboot>
      <on_crash>restart</on_crash>
      <devices>
        <emulator>/usr/local/sbin/qemu</emulator>
        <disk type='block' device='disk'>
          <driver name='qemu' type='raw' cache='writeback'/>
          <source dev='/dev/disk/by-id/ata-TOSHIBA_HDWF180_Y731Y0CVFZ1D'/>
          <target dev='hdc' bus='sata'/>
          <boot order='1'/>
          <address type='drive' controller='0' bus='0' target='0' unit='2'/>
        </disk>
        <controller type='usb' index='0' model='ich9-ehci1'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci1'>
          <master startport='0'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci2'>
          <master startport='2'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
        </controller>
        <controller type='usb' index='0' model='ich9-uhci3'>
          <master startport='4'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
        </controller>
        <controller type='pci' index='0' model='pci-root'/>
        <controller type='sata' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
        </controller>
        <controller type='virtio-serial' index='0'>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
        </controller>
        <interface type='bridge'>
          <mac address='52:54:00:fb:b2:cf'/>
          <source bridge='br0'/>
          <model type='virtio-net'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
        </interface>
        <serial type='pty'>
          <target type='isa-serial' port='0'>
            <model name='isa-serial'/>
          </target>
        </serial>
        <console type='pty'>
          <target type='serial' port='0'/>
        </console>
        <channel type='unix'>
          <target type='virtio' name='org.qemu.guest_agent.0'/>
          <address type='virtio-serial' controller='0' bus='0' port='1'/>
        </channel>
        <input type='mouse' bus='ps2'/>
        <input type='keyboard' bus='ps2'/>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/>
          </source>
          <rom file='/mnt/user/domains/roms/msi1080.rom'/>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x0a' slot='0x00' function='0x3'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x08' slot='0x00' function='0x1'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='pci' managed='yes'>
          <driver name='vfio'/>
          <source>
            <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
          </source>
          <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x045e'/>
            <product id='0x02fe'/>
          </source>
          <address type='usb' bus='0' port='1'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x046d'/>
            <product id='0xc539'/>
          </source>
          <address type='usb' bus='0' port='2'/>
        </hostdev>
        <hostdev mode='subsystem' type='usb' managed='no'>
          <source>
            <vendor id='0x04d9'/>
            <product id='0x0296'/>
          </source>
          <address type='usb' bus='0' port='3'/>
        </hostdev>
        <memballoon model='none'/>
      </devices>
    </domain>

     

  8. Having an issue with the permissions for this container. I'm trying to set the GID to 100 just like the rest of my containers but it keeps settings the permissions on all it's files to GID 101. Any idea what's going on with this? I see the below in the logs when starting the container ...

    groupmod: GID '100' already exists

    but I don't see this error for other groups that exist on the host, I'm guessing this is something it's trying to do inside the container. How can I run this container with GID 100?

  9. 3 hours ago, Coryy said:

    My docker container has not been able to start since last night, I keep getting this on a loop: https://pastebin.com/CV1Ub2aE

    This happened without me changing any settings.

     

    I've tried switching to other PIA servers, but it continues to fail with that same error. I'm not sure if I should be able to access 'http://209.222.18.222:2000' from my end when not using PIA, but that page also fails to load.

     

    Any ideas?

     

    I ran into this same issue, it looks like the VPN server I was using (CA Vancouver) either removed support for port forwarding or is just down or gone. I swapped out to Spain and everything was fine. If you check the output of the docker logs it will list all the servers that support port forwarding and it appears to be a real time check so if your server ever comes back it should show up in the list.

  10. I'm also having an issue with the sabnzbdvpn container in the last day or two. It pegs my CPU at 100% and after a while it will spawn so many processes that my system will lock up and I had to reboot to get it back (though had I known this container was doing this at the time, I probably could have just stopped it to kill the processes but didn't know that at the time). It spawns a ton of processes running `/root/prerunget.sh` which spawns a `sleep 5s` command for each one. There were also a ton of openvpn processes. The docker log if full of this.

     

    2020-01-03 18:25:16,893 DEBG 'start-script' stdout output:
    [debug] Having issues resolving name 'www.google.com', sleeping before retry...

     

  11. 2 hours ago, johnnie.black said:

    If there are 17.82GB allocated it would mean that at some point in the past the actual used space was very close to that, as new chunks are allocated as needed, usually 1GB size, but after that a lot of space was freed.

    Just so I understand what those numbers actually mean, the total space within the image is 17.82GiB and I am using 8.54GiB of it, and as more data gets added(new image downloads etc) it will fill up the gap without getting close to the 20GiB total image size? Am I understanding that right?

  12. I'm having an issue with my docker image file. It is getting close to full at 17.82GiB of 20GiB. I have done lots of searching and seen many forum posts and the solution to this was almost always some log file writing a ton of data or a container misconfiguration causing the containers volume to take up space. The best I can tell neither of these are the issue for me. The 'total' usage according to the docker settings page is 8.54GiB but the 'devid' usage is reported as 17.82GiB.

    Label: none  uuid: c648ac9f-3453-4627-a91a-866facd87c32
    	Total devices 1 FS bytes used 8.54GiB
    	devid    1 size 20.00GiB used 17.82GiB path /dev/loop2

    I don't have any old/orphaned images taking up space

    root@mnemos:~# docker images -a
    REPOSITORY                 TAG                 IMAGE ID            CREATED             SIZE
    titpetric/netdata          latest              35a988c488aa        12 hours ago        291MB
    linuxserver/tautulli       latest              0a9ad4a04ee0        31 hours ago        180MB
    linuxserver/resilio-sync   latest              7f93f70eb69d        32 hours ago        147MB
    linuxserver/sonarr         latest              60b2e12c7544        36 hours ago        638MB
    linuxserver/jackett        latest              382633bb0b33        38 hours ago        590MB
    telegraf                   alpine              4460b53d200f        45 hours ago        74.1MB
    linuxserver/ombi           latest              49c7b66ee5e5        3 days ago          400MB
    linuxserver/radarr         latest              f71d4d023fb9        3 days ago          595MB
    grafana/grafana            latest              aa7706222b78        4 days ago          256MB
    binhex/arch-delugevpn      latest              b8df8a00c94e        2 weeks ago         1.12GB
    influxdb                   latest              92ed49eb33b3        2 weeks ago         239MB
    jlesage/handbrake          latest              3e7eefee08e6        2 weeks ago         296MB
    jlesage/mkvtoolnix         latest              e4d43a6e327c        2 weeks ago         256MB
    lsiocommunity/organizr     latest              eebb3f0b61cc        3 weeks ago         67.6MB
    nicolargo/glances          latest              e11d9ef79840        4 weeks ago         618MB
    binhex/arch-sabnzbdvpn     latest              e84a82db1c8e        6 weeks ago         1.16GB
    plexinc/pms-docker         beta                bffed2f1e11c        6 weeks ago         173MB
    writl/pyload               latest              56bee8123023        2 months ago        826MB
    google/cadvisor            latest              eb1210707573        3 months ago        69.6MB
    hexparrot/mineos           latest              580613ccf129        5 months ago        508MB

    And the usage report from Container Size on the Dockers page seems to be more inline with the 'Total' usage rather than the 'devid' usage, but still not quite the same

    Name                              Container     Writable          Log
    ---------------------------------------------------------------------
    binhex-sabnzbdvpn                   1.17 GB      13.4 MB       286 kB
    binhex-delugevpn                    1.12 GB      1.93 MB      61.5 kB
    pyload                               879 MB      53.3 MB      3.23 kB
    sonarr                               744 MB       106 MB      1.22 MB
    ombi                                 629 MB       229 MB      3.20 MB
    glances                              618 MB       359 kB          0 B
    jackett                              618 MB      28.4 MB      89.1 kB
    radarr                               617 MB      22.2 MB      76.5 kB
    mineos-node                          509 MB       754 kB      52.9 kB
    plex                                 410 MB       237 MB      3.19 MB
    Netdata                              367 MB      75.7 MB       211 kB
    HandBrake                            296 MB        35 kB       105 kB
    Grafana                              256 MB          0 B      20.2 kB
    MKVToolNix                           256 MB      23.8 kB      99.8 kB
    Influxdb                             239 MB          0 B       270 kB
    tautulli                             214 MB      33.9 MB      12.8 kB
    resilio-sync                         147 MB       300 kB      19.4 MB
    telegraf                            74.1 MB          0 B      6.09 MB
    cadvisor                            69.6 MB          0 B      5.81 kB
    organizr                            67.6 MB      34.9 kB      8.10 kB

    The only thing under /var/lib/docker (which is where it says the image is mounted) that's taking up any space is the btrfs folder, which is using far more space than the image has(58G vs 20GiB).

    root@mnemos:/var/lib/docker# du -sh *
    58G	btrfs
    16K	builder
    56K	buildkit
    768K	containerd
    34M	containers
    68M	image
    144K	network
    0	plugins
    0	runtimes
    0	swarm
    0	tmp
    0	trust
    0	unraid
    4.0K	unraid-autostart
    8.0K	unraid-update-status.json
    456K	volumes

    I'm not really sure how btrfs works, or what's going on here. Can anyone shed any light into why the usage on my image is so high compared to the space being reported as used and how to remedy the situation? Am I just reading something here wrong? Any help is appreciated, thanks!

     

  13. 2 minutes ago, rjorgenson said:

    I am also experiencing this since updating the container to "e5e3..5a77" - I see the below in the docker log

    
    2018-12-18 20:14:30,977 DEBG 'start-script' stderr output:
    Error: argument "UI" is wrong: Failed to parse rule type
    
    
    2018-12-18 20:14:30,979 DEBG 'start-script' stderr output:
    Error: either "to" is duplicate, or "UI" is a garbage.

    The container is still running and things can connect to it just fine and things are still seeding, but the web UI times out.

    This appears to be the issue - https://github.com/binhex/arch-delugevpn/commit/77caf3f2fd7bae55c9c19bd7999ee864f7f32d42#diff-181aca646a6bd54fbde2c6c0736e52d8 - I checked updates and it was already pushed out. Make sure your container is up to date, this update resolved the issue for me. 

  14. 3 hours ago, Dasweb said:

    I've already done this, still no go.

     

    Not sure if I've missed something.

    I am also experiencing this since updating the container to "e5e3..5a77" - I see the below in the docker log

    2018-12-18 20:14:30,977 DEBG 'start-script' stderr output:
    Error: argument "UI" is wrong: Failed to parse rule type
    
    
    2018-12-18 20:14:30,979 DEBG 'start-script' stderr output:
    Error: either "to" is duplicate, or "UI" is a garbage.

    The container is still running and things can connect to it just fine and things are still seeding, but the web UI times out.

  15. 15 minutes ago, saarg said:

     

    That is how the security works when making macvlan in docker. The container can't talk to host. Only way around it is to set up some routing if I remember correctly. Don't know how, so use the search function of the forum to find it. 

     

    Yeah I was just reading about that shortly after I posted. I had some spare NIC's on the box so I was able setup a second interface solely for use with docker which has allowed the container to communicate with the host. Thanks for the quick reply =]

  16. So I'm trying to migrate from a standalone instance of this container to the unraid container now that I can assign IP addresses directly to containers. I'm running into an issue where the container doesn't seem to be able to reach the host(where all the services being reverse-proxied live). The container can talk to other systems on the same network with no issue but not the unraid host it is running on.

     

    # letsencrypt container to an nzbget container on unRAID
    root@73977ce49f97:/root$ nc -vz 192.168.1.10 6789
    nc: 192.168.1.10 (192.168.1.10:6789): Host is unreachable
    root@73977ce49f97:/root$
    
    # nzbget container accessible from another system on my network
    nc -vz 192.168.1.10 6789
    Connection to 192.168.1.10 6789 port [tcp/*] succeeded!
    
    # letsencrypt container can talk to systems that aren't unraid on the network
    root@73977ce49f97:/root$ nc -vz 192.168.1.11 5000
    192.168.1.11 (192.168.1.11:5000) open
    root@73977ce49f97:/root$

    Am I missing something in my configuration to make them able to talk to each other over the network? here is my container config in unraid

     

    5a851f334e1b5_ScreenShot2018-02-14at10_46_37PM.thumb.png.d4730d5c96215641cd68e532998896a0.png