Not signed in (Sign In)

Vanilla 1.1.5a is a product of Lussumo. More Information: Documentation, Community Support.

    • CommentAuthorjfk
    • CommentTimeApr 22nd 2010
     
    Jet profiler for linux versions 1.0.7 and 1.0.8
    I am still getting "Database connection error"
    I've checked all sugesstions displayed in error promt and everything is ok.
    I can connect from the same computer via cli mysql client:
    mysql -h example.com -ujetprofiler -p
    But using same host,username and password settings i can't connect from jetprofiler.
    Where did i went wrong?
  1.  
    What does the hostname resolve to? If you type

    ping example.com

    Try connecting to the ip address instead of the hostname.
    • CommentAuthorjfk
    • CommentTimeApr 22nd 2010 edited
     
    Hostname resolves to proper ip. Connecting by this ip gives same results:
    cli - ok
    jetprofiler - error.
    Ping of course 0% packet loss in both cases (ip, hostname).
    • CommentAuthorjfk
    • CommentTimeApr 22nd 2010 edited
     
    Iptables on both source and destination machine has no entries.
  2.  
    Sounds strange. I've never encountered a similar error before. Could you please email screenshots of the connection dialog + error and the cli window? to support at jetprofiler dot com.
    • CommentAuthorjfk
    • CommentTimeApr 22nd 2010
     
    Solved:
    I've chnaged java version to:
    java version "1.6.0_18"
    OpenJDK Runtime Environment (IcedTea6 1.8) (6b18~pre4-1)
    OpenJDK Server VM (build 16.0-b13, mixed mode)

    and everything works fine.
    • CommentAuthorpetere
    • CommentTimeSep 30th 2011
     
    This is due to that mysql tries to resolve the hostname of the connecting party, but if that machine does not have reverse resolve configured it gets a timeout. And since the 10s timeout is quite short and if you run it over a slower network connection or vpn (like I do). Jetprofiler will timeout.

    I solved it by adding: skip-name-resolve to my.cnf

    However, if you have other users by hostname you have to change them to per ip, since it will skip the name resolve entirely.

    -P
  3.  
    Hi Peter,

    generally, it is a good idea to disable name resolving on all your databases. We always recommend using ip-based grants since host lookups depend on the dns service being fast and working as expected, as well as your ips not being changed anytime. It is kind of weird that the default setting is on.

    Anyway, we will try to make the connection timeout configurable in the next release.

    Thanks,
    Bjorn