Jump to content

CHBMB

Community Developer
  • Posts

    10,620
  • Joined

  • Days Won

    51

Posts posted by CHBMB

  1. 7 hours ago, Boren3459 said:

    cool, thanks for the heads up.  I will keep messing with it, and keep an eye here just in case someone else might have solved this problem.  

    Could you give us more details on the form of the license?  Is it a text string you enter somewhere?   And if you can get OpenVPN to tell us where that information is stored a solution may be possible.

  2. latest reply: 
    Please be advised that running Access Server in docker is not supported. You may run int at your own risk.
    And yes, each time your container restarted your license key will fail. Re-adding the key will not help.
     
    I guess it is not going to work.  Before I ran it on my pfsense setup I thought I had it running flawless on Unraid a couple years ago.  Who knows maybe I am just doing something wrong.  
    It might work if you found the location that it is added to, could then conceivably add it to appdata and symlink it to it's desired location.

    Sent from my Mi A1 using Tapatalk

  3. Mylar stopped working properly for me sometime in April. Prior to that it worked like a champ, since then I've had maybe 5 downloads total. Logs attached, any ideas? Sab seems fine, Mylar has just stopped finding stuff, but can be found manually from my indexers no problem. Sonarr etc. still working fine with Sab. Thanks.
    logs.zip
    Sounds like something you should be approaching the Mylar team with

    Sent from my Mi A1 using Tapatalk

  4. I reran ./download.sh and my 404s are gone. rebooting currently, then I'll confirm if DVB is working for me now.
     
    Edit: Still the same issues. Loading the plugin times out on the splash (no DVB version or driver version in the background), and I get a "no such file or directory" when I add "--device=/dev/dvb/" to plex.
     
    CHBMB, what do you mean in your instructions when you say "Then copy the files across to the flash disk."?
     
    Copy the bzroot bzimage bzroot-gui bzmodules and bzfirmware files to your USB stick from which you boot Unraid, replacing the existing files.

    Sent from my Mi A1 using Tapatalk

  5. Mobo: X8SIL
    CPU: X3470
    RAM: 32 GiB DDR3 Single-bit ECC
    Cache is 240 GB PNY SSD and I have 2 8TB whites (one is parity)
     
    I'm trying to get a Hauppauge USB antenna to work in plex.
     
    Need any other hardware? 
    Can you tell me the exact Hauppage model please?

    Sent from my Mi A1 using Tapatalk

  6. As a user of Unraid NVIDIA _and_ tools using SQLite the delayed 6.7.2 Unraid NVIDIA release is a real problem here. We can't change back to stock Unraid. On the other side some important SQLite based tools don't work any longer. In fact it has bitten us because after applying 6.7.1 SQLite tools and SQLite dumps did overwrite backups with empty files. We simply did not expect that somebody would remove a tool like SQLite from Unraid.
     
    Now Unraid 6.7.2 is out and SQLite is back - but not for us. We have to wait for the Unraid NVIDIA 6.7.2 release. Going back to 6.7.0 without these additional security patches is no option either.
     
    So now we have lot of time to change our own SQLite tools to check for SQLite in Unraid before dumping data or whatever. New data is not coming into the house - so everything cool, no?
     
    Just some other 0.02 USD.
     
    It might be a real problem for you, it isn't for me, I've just got back from the hospital after seeing a very close relative for what may be the last time.

    That's a problem, with no solution.

    You could however downgrade to v6.6.7

    Sent from my Mi A1 using Tapatalk

    • Like 1
  7. @Mike Rando

     

    Might be helpful if you tell us what hardware you're trying to get working and what build you've tried There's no point in just keep trying the same thing and posting snippets of bash outputs, it has no context and I can't interpret that.

     

    The more information you can provide me, the more I can help, I'm busy with a lot of real life stuff at the moment, and that has priority, so when I see any post which doesn't have enough info, I'm filtering them out my brain due to time constraints.

     

     

  8. 10 minutes ago, Mike Rando said:

     

    That didn't get me an error message, but it didn't appear to do anything.

     

     

    Have you ensured this bit in the link I posted has been attended to appropriately?
     

    Quote

    Make sure you use a text editor with Linux line endings and that they're set as such.  Notepad++ if you're using Windows would be my recommendation. 

     

  9.  
    The only change from 6.7.1 to 6.7.2 that could affect this is kernel patch release from 4.19.55 to 4.19.56, and it doesn't appear like anything in that change log would account for suddenly nvidia driver not working.  A possibility is usb boot flash corruption.
     
    Nothing can be diagnosed unless you post diagnostics (Tools/Diagnostics) captured at the time the issue presents itself.
    The Nvidia drivers weren't working as I haven't built it yet.....



    Sent from my Mi A1 using Tapatalk

    • Upvote 1
  10. I can see a situation where someone has the false impression that plugins are curated by limetech, like the apple ecosystem, instead of user managed, like android.
     
    Perhaps make the warning more prominent that you are stepping off the limetech reservation when you install plugins?
    It's got a big LinuxServer logo at the top of the thread and lots of red warnings, and the first two posts go into some detail about how it works. The plugin is installed from Community Applications, with an author of LinuxServer.io

    How much clearer can we make it?


    Sent from my Mi A1 using Tapatalk

    • Like 2
    • Upvote 2
  11. It could be an option to add a check to the Update Assistant from the Fix Common Problems Plugin hat community tool already supports plugin compatibility.
     
    No, let's be honest here, the end user needs to take some responsibility with this one.

    LimeTech publishes an update, user knows that they're using an Nvidia or DVB build then you got to wait till it's done until you upgrade. As soon as I build them I post in the support thread so set up an email alert.

    Why do we need to do more and more work to essentially spoon feed?

    Come on guys, really?

    Sent from my Mi A1 using Tapatalk

    • Like 3
  12. For those of us running unRAID with the NVidia drivers, and I expect that's a fair number of users, perhaps update checks could verify that a build with the NVidia drivers is available before unRAID tells us that a new version is available? I just had to roll back as my Plex docker and my VM rely on the GPU passthrough and the NVidia drivers/tools. My Plex docker wouldn't even start with 6.7.2 because of the missing NVidia components.
     
    EDIT: it's actually worse than that... my install is hosed. The console at the server reports a 'segmentation fault'.  I've done a shutdown after logging in at the console and have backed up my /config folder. About to use the unRAID creation tool to re-do the flash drive with a clean 6.7.1 and then restore some of my config including my Pro.key file. I noticed that network config was definitely corrupt so I'll replace that with one from last night's backup of 6.7.1. Hopefully nothing much else is wrong.
     
    EDIT 2: And now it's booting and the webgui is available, but it's started another parity check. 24 hrs to go.... [emoji20]
     
    EDIT 3: Had to stop the parity check as I had to reboot after re-installing the unRAID NVidia build for 6.7.1. It didn't restart the parity check after rebooting, but I suspect I'll go ahead and start a manual parity check to ensure all is OK. At least I'm back to what appears to be a functional 6.7.1 with NVidia extensions available and my Plex docker started fine. The only files I replaced from my previous flash config were network.cfg and ident.cfg.
     
    You're using an Unraid build with Nvidia, onus is on you to check. It's nothing to do with LimeTech. Same as DVB.

    Builds will get done when I get to them. Unlikely to be today, maybe tomorrow.

    Sent from my Mi A1 using Tapatalk

    • Like 2
  13. 29 minutes ago, Mike Rando said:

    I don't see any errors in my Console, but I do in my system log:

     

    > Jun 24 07:41:57 Tower nginx: 2019/06/24 07:41:57 [error] 2482#2482: *304 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.2.123, server: , request: "POST /plugins/UnraidDVB/include/exec.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "tower", referrer: "http://tower/Settings/UnraidDVB"

     

    I looked in the network tab and there's a flurry of activity when I go to "updating avilable builds" but I can't differentiate between requests and responses. After a minute my console did show an error: 

     

    > Result checkPlugin
    > POST http://tower/plugins/UnraidDVB/include/exec.php 504 (Gateway Time-out)

    You could try this script I wrote.

     

    https://forums.unraid.net/topic/46194-plugin-linuxserverio-unraid-dvb/?do=findComment&comment=741713

  14. 3 minutes ago, Mike Rando said:

    I downloaded "Unraid DVB | LinuxServer.io" and rebooted. Haven't gotten past the splash screen to see if my TV tuner shows up.

     

    Under unRAID tools > System devices I see "Bus 002 Device 002: ID 2040:826d Hauppauge" but I saw that before I did any of this.

     

    My root problem is I want to see my Hauppauge tuner in Plex, but haven't figured out how. I was directed here. Not sure if this is even the right plugin.

    I have no idea what you mean by Unraid DVB | LinuxServer.io

     

    Have you actually downloaded one of the DVB builds?  Or read the instructions?

  15. 1 hour ago, Mike Rando said:

    I'm assuming I'm having an issue with this because when I add "--device=/dev/dvb/" to Extra Parameters in Plex, I get:

     

     > Error response from daemon: linux runtime spec devices: error gathering device information while adding custom device "/dev/dvb": no such file or directory.

     

    I try to manually add it and confirmed that "/dev/dvb/" does not exist.

     

     

     

    Have you actually downloaded a DVB build, rebooted your machine and confirmed that your device is found?

  16. 42 minutes ago, limetech said:

    For tehuti in this 6.7.1 release we're using tn40xx-0.3.6.17

    for 6.8 beta we're using tn40xx-0.3.6.17.2 - which only change supposedly is to compile against 5.x Linux kernel.

     

    For intel in 6.7.1 release, correct: 5.5.5

    for Unraid 6.8 beta - we still use stock ixgbe drivers because still Intel has not released build for Linux 5.x kernel.

    Awesome Thanks

×
×
  • Create New...