djhifi 55 Posted June 15, 2019 Share Posted June 15, 2019 (edited) Ok so I've recently moved to the stable channel of the Emby Server on my Synology (was beta testing .NET Core for the staff) and I've updated Emby for Kodi to the 4.0.27a version. I've resetted the database on 2 of my 3 SHIELDS (I'm going in turns), and started the new database building process. On both of those SHIELDS, the process starts but along the way in the movies library (I have a huge collection) it has already stopped twice (prompting the error message "if the problem persists, etc etc", and I have to terminate KODI and re-open it. The scan resumes from where it stopped (love this feature). But I'm afraid I'm creating a corrupted .db The scan didn't even reach TV Shows library I am trying to figure out in the logs what can possibly be going wrong but other than connection time out errors I cannot seem to pinpoint anything accurate, or something that may be happening at the SAME time on both machines than can possibly be interrupting the scan. Maybe because I'm tired as it's late right now. I will call it a day and relook at the logs tomorrow. But please if you could check those logs as well... (attached below) Quick notes: - Leia 18.2 - Emby for KODI 4.0.27a - Emby Server 4.1.1.0 - Im using Native Path (since always) - Caching images (since always) - Syncing all libraries (since always) - Syncing RT ratings (yes) - Sync empty TV Shows (no) PS: Long time user as most of the devs know, and this random stopping of the database creation never happened on both machines, out of my 3 SHIELDS, at the same time. SHIELD 1 -kodi.old.log SHIELD 2 - kodi.old.log Edited June 15, 2019 by djhifi Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted June 15, 2019 Share Posted June 15, 2019 Thanks for providing your logs, I will look into it. 1 Link to comment Share on other sites More sharing options...
djhifi 55 Posted June 15, 2019 Author Share Posted June 15, 2019 (edited) Thanks for providing your logs, I will look into it. Thanks. I will also look again and make further testing, tomorrow. Was just finishing up an edit to the first post to make it as clear as possible. I'm dying right now, I will probably start the database rebuild on that 3rd SHIELD while I sleep, to see if it goes wrong as well and have something else (or not) to report back tomorrow. Edited June 15, 2019 by djhifi Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted June 15, 2019 Share Posted June 15, 2019 Is your server still scanning your library in? It takes a while, but your server response times out. Are you able to restore the sync once restarting Kodi? Link to comment Share on other sites More sharing options...
djhifi 55 Posted June 15, 2019 Author Share Posted June 15, 2019 (edited) Is your server still scanning your library in? It takes a while, but your server response times out. Are you able to restore the sync once restarting Kodi? The server was processing quickly new added content not scanning the library in (that had already finished several hours before) at the time I was resetting+rebuilding the database on those 2 SHIELDS. That was my suspicion exactly and it seems I was right. Maybe that's really the reason, because I then resetted the database and rebuilt it on the third SHIELD and all went well. In the future I should not add new content to the server while rebuilding databases. And yes, I was able to restore the sync on both SHIELDS every time it was failing. One of the SHIELDS ended up missing 100+- TV Shows, I'm now repeating the process there though. PS: Is it too much to also reset+rebuild .db on 2 SHIELDS at the same time? Never happened before actually. But the problem is solved then. Edited June 15, 2019 by djhifi Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted June 15, 2019 Share Posted June 15, 2019 Not that I’m aware of. The server should be able to handle it, but it does seem like the server stopped responding after a while. You’d have to retry to confirm if it was due to having two syncs running. When I upgraded from server 3 to 4, the database migration took a while to finish. During that time, my server would stop responding pretty often. I left it alone for about a day and it was fine then. Link to comment Share on other sites More sharing options...
Angelblue05 4130 Posted June 29, 2019 Share Posted June 29, 2019 @@djhifi Can you retry with 4.1.0? Does this issue persists? Link to comment Share on other sites More sharing options...
Recommended Posts