EPG/Schedules Direct

[Epitaph]

My EPG is beginning to show "No Show" on a bunch of channels. When I go into settings and manually update the EPG I am seeing a date error(Happens to fast to catch but it starts with "Date requested(2020-01-01) not within...". I have included my logs. Viewing the logs I see the following:

Code:

{"account":{"expires":"2020-10-01T01:33:18Z","messages":[],"maxLineups":4},"lineups":[{"lineup":"USA-OTA-23502","modified":"2019-11-09T06:39:03Z","uri":"\/20141201\/lineups\/USA-OTA-23502","name":"Local Over the Air Broadcast "}],"lastDataUpdate":"2019-12-11T21:50:37Z","notifications":[],"systemStatus":[{"date":"2015-09-08T00:00:00Z","status":"Online","message":"No known issues."}],"serverID":"20141201.web.1","datetime":"2019-12-12T00:55:40Z","code":0}
2019-12-11 19:55:40.442    [ERROR][6]    Unexpected error in EPGEvent.LoadByOID(): System.Data.SQLite.SQLiteException (0x80004005): database disk image is malformed
database disk image is malformed
   at System.Data.SQLite.SQLite3.Reset(SQLiteStatement stmt)
   at System.Data.SQLite.SQLite3.Step(SQLiteStatement stmt)
   at System.Data.SQLite.SQLiteDataReader.NextResult()
   at System.Data.SQLite.SQLiteDataReader..ctor(SQLiteCommand cmd, CommandBehavior behave)
   at System.Data.SQLite.SQLiteCommand.ExecuteReader(CommandBehavior behavior)
   at System.Data.SQLite.SQLiteCommand.ExecuteDbDataReader(CommandBehavior behavior)
   at System.Data.Common.DbCommand.ExecuteReader()
   at NUtility.EPGEvent.GetListingsForTimePeriodForChannel(Channel channel, DateTime startTime, DateTime endTime)

This is repeated several times then I see:

Code:

2019-12-11 19:55:40.519    [DEBUG][6]    Requesting /schedules
2019-12-11 19:55:41.016    [DEBUG][6]    Got /schedules:
2019-12-11 19:55:41.153    [DEBUG][6]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-29",
  "message": "Date requested (2019-12-29) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 19:55:41.153    [ERROR][6]    (3.1 - WTKR-DT): Date requested (2019-12-29) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 19:55:41.153    [DEBUG][6]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-30",
  "message": "Date requested (2019-12-30) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 19:55:41.153    [ERROR][6]    (3.1 - WTKR-DT): Date requested (2019-12-30) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 19:55:41.153    [DEBUG][6]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-31",
  "message": "Date requested (2019-12-31) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 19:55:41.153    [ERROR][6]    (3.1 - WTKR-DT): Date requested (2019-12-31) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 19:55:41.153    [DEBUG][6]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2020-01-01",
  "message": "Date requested (2020-01-01) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 19:55:41.153    [ERROR][6]    (3.1 - WTKR-DT): Date requested (2020-01-01) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 19:55:41.155    [DEBUG][6]    3.2 ThisTV
{
  "stationID": "30442",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-10",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-29",
  "message": "Date requested (2019-12-29) not within 2019-12-10 -> 2019-12-28 for stationID 30442."
}

And that repeats for other channels. NPVR and SchedulesDirect have been working fine on my system for several years, whats going on with my setup? 

Thanks

[mvallevand]

It has nothing to do with Schedules Direct you are getting database error

2019-12-10 23:24:10.048 [ERROR][9] Unexpected error doing DBHouseCleaning: constraint failed
PRIMARY KEY must be unique

and many more after that

First think I'd look at is disk space. If that is not it stop your server backup npvr.db3 and see if there are any hidden file or journals the look like they might be related to npvr.db3 delete them and then restart the server.

Martin

[sub]

also try an 'empty epg' followed by an 'update epg'

[Epitaph]

I actually tried an empty epg and update epg first, @sub. It did not work. I followed the previous instructions by @mvallevand, I have hidden files unchecked and see nothing else related to the npvr.db3. All of the other files are less than 18kb. I removed the database and restarted, added my channels back, re-attached the mappings and the issue persists. Did I miss something?

[sub]

Are you still getting that "database disk image is malformed" message in your logs?

[Epitaph]

Nope, looks like it jumped straight to the channels which are throwing up the range exceeded message.

Code:

2019-12-11 22:38:38.315    [DEBUG][7]    Doing EPG update from Schedules Direct JSON
2019-12-11 22:38:38.577    [DEBUG][7]    Using URL: https://json.schedulesdirect.org/20141201
2019-12-11 22:38:38.604    [DEBUG][7]    
{"account":{"expires":"2020-10-01T01:33:18Z","messages":[],"maxLineups":4},"lineups":[{"lineup":"USA-OTA-23502","modified":"2019-11-09T06:39:03Z","uri":"\/20141201\/lineups\/USA-OTA-23502","name":"Local Over the Air Broadcast "}],"lastDataUpdate":"2019-12-11T21:50:37Z","notifications":[],"systemStatus":[{"date":"2015-09-08T00:00:00Z","status":"Online","message":"No known issues."}],"serverID":"20141201.web.1","datetime":"2019-12-12T03:38:38Z","code":0}
2019-12-11 22:38:38.799    [DEBUG][7]    Requesting /schedules
2019-12-11 22:38:39.810    [DEBUG][7]    Got /schedules:
2019-12-11 22:38:39.940    [DEBUG][7]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-29",
  "message": "Date requested (2019-12-29) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 22:38:39.940    [ERROR][7]    (3.1 - WTKR-DT): Date requested (2019-12-29) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 22:38:39.940    [DEBUG][7]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-30",
  "message": "Date requested (2019-12-30) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 22:38:39.940    [ERROR][7]    (3.1 - WTKR-DT): Date requested (2019-12-30) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 22:38:39.940    [DEBUG][7]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-31",
  "message": "Date requested (2019-12-31) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 22:38:39.940    [ERROR][7]    (3.1 - WTKR-DT): Date requested (2019-12-31) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 22:38:39.940    [DEBUG][7]    3.1 WTKR-DT
{
  "stationID": "30441",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-11",
  "maxDate": "2019-12-28",
  "requestedDate": "2020-01-01",
  "message": "Date requested (2020-01-01) not within 2019-12-11 -> 2019-12-28 for stationID 30441."
}
2019-12-11 22:38:39.940    [ERROR][7]    (3.1 - WTKR-DT): Date requested (2020-01-01) not within 2019-12-11 -> 2019-12-28 for stationID 30441.
2019-12-11 22:38:39.941    [DEBUG][7]    3.2 WTKRDT2
{
  "stationID": "30442",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-10",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-29",
  "message": "Date requested (2019-12-29) not within 2019-12-10 -> 2019-12-28 for stationID 30442."
}
2019-12-11 22:38:39.941    [ERROR][7]    (3.2 - WTKRDT2): Date requested (2019-12-29) not within 2019-12-10 -> 2019-12-28 for stationID 30442.
2019-12-11 22:38:39.941    [DEBUG][7]    3.2 WTKRDT2
{
  "stationID": "30442",
  "serverID": "20141201.web.1",
  "code": 7020,
  "response": "SCHEDULE_RANGE_EXCEEDED",
  "minDate": "2019-12-10",
  "maxDate": "2019-12-28",
  "requestedDate": "2019-12-30",
  "message": "Date requested (2019-12-30) not within 2019-12-10 -> 2019-12-28 for stationID 30442."
}

[mvallevand]

That message is normal some channels don't have as much data as others

Martin

[Epitaph]

Just checked my guide, things are back to normal. Thanks for the help. 

I registered this account in 2010 when I first needed help, and this is the first time I have ran into another problem I needed to ask help for.