Suddenly can't connect to MySQL

[legry]

Hi,

I am a novice when it comes to software, but was able to download, install, and properly run Sugar using MySQL for more than one week before somehow getting the following error message when trying to connect last Friday:

Could not connect to server localhost as root.Can't connect to MySQL server on 'localhost' (10061)



Anyone with any ideas please let me know. I am running version 5.0.0e and have not changed anything or tinkered with it. Did Sugar change anything without notifying us?

If I uninstall and re-install, will I lose everything that was entered?

Simple instructions would be welcome too if anyone knows the answer


Cheers!

[mikesolomon]

Hi,

I am a novice when it comes to software, but was able to download, install, and properly run Sugar using MySQL for more than one week before somehow getting the following error message when trying to connect last Friday:

Could not connect to server localhost as root.Can't connect to MySQL server on 'localhost' (10061)



Anyone with any ideas please let me know. I am running version 5.0.0e and have not changed anything or tinkered with it. Did Sugar change anything without notifying us?

If I uninstall and re-install, will I lose everything that was entered?

Simple instructions would be welcome too if anyone knows the answer


Cheers!

Have you checked if MySql is running?

[legry]

I have stopped and restarted MySQL, Apache, and SugarCRM, but no difference.

I am surprised because it just suddenly happened, so my guess is either something was updated by SugarCRM or MySQL, or something changed on my end, but I have not installed anything new lately.

If I re-install, will I lose all the contact and account info I have already entered into Sugar?

[mikesolomon]

If you reinstall MySql you will lose your data

Check in config.php and make sure your password settings are OK

[legry]

Thanks Mike,

I checked on config.php and the password is fine, but the user is defined as "root", not "admin". What program can I use to modify config.php (that gives away how much I know about this)...and why would it change from admin to root?

Do you think the problem lies there? I am curious whether this kind of stuff happens often with Sugar and I am better off just purchasing something simple. My company's needs are not big at this point, and if we need to troubleshoot Sugar on a regular basis I am wondering if it is worth it for us (even though the program is great and I would hate to have to give it up now).

Cheers.

[roblaus]

Hi,

Did you use the LAMP installer? Means - did you install the entire suite (Apache, MySQL, PHP and Sugar) under Linux? Because I did have the same problem in this environment. And I solved it but unfortunately I can't remember how...
Give us more information - I will try to activate whatever is left of my gray cells.

rgds
rl

[legry]

I used the Installation Wizard for the open source version with MySQL, Apache, and PHP included. I have not edited anything at any point in time.

Everything went smoothly. I used the software without problems for about 10 days, and then suddenly I can't access the login page.

If I understand this correctly, somehow my user name was changed from admin to root in the config.php and that is why I can't access MySQL.

Does this make any sense?

Cheers and thanks for the concern!

[roblaus]

Nope, doesn't make sense. Check in ../mysql/data/mysqld.log for lines like

080603 11:53:12 [ERROR] Can't start server : Bind on unix socket: Permission denied
080603 11:53:12 [ERROR] Do you already have another mysqld server running on socket: XXX/sugar/mysql/tmp/

I believe (I am not sure) that this happened because I started the script as root (sudo) and not as the user who installed it. No explanation. Just trial and error.

[legry]

Rob,

I found the error log and copied the last instance in which it recovered properly and the first instance in which it gave me the error:

Version: '5.0.37-community-nt-log' socket: '' port: 3306 MySQL Community Edition (GPL)
080613 15:35:56 InnoDB: Started; log sequence number 0 43655
080613 15:35:56 [Note] Recovering after a crash using mysql-bin
080613 15:35:56 [Note] Starting crash recovery...
080613 15:35:56 [Note] Crash recovery finished.
080613 15:35:57 [Note] C:\PROGRA~1\SUGARC~1.0E\mysql\bin\mysqld.exe: ready for connections.
Version: '5.0.37-community-nt-log' socket: '' port: 3306 MySQL Community Edition (GPL)
080613 19:30:15 InnoDB: Started; log sequence number 0 43655
C:\PROGRA~1\SUGARC~1.0E\mysql\bin\mysqld.exe: File '' not found (Errcode: 2)
080613 19:30:15 [ERROR] Failed to open log (file '', errno 2)
080613 19:30:15 [ERROR] Could not open log file
080613 19:30:15 [ERROR] Can't init tc log
080613 19:30:15 [ERROR] Aborting

It seems that mysqld.exe is no longer available...and I could actually not find the file on my computer.

Any clues?

[roblaus]

Hi,

This looks interesting. Under normal circumstances files do not disappear. But from the .exe I take that you are running Windows?!
Without knowing the circumstances I believe it's the best to re-install. If you didn't customize your Sugar then it is enough to back up your data (dump the Sugar database), re-install the suite (preferably with the same db name and access) and restore the dump over your newly created db (restore "over" means copy the new one to a new name and drop the original, then import).
If you customized Sugar then you should also copy the actual Sugar directory (under htdocs) to a safe place and then overwrite your new directory with it.
Hope that this is not too confusing.

rgds
rl