Jump to content

unJim

Members
  • Posts

    48
  • Joined

  • Last visited

Posts posted by unJim

  1. 9 hours ago, jonathanm said:

    You assume correctly. Any containers assigned different IP's from the host will be firewalled from the host. If you want a container to be able to access other containers using non-host IP addresses, you must assign ALL of them unique IP's (as you found out)

     

    Is there any reason for this? I would try and get this working but I'm not sure I can mess with my configuration that much, most of the dockers I have interact with another in one way or another and giving them all separate static ip addresses and changing all my firewall and port forwarding rules to match may be to much of a hassle. 

  2. 13 hours ago, alturismo said:

     

    yes, i guess u have a common setup as i do, plex, tvh and proxy all on unraid, if u assign a ip to tvhproxy it cant be accessed by the other dockers, i assume some sort of security,

    u need all dockers assign an ip ... tvh, plex and tvhproxy, then it works.

     

    the webgui of the proxy (192.x.x.x:5004) will always end up in 404, doesnt matter.

     

    Thank you alturismo, I had given up with it but it's good to know there is a solution. 

  3. I'm trying to get tvhproxy working but Plex doesn't find it, makes no difference if I supply it with the IP address of the docker.

     

    If I go to http://192.168.1.159:5004 (the IP address I have assigned to tvhproxy) with a web browser it returns a 404 error which the tvhproxy docker logs show so it's kind of running but something isn't right. Does anybody have this working?

  4. 37 minutes ago, manifest3r said:

    Correct me if I'm wrong, but I believe your parity is as fast as your slowest disk. In this case, it would be sde.

     

    I think you're correct as long as that disk is involved (during a parity check for example), disk 1 (sde) is actually only 2 tb, disk 2 and disk 3 are 3 tb and the parity disk is 4 tb. So halfway through the parity check disk 1 is finished with and things should speedup again with disk 2 now being the bottleneck. 

     

    But let's say for example I want to write to disk 2 and 3 at the same time, disk 1 isn't even spun up, I guess disk 2 would still be the bottleneck. 

     

    I'm also kind of thinking of the best way to lay them out for future upgrades, if I already have the fastest disk as parity, if / when I replace that smaller disks (because I want larger ones or one had failed) having the current speediest disk as parity would mean as I replace disks things would get incrementally faster. 

     

    Writing this out has made me realise I'm probably overthinking it :)

     

    I'll just add it as a data disk! 

  5. I have just precleared a disk to add to the array and noticed it was pretty quick;

    ############################################################################################################################
    #                                                                                                                          #
    #                                         unRAID Server Preclear of disk WDH2L9ZA                                          #
    #                                       Cycle 1 of 1, partition start on sector 64.                                        #
    #                                                                                                                          #
    #                                                                                                                          #
    #   Step 1 of 5 - Pre-read verification:                                                   [7:04:40 @ 157 MB/s] SUCCESS    #
    #   Step 2 of 5 - Zeroing the disk:                                                        [7:00:47 @ 178 MB/s] SUCCESS    #
    #   Step 3 of 5 - Writing unRAID's Preclear signature:                                                          SUCCESS    #
    #   Step 4 of 5 - Verifying unRAID's Preclear signature:                                                        SUCCESS    #
    #   Step 5 of 5 - Post-Read verification:                                                  [7:07:31 @ 155 MB/s] SUCCESS    #
    #                                                                                                                          #
    #                                                                                                                          #
    #                                                                                                                          #
    #                                                                                                                          #
    #                                                                                                                          #
    #                                                                                                                          #
    #                                                                                                                          #
    ############################################################################################################################
    #                              Cycle elapsed time: 21:13:06 | Total elapsed time: 21:13:07                                 #
    ############################################################################################################################
    
    
    ############################################################################################################################
    #                                                                                                                          #
    #                                               S.M.A.R.T. Status default                                                  #
    #                                                                                                                          #
    #                                                                                                                          #
    #   ATTRIBUTE                    INITIAL  CYCLE 1  STATUS                                                                  #
    #   5-Reallocated_Sector_Ct      0        0        -                                                                       #
    #   9-Power_On_Hours             0        21       Up 21                                                                   #
    #   183-Runtime_Bad_Block        0        0        -                                                                       #
    #   184-End-to-End_Error         0        0        -                                                                       #
    #   187-Reported_Uncorrect       0        0        -                                                                       #
    #   190-Airflow_Temperature_Cel  24       30       Up 6                                                                    #
    #   197-Current_Pending_Sector   0        0        -                                                                       #
    #   198-Offline_Uncorrectable    0        0        -                                                                       #
    #   199-UDMA_CRC_Error_Count     0        0        -                                                                       #
    #                                                                                                                          #
    #                                                                                                                          #
    #                                                                                                                          #
    ############################################################################################################################
    #   SMART overall-health self-assessment test result: PASSED                                                               #
    ############################################################################################################################
    
    
    --> ATTENTION: Please take a look into the SMART report above for drive health issues.
    
    --> RESULT: Preclear Finished Successfully!.

    So I ran the diskspeed.sh script to compare it to the other disks;

    diskspeed.sh for UNRAID, version 2.6.4
    By John Bartlett. Support board @ limetech: http://goo.gl/ysJeYV
    
    Warning: Files in the array are open. Please refer to /tmp/lsof.txt for a list
    /dev/sdb (Disk 2): 113 MB/sec avg
    /dev/sdc (Disk 3): 120 MB/sec avg
    /dev/sdd (Cache): 470 MB/sec avg
    /dev/sde (Disk 1): 89 MB/sec avg
    /dev/sdf: 163 MB/sec avg
    /dev/sdg (Parity): 124 MB/sec avg
    
    To see a graph of the drive's speeds, please browse to the current
    directory and open the file diskspeed.html in your Internet Browser
    application.

    The new disk is sdf.

     

    As it is currently empty (and is the same size as the parity disk) I just wondered if there would be a speed advantage to be had by using the new disk as parity and moving the current parity to the array?

  6. I can't seem to get hardware acceleration working within a windows 10 VM, latest drivers are installed, I've been using this VM as a workstation with the HD5450 passed through for a while and it has been working well but never used it to play media, I'm now planning on using it mainly as a HTPC but playing videos hammers the CPU so I'd like to get DXVA working.

     

    Is it possible to have DXVA working inside a windows 10 VM?

    I'm not sure if the problem is the cards compatibility with Windows 10, a driver issue, or an incompatibility with hyper V and DXVA (a Google search has lead me to believe this could be the case). 

     

    Any ideas? Does anyone have DXVA working with this card (or any other for that matter)? 

     

     

  7. 11 minutes ago, saarg said:

     

    I have never used bouquets. It's basically just a tag on every channel to easily get to a specific type of channels, right?

     

    Basically yep;

    1_0_19_1B1D_802_2_11A0000_0_0_0.jpg.e25f3832cf9383fc1a623c36715d3d4b.jpg

    channel numbers are automatically assigned to be the same as the provider and it updates itself when numbers get changed around.

    1_0_19_1B1D_802_2_11A0000_0_0_0_1.jpg.d696e070e6dcb2a73513305700b3f246.jpg

    everything is categorised and easy to find and it's all automated.

     

    When I first started playing around with this stuff it took too much babysitting, when providers moved channels around things broke. This I just set and forget.

  8. 9 minutes ago, saarg said:

     

    Ditch the dreambox and get a shield Tv and let tvheadend deal with recording and streaming to clients :)

     

    I've considered it, they do look nice :). Can't tear myself away from the dreambox at the moment though, I can't find anything that handles bouquets as well as it does (AutoBouquetMaker), it "just works".

  9. 1 hour ago, saarg said:

     

    If the problem was only with the dreambox, you might want to bug the developers to fix it. It doesn't sound like a minisatip bug if every other client works. 

     

    Yeah, I've now had tvheadend running sat>ip on port 554, it did allow me to tune into a few channels intermittently, sometimes it would work, sometimes it wouldn't, when it wouldn't it would flood the logs with;

    2017-02-24 19:11:32.352 http: 192.168.1.5: RTSP/1.0 SETUP rtsp://192.168.1.10:554/?pids=0 -- 400

    and pretty much kill the tvheadend web interface, it doesn't look like it is always asking for the correct stream.

    Has to be a problem with the sat>ip client on the dreambox. Guess I'll have to find another way.

  10. 25 minutes ago, j0nnymoe said:

    Ahh ok, not sure what else to suggest! I haven't used tvheadend itself as a satip server. Personally for my DVB-S stuff, I run a Digibit R1 which is a network satip device, which I use via tvheadend, great bit of kit.

     

    It's quit possible when I get tvheadend listening on port 554 I'll have the same issue, although I'm hoping not.

    That Digibit R1 looks nice, probably should have bought one of them instead :)

  11. 11 minutes ago, saarg said:

     

    As far as I know there is an enigma2 Plugin to connect to tvheadend. This way you could record everything on tvheadend and still use your dreambox. 

     

    Thanks, I wasn't aware of that, I currently have it set up to record to unRAID using NFS but that might actually be better, I'll look into it.

  12. Just now, j0nnymoe said:

    I think your best option would be to do the following and setup minisatip docker on your server (Make sure host networking is enabled). This should present your DVB-S card to the network as a satip device. Once you have done that, test your satip receivers (dreambox or even satip app on android for example) and if that works, I can help you on the next step :)

     

     

    Tried that, it doesn't work with the dreambox for some reason, I don't know why as it works with everything else but the dreambox doesn't get the correct frequencies from minisatip (I'm thinking the DiSEqC commands aren't getting passed through) so I gave up on that idea :)

  13. 10 minutes ago, saarg said:

     

    I forgot it uses multicast. That is a no go in bridge mode. If I remember correctly, you might be able to get it working with macvlan. Google docker and multicast and you should find some info about it. 

     

    Minisatip runs as root for some reason. 

    You can set tvheadend to run as root if you remove s6-setuidgid abc in the /etc/services.d/tvheadend/run file in the container. 

    This will be removed every time you update or edit the container template. 

    You will also have the wrong permission on all recordings and files stored by Tvheadend. 

     

    Thanks I'll give that a go, if I can get things working correctly with tvheadend running sat>ip on port 554 then I'll be one step closer to getting things working how I want :)

  14. 12 minutes ago, j0nnymoe said:

    @unJim Sorry if you have already mentioned this, but what are you trying to achieve in the grand scheme of things? what kinda devices are you trying to get live tv on?

     

    My setup is a bit more complex than the norm, I have a 90cm dish with 4 quattro LNB's connected to a 17x8 multiswitch, 1 output is connected to a dreambox (it only has a single tuner), it can be set up with 2 additional sat<ip based tuners for which I'd like to use tvheadend, I'd then be able to watch 1 channel and record 2 others. I would also like to set up a couple of kodi boxes using tvheadend as the PVR back end.

  15. 12 minutes ago, saarg said:

    The same error or just doesn't work? 

    You also need to map all the ports satip uses. I don't know which one. 

     

    No error in tvheadend as it is running on port 9983, the error is related to getting it running on port 554, it just doesn't work.

     

    I think satip needs multicast, which needs host mode, so I need to run it as root to use port 554.

     

    The minisatip docker runs in host mode and uses port 554, is it running as root? how can I make tvheadend do it?

  16. 4 minutes ago, saarg said:

     

    It's not going to be run as root. 

    Try switching to bridge mode and add a new port mapping with 9983 on the container side and 554 on the host side. 

     

    Have already tried, didn't help. I think it needs to be run in host mode for multicast to work.

  17. 4 hours ago, saarg said:

     

    Did you change the port to 554 in the tvheadend settings? Configuration --> General -- SAT>IP Server

     

    I did and it gives me this error and sets it back to 9983;

     

    14 hours ago, unJim said:

     

    
    2017-02-23 22:22:43.161 satips: RTSP port 554 specified but no root perms, using 9983
    
    2017-02-23 22:22:43.161 satips: SAT>IP Server reinitialized
    
    2017-02-23 22:22:43.161 satips:   HTTP 192.168.1.10:9981, RTSP 192.168.1.10:9983

     

     

    Looks like it needs root permissions to use port 554.

  18. 16 minutes ago, CHBMB said:

    AFAIK Mini-Satip requires you to run tvheadend in host mode.

     

    Yeah, I have given minisatip a whirl too but have encountered other issues which is why I'm trying to get sat>ip working in tvheadend.

     

    Looks like I might be right about the problem being the port;

    http://docs.tvheadend.org/webui/config_misc/

    Quote

    RTSP Port : Select RTSP port (TCP) for realtime commands from SAT>IP clients. Usually (as defined in the specification) this port is 554. But as extension, Tvheadend can use any TCP port value (which is default 9983 for non-root users). But the SAT>IP client must allow to set this value (Tvheadend client will obtain the RTSP port number automatically using the XML description). If the RTSP port value is zero, the SAT>IP server functionality is not enabled.

     

  19. Just now, saarg said:

     

    So it works if you have it in host mode?

     

    It works in host mode if I specify the port in the client, which I can do with DVBViewer, my dreambox on the other hand sees that it is available but won't tune anything (I can't specify the port on the dreambox), and watching the tvheadend logs shows it's not even trying.

     

    In bridge mode (even with port 1900 set) it is invisible in the network.

  20. I'm having some issues with the sat>ip server in tvheadend, some clients can't find the server (clients that allow me to specify the port are working okay, e.g dvbviewer), I think it could be that it's not running on the default port, changing it to port 554 gives me this...

     

    2017-02-23 22:22:43.161 satips: RTSP port 554 specified but no root perms, using 9983
    
    2017-02-23 22:22:43.161 satips: SAT>IP Server reinitialized
    
    2017-02-23 22:22:43.161 satips:   HTTP 192.168.1.10:9981, RTSP 192.168.1.10:9983

     

×
×
  • Create New...