Bug #77770 | Python connector cannot connect to fabric XML RPC server on remote machine. | ||
---|---|---|---|
Submitted: | 17 Jul 2015 19:54 | Modified: | 20 Mar 2017 11:41 |
Reporter: | Sterling Cox | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | Connector / Python | Severity: | S2 (Serious) |
Version: | 2.0.4 | OS: | Any (same in OSX & Ubuntu 14.04LTS) |
Assigned to: | CPU Architecture: | Any | |
Tags: | Connection, error, fabric, host, python, rpc, XML |
[17 Jul 2015 19:54]
Sterling Cox
[17 Jul 2015 20:22]
Sterling Cox
Corrected Ubuntu version listed in original report.
[15 Sep 2015 21:27]
Sterling Cox
Hi - it's been a while since this was filed, and it seem like something that would prevent anyone from using Fabric in a real environment. Is there anyone out there one might reach out to just for verification?
[11 Jan 2016 18:31]
Joel Bradshaw
I can verify this behavior - we ran into this same issue in our (almost finished) implementation of Fabric in production. For us, the Python connector was just for testing, we are actually using the PHP connector (which is a whole different ball of issues, but not under MySQL's purview), so it's not a blocking issue for us, but we did run into it when trying to test from outside localhost. Issue seems to be the same as Sterling's: watching the output of a tcpdump, it seems to start accessing the Fabric server via the proper hostname, and then switch to attempting to access it via 0.0.0.0, which of course fails on anything other than the Fabric server itself. I believe we've noticed this only happens if the listen address in the Fabric config is also 0.0.0.0 - I can run some tests on my end and confirm that, it's been a while since I've dealt with this issue, since we just abandoned the Python connector once I got the PHP connector working sufficiently for testing.
[20 Mar 2017 11:41]
Chiranjeevi Battula
Hello Sterling, Thank you for the bug report. I could not repeat the issue at my end using with latest version of Connector / Python. If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL. Thanks, Chiranjeevi.