I updated my MySQL server from 8.0.28 to 8.0.29 and now the tvservice crashes on start. The attached log doesn't give me a clue what's going wrong.
This affects MediaPortal 1.29 and 1.30 Pre-Release.
I did a packet capture of the communication with the tvservice and MySQL but cannot see anything obviously wrong there, too - however, I don't know the normal communication pattern between these two programs.
Currently, I'm running MySQL 8.0.29 for everything but MediaPortal and a second MySQL installation (8.0.28) on a different port for the MediaPortal tvservice. TVSetup doesn't respect the port setting in the gentle.config and tries to connect to my MySQL 8.0.29 instance.
On MediaPortal update, this caused the DbSetup dialog to appear - in which I cannot change the port. But it seems that DbSetup is able to communicate with my MySQL 8.0.29 instance after I setup the mediaportal user and DB!
So DbSetup and TVSetup isn't able to communicate with a MySQL instance on non-default port.
TVService isn't able to worh with MySQL 8.0.29 (but does work with 8.0.28).
This affects MediaPortal 1.29 and 1.30 Pre-Release.
I did a packet capture of the communication with the tvservice and MySQL but cannot see anything obviously wrong there, too - however, I don't know the normal communication pattern between these two programs.
Currently, I'm running MySQL 8.0.29 for everything but MediaPortal and a second MySQL installation (8.0.28) on a different port for the MediaPortal tvservice. TVSetup doesn't respect the port setting in the gentle.config and tries to connect to my MySQL 8.0.29 instance.
On MediaPortal update, this caused the DbSetup dialog to appear - in which I cannot change the port. But it seems that DbSetup is able to communicate with my MySQL 8.0.29 instance after I setup the mediaportal user and DB!
So DbSetup and TVSetup isn't able to communicate with a MySQL instance on non-default port.
TVService isn't able to worh with MySQL 8.0.29 (but does work with 8.0.28).