[jte091805]

Mahesh wrote on Oct 20 2008, 07:38 AM:

Hi,

1) You mentioned that using ubuntu it is working without any problems , can you tell what is the wine version there ?

2) Also, wine v 1.1.5 is not a stable version,can you try with wine v 1.0.1 which is stable one ?

its wine 0.9.59 for ubuntu No problem working well

Ok. i'll try 1.0.1 for fedora

[jte091805]

peterlaursen wrote on Oct 19 2008, 03:58 PM:

I think it is commonly realized the Fedora 9 has its 'weirdities' (from time to time the Fedora community does weird things — such as Fedora 6 not to forget!). But we are 'the small guys' here so likely we will have to fix it if reproducable.

Please tell:

— Wine version?

— Could you try same thing with a few other Windows programs?

I think we have a F9 running in office and can test tommorow too! But I think it should be enogh to restart/kill 'wineserver' and not the complete OS?

Hi sorry for the late reply… I'm in the Philippines so the time is different than yours.

I have wine 1.1.5 from fedora installed via yum install wine.

I dont have other windows program installed in my wine, just sqlyog since I am a not a fan of windows I just love and use SQLyog so much but there is no version for linux thats why I have to use it under wine

[jte091805]

OK… I have uninstalled/removed 5.0.51a and installed 5.0.67

then SQLYog was able to connect to it.. I dont know but for some reason, in 5.0.51a SQL cant

Thanks

[jte091805]

Thanks.. OK i'll download the sources for mysql gui administrator and compile it..

Also I have another server and I cant connect to it using sqlyog.

Thanks again

[jte091805]

Im using Slackware 12.1

it has mysql version 5.0.51a installed

i have a line

Quote:

127.0.0.1 localhost

in my /etc/hosts

I tried also in my SQLyog

hostname 127.0.0.1

username root

password ********

Still the same error

Error No, 2003

Can't connect to mysql server on '127.0.0.1' (10061)

I have restarted mysql service in /etc/rc.d/rc.mysqld restart

and same error with SQLyog but successful via command line log in

[jte091805]

The fix was done in 6.5 RC and it really worked for my though I'm using Linux and wine for SQLYOG.

I think for windows, 6.5 RC is good and fixed the bug.

[jte091805]

Hey I think this might help you. It was solved

http://www.webyog.com/forums//index.php?showtopic=3865

[jte091805]

HEY I THINK I SOLVED THE PROBLEM. I am now ABLE TO DUMP!

I downgraded my WINE from 0.9.58 to 0.9.41

I think wine is the problem. But I really don't know the inner workings of it. Anyway, Thanks Peter for helping me. Will you be patching 6.5 RC for that error messages? Or will you be issuing statement regarding the bugs if sqlyog is used with wine 0.9.58?

Thanks again great work

[jte091805]

OK. this is the show -> variables in my sqlyog

max_connection = 100

max_connect_error = 10

wait_timeout = 28800

I'm connected as root to mysql

I also tried restarting mysql with bind address commented

Yes I have done /etc/init.d/mysql restart for many times still error is not changed

I'm using WINE 0.9.58

Can't remember if it was included in the update because, ubuntu issue updates daily and I just click update. Myabe I haven't check what's included on the update.

Thanks. I will wait for your further analysis and I hope you could fix this, Right now Im using MYSQL Administrator to dump my database. I really like SQLyog

[jte091805]

I have managed to open another instance of sqlyog. It worked fine. I have attached the screenshot.

I have killed all the processes and restart mysql.

I have started again sqlyog and then nothing changes.. Error 2003 once again

I failed.

[jte091805]

I'm only using one instance of sqlyog open. I'm able to run select, update and other queries but only the dump function is not working. I'm using this my.cnf:

here is a partial code of my.cnf

[client]

port = 3306

socket = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs

# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.

[mysqld_safe]

socket = /var/run/mysqld/mysqld.sock

nice = 0

[mysqld]

#

# * Basic Settings

#

user = mysql

pid-file = /var/run/mysqld/mysqld.pid

socket = /var/run/mysqld/mysqld.sock

port = 3306

basedir = /usr

datadir = /var/lib/mysql

tmpdir = /tmp

language = /usr/share/mysql/english

skip-external-locking

#

# 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

# * Fine Tuning

#

key_buffer = 16M

max_allowed_packet = 64M

thread_stack = 128K

thread_cache_size = 8

#max_connections = 100

#table_cache = 64

#thread_concurrency = 10

#

# * Query Cache Configuration

#

query_cache_limit = 1M

query_cache_size = 16M

I'm accessing mysql on the same computer. I'm on a stand alone setting. I'm using Linux Ubuntu 7.04 and mysql 5.0.38 I use WINE for SQLyog 6.5 RC.

I haven't changed any config. It was all fine last week, and to my surprise when I tried to dump yesterday, boom ERROR!.

What would be next step I would do to fix this? Or is anything I can do at all about it?

[jte091805]

I mean sqlyog 6.5 RC

I have tried to execute an update and insert query and it is successful.

However, on creating an sql dump, Error no.: 2003 shows up and again I'm not able to backup my database.

[jte091805]

I have downloaded and installed RC 5 just now. Then I tried to dump again, here is the error

– Error no.: 2003: Can't connect to mysql on localhost (10061)

Please help

Thanks

[jte091805]

by the way i use sqlyog community 6.16, I have mysql 5.0.x.

I have just experience the problem now. Please help.

[Author]

Posts