FINAL WARNING: Complete database reset is required!

[nuentes 40]

Here's the headline: I have automatic updates disabled, haven't updated Emby For Kodi for more than 2 weeks, and I got this alert this morning.

I've seen this at least 5 different times in the last 3 months. I've resolved it in the past by either restoring from backup, or just purging Emby For Kodi Next Gen, and reinstalling. I've seen it with 10.X and 11.X now as well. Actually, the first time I got it is when I upgraded from 10.X to 11.X.

It just started happening most recently this morning. We woke up, and all our Emby For Kodi content was unplayable. After a Kodi restart, it seemed to work again. I get the prompt on Kodi startup, but otherwise Emby For Kodi appears to be working normally. No changes were made to my system last night or this morning, and I have automatic updates turned off for Emby For Kodi next gen. I went to pull a log from when this occurred, but it seems the log from before we woke up has been purged now.

 

[quickmic 1571]

This message should only appear when you update from 10.X to 11.X, when you update Emby server from stable to beta and when Kodi's internal database is corrupt.

You could send me a kodi.log for review, after the message appears OR the kodi.old.log which is the one from before. Probably both.

btw, in 11.2.X which is currently under development, I'll automatically trigger the resync.

Edited March 12 by quickmic

[nuentes 40]

9 hours ago, quickmic said:

This message should only appear when you update from 10.X to 11.X, when you update Emby server from stable to beta and when Kodi's internal database is corrupt.

You could send me a kodi.log for review, after the message appears OR the kodi.old.log which is the one from before. Probably both.

btw, in 11.2.X which is currently under development, I'll automatically trigger the resync.

ok, so perhaps my kodi database keeps getting corrupt? Because I only use Emby stable and I didn't touch Emby For Kodi.

I wish I knew what I keep doing to make this happen to me so often.

The kodi.old.log was already gone. Either kodi crashed, or was closed by FireOS during the night. Then my wife opened kodi, nothing worked, and then I did a kodi restart without thinking to save a logfile - so the kodi.old was only from after the crash. Next time this happens I'll be sure to save logfiles and update this thread. I just did the full reset that was suggested (clicked 'yes'), and that appears to have resolved it. This is helpful knowing that the db file's are the actual root cause, and I can focus on those if/when this recurs, so I don't need to do a full restore from backup.

Much appreciated!

[js28194 27]

If it makes a difference, I am on the latest 11.1.24, been on it for a couple of weeks now, and suddenly two Nvidia Sheilds prompted this out of nowhere.  It's early AM so I when ahead and did the reset as requested.

[atcronin 0]

i too had this happen to 2 devices running 11.1.24.

Happened after Emby server updated from 4.8.10 to 4.8.11.

 

No logs left, but i went looking through code and wondered if this is the cause:

plugin.video.emby/emby/emby.py

 def TestConnections(self):

#

if (EmbyServerVersionPreviousCompare < EmbyServerVersionResyncCompare >= ServerVersionCompare) or (ServerVersionCompare < EmbyServerVersionPreviousCompare >= EmbyServerVersionResyncCompare):
                                Resync = ServerVersion

That seems to force a resync with every server update.

4008010 < 4009000025 >= 4008011

 

 

Edited Wednesday at 07:43 AM by atcronin

[quickmic 1571]

5 hours ago, atcronin said:

That seems to force a resync with every server update.

4008010 < 4009000025 >= 4008011

 

 

Hmm, not good. Could be the issue, I'll check that.

The reason for this line, a server upgrade from < "4.9.0.25" to >= "4.9.0.25" requires a one time only mandatory resync (due to server code modifications).

I could simplify the version check but with the lag of auto re-syncs on Server downgrades. Anyway, that's a small price to pay and will fix it once and for all.

 

 

Edited Wednesday at 01:03 PM by quickmic

[quickmic 1571]

I checked, the line should be that:

Quote

                            if (EmbyServerVersionPreviousCompare < EmbyServerVersionResyncCompare and ServerVersionCompare >= EmbyServerVersionResyncCompare) or (ServerVersionCompare < EmbyServerVersionPreviousCompare and EmbyServerVersionResyncCompare >= EmbyServerVersionPreviousCompare):

I'll double check and release a new version tomorrow.

btw, the 4.8.0.10 and 4.8.0.11 would be 4008000010 and 4008000011 and not as you reported 4008010, 4008011

[atcronin 0]

no worries, I just ran the code blocks against the version number strings reported by the server dashboard e.g. "4.8.11.0".

 

 

[atcronin 0]

oops, I entered:

ServerVersionPrevious = '4.8.10'
ServerVersion ='4.8.11'
EmbyServerVersionResync = "4.9.0.25"

Still, got there in the end.

Edited Wednesday at 11:50 PM by atcronin

[quickmic 1571]

Should be fixed by 11.1.26 beta