Jump to content

Green Dragon

Members
  • Posts

    85
  • Joined

  • Last visited

Posts posted by Green Dragon

  1. Well now today I am able to login to the webui and seeding is working fine but none of the other dockers pointing to this one (sonarr, radarr, etc) are able to connect.  As indicated before, QBitTorrentVPN is on the default (ip) bridge network while the other dockers are on a custom (macvlan) network.  All work fine otherwise.  Essentially, nothing is able to connect to QBitTorrentVPN since the last UnRaid and QBitTorrentVPN updates.  One of those updates 'fixed' something which has sporatically 'broken' QBitTorrentVPN.

     

    Ill work more on this after work tonight...  <sigh>

  2. Thanks @binhex for everything you do for the community!

     

    This docker has always worked great for me using the default (ip) bridge network and does so even today.  However, I recently found that when I try to move it to my custom (macvlan) network which all of my other media management dockers (sonarr, radarr, lidarr, sabnzbd, etc) are on the media management dockers all time out trying to connect to qbittorrentvpn and I cannot access the qbittorrentvpn docker webui.  Essentially, nothing is able to connect to it.

     

    Here are my networks:

    default unraid bridge (ip) network address: 172.16.1.100/24

    bridge (macvlan) network address: 172.16.1.168/24 (qbtvpn address. each docker has its own static address)

     

    Attached is the supervisord.log that is generated when the docker is using the custom (macvlan) network (address .168) that does not work...

     

    Thoughts?

    168.supervisord.log

  3. Hiya!

     

    Im not sure if this goes here or general support but here is my question:

     

    I have two unraid servers.  On one the Connect dropdown icon in the upper right corner is standard unraid logo, the other is a weird representation of my unraid account name (see image)

     

    image.png.b5b75b8dfca03621d9b747c6e372265f.png

     

    My OCD cannot ignore the goofy icon on the right.  Any thoughts on why this is happening and perhaps even how to fix it?

     

    Thanks!

    • Like 1
  4. 7 hours ago, ich777 said:

    Please double check in your BIOS that you've set your iGPU as the primary graphics adapter since most motherboards deactivate the iGPU when a dGPU is installed.

     

    DOH!  Sometimes I just forget to check the fuel level...  <sigh>

     

    Thank You!

  5. I recently installed a GTX1650 to add nvenc support to my test rig.

    The i7-6700k CPU has onboard graphics.  Before installing the 1650, Ispci -Dmm | grep -E 'Display|VGA' properly reported:


    0000:00:02.0 "VGA compatible controller" "Intel Corporation" "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller" -r06 -p00 "ASUSTeK Computer Inc." "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller"

     

    After installing the 1650  Ispci -Dmm | grep -E 'Display|VGA' now reports:

     

    0000:01:00.0 "VGA compatible controller" "NVIDIA Corporation" "TU116 [GeForce GTX 1650]" -ra1 -p00 "Gigabyte Technology Co., Ltd" "TU116 [GeForce GTX 1650]"

     

    GPU Statistics now only lists the 1650.

    Thoughts as to why the Intel GPU is no longer seen??

     

    Thanks!

     

  6. Hiya!

     

    I am finding conflicting results from the following question, 'Is the flash drive used for booting the UnRaid OS included in the total drive count for licensing?'

    EXAMPLE: If I have the flash drive for booting the OS along with one parity drive and five data drives do I need a Basic (6 drives) or Plus (7 drives) license?

     

    Thanks!

  7. 29 minutes ago, JonathanM said:

    Since the tower was physically moved, reseating all moveable connections like cables and PCIe cards would be my first stop, as well as verifying all the connections are identical, for example if it has a GPU as well as CPU based graphics, connecting to the "wrong" video port could make a difference.

     

    Trying safe mode or GUI mode could also give hints. Also check the router to see if it assigned a DHCP address to the ethernet's MAC, if it did, see if the GUI is available on that IP even though the boot process appears to stop on the local console.

    Tried all of your suggestions and no joy.  Still stops at random points in the boot process.

    Thanks for the suggestions!

  8. 16 hours ago, axipher said:

     

    I kept seeing this in my inbox and and didn't think someone was still running Haswell iGPU like me on my kids gaming PC.


    I can confirm that my Haswell i5-4570s would have its Intel Graphics 4600 show up as Xeon as well before I installed the Intel driver in Windows.

    Thank you very much!

  9. 9 hours ago, SimonF said:

    What do you get from

     

    lspci -Dmm | grep -E 'Display|VGA'

    cat /tmp/gpujson

    cat /boot/config/plugins/gpustat/gpustat.cfg 

    timeout -k .500 .600 intel_gpu_top -Jo - -d pci:slot=0000:00:02.0

     

    Thanks for the reply!

    Here is the output you requested:

     

    root@Battarang:~# lspci -Dmm | grep -E 'Display|VGA'
    0000:00:02.0 "VGA compatible controller" "Intel Corporation" "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller" -r06 -p00 "ASUSTeK Computer Inc." "Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller"

     

    root@Battarang:~# cat /tmp/gpujson
    Time = Sat, 12 Aug 2023 05:47:10 -0700

    root@Battarang:~# cat /boot/config/plugins/gpustat/gpustat.cfg 
    VENDOR=""
        GPUID=""
        TEMPFORMAT="C"
        DISPCLOCKS="1"
        DISPENCDEC="1"
        DISPPCIUTIL="1"
        DISPTEMP="1"
        DISPFAN="1"
        DISPPWRDRAW="1"
        DISPPWRSTATE="1"
        DISPTHROTTLE="1"
        DISPSESSIONS="1"
        UIREFRESH="1"
        UIREFRESHINT="1000"
        DISPMEMUTIL="1"
        DISP3DRENDER="1"
        DISPBLITTER="1"
        DISPVIDEO="1"
        DISPVIDENH="1"
        DISPINTERRUPT="1"
        DISPEVENT="1"
        DISPVERTEX="1"
        DISPTEXTURE="1"
        DISPSHADEREXP="1"
        DISPSEQUENCER="1"
        DISPSHADERINTER="1"
        DISPSCANCON="1"
        DISPPRIMASSEM="1"
        DISPDEPTHBLK="1"
        DISPCOLORBLK="1"
        DISPGFXTRANS="1"

     

    root@Battarang:~# timeout -k .500 .600 intel_gpu_top -Jo - -d pci:slot=0000:00:02.0

    {
            "period": {
                    "duration": 0.035772,
                    "unit": "ms"
            },
            "frequency": {
                    "requested": 0.000000,
                    "actual": 0.000000,
                    "unit": "MHz"
            },
            "interrupts": {
                    "count": 0.000000,
                    "unit": "irq/s"
            },
            "rc6": {
                    "value": 97.967684,
                    "unit": "%"
            },
            "power": {
                    "GPU": 0.000000,
                    "Package": 0.000000,
                    "unit": "W"
            },
            "imc-bandwidth": {
                    "reads": 61.424176,
                    "writes": 23.887180,
                    "unit": "MiB/s"
            },
            "engines": {
                    "Render/3D/0": {
                            "busy": 0.000000,
                            "sema": 0.000000,
                            "wait": 0.000000,
                            "unit": "%"
                    },
                    "Blitter/0": {
                            "busy": 0.000000,
                            "sema": 0.000000,
                            "wait": 0.000000,
                            "unit": "%"
                    },
                    "Video/0": {
                            "busy": 0.000000,
                            "sema": 0.000000,
                            "wait": 0.000000,
                            "unit": "%"
                    },
                    "VideoEnhance/0": {
                            "busy": 0.000000,
                            "sema": 0.000000,
                            "wait": 0.000000,
                            "unit": "%"
                    }
            }
    }root@Battarang:~# 

  10. Hita!

     

    PROBLEM: GPU Statistics is displaying stats from an old gpu

    DETAILS: I recently changed motherboards.  I went from an Intel Xeon to an Intel i7 4790.  I only just installed gpu top and gpu statistics.  When i select 'Unit ID for Dashboard(Multiple):' dropdown it lists '00:02.0: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller - 0000:00:02.0' which of course was the old gpu prior to replacement.

    Running intel_gpu_top from the console reports the following:

     

    image.thumb.png.45846435d48b8d5e9f57b51922d1aa20.png

     

    Thoughts?

  11. shutdown unraid server, pulled the drive, reinstalled from backup, restarted, VIOLA!

    this is the second time this flash drive has lost its mind (and GUID).

    the guid normally looks something like this: 53209-234590-672075320707808932

    when it fails it looks like this: 53209-234590-000000000000000000

    <idk>....

  12. I have been running a 6.11.5 server for some time now without much issue. Well, it seems my flash drive is now either corrupted or 'offline'.

    (missing key file??)   I logged in today to see this:

    image.thumb.png.550ac6a699396272afe9a7188ba2d204.png

    So, I logged in to Connect to download the backup and pro.key.  After downloading both I now see that the drive is BLACKLISTED:

    image.thumb.png.cecd7c3d368bac9493e56b59a9c91956.png

    Flash config shows a clearly invalid GUID:

     

     

    So, I have just a few key questions for clarification:

    1. Can I just install the same 6.11.5 OS on a new USB drive, boot without the backup config or pro.key, 'transfer' the license to new drive from the console' then shutdown and copy the (backup) /config to the new drive then boot to UnRaid and my good config?  I guess what im asking here is, is there any danger of corrupting my unraid server by booting to a basic (demo) usb flash drive and looking around before transferring then copying my good configs to the new drive?

    2. How the heck does this just 'happen'?  I did not transfer my license (didnt even remove the bad one) so why did my bad usb drive get automagically blacklisted?  What usb flash drive is my license now assigned to?

    3. How would YOU recover from this?

     

    Thanks!

    image.thumb.png.cecd7c3d368bac9493e56b59a9c91956.png

  13. In rutorrent, I have ratio group actions set to continue seeding regardless of the ratio (I never want them to stop seeding). I do have a ratio group action configured to change the channel to 'delete ok' once the configured seed TIME is met (as you would expect, different per tracker). I do this so that when the time comes for me to manually remove torrents I'll know which have met the trackers seed requirements and can be deleted.

    Nonetheless, once a seeded torrent exceeds a 1:1 upload ratio its marked as finished and seeding stops. I must then go in and manually start them. As configured, the channel does change to 'delete ok' once the configured seed TIME is reached so I know that the ratio rules are otherwise working. In all cases, if the ratio has not yet reached 1:1 then the torrent continues to seed. 

     

    I may have narrowed this down to the watchdog script restarting and re-initializing plugins when the VPN IP address expires or otherwise no longer works (network failure?). I think that somewhere in this process any torrents with greater that 1:1 ratio are changed to 'finished' status.  I have tried enabling the default ratio group in rtorrent.rc but this does not help.

     

    Anyone else having a similar experience?

     

    EDIT: SOLVED!

     

    After weeks of researching and testing this (and no response here) I seem to have found the reason for the problem!  The watchdog script restarts rtorrent whenever there is a problem with the vpn (as indicated above).  Part of this restart reinitializes the plugins with the following line in rtorrent.rc and /home/nobody/initplugins.sh:

     

    execute = {/bin/bash,-c,/usr/bin/sleep 10s && /usr/bin/php /usr/share/webapps/rutorrent/php/initplugins.php $WEBUI_USER &}

     

    This 'reset' appears to have the effect of causing any torrents with a ratio of 1:1 or better to stop seeding regardless of configuration.  The remarks in the files indicate that it is there so that the plugins 'rss' and 'scheduler' will work properly.  I do not use these plugins so I disabled them and commented out the line in both files.  So far (48 hours) I have not seen a problem and my initial problem is GONE!

     

    This is a great docker and i sincerely hope this saves someone else the frustration I experienced.

     

    gd

  14. 4 hours ago, bosswaz said:

    Solved my problem by isolating iommu for my radeon video card and then binding to vfio...in the tools system devices tab...took a long while to find the solution but im happier now...

    Awesome!  Could it be as simple as me needing to bind the 'Serial bus controller: Intel Corporation Comet Lake' to iommu for my 2003 server qemu issue referenced above?

  15. 13 minutes ago, SimonF said:

    There messages are likely due to the virsh client disconnecting from libvirtd are you running VMBackup or similar plugins?

    I am running VMBackup.  No other VM related plugins though.  Is this typical behavior for a plugin such as VMBackup to cause a connect/disconnect which generates a libvert I/O error every ten minutes?  Is this a reportable bug?  VMBackup?  Libvert? UnRaid?

  16. 14 minutes ago, Stan464 said:

    You may need to try an Older version of the QEMU Guest Tools / Installers. 2003 is getting very very old and good portion of things do not support it anymore.

    Seems reasonable.  Believe me when I say that I wish this software would run on a newer OS.

    Where can I find older versions of the tools?

  17. Hiya!

     

    After upgrading to 6.11.5 I am seeing the following errors in the libvirt log, about every 10 minutes:

     

    2022-11-21 02:38:20.190+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
    2022-11-21 02:48:23.307+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
    2022-11-21 02:58:26.536+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
    2022-11-21 03:08:29.686+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error
    2022-11-21 03:18:32.955+0000: 13082: error : virNetSocketReadWire:1791 : End of file while reading data: Input/output error

     

    Thoughts?

×
×
  • Create New...