Duplicate Recordings

[johnsonx42]

perhaps you have not noticed that your disk is full? your logs have this message all over the place:

Code:

Unexpected error saving scheduled recording: System.Data.SQLite.SQLiteException: Insertion failed because the database is full
database or disk is full
   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.ExecuteNonQuery()
   at NUtility.ScheduledRecording.Save()

[nia]

See attachments - XMLTV file and screendump of recirdings screen

[sub]

I dont know if it'll be the cause of your duplicates, but you should absolutely sort out that problem johnson spotted. That sounds pretty critical.

[johnsonx42]

as to your doubled recordings, I'm assuming you're talking about these two (edit: confirmed from the screenshot you posted):

Code:

2010-09-13 23:02:47.165    [DEBUG][7]    Requesting wake up for 'RecordingOID6039' at 18-09-2010 10:16
2010-09-13 23:02:47.165    [DEBUG][7]    Requesting wake up for 'RecordingOID6071' at 18-09-2010 10:16
2010-09-13 23:02:47.165    [DEBUG][7]    Requesting wake up for 'RecordingOID6040' at 18-09-2010 10:36
2010-09-13 23:02:47.165    [DEBUG][7]    Requesting wake up for 'RecordingOID6115' at 18-09-2010 10:36

that's from the nrecord.log earlier in the week; now here are the same two recordings from the most recent nrecord.log:

Code:

2010-09-17 21:55:25.958    [DEBUG][7]    Requesting wake up for 'RecordingOID6039' at 18-09-2010 10:16
2010-09-17 21:55:25.958    [DEBUG][7]    Requesting wake up for 'RecordingOID6640' at 18-09-2010 10:16
2010-09-17 21:55:25.958    [DEBUG][7]    Requesting wake up for 'RecordingOID6040' at 18-09-2010 10:36
2010-09-17 21:55:25.958    [DEBUG][7]    Requesting wake up for 'RecordingOID6720' at 18-09-2010 10:36

Notice how the RecordingOID for the first recording of each pair has not changed, while the second recording of each has a new OID. To me that means the first one is a one-off recording, the second is a recurring recording; NPVR therefore never changes the first recording, nor should it, while the second instance gets properly rescheduled with each EPG update. Again, the actual scheduling has happened before your logs begin, so we can't see what happened when you scheduled it (which if I had to guess I would say happened some time on the 12th).

The SQL database errors I posted above though may well be fouling up the whole works though.

[nia]

perhaps you have not noticed that your disk is full? your logs have this message all over the place:

Hmmm... not recently. I have just recorded and watched a show. I had 1,9GB left when I saw yor post just now. Deleted some stuff, but the issue remains.

[nia]

Johnson, thank you for analysing.

But these recordings are recurring recordings that I haven't touched in any way for weeks. They are simply just autoscheduled. I have not additionally set up a manual recording for them (believe me - I have more than enough Pokemon already )

What usually happens is that doubles are recorded from the same tuner.

Edit: It appears from the recurring screen, that I set up "Troldspejlet" as recurring some time before 28/8 and Pokemon before 12/7. WSo the window of initial double recoring is long passed for both.

[sub]

We need to gett rid of that database error message before its worth investigating the duplicates. If your disk is not full, then it sounds like the db3 file has somehow corrupted itself, and you maybe need to try setting it up again from scratch.

[nia]

Yikes - complete from scratch reinstall - delete all? :eek:

Well - it's beta so it's a risk. But no way to attempt a repair?

[sub]

You could try looking for some sqlite repair tool.

I dont think its necessary "beta" related. We occasionally saw people with corrupt db3 database files in GBPVR too.

[nia]

I was referring to the general risk of running beta can mean that you have to reinstall, so the risk of having to reinstall was already calculated. I did not mean to imply that it necessarily was related

For the record, the double recordings go back to before my disk space has approached the perhaps critical low disk state. I'll try to repair or else probably reinstall and post back.