Opened 7 years ago
Closed 7 years ago
Last modified 7 years ago
#13099 closed Bug Report - General (fixed)
Unexpected warning messages from Scheduler with cardinput.schedorder = 0,
Reported by: | Peter Bennett | Owned by: | jpoet |
---|---|---|---|
Priority: | minor | Milestone: | 30.0 |
Component: | MythTV - Scheduling | Version: | v29.0 |
Severity: | medium | Keywords: | |
Cc: | Ticket locked: | no |
Description
I upgraded my Production system from 0.28 to 29.
I have 6 tuners, one of them has 0 for schedule order because I do not want it used for recording.
When I start the backend, there are 322 warning messages in the log. They appear after the message "(HandleReschedule) Reschedule requested for MATCH 0 0 0 - SchedulerInit" Here is a sample
Aug 13 11:16:12 serenity mythbackend: mythbackend[5678]: W Scheduler scheduler.cpp:4628 (AddNewRecords) Scheduler: Channel Turner Broadcasting System, Title The Guest Book Fri Aug 18 02:30:00 2017 GMT cardinput.schedorder = 0, it must be >0 to record from this input. Aug 13 11:16:12 serenity mythbackend: mythbackend[5678]: W Scheduler scheduler.cpp:4628 (AddNewRecords) Scheduler: Channel TBS HD, Title The Guest Book Fri Aug 18 02:30:00 2017 GMT cardinput.schedorder = 0, it must be >0 to record from this input.
There are 322 warning messages, but only some 90 programs are scheduled. There are 5 tuners available and only one has the schedule order of 0. I think 1 warning message would be enough.
I have now deleted that tuner and the warning messages no longer occur. However some people may want to dedicate one tuner to Live TV and therefore set the schedule order to 0, and then they would see all these extra messages.
Change History (6)
comment:1 Changed 7 years ago by
Owner: | changed from gigem to Peter Bennett |
---|---|
Status: | new → accepted |
comment:3 Changed 7 years ago by
Owner: | changed from Peter Bennett to jpoet |
---|---|
Status: | accepted → assigned |
comment:4 Changed 7 years ago by
Status: | assigned → accepted |
---|
comment:5 Changed 7 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
comment:6 Changed 7 years ago by
Milestone: | needs_triage → 30.0 |
---|---|
Version: | Unspecified → v29.0 |
I see this message only occurs if the tuner is offline and also marked with sched order of 0.
I think it is valid to set a sched order of 0 if you want to prevent recording with a particular tuner. For example you my want to reserve one tuner for live tv, or one tuner may be giving problems and you want to temporarily stop using it.
This message was added a year ago in this commit: 4cbfba5