Bug #1603
closed
Satellite config changed to Unset. Channel not working
Added by Blade Pif about 12 years ago.
Updated about 12 years ago.
Description
Hello,
we have some Problem on Tvheadend 3.2.34. From time to time the muxes change in the satellite config to Unset.
We have observed this on Astra 19.2 and Astra 28.2
You look at a channel, get a freeze, and if you look in the log, the info is No Satconf.
When you go to Multiplexes, you can see the sattelite config is unset.
Only solution is to remove all unset multiplexes and rescan the Sat, then it works again.
System is installed on an ubuntu Minimal 12.04 with XNMC frodo 12.0 final.
Receiver card is a TBS 5980 S2
- Status changed from New to Need feedback
Can you please check this with a build from git master, a bug was recently fixed in this area. And since we're planning the 3.4 release shortly its unlikely further updates to 3.2 will be made.
Adam
Something similar happend to me last weekend, have to reinstall server/rebuild network, so xbmc machine runs for a few hours without connection to CS, whet i check tvh later, a lot of muxes was sat conf unset.. it wasnt too paintfull for me cause, last few month i use to make a "working" backup of tvh folder so im just copy it backup over. last spotted on ce67dd9
There is definitely a bug in 3.2 in that satconf doesn't get properly copied across when setting up muxes in certain ways, can't remember if its when manually or auto adding. This has been fixed in master in last few days, so if you could check that I would appreciate it.
Adam
OK have build from git.
Aktual Version is now: 3.3.461~g0fd2aaf-dirty
I will let it run on same channel the problem occur before and give feedback in a few days.
Bladepif
hmm, nobody spoke about copying muxes from adapter to adapter. btw mux copy working allright, as i said from time to time /in my case when tvh is not connected to CS/ satconf dissapear.
My Report after a week of test with the Version compiled from Git: 3.3.461
The problem was not showing up any more.This version seem to solved this problem
Bug can be clause for 3.3.461
Thx
- Status changed from Need feedback to Fixed
- Affected Versions 3.4 added
Closing based on user feedback.
Adam
Also available in: Atom
PDF