himisk71
-
Posts
24 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by himisk71
-
-
On 14.12.2017 at 9:48 AM, saarg said:
You can try to add :xenial_test in the repository field. It's a test we did 7 months ago.
But thinking back, I think I didn't find this on my own tvheadend container when you mentioned it the last time? It was Ubuntu based.
On 17.12.2017 at 8:05 AM, himisk71 said:Ok, no problems so far! docker is working good. Only the tvheadend is not the best choice, because around this version (4.3-48) it comes to problems with lagging on some channels with the following spamming logs:
2017-12-17 07:56:40.975 [WARNING] parser: DVB-C Netzwerk/642MHz/zdf_neo HD: DVBSUB @ #540: PTS and PCR diff is very large (400498)this was solved since around version ~ 4.3-100 i think. so it has nothing to do with the docker.
hi there!
i am really happy with the ":xenial_test"-release of the docker! but is there a chance to get a updated version of this to get a newer tvheadend release? on some channels the stuttering described above is a little bit annoying..
-
On 18.12.2017 at 10:11 AM, himisk71 said:
Since i have tvheadend and embyserver in a docker (before they was installed in a ubuntu vm) i can't connect them when i have a vpn-connection. Not the webgui nor through e.g. tvhclient.
Anybody knows how i have to configure openvpn-as that i can connect them again?
I wonder if this is a configuration on the openvpn-as docker-side or is it a configuration within the other docker? e.g. like a firewall, you have to open something?
-
Since i have tvheadend and embyserver in a docker (before they was installed in a ubuntu vm) i can't connect them when i have a vpn-connection. Not the webgui nor through e.g. tvhclient.
Anybody knows how i have to configure openvpn-as that i can connect them again?
-
Ok, no problems so far! docker is working good. Only the tvheadend is not the best choice, because around this version (4.3-48) it comes to problems with lagging on some channels with the following spamming logs:
2017-12-17 07:56:40.975 [WARNING] parser: DVB-C Netzwerk/642MHz/zdf_neo HD: DVBSUB @ #540: PTS and PCR diff is very large (400498)this was solved since around version ~ 4.3-100 i think. so it has nothing to do with the docker.
-
2 hours ago, saarg said:
hmm… no reaction (beside himisk71)?
hi, sorry but had much trouble @work and the christmas time, but.....
i created a docker like you with the test build and must say : no errors, recordings work great, no transport errors or something while recording..
in short words: fantastic!!
so, because my girlfriend is a heavy user of recordings and live-tv i will test one more days with this build to see if errors will come or not.
-
10 hours ago, s.Oliver said:
oh no, not for docker on unRAID. i meant, when you setup a VM on unRAID and installing TVH inside the VM.
so which template you choose for the VM, which hardware specs you give it (ram, cores, etc.), which linux distro/version you install and on top of that how would you install/compile TVH then?
i can, but i have to work today - so in the next 1,2 days! I am not really good @linux but the overal things how i install tvh in a vm i can do..
-
i did everytime a fresh docker install.
i use the docker "Linuxserver.io - TVHeadend"
docker configuration like my older post the attached image + "--device=/dev/dvb" in the extra parameter for my "dd cine tv"
search for channels
tvheadend "/recordings/ for the records
i mean nothing really special. like i do often before.
can i do some logging that can help?
-
1 minute ago, saarg said:
Then you need to make a bug report at the tvheadend site as we don't develop the software.
But i think they will say its a docker problem (or tvh with docker problem) as tvh will work as expect in a normal installation.
Nevertheless lots of thanks! but i think i will turn back to a vm.
-
Ah, ok. But only in the tvh docker image?
I had befor tvh installed in a vm and i cant remember a crash, i could play the recordings
-
Id did install -latest / release-4.2 / stable-4.2.1 and no difference.
-
ok, i have now really a problem.
i did install the tvh docker about 10 times today with channel search etc. because of the following i can reproduce:
delete the tvh docker with image.
install new docker.
configure tvh with channelsearch.
record a channel few minutes.
try to play the recorded in the webgui (through external player vlc) OR play a recording with tvhclient.
it will come an error message from vlc and something crashed (i will logout from tvh in the same second)
error message in the unraid log:
Dec 13 18:57:42 tower kernel: traps: tvh:tcp-start[13124] general protection ip:56143abd62c9 sp:152b07181da0 error:0 in tvheadend[56143aa5f000+38c000]i delete the docker.img, i delete all configs in appdata, i do the whole day nothing other then try to get this working. can someone help me?
-
Ok, now is only one thing left. all is working very well except some entrys in the log from the unraid:
Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 Dec 9 16:22:30 tower shfs: error: shfs_rmdir, 1511: Directory not empty (39): rmdir: /mnt/cache/appdata/tvheadend/timeshift/buffer/2 -
lol, 0 or 1 is a big difference
i did the configuration from here: Configuration for DD Cards
But i did set
set append initrd=/bzroot ddbridge.msi=1instead of now:
set append initrd=/bzroot ddbridge.msi=0for now it worked (3 records, 1 live tv) - so for now its solved i think // thank you very much for give me the hint!!
-
hi there.
i have the tvheadend docker installed and configured, it worked good .....
.... until after a while i get this:
2017-12-08 21:20:42.355 linuxdvb: STV0367 DVB-C DVB-T #0 : DVB-C #0 - poll TIMEOUT 2017-12-08 21:20:50.014 linuxdvb: STV0367 DVB-C DVB-T #0 : DVB-C #0 - poll TIMEOUT 2017-12-08 21:20:57.672 linuxdvb: STV0367 DVB-C DVB-T #0 : DVB-C #0 - poll TIMEOUT 2017-12-08 21:21:05.330 linuxdvb: STV0367 DVB-C DVB-T #0 : DVB-C #0 - poll TIMEOUTon all 4 tuners from my digital device cinetv.. one after the next is dying!
after a reboot from unraid it is ok for a while. until the tuners have to work again.
-
58 minutes ago, Marv said:
After upgrading to the latest container my Emby server is stuck (even after rebooting) with the following log entry.
Cannot open assembly '/usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe': No such file or directory.
Is there another update comming to fix this?
I have the same problem:
Cannot open assembly '/usr/lib/emby-server/bin/MediaBrowser.Server.Mono.exe': No such file or directory.
-
24 minutes ago, saarg said:
Is there a reason you want to have the recordings in tvheadend? I always move them into my TV Show share. Then I have much easier access in kodi to the show
so you mean record inside the container and then move (with mover?) the records to another share?
if i would have all (epg-)information when i transfer the records to another share, i should have no problem to do that this way.. but i think i dont have, or?
i dont have only kodi, as clients i have tvhclient and emby too.
-
1 hour ago, saarg said:
Does the recordings show up in missing recordings tab?
Do you use the latest version or the stable version?
no recordings, not in the finished nor in the missing tab..
it is HTS Tvheadend 4.3-65~g016de1aae, so nearly the same i use in ubuntu.. (4.3-68~gce6f517)
its a little bit crazy, because some old configs are there (network, services, 1 user), some not (channels, recordings) and some now are double (streaming profiles..).
when i look in the recording config, there stand "/recordings/" as the recordingspath, in the old tvheadend "/home/mike/Aufnahmen"
-
ok, i tried a little bit.
1. create the docker with recording mapping container path: /home/mike/Aufnahmen (like the path in ubuntu-tvheadend) and host path: /mnt/user/Aufnahmen/
2. copy all the files and folders from .hts in ubuntu to /mnt/cache/docker/tvheadend/ where my docker config is.
3. start docker and.....: no recordings, no configs. only 2 users are there, the stream profiles 2 times now and ok, the network and services are there.
-
25 minutes ago, saarg said:
ou probably also need to have the same path for recordings inside the container
thats bad, because i have in the ubuntu mapped "/home/user/Aufnahmen" to "/mnt/user/Aufnahmen/", but in the in the docker config i write immediately "/mnt/user/Aufnahmen/".
that you cannot import "old" records is the most bad thing within tvheadend
![:-\](//content.invisioncic.com/u329766/emoticons/undecided.gif.dbe6a6da3e2da905b5453618390ca776.gif ":-\")
-
i have installed tvheadend 4.3-68~gce6f517 in an ubuntu vm. if i crate a docker with tvheadend, is there any chance to get the records (and maybe the cofigs/channels) over there?
![:-\](http://content.invisioncic.com/u329766/emoticons/undecided.gif.dbe6a6da3e2da905b5453618390ca776.gif ":-\"){kind=small}
[Support] Linuxserver.io - TVHeadend
in Docker Containers
Posted
pity but ok! and thanks for the testbuild!!