home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Support
General Support
Mediaportal MySQL Dependency Issues
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mm1352000" data-source="post: 987929" data-attributes="member: 82144"><p>Understood.</p><p> </p><p></p><p>Lets break it down logically.</p><p> </p><p>To have two MySQL instances running on the same machine you must set the instances up to listen on different ports, right?</p><p>To have TV Server (or any other application) connecting to a specific MySQL instance you must specify the port that the target instance is listening on in the connection string, right?</p><p>As you can see, the connection string in your gentle.config file does not include any port specification, so the default port (3306) will be used. Are we still in agreement?</p><p>In your case, which instance is running on the default port: the WAMP one, or the old one?</p><p> </p><p>As far as I can see, the service name and port are not hard-coded anywhere in TV Server.</p><p>So that means the connection is entirely dependent on the connection string.</p><p>And since the connection string doesn't currently contain any port specification...</p><p>...well, if your old instance is listening on port 3306 then it is no surprise that TV Server is connecting to that instance.</p><p> </p><p>Now having said that, if you are configuring the DB connection with a specific port and SetupTv.exe is somehow mangling the port specification... that would be a problem that could be investigated.</p><p>Otherwise, as far as I can see there are no hard-coded references to service names (MySQL5, MySQL51, MySQL55) or port numbers (eg. 3306) that would cause what you're seeing.</p><p>But if I'm right above, I would suggest to make sure you specify the port in the hostname/server field as "<hostname>:<port>".</p><p> </p><p></p><p>The dependency is *not* used to specify the instance to connect to - correct.</p><p>That is only used to set up the TVService startup dependency (ie. to ensure the correct DB service is started before TVService can attempt to start), and that is one time configuration. Again and in other words, that is configuration for the Windows service manager; it has no bearing on which instance of MySQL TV Server will actually connect to during normal operation.</p><p>My understanding is that you should be specifying the TCP port to connect to as part of the hostname field.</p><p> </p><p>mm</p></blockquote><p></p>
[QUOTE="mm1352000, post: 987929, member: 82144"] Understood. Lets break it down logically. To have two MySQL instances running on the same machine you must set the instances up to listen on different ports, right? To have TV Server (or any other application) connecting to a specific MySQL instance you must specify the port that the target instance is listening on in the connection string, right? As you can see, the connection string in your gentle.config file does not include any port specification, so the default port (3306) will be used. Are we still in agreement? In your case, which instance is running on the default port: the WAMP one, or the old one? As far as I can see, the service name and port are not hard-coded anywhere in TV Server. So that means the connection is entirely dependent on the connection string. And since the connection string doesn't currently contain any port specification... ...well, if your old instance is listening on port 3306 then it is no surprise that TV Server is connecting to that instance. Now having said that, if you are configuring the DB connection with a specific port and SetupTv.exe is somehow mangling the port specification... that would be a problem that could be investigated. Otherwise, as far as I can see there are no hard-coded references to service names (MySQL5, MySQL51, MySQL55) or port numbers (eg. 3306) that would cause what you're seeing. But if I'm right above, I would suggest to make sure you specify the port in the hostname/server field as "<hostname>:<port>". The dependency is *not* used to specify the instance to connect to - correct. That is only used to set up the TVService startup dependency (ie. to ensure the correct DB service is started before TVService can attempt to start), and that is one time configuration. Again and in other words, that is configuration for the Windows service manager; it has no bearing on which instance of MySQL TV Server will actually connect to during normal operation. My understanding is that you should be specifying the TCP port to connect to as part of the hostname field. mm [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Support
General Support
Mediaportal MySQL Dependency Issues
Contact us
RSS
Top
Bottom