Recordings with file size zero

[mtimmerm]

Hi,

Lately I get more and more recordings that have a filelength of zero bytes. I have included a part of the logging where the recording is started. I am not sure if there is anything wrong here:

Code: Select all

2017-Jun-16 21:52:48:   [I] rtv_content_storage_t::check_and_reload_content: Reading recorded content from recorder
2017-Jun-16 21:55:00:   [I] recorder_engine_impl::start_active_recording. Starting recording for timer 279-10450000-1497643200 on channel 10450000
2017-Jun-16 21:55:00:   [I] broker::change_channel(): sink: 8c3567b6-6d18-4194-b2cd-d045bac725a0, log channel: 10450000, client id: 63fc93d2-15ee-4609-93b9-66fa8387068c
2017-Jun-16 21:55:00:   [I] channel_manager::change_channel(): sink: 8c3567b6-6d18-4194-b2cd-d045bac725a0, channel: 10450000
2017-Jun-16 21:55:00:   [I] stream_manager::remove_stream_for_sink. Remove stream request for sink 8c3567b6-6d18-4194-b2cd-d045bac725a0
2017-Jun-16 21:55:00:   [I] stream_manager::add_stream. New stream request: channel 10450000, sink 8c3567b6-6d18-4194-b2cd-d045bac725a0, sink prio 255
2017-Jun-16 21:55:00:   [I] stream_manager::add_stream_to_existing_source. Transponder conflict: channel 10450000, sink 8c3567b6-6d18-4194-b2cd-d045bac725a0 to source 0da14b08-d8bd-4b79-ac40-fdfee8e9befc
2017-Jun-16 21:55:00:   [I] transponder_streamer::start_channel. Start request for channel 207f2074-03cf-4da7-90dd-e24222ab6854:506750:1536:2061:19165
2017-Jun-16 21:55:00:   [I] transponder_streamer::stop_idle_timer
2017-Jun-16 21:55:00:   [I] CTVSStreamSource::LoadDriver. Loading driver /var/packages/DVBLinkServer/target/sources/TVSource-2/devices/libhdhr.dev
2017-Jun-16 21:55:01:   [I] HDHR StartDevice. Starting device 336605648, frontend 0
2017-Jun-16 21:55:01:   [I] CTVSStreamSource::TuneTransponder. Transponder tuning request: diseqc 0, freq 506750, modulation 0, polarization 0, symbol rate 6900000, LOF 7, LNB selection signal 0, FEC 0
2017-Jun-16 21:55:01:   [I] HDHR get_tuning_string: a8qam256-6900:506750000
2017-Jun-16 21:55:01:   [I] HDHR SetTuner. wait_for_lock status: 1, 70
2017-Jun-16 21:55:01:   [I] dl_exclusions_t::read. Reading exclusions from /var/packages/DVBLinkServer/target/share/common/exclusions.xml
2017-Jun-16 21:55:02:   [I] tvs_program_streamer::tvs_program_streamer. Select program for nid 1536, tid 2061, sid 19165
2017-Jun-16 21:55:02:   [I] stream_manager::add_stream_to_source. Successfully added a new stream for channel 10450000, sink 8c3567b6-6d18-4194-b2cd-d045bac725a0 to source 23616569-360f-42e5-8b8a-548ef15292c0
2017-Jun-16 21:55:02:   [I] channel_manager::change_channel(): sink: 8c3567b6-6d18-4194-b2cd-d045bac725a0, ...end
2017-Jun-16 21:55:02:   [I] tvs_program_streamer::tuning_thread. Starting tuning thread for program 207f2074-03cf-4da7-90dd-e24222ab6854:506750:1536:2061:19165
2017-Jun-16 21:55:02:   [I] tvs_program_streamer::SetPATScanState. Waiting for PAT...
2017-Jun-16 21:55:02:   [I] CTVSStreamSource::AddPID. Requesting PID 0, client 207f2074-03cf-4da7-90dd-e24222ab6854:506750:1536:2061:19165
2017-Jun-16 21:55:02:   [I] HDHR add_pid. Adding pid 0
2017-Jun-16 21:55:02:   [I] CTVSStreamSource::AddPID. Requesting PID 1, client 207f2074-03cf-4da7-90dd-e24222ab6854:506750:1536:2061:19165
2017-Jun-16 21:55:02:   [I] HDHR add_pid. Adding pid 1
2017-Jun-16 21:55:02:   [I] recorder_engine_impl::update_wakeup_timers. Setting wakeup timer to fire at 1497646500
2017-Jun-16 21:55:02:   [I] recorder_engine_impl::update_wakeup_timers. Wakeup timer successfully set to 1497646500
2017-Jun-16 21:57:53:   [I] rtv_content_storage_t::check_and_reload_content: Reading recorded content from recorder
2017-Jun-16 22:02:59:   [I] rtv_content_storage_t::check_and_reload_content: Reading recorded content from recorder
2017-Jun-16 22:08:04:   [I] rtv_content_storage_t::check_and_reload_content: Reading recorded content from recorder
2017-Jun-16 22:13:09:   [I] rtv_content_storage_t::check_and_reload_content: Reading recorded content from recorder
2017-Jun-16 22:18:14:   [I] rtv_content_storage_t::check_and_reload_content: Reading recorded content from recorder


