(2021-07-22, 18:33)Klojum Wrote: (2021-07-22, 18:12)zebraitis Wrote: OK... so since this has gone unanswered, I will start a different thread.
Creating multiple threads on this forum on the same subject, simply because you didn't get a fast enough answer, will not make this a more transparent problem nor will it be solved faster.
Not all of us are database experts / Not all of us have 9-5 time for Kodi / Not every problem is as easy to solve. If this all was a generic Windows/MySQL/MariaDB problem, there would be many more complaints on the subject.
So for some reason your Windows PC setup is now allergic to MySQL. I'm sure you'll understand that for us it's hard and perhaps impossible to reproduce your database experiences. Do you maybe still have a Windows 7 setup available to test with?
I think what you are saying is fair, so I will stay in this thread.
However, as Windows 7 was end of support on Jan 14, 2020, respectfully, I cannot in good faith troubleshoot on a platform that is not receiving security updates.
Additionally, I do disagree with the allergy metaphor (and you will see why, below), but let's get to the good stuff:
Let's discuss my
implementation today that is running Kodi 18.9 w/MySQL successfully:
As I have completely rebuilt both the server layer and the presentation PC layer, I can honestly say that this is a current fully functional Win10 platform.
My home sever is a home-built box with Gigabyte GA-Z68XP-UD3P motherboard. Not a big fan of Gigabyte, but I did need some SATA 3 ports and it had 'em, and it was a cheap used upgrade choice on craigslist.
Running on that motherboard is an Intel 8-core i7-3770 CPU @ 3.40GHz. The box also has 16GB RAM, and a gig ethernet port There are no additional boards-in-slots. The boot drive is a 240GB SSD, and I have 4 @ 10TB drives.
I now use Macrium Reflect Free and another 240 GB drive as my boot drive backup via imaging. To backup my 40TB drives, I have a Buffalo Terrastation TS5800D NAS connected via ethernet cable.
The software running on my home "server" is Win10 Pro 64 bit ver 21H1 and MySQL 5.7.33. The MySQL implementation followed the standard instructions for MySQL implementation from the Kodi Wiki. The only deviation is that I chose was to allow for more resources to be accessible to MySQL by selecting "server machine" rather than "development machine" for config type
I have loaded a local copy of Kodi 18.9 so that I can update locally on that machine to the local MySQL DB. This is new, as I used to do that on the living room TV, but it finally dawned on me that the WAF would be improved if I did this on the home server either at my desk or via remote desktop.
My Kodi implementation is multi-room and also is implemented with 8 profiles. All profiles appear on all remote machines and connect to the MySQL DBs. All remotely connected Kodi running machines are windows based, same Kodi version, and all ethernet connections are hard-wired except for one tablet. Nearly all run the confluence skin. In practice, no more that 3 of these remote machines would connect to the shared MySQL DBs at any one time.
So that you can get a view of what I have just said, here is a debug-enabled log of the Kodi 18.9 that is running on my home server:
https://paste.kodi.tv/hucapagafe.kodi
SUMMARY: As I said,
this implementation works FLAWLESSLY for Kodi 18.9 and, this has been working successfully in many other previous major release Kodi versions. (And when I say "previous versions", I'm taking MySQL all the way back to XBOX w/ XBMC.)
WHAT CHANGED:
1) When I went to Kodi 19.0, I ran into the Kodi Crash-on-launch issue that was resolved by KodiSetup-20210525-fd5acfb5-Matrix-x64
2) When I went to 19.x, Kodi automatically updated my DB's, and that seemed to work, but updating seemed slower.
3) Tried reloading a remote machines to see if a new fresh version of windows & Kodi would make scanning for new media faster, but did not seen improvement.
4) With the Win11 rollout, I gave that a shot on my home server, was unimpressed, and all-too-late found out that the only way that I could undo that "development" implementation was a complete wipe of the hard drive. And with that wipe, and reload from scratch in Win10 running Kodi 19.x environment, that is when I found that I COULD NOT get through a Kodi scan of media without crashing the MySQL application. Of course, that led to this thread and why I listed it: [BROKEN]. I too have a "regular job" but I spent well over a week and many sleepless nights in this thread trying to get 19.x to work with MySQL.
And that is why I wiped everything and fell back to 18.9, and a successful stable system.
So, while there may be a handful of folks regularly using MySQL (compared to standard Kodi deployments) that have migrated from 18.9 to 19.x with a DB upgrade occurring automatically, there may be very few that have actually tried to load this new in 19.1 And that may be why I am the only one that is saying that something is wrong. This, however, is just a theory and even with my experience I would say it's a possibility, but I cannot be sure.
WHAT I WOULD LIKE TO KNOW: Is this MySQL implementation still a supported configuration in 19.1x ? Does the KODI development team feel that they can stand behind Kodi with MySQL with confidence?
I am more than willing to provide more info, additional logs or test various options in an attempt to better the product. We would be starting from a configuration that works successfully, so any glitches that we found may be easily traced.
Let me know the next steps that you all recommend.