BurntOC

Members
  • Posts

    160
  • Joined

  • Last visited

Posts posted by BurntOC

  1. This server, and the other  one I referenced, are on 6.12.8.

     

    I checked the usb.ini file and I think it looks okay (pasted code block below).   I'm not sure I follow on the USB Manager code block.  Are you suggesting I copy the code from one or both of the replies above into a manually created path and file, then assign the executable permission?   If I uninstalled the plugin altogether and reinstalled, would I be able to get it to automatically create the startup stuff and restore my current assignments?

     

    
    [001/002]
    connected = ""
    bus = 001
    dev = 002
    ID_VENDOR_FROM_DATABASE = "Ports=4
     Power=0mA
    "
    ID_VENDOR_ID = "0bda"
    ID_MODEL = ""
    ID_MODEL_ID = 5411
    USBPort = "1-1"
    class = "hub"
    parents = "usb1,0000:00:15.0,pci0000:00"
    ID_SERIAL = "Generic_4-Port_USB_2.0_Hub"
    isSerial = ""
    isSerialPath = ""
    
    [001/004]
    connected = 1
    bus = 001
    dev = 004
    ID_VENDOR_FROM_DATABASE = "Silicon Labs"
    ID_VENDOR_ID = "10c4"
    ID_MODEL = "CP2102N_USB_to_UART_Bridge_Controller"
    ID_MODEL_ID = "ea60"
    USBPort = "1-1.1"
    class = "interface"
    parents = "1-1,usb1,0000:00:15.0,pci0000:00"
    ID_SERIAL = "Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_5e2708b05fbcea11944693e368aed703"
    isSerial = 1
    isSerialPath = "usb-Silicon_Labs_CP2102N_USB_to_UART_Bridge_Controller_5e2708b05fbcea11944693e368aed703-if00-port0"
    virsherror = ""
    VM = "Home Assistant"
    virsh = "Device attached successfully
    
    "
    connectmethod = "Manual"
    connectmap = "Device"
    
    [001/006]
    connected = 1
    bus = 001
    dev = 006
    ID_VENDOR_FROM_DATABASE = "Silicon Labs"
    ID_VENDOR_ID = "10c4"
    ID_MODEL = "SkyConnect_v1.0"
    ID_MODEL_ID = "ea60"
    USBPort = "1-1.2"
    class = "interface"
    parents = "1-1,usb1,0000:00:15.0,pci0000:00"
    ID_SERIAL = "Nabu_Casa_SkyConnect_v1.0_9c33dedc57e2ed11b233ec5162c613ac"
    isSerial = 1
    isSerialPath = "usb-Nabu_Casa_SkyConnect_v1.0_9c33dedc57e2ed11b233ec5162c613ac-if00-port0"
    virsherror = ""
    VM = "Home Assistant"
    virsh = "Device attached successfully
    
    "
    connectmethod = "Manual"
    connectmap = "Device"
    
    [002/001]
    connected = ""
    bus = 002
    dev = 001
    ID_VENDOR_FROM_DATABASE = "Ports=7
     Power=0mA
    "
    ID_VENDOR_ID = "1d6b"
    ID_MODEL = ""
    ID_MODEL_ID = 0003
    USBPort = "2-0"
    class = "roothub"
    parents = "0000:00:15.0,pci0000:00"
    ID_SERIAL = "Linux_6.1.74-Unraid_xhci-hcd_xHCI_Host_Controller_0000:00:15.0"
    isSerial = ""
    isSerialPath = ""
    
    [002/002]
    connected = ""
    bus = 002
    dev = 002
    ID_VENDOR_FROM_DATABASE = "Ports=4
     Power=0mA
    "
    ID_VENDOR_ID = "0bda"
    ID_MODEL = ""
    ID_MODEL_ID = 0411
    USBPort = "2-1"
    class = "hub"
    parents = "usb2,0000:00:15.0,pci0000:00"
    ID_SERIAL = "Generic_4-Port_USB_3.0_Hub"
    isSerial = ""
    isSerialPath = ""
    
    [002/003]
    connected = ""
    bus = 002
    dev = 003
    ID_VENDOR_FROM_DATABASE = "Ports=2
     Power=0mA
    "
    ID_VENDOR_ID = "0bda"
    ID_MODEL = ""
    ID_MODEL_ID = 0415
    USBPort = "2-6"
    class = "hub"
    parents = "usb2,0000:00:15.0,pci0000:00"
    ID_SERIAL = "Generic_2-Port_USB_3.0_Hub"
    isSerial = ""
    isSerialPath = ""
    
    [004/001]
    ishub = 1
    connected = ""
    parents = "vhci_hcd.0,platform"
    bus = 004
    dev = 001
    ID_VENDOR_FROM_DATABASE = "Linux Foundation"
    ID_VENDOR_ID = "1d6b"
    ID_MODEL = "USB_IP_Virtual_Host_Controller"
    ID_MODEL_ID = 0003
    USBPort = "usb4"
    class = ""
    ID_SERIAL = "Linux_6.1.74-Unraid_vhci_hcd_USB_IP_Virtual_Host_Controller_vhci_hcd.0"
    isSerial = ""
    isSerialPath = ""
    bNumInterfaces = ""

     

  2. 19 minutes ago, SimonF said:

    Which vers of the plug and unraid are you running

     

    Does this file exist 

    root@computenode:~# cat /etc/libvirt/hooks/qemu.d/USB_Manager 
    #!/usr/bin/env php

    <?php

    #begin USB_MANAGER
    if ($argv[2] == 'prepare' || $argv[2] == 'stopped'){
          shell_exec("/usr/local/emhttp/plugins/usb_manager/scripts/rc.usb_manager vm_action '{$argv[1]}' {$argv[2]} {$argv[3]} {$argv[4]}  >/dev/null 2>&1 & disown") ;
    }
    #end USB_MANAGER
    ?>
    root@computenode:~# 

     

    @SimonF Thanks for the quick response. Under hooks I don't have any subfolders - qemu.d or otherwise - so that cat command is giving me an error.  Only thing there atm is a qemu file. I checked one of my other servers and it actually doesn't even have the hooks folder under libvirt (but it's not running USB Manager either, just an FYI).

  3. Anyone having a problem with devices auto-attaching on server or VM start?  I've had it configured that way since Day 1 and it worked great for almost a year, but the last couple of months it seems to ignore that setting and I still have to go in to click "VM ATTACH" to get my Zwave and Zigbee sticks to show up in my HA VM.  Maybe something got corrupted when I was tweaking to switch my Zigbee stick out for a newer one with a better chipset.

    Open to any fixes, even blowing it away and starting over but IIRC I tried that from the GUI about 6 weeks ago and it didn't resolve this for me.

  4. 2 hours ago, SimonF said:

    No both ways work the same its just the a usb connected to that port will be passed through to a VM, but if you change the device it would pass that new device. With name its does not matter which port you connect it do it will map it to the VM.

     

    So if they stay in the same ports either can work.

     

    That's what I figured as I worked my slow mind through it, but I'm glad I asked to be sure.  Thanks for the response, and for the great plugin.

    • Thanks 1
  5. Greetings, all.  I have a Home Assistant VM running and I've been passing my Z-wave and Zigbee dongles to it successfully for a long time.  Now Zigbee2MQTT is getting twitchy, which appears to be an open issue with the newer versions and my hardware, but I am trying to minimize any hiccups.  As passing both dongles seem to work whether or not I map them both as ports, both as devices, or one of each (even though they both show as CP210N UART Bridges in the USB Manager mapping, my question is this:

     

    Is one of those configurations preferable over the others?  Even when I pass as port I set the devices /dev/serial/by-id in Home Assistant, so it doesn't seem to matter but I just wanted to double-check.

  6. Fixed it myself.  In case this helps others, here's my template, through you'd want to verify the network type and paths match what you want. 

     

    <?xml version="1.0"?>
    <Container version="2">
      <Name>NextPVR</Name>
      <Repository>nextpvr/nextpvr_amd64:stable</Repository>
      <Registry>https://hub.docker.com/r/nextpvr/nextpvr_amd64</Registry>
      <Network/>
      <MyIP/>
      <Shell>bash</Shell>
      <Privileged>false</Privileged>
      <Support/>
      <Project/>
      <Overview>NextPVR TV recording and video player software.</Overview>
      <Category>MediaApp:Video</Category>
      <WebUI>http://[IP]:[PORT:8866]/index.html</WebUI>
      <TemplateURL/>
      <Icon>https://hub.docker.com/r/nextpvr/nextpvr_amd64</Icon>
      <ExtraParams>--security-opt=no-new-privileges</ExtraParams>
      <PostArgs/>
      <CPUset/>
      <DateInstalled>1695046806</DateInstalled>
      <DonateText/>
      <DonateLink/>
      <Requires/>
      <Config Name="Recordings" Target="/recordings" Default="" Mode="rw" Description="Recordings Folder" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/media/recordings</Config>
      <Config Name="Buffer" Target="/buffer" Default="" Mode="rw" Description="Live TV Folder" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/nextpvr/buffer</Config>
      <Config Name="Configuration" Target="/config" Default="" Mode="rw" Description="Configuration Path" Type="Path" Display="always" Required="false" Mask="false">/mnt/user/appdata/nextpvr/config/</Config>
    </Container>

     

    • Like 1
  7. Hi all, revisiting this after some successful tests a couple years back.  I'm ready to migrate from Unifi and I've gotten one of my two new switches adopted, though I did enable cloud access to do that.  I'd strongly prefer NOT to enable cloud access, so now that I've disabled it I cannot for the life of me get the controller to show the second switch I want to adopt.  The controller and the switches are on different subnets and VLANs, but I believe the port for the container (Unraid GUEST interface VLAN/net) and the switch (INFRA VLAN/net) have the PVID and tagged VLANs set properly, and I can ping back and forth both ways.  I also have all the 29810-29816 ranges,18043, 27001 (and actually just all the dang high ports for now) opened between the two on the firewall.  Lastly, I've gone into the new switch interface and told it the IP of the controller.  All that done and I just cannot get it to show. 

     

    I figure many of you are running standalone with cloud access disabled.  Any advice on how I can resolve this?

  8. 1 hour ago, BurntOC said:

    Did y'all ever fix this?  The ongoing instability issues I have had with 6.12.x on my 11th gen i5 drove me to downgrade back to 11.5, but none of my containers will start.  They are giving the same messages you were seeing.

     

    Seems like deleting my docker image fixed it.

  9. I noticed a FCP error today that said my /var/log was getting full.  In looking at it, the culprit seems to be that the logs are getting spammed by these 3 messages over and over.

     

    Aug  9 07:41:58 myunraidserver kernel: XFS (dm-0): Internal error !xfs_dir2_namecheck(dep->name, dep->namelen) at line 466 of file fs/xfs/xfs_dir2_readdir.c.  Caller xfs_dir2_leaf_getdents+0x220/0x322 [xfs]
    Aug  9 07:41:58 myunraidserver kernel: CPU: 10 PID: 1579 Comm: find Tainted: P    BU  W  O       6.1.38-Unraid #2
    Aug  9 07:41:58 myunraidserver kernel: Call Trace:

     

    Any idea what might cause this, and how I can fix it? My array is xfs, as you can see from the message, and I have a single parity.  Also a cache drive that's xfs, fwiw.  Also, the 6.1.38 reference looks interesting to me.  I'm not sure what that's referencing, but I'm on version 6.12.3.

     

     

  10. On 7/24/2023 at 1:12 AM, binhex said:

    do you mean the arrs are sharing the qbittorrentvpn containers network?, if so check out Q25:-  https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

     

    So weird....I'm on vacation and thought I'd pop it to check for an update and it seems I somehow didn't post the reply I'd typed out somewhere.  Anyway, I'm not routing any containers through another container.  I have a quad NIC with each port having one or two VLANs and each of those with their on /24 subnet.  The *arrs and this container are on the same VLAN and each has a static IP assigned in the same subnet.  It is working for over 20 other containers, but I can't get them to be able to connect to this one for some reason.

  11. What is the secret to getting other containers (like Sonarr) to be able to connect to this??  I had hotio's version running, then decided to switch to OpenVPN to avoid some logging issues.  Each of my *arrs and this container are on the same /24 subnet and I even just used the same IP and login credentials as the hotio container.  No dice, they won't connect.  They can ping this container, but not access it.  I'm using the default ports (except for the peer of course) and I've tried putting 8080 in vpn input ports, output ports, both, neither, and it fails every time.  

  12. On 7/7/2023 at 12:11 PM, metalchad said:

    Were you able to find a resolution to your issue with your MariaDB containers? I'm experiencing the same issue on 6.11.5 but was not previously upgraded to 6.12.1

     

    UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
    The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
    UMASK corrected from 022 to 0640 ...
    230707 14:09:14 mysqld_safe Logging to '/config/databases/608d93154c87.err'.
    230707 14:09:14 mysqld_safe Starting mariadbd daemon with databases from /config/databases
    Caught SIGTERM signal!
    cat: /var/run/mysqld/mysqld.pid: No such file or directory

     

    EDIT:

    Looking into the referenced log I found

    [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.12. You must start up and shut down MariaDB 10.7 or earlier.

    So, I changed the tag in the repository field to  :10.5.12

    Chances are you have a similar log entry

     

    Sorry for the delay - I'm not getting notifications on this.  Been a crazy month so my memory is shot, honestly, but IIRC I just restored via my appdata backups.

  13. So 6.12.x was giving me fits.  I downgraded back to 6.11.5, but I also had to use mover and dynamix file manager to move my files off cache and reformat back to xfs, then put the files back on (since 6.11 didn't natively support zfs).  My other containers are starting fine, but I have 3 Mariadb dockers that are throwing errors like this:

     

    Caught SIGTERM signal!
    UMASK corrected from 022 to 0640 ...
    230628 16:41:31 mysqld_safe Logging to '/config/databases/c6cc2824f233.err'.
    230628 16:41:31 mysqld_safe Starting mariadbd daemon with databases from /config/databases

     

    I tried changing the UMASK to 0640 in the template but it seems to revert.  I tried copying the directory from an extracted backup and it fails with a different error.  Thought maybe permissions needed to be reset to nobody:users and 744 like the others, but the error remains the same:

     

    ───────────────────────────────────────
    GID/UID
    ───────────────────────────────────────
    
    User UID:    99
    User GID:    100
    ───────────────────────────────────────
    
    Setting Up Initial Databases
    Couldn't set an owner to '/auth_pam_tool_dir/auth_pam_tool'.
    It must be root, the PAM authentication plugin doesn't work otherwise..
    
    Cannot change ownership of the '/auth_pam_tool_dir' directory
    to the 'abc' user. Check that you have the necessary permissions and try again.
    
    Installing MariaDB/MySQL system tables in '/config/databases' ...
    
    Installation of system tables failed!  Examine the logs in
    /config/databases for more information.

     

    I also have one PostgreSQL database that is erroring with this type of message, but it seems it might be continuing to launch properly after that and chmod and chowning as above didn't seem to help here either.

     

    2023-06-27 22:54:22.998 PDT [30] WARNING:  could not open statistics file "pg_stat_tmp/global.stat": Permission denied
    2023-06-27 22:54:23.008 PDT [30] LOG:  using stale statistics instead of current ones because stats collector is not responding
    2023-06-27 22:54:23.008 PDT [30] WARNING:  could not open statistics file "pg_stat_tmp/global.stat": Permission denied
    2023-06-27 22:54:40.470 PDT [243] FATAL:  could not open file "global/pg_filenode.map": Permission denied
    2023-06-27 22:55:10.539 PDT [1] LOG:  received fast shutdown request
    2023-06-27 22:55:10.539 PDT [1] LOG:  could not open file "postmaster.pid": Permission denied
    2023-06-27 22:55:10.540 PDT [1] LOG:  aborting any active transactions
    2023-06-27 22:55:10.541 PDT [1] LOG:  background worker "logical replication launcher" (PID 32) exited with exit code 1
    2023-06-27 22:55:10.541 PDT [27] LOG:  shutting down
    2023-06-27 22:55:10.542 PDT [27] PANIC:  could not open file "/var/lib/postgresql/data/global/pg_control": Permission denied
    2023-06-27 22:55:10.542 PDT [1] LOG:  checkpointer process (PID 27) was terminated by signal 6: Aborted
    2023-06-27 22:55:10.542 PDT [1] LOG:  terminating any other active server processes
    2023-06-27 22:55:10.542 PDT [31] LOG:  could not open temporary statistics file "pg_stat/global.tmp": Permission denied

     

    Any ideas why just my databases seem to be jacked and how to fix them?

     

    UPDATE - yes, the PostgreSQL db seems to be working okay for Immich.  This just seems to be a problem with my MariaDB containers.

  14. 2 hours ago, JorgeB said:

    You only extract the bz* files, not the complete zip.

     

    That's all you need.

     

    Try recreating the flash drive with a stock install then restore only the backup config.

     

    Thanks for the response.  In reading that on the Downgrade instruction page it had confused me.  I presumed I misread it as I didn't recognize them as compressed files without an extension.

     

    I ended up copying the config files from my backup last week, reformatting cache to xfs, and using previous apps to reinstall all of my containers.  Other than the fact that most didn't originally start and showed "not available" despite having installed the Docker Update Patch plugin, they seem to come up after a forced update.  I'm going to reboot when done with that, but I'm optimistic that I'm back on 6.11.5 ok.  Marking as solved for now.

     

    UPDATE - Welp, that's depressing.  Seeing all sorts of oddness now.  Can't SSH in on some of the interfaces I could before.  None of my containers autostarted as configured.  They can be manually started, but I can't access any of them.  Guess I'll have to start back with the bz file extract and restore again.

     

    UPDATE 2 - I ended up wiping my Unraid usb, copying all the files from the backup archive I made several days ago, and then copying the bz* files from the 6.11.5 as @JorgeB suggested and it seems to be working again.  

  15. So the 6.12.x firmwares have caused serious instability and performance issues with one of my two servers.  I finally decided I'd had enough and this morning I ran mover, reformatted my cache drive from zfs back to xfs, and I attempted to downgrade my firmware to 6.11.5  My understanding was that you download the zip file, extract it, and copy those files and folders over the ones on your usb.  I did that, and when I booted I realized I had a default config when I saw the server name "Tower" and it wouldn't accept my credentials.

     

    It's been probably a week since I did a server flash drive backup, in a moment of laziness this morning instead of doing that I did at least copy my existing config directory off in case I needed it.  Anyway, I copied that config directory over the one on the usb and tried to boot, but now I'm not even seeing a gui.  

     

    Can someone tell me how I fix this?

  16. 36 minutes ago, sonic6 said:

    You should open a Bug Report with your Diagnostic File 

     

    I figured out that removing macvlan via modprobe and clearing out the syslog entries for it stopped the bogus message (credit to another post here for that).  I'll probably do the diag submission, but honestly I'm tempted to wait a month or two to see if kernel updates fix it as there seems to be a number of these oddities with 11th gen systems right now.