NextPVR Forums
  • ______
  • Home
  • New Posts
  • Wiki
  • Members
  • Help
  • Search
  • Register
  • Login
  • Home
  • Wiki
  • Members
  • Help
  • Search
NextPVR Forums Public NextPVR Support Legacy (v4.x and earlier) v
« Previous 1 … 12 13 14 15 16 … 433 Next »
EPG/Schedules Direct

EPG/Schedules Direct
Epitaph
Offline

Junior Member

Posts: 20
Threads: 2
Joined: Mar 2010
#1
2019-12-12, 02:13 AM
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
Offline

Posting Freak

Ontario Canada
Posts: 53,117
Threads: 957
Joined: May 2006
#2
2019-12-12, 02:19 AM
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
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,789
Threads: 769
Joined: Nov 2003
#3
2019-12-12, 02:51 AM
also try an 'empty epg' followed by an 'update epg'
Epitaph
Offline

Junior Member

Posts: 20
Threads: 2
Joined: Mar 2010
#4
2019-12-12, 03:24 AM (This post was last modified: 2019-12-12, 03:24 AM by 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
Offline

Administrator

NextPVR HQ, New Zealand
Posts: 106,789
Threads: 769
Joined: Nov 2003
#5
2019-12-12, 03:27 AM
Are you still getting that "database disk image is malformed" message in your logs?
Epitaph
Offline

Junior Member

Posts: 20
Threads: 2
Joined: Mar 2010
#6
2019-12-12, 03:41 AM
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
Offline

Posting Freak

Ontario Canada
Posts: 53,117
Threads: 957
Joined: May 2006
#7
2019-12-12, 03:44 AM
That message is normal some channels don't have as much data as others

Martin
Epitaph
Offline

Junior Member

Posts: 20
Threads: 2
Joined: Mar 2010
#8
2019-12-12, 03:59 AM
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. Big Grin 
« Next Oldest | Next Newest »

Users browsing this thread: 1 Guest(s)



Possibly Related Threads…
Thread Author Replies Views Last Post
  EPG Schedules Direct jwalbrook 6 4,145 2020-12-07, 07:43 PM
Last Post: mvallevand
  How to delete a Schedules Direct Lineup from Version 4? mwkurt 2 1,702 2020-07-19, 02:32 PM
Last Post: mwkurt
  Schedules Direct issues artmetz 4 2,020 2020-04-22, 12:13 AM
Last Post: artmetz
  Record direct from live tv? rv0987 3 1,990 2019-11-01, 12:29 PM
Last Post: rv0987
  How do you get channel icons from Schedules Direct SilverTiger 17 6,124 2019-06-28, 02:13 AM
Last Post: sub
  Schedules direct Username and password within the config file Brucek2839 5 2,347 2019-06-16, 02:44 PM
Last Post: Brucek2839
  NextPVR with Ceton InfiniTV, Comcast Card and Schedules Direct add new channels EiEiOhh 5 5,732 2019-06-02, 12:47 AM
Last Post: EiEiOhh
  Schedules Direct Password Change weisguy 1 1,902 2018-10-01, 03:32 PM
Last Post: sub
  NextPVR and Schedules Direct defelradar 2 2,066 2018-09-20, 02:45 AM
Last Post: defelradar
  Problems with Schedules Direct for UK? andrewj 11 3,617 2018-09-02, 05:48 PM
Last Post: JEF

  • View a Printable Version
  • Subscribe to this thread
Forum Jump:

© Designed by D&D, modified by NextPVR - Powered by MyBB

Linear Mode
Threaded Mode