Watch statuses are getting lost after upgrade to 4.2.1.0

[Pittiplatsch 2]

Hi,

 

I updated my Emby server from 3.5.2.0 to 4.2.1.0 in a safe testing environment. The process itself didn't had any issues, but the watch status of almost all media files for all users seems to be lost. Interestingly the status of two or three titles (of thousands) is correct. It looks like a database upgrade might got interrupted or something.

 

I couldn't figure out the problem yet. I tried to disable all plugins (esp. trakt) with no success so far. I also couldn't find any related information in the logs.

 

Since I'm on Docker and having several configurations for several environments (beta, test, production) mounted to the appropriate container, I never used a beta release of Emby with the actual production related configuration. The configuration of the test environment, I having the described issue with, is a fresh and full copy of the production config. I had problems with upgrades in the past, so I'm pretty picky never mixing up the configurations ever since.

 

It's not a big deal at the moment, I easily can continue with 3.5.2.0 and a working config, but since 4.2. solved many issues relevant to me, it would be great updating the server one day.

 

So any idea what's going on with database?

 

Thanks,

Peter

embyserver.txt

hardware_detection-63701066418.txt

[Luke 37009]

Hi there, have you run a library scan since updating?

[Pittiplatsch 2]

Hi there, have you run a library scan since updating?

Hi Luke, thanks for your suggestion. I just did a manual rescan on a single library. It actually added a couple of titles to "is played", but it's far from being complete.

 

[Luke 37009]

I would do a full scan of all libraries. You'll probably also have better success with this by first upgrading to 4.1, and then from 4.1 to 4.2. 

[Pittiplatsch 2]

I would do a full scan of all libraries. You'll probably also have better success with this by first upgrading to 4.1, and then from 4.1 to 4.2. 

Hey Luke. Updating to 4.1 first and to 4.2. after that did the trick. A rescan wasn't necessary.

 

I just tried it with the test environment. I'll give it a try with the production env in the next couple of days too. But I am sure it will work there as well, I keep you posted.

 

Many thanks, you saved the day.

 

Peter

[Luke 37009]

Thanks for the feedback.

[Pittiplatsch 2]

Hey Luke. Updating to 4.1 first and to 4.2. after that did the trick. A rescan wasn't necessary.

 

I just tried it with the test environment. I'll give it a try with the production env in the next couple of days too. But I am sure it will work there as well, I keep you posted.

 

Many thanks, you saved the day.

 

Peter

The update process for my actual production setup was working the way it was described as well. So thanks again.

 

Peter

[Luke 37009]

Thanks for the feedback.