Bug #863
TVheadend crashes on initial scan
0%
Description
My TVheadend install crashes on the mux initial scan. Upon reboot it can no longer connect to a secondary tuner and goes back to showing that all but one muxes are awaiting initial scan and hangs. This result has happened to me twice, I first build on mythbuntu, and now on ubuntu server 11.10.
Hardware
Device path:
Device name:
Host connection:
Frequency range:
kHz - kHz, in steps of kHz
Status
Currently tuned to:
Services:
0
Muxes:
124
Muxes awaiting initial scan:
123
Options:
Autodetect muxes enabled
idle scan enabled
Hardware:
HDHeadend server: Zotac AD10 (AMD E350 processor, 4GB RAM, 60GB HD)
DVB device: HDHomerun HDHR3-cc (Cable card network decoder)
Server Build Steps
Install ubuntu server 11.10, enable ssh
Install the following
###
#HDHomeRun Driver
###
sudo apt-get install python-software-properties
sudo add-apt-repository ppa:tfylliv/dvbhdhomerun
sudo apt-get update
sudo apt-get install dvbhdhomerun-dkms dvbhdhomerun-utils
sudo service dvbhdhomerun-utils start
###
#HDHomeRun App
###
sudo apt-get isntall hdhomerun-config
###
#TVHeadEnd
###
Add :
deb http://www.lonelycoder.com/debian/ hts main
to /etc/apt/sources.list
sudo aptitude update
sudo aptitude install hts-tvheadend
Device is on the same subnet and responds to my windows computer.
hdhomerun-config discover finds the device
History
Updated by Dan Mezyn almost 13 years ago
Updated by I just wiped out the install completely, it appears that I lose the devices from /dev/dvb/. I'm rerunning the initial scan now. I will update with results and logs.
Updated by Dan Mezyn almost 13 years ago
I turned on Write full db mux to disk. after about 24 hours the initial scan completed. I tried to run the Map DVB services to channels but it did nothing. nothing entered the logs. I then tried to manually create a few channels just to test if the video worked. VLC could not connect through TV headend, the logs showed:
Feb 02 17:35:08 dvb: "_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002" unable to configure demuxer "/dev/dvb/adapter0/demux0" for pid 2048 -- Device or resource busy
Feb 02 17:35:08 dvb: "_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002" unable to configure demuxer "/dev/dvb/adapter0/demux0" for pid 2049 -- Device or resource busy
Feb 02 17:35:08 dvb: "_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002" unable to configure demuxer "/dev/dvb/adapter0/demux0" for pid 1073 -- Device or resource busy
Feb 02 17:35:08 subscription: "RTSP" direct subscription to adapter: "HDHR1 ATSC", network: "", mux: "759,000 kHz", provider: "", service: "", quality: 100
Feb 02 17:35:18 subscription: "RTSP" unsubscribing
Feb 02 17:35:18 RTSP: 192.1.1.42: rtsp://192.1.1.109:9981/service/_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002 -- No input detected
Feb 02 17:35:18 dvb: "_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002" unable to configure demuxer "/dev/dvb/adapter0/demux0" for pid 2048 -- Device or resource busy
Feb 02 17:35:18 dvb: "_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002" unable to configure demuxer "/dev/dvb/adapter0/demux0" for pid 2049 -- Device or resource busy
Feb 02 17:35:18 dvb: "_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002" unable to configure demuxer "/dev/dvb/adapter0/demux0" for pid 1073 -- Device or resource busy
Feb 02 17:35:18 subscription: "RTSP" direct subscription to adapter: "HDHR1 ATSC", network: "", mux: "759,000 kHz", provider: "", service: "", quality: 100
Feb 02 17:35:28 subscription: "RTSP" unsubscribing
Feb 02 17:35:28 RTSP: 192.1.1.42: rtsp://192.1.1.109:9981/service/_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002 -- No input detected
Feb 02 17:35:28 HTTP: 192.1.1.42: /service/_dev_dvb_adapter0_HDHomeRun_ATSC759000000_0002 -- 404
Finally I rebooted the server and now TVheadend shows that all the channels are still awaiting initial scan, they also do not process
Should Service name or network be populated on the scan? They are all blank.
Example of Mux
Enabled Network Freq Modulation MuxID Quality
Y 207,000kHz QAM256 10368 100%
Related Services
Enabled Service Name Play Chan Name Type Provider Network Mux
y play unmapped Other 207,000kHz
y play unmapped Other 207,000kHz
y play unmapped Other 207,000kHz
y play unmapped Other 207,000kHz
y play unmapped Other 207,000kHz
I have SchedulesDirect configured, it pulls back results.
How do you choose the correct NIT -o?
Is there a way to know which DVB Network to choose? Once the process runs once choosing a new DVB network adds the muxes but they do not process.
Thank you.
Updated by Adam Sutton over 12 years ago
Updated by - Status changed from New to Invalid
I think this might be covered elsewhere, but either way its quite old. If the problem still exists please re-submit.