Bug #4467
Autorec records two or more instances of the same show
0%
Description
Hi,
I'm currently running tvh version 4.2.2-83~gc4950973d, but I updated release 4.2 several times during the last few months.
I'm compiling tvh myself on Debian Stable (currently Stretch) for ages.
Starting a couple of weeks ago (like 3 or so, maybe a couple more) I' m facing what the title says.
I had a autorec for the daily news starting half past seven at a specific channel, that was always OK.
Suddenly tvh started to record 2 instances of the same show, with two corresponding files (duplicates) in the recording folder.
So I deleted the autorec from disc using the webif and recreated it from within Kody Krypton's epg today. But that resulted in 3 instances of the same show, not just 2.
I don't have a clue as to what's going on, but I'd really appreciate that you fix the autorec issue.
Mind you, in this case the 3 (or 2) instances of the same show are recorded at the exact same time.
I've been having another autorec issue that may or may not be related: a show that was autorec scheduled to run at a specific time. But the network repeats this broadcast at a much later time the same evening. Now, if I reboot my tvh backend beforehand (like at 10:00 AM), it would also record this repeat, later the same evening. If I don't reboot, this would not happen. Very strange...
Anyhow, the autorec for the daily news show that I made using the webif and recently resulted in duplicate recordings looks like this:
{
"enabled": true,
"title": "RTL Nieuws",
"fulltext": false,
"channel": "03d8382c52d178be7cd6ab813e393c7b",
"tag": "",
"btype": 0,
"content_type": 0,
"start": "19:20",
"start_window": "19:40",
"start_extra": 0,
"stop_extra": 0,
"weekdays": [
1,
2,
3,
4,
5,
6,
7
],
"minduration": 0,
"maxduration": 0,
"pri": 2,
"record": 0,
"retention": 0,
"removal": 0,
"maxcount": 0,
"maxsched": 0,
"config_name": "8d4b1051df415537cddc5659d7c23cec",
"brand": "",
"season": "",
"serieslink": "",
"creator": "192.168.1.5",
"comment": "Created from EPG query"
}
The autorec entry created using Kody Krypton and resulting in triple recordings looks like this:
{
"enabled": true,
"name": "RTL Nieuws",
"title": "RTL Nieuws",
"fulltext": false,
"channel": "03d8382c52d178be7cd6ab813e393c7b",
"tag": "",
"btype": 0,
"content_type": 0,
"start": "19:15",
"start_window": "19:45",
"start_extra": 0,
"stop_extra": 0,
"weekdays": [
1,
2,
3,
4,
5,
6,
7
],
"minduration": 0,
"maxduration": 0,
"pri": 2,
"record": 0,
"retention": 2147483646,
"removal": 2147483646,
"maxcount": 0,
"maxsched": 0,
"config_name": "8d4b1051df415537cddc5659d7c23cec",
"brand": "",
"season": "",
"serieslink": "",
"creator": "192.168.1.5"
}
Should I do something to help you debug this, please say what I have to do.
I'll be very happy to do anything within my capabilities to help.
I guess the first move I should make is recompiling tvh with debug symbols, right?
Cheers,
Tycho
History
Updated by bas t over 7 years ago
Hm, looking at ./configure --help, I don't see an apropriate option to compile with debug symbols, maybe that's obsolete..
Updated by bas t over 7 years ago
Forgot to mention: I'm running tvh from systemd (though I don't expect it to be relevant to the issue):
[Unit]
Description=tvheadend
Wants=network.target
After=network.target
Wants=oscam.service
After=oscam.service
[Service]
Type=forking
PIDFile=/run/tvheadend.pid
ExecStartPre=/bin/touch /home/tycho/.hts/tvheadend/epgdb.v2
ExecStartPre=/bin/rm -f /home/tycho/.hts/tvheadend/epgdb.v2
ExecStartPre=/bin/touch /home/tycho/.hts/tvheadend/epgdb.v2
ExecStartPre=/bin/chown tycho:video -R /home/tycho/.hts/tvheadend
ExecStart=/usr/src/tvheadend/build.linux/tvheadend -f -p /run/tvheadend.pid -C -u tycho -g video
ExecStop=/bin/rm /run/tvheadend.pid
Restart=always
RestartSec=5
[Install]
WantedBy=multi-user.target
Updated by bas t over 7 years ago
On a closer look, my report of triple instances of the same recording are bogus. I did not look close enough. In the end there was just the duplicate recording of yesterday, that I reported, plus a single recording from today.
I apologise for the extra noise.
However, since I've got a single recording from autorec today, I guess I'll have to investigate some more to get the details, if there are any left that is...
Let's put this issue on hold for now.
Will report back asap.
Cheers,
Tycho.
Updated by bas t over 7 years ago
Hi,
I can't reproduce the issue anymore.
The only thing that I changed is remove all the lines starting with "ExecStartPre" from my systemd startup file and recreate all autorec rules from within Kodi Krypton.
Not sure if that is even remotely related though.
I guess that this ticket is invalid and can be closed.
Cheers,
Tycho.