6 messages in com.mysql.lists.gui-toolsRe: Bugs with mycc 0.8.4-alpha| From | Sent On | Attachments |
|---|---|---|
| Carl B. Constantine | 06 Jul 2002 14:25 | |
| Adam Hooper | 06 Jul 2002 15:03 | |
| Carl B. Constantine | 06 Jul 2002 16:13 | |
| Adam Hooper | 06 Jul 2002 21:13 | |
| Carl B. Constantine | 06 Jul 2002 22:22 | |
| Carl B. Constantine | 06 Jul 2002 22:57 |
| Subject: | Re: Bugs with mycc 0.8.4-alpha |
|---|---|
| From: | Adam Hooper (ada...@densi.com) |
| Date: | 07/06/2002 03:03:40 PM |
| List: | com.mysql.lists.gui-tools |
1) Make sure you have the qt-devel package installed on the RedHat machine (and
probably on Debian also, I don't know though). The reason the binary works is
that it's statically compiled - it'd work if you didn't have QT installed at
all.
2) You have two options: 1. If you figure out how to compile MyCC, add below
line 419 of src/CConnectionDialog.cpp the line:
sock_path.append("/var/run/mysqld/mysql.sock");
2. Edit /etc/my.cnf. Under the [mysqld] section, add (or change) the line
socket = /var/run/mysqld/mysql.sock
to
socket = /tmp/mysql.sock
As far as I know, /tmp/mysql.sock is the standard place for it.
3) This sounds a lot like a firewall or configuration issue on the server. On a
terminal window on the laptop, run:
[user@computer user]$ telnet 192.168.1.25 3306
Three things can happen:
1. You connect immediately, get the version number and then some gibberish. This
means it's not a firewall issue, but probably something wrong in the server
registration in MyCC.
2. This is what probably happens. You wait for a couple of minutes before an
error. This means a firewall issue - port 3306 is being blocked. As a simple
workaround, run the following on the server:
iptables -I INPUT 1 -p TCP --dport 3306 -j ACCEPT
iptables -I OUTPUT 1 -p TCP --dport 3306 -j ACCEPT
Then try connecting again. If it works, your firewall needs to be tinkered with.
3. You get the message "telnet: Unable to connect to remote host: Connection
refused" soon after pressing Enter. If this is the case, it still could be the
firewall so try using iptables as above. More probably there's something wrong
with the MySQL configuration of the server. Make sure under the [mysqld]
section, "port" is either unspecified or 3306. Beyond that, you should ask on
the mysql list at mys...@lists.mysql.com, since it's not a MyCC problem.
Besides the first issue, these problems are almost certainly general MySQL
problems and not MyCC issues. mys...@lists.mysql.com is the place to ask them :).
Hope this helps!
--------------- Adam Hooper ada...@densi.com
On Sat, 6 Jul 2002 14:26:19 -0700 "Carl B. Constantine" <duck...@duckwing.ca> wrote:
I'm runnind MyCC on two systems, my desktop machine running Debian (using the Debian Qt packages) and one on my laptop running RedHat 7.3 (using the RedHat Qt packages).
There are 3 problems I've found so far.
1) compling mycc with the --with-qt option does not work. I tried it several times and it just wouldn't find the Qt development libs in any other spot but what it thought they should be. And even though I set the QTDIR variable to /usr (which is where it would be for package installs) the compile couldn't find Qt, it always wanted to look elswhere. The binary version works just fine though.
2) MyCC will NOT connect to a database unless you specify the socket file (/var/run/mysqld/mysqld.sock on my desktop machine). the port should be available to the local host and it isn't.
3) I can't use my Laptop to connect to my desktop's mysql at all. I've added mysqld to the hosts.allow file like this:
mysqld: 192.168.1.
and the mysql libs are on my laptop so I don't get why it won't connect. This is kind of important if you want to manage multiple database machines that it be able to do a remote connect and use the port instead of the socket file all the time.
any help anyone can give me in this regard would be good. Interestingly, msql isn't even turning up as an open port in an nmap scan, even though mysql is running and I can connect to it (via the socket at least, just not the port for some reason).
nmap -sT 192.168.1.25
Starting nmap V. 2.54BETA33 ( www.insecure.org/nmap/ ) Interesting ports on Mallard (192.168.1.25): (The 1544 ports scanned but not shown below are in state: closed) Port State Service 9/tcp open discard 13/tcp open daytime 22/tcp open ssh 25/tcp open smtp 37/tcp open time 80/tcp open http 111/tcp open sunrpc 113/tcp open auth 631/tcp open cups 10000/tcp open snet-sensor-mgmt
Nmap run completed -- 1 IP address (1 host up) scanned in 1 second
Thanks in advance.