Anyone that can give me some tips?

Kind regards,

Marcel

[the_man]

A Full log files required.

[mtimmerm]

A Full log files required.

The file is to big to attach

[the_man]

make an archive or upload it to some filesharing system, and share a link to it.

[mtimmerm]

Attached the log file:


https://www.dropbox.com/s/q88kekp8hoj52 ... r.zip?dl=0

[the_man]

Where is your DVBlink server running? Is there any USB tuners connected?
Also i saw some issues regarding parsing of GuideXmltv.xml - or it is corrupted or outdated.

[mtimmerm]

Hi,

Thanks for looking in to this. I am running this on a Synology Ds214 Play. To the network I have connected HDHomeRun which a 4 tuners. This works already more then 2 years fine. Only lately I have most recordings a zero file recording. The harddisk has more than enough space.

[NRWler04]

BTW ... I have the same. I'm running it on WSE2016 ....

[the_man]

Please, make a repair of database:
http://dvblogic.com/wiki/index.php/How_ ... er.db_file

Then conduct next test:
- install and launch the VLC player (on mac and on the win pc) and press the combination Ctrl+N
- in the "Please, enter a Network URL" enter:

Code: Select all

http://www.ip-of-your-server.com:8100/mobile/?command=get_playlist_m3u

- start to play any of channels from one machine and go to Monitoring tab, (dvblink web interface) check what tuner is used
- start another VLC and start another channel (from the another transponder) and so on ...
- meanwhile check the Monitoring tab and see whether all tuners works like they should.

[mtimmerm]

Please, make a repair of database:
http://dvblogic.com/wiki/index.php/How_ ... er.db_file

Then conduct next test:
- install and launch the VLC player (on mac and on the win pc) and press the combination Ctrl+N
- in the "Please, enter a Network URL" enter:

Code: Select all

http://www.ip-of-your-server.com:8100/mobile/?command=get_playlist_m3u

- start to play any of channels from one machine and go to Monitoring tab, (dvblink web interface) check what tuner is used
- start another VLC and start another channel (from the another transponder) and so on ...
- meanwhile check the Monitoring tab and see whether all tuners works like they should.

Thanks, I will try this

[michael47]

Perhaps nothing to do, but I've also the 0 file size problem.
Not easy to be sure, because it's one or two in 1 week, but with the time it's more and more, and the last week all records from 1 mux.
With the same Mux I've also lost the EPG data (french TNT TV), i reset the configuration.
And the next days I found more 0 size files for TNT chains from this MUX.
Repair Dbrecorder do nothing.
My Workaround was be to delete all records in the db, and now it works fine since three days.
Other information. Usually I used the WEB GUI (Synology NAS) to program the record for TNT TV, but In the same time I start to use more and more the Android app to do that. And I've see sometime that i'ven't the same information’s for record status in Android and in the Web GUI.

Michael

[mtimmerm]

I have rebuild the configuration and all is working again. Thanks all for the help!

[Oceanwaves]

I also have the zero file size recording problem sometimes. This is on a DS214play with TVButler connected to an USB2 port (front of DS214play).

Last time it happened I was in holidays. When I checked the RecordedTV folder I saw that the last recording was only 0 bytes. I rebooted the NAS from remote hoping that this would fix the problem. When I returned home 2 days later I found that another 2 recordings where done with 0 byte size . This time I disconnected the TVButler from the USB port, waited some 30 seconds and reconnected it to the port. Since then, recordings are working fine again.

I don't know why the reboot didn't help. Maybe shutting down the NAS completely would have been better but I couldn't switch it on from remote.

Since the 0 byte problem happens every 3 or 4 weeks I will try to remove the TVButler from the USB port every weekend for some seconds. I hope this workaround prevents 0 byte recordings.

Oliver

[the_man]

I also have the zero file size recording problem sometimes. This is on a DS214play with TVButler connected to an USB2 port (front of DS214play).

Last time it happened I was in holidays. When I checked the RecordedTV folder I saw that the last recording was only 0 bytes. I rebooted the NAS from remote hoping that this would fix the problem. When I returned home 2 days later I found that another 2 recordings where done with 0 byte size . This time I disconnected the TVButler from the USB port, waited some 30 seconds and reconnected it to the port. Since then, recordings are working fine again.

I don't know why the reboot didn't help. Maybe shutting down the NAS completely would have been better but I couldn't switch it on from remote.

Since the 0 byte problem happens every 3 or 4 weeks I will try to remove the TVButler from the USB port every weekend for some seconds. I hope this workaround prevents 0 byte recordings.

Oliver

Your description makes me think that it is a powering issue. Tuner just can't get enough powering from USB port of the NAS. Usually powered USB HUB does the job well.