[kbutler]

peterlaursen wrote on Feb 23 2009, 12:03 PM:

Please

1) tell the MONyog version you are testing (and what build: Windows/Linix, 32 bit/64 bit)

2) tell what browser you are using (and try a few different)

3) check browser security settings

4) tell if are you using SSH tunnel?

5) check if MONyog.log has some details

6) experiment a little (temporarily disable) with what security programs you may have installed ('script-stoppers' etc.)

Can you share a screesnshot ofthe main 'register servers' page (you can hide what details you like).

1) 3.02

2) Firefox (tried IE – it locked IE up)

3) ??? Works on several other sites – not sure what I need to check

4) No

5) log was blank, checked that

It ended up being a dns issue, the dns did not resolve correctly so it couldn't find a server. When I entered the IP address it worked fine. My question is, why doesn't it give me an error and tell me that? Or at least indicate that it's trying to connect? It literally just sat there, no logs, no nothing.

[kbutler]

As a follow-up to possible future visitors – it was the bind-address. I commented this out and it works great now!

[kbutler]

peterlaursen wrote on Jun 27 2007, 11:22 AM:

“is running locally …”

do you mean on LOCAL MACHINE or LOCAL NETWORK ?

“I can connect to it outside of sqlyog ..”

How? With what client can you connect? If you are connecting from the same host are you sure that the details are identical?

This FAQ:

http://webyog.com/faq/23_15_en.html

.. deals with the error 2003!

(note: this is a connection issue, not an authentication issue)

Local network, my apologies.

I can connect to it via Putty – an SSH client.

Quote:

* There is no MySQL server running at the specified host

There is…

Quote:

* Connection to the MySQL server is not allowed using TCP-IP. Check the 'skip-networking' setting in the MySQL configuration file (my.ini on Windows, my.cnf on Unix/Linux). It shall be commented out like '#skip-networking'. If it is not commented out, then do it and restart the MySQL server for the change to take effect. SQLyog needs to connect using TCP-IP.

skip-networking is not even present in the my.cnf:

Code:

#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address = 127.0.0.1

I am thinking that it may have something to do with this – that mysql is only listening to localhost – while I am trying to connect directly.

Quote:

* Some networking issue prevents connection. It could be a network malconfiguration or a firewall issue. We have experienced sometimes that some firewalls (ZoneAlarm in particular) is blocking TCP-IP connections even if it claims to be disabled. Most often it will help to uninstall and reinstall the firewall.

The LAN is behind a firewall – I don't have any local firewalls.

Quote:

* When trying to connect to a MySQL server at an ISP this error message often indicates that direct connection to MySQL has been blocked. You must then use HTTP-tunnelling or SSH-tunnelling to connect.

LAN – this is not valid in my case.

Quote:

* Also this FAQ may have relevant information. It describes some more special situations when connection to MySQL on Linux.

Feel a bit lost in this post – as I said – I am somewhat new to configuring this sort of thing.

[Author]

Posts