unable to connect to local mysql server

[icefaerie]

So, I've been out of the loop, apparently, while there have been massive upgrades to apache, php, and mysql. I'm now trying to fix the issues with these things.

I have a cron job to automatically emerge sync and world every week, and in retrospect, perhaps this was not the brightest of ideas. In short, I used to be running mysql 4.0.2x (don't remember exactly), but my server's installed 4.1.19 without my being able to go through the upgrade process.

I've restarted my mysql init script several times.

[andyrewbobb]

after you have started it, try

[icefaerie]

[bunder]

- check /var/run for a pid file, delete it (or run /etc/init.d/mysql zap)
- check /var/log for errors, probably in mysql.log or syslog/messages/daemon.log

let us know if you find anything,

bunder
_________________

[Tortue]

I've got the same problem and I have Gallery (for showing pictures on the web) that depends on it!
Here is what /var/log/mysql/mysqld.err shows:

[Tortue]

I checked the content of /var/run/mysqld/ after zapping and restarting the server

There was a 0 byte mysqld.sock file, but no .pid file. It seems mysql doesn't create that .pid file

J-M

[magic919]

https://forums.gentoo.org/viewtopic-t-460595-highlight-innodb.html

This one gives you some useful clues.

[Tortue]

Yessss!

Thanks Magic919, it works! simply changing

[icefaerie]

[MasquedAvenger]

I've changed it to 8M too (before even starting it for the first time.) That didn't solve the problem for me either.

James
_________________
"There are no uninteresting things; only uninterested people." --G.K. Chesterton

[csjean]

Hi,

I've experienced the same problems emerging from mysql-4.1.14-r1 to mysql-4.1.19:

1- Problem with 5M logfiles (which was soved by changing logfile size to 8M).
2- After problem 1 was solved, problem 2: "damaged" mysql.user table.

Can anybody see a solution? Or a way to unload the data and reload it?

Thanks.
_________________
Claude

[csjean]

After continuing to search for solutions,

I came across a post about charset problems. The new 4.1.19 version defaults to multibyte charsets (UTF8) and the old one was a Latin1 charset.

So the simple solution is:

1- reemerge mysql-4.1.19 and add latin1 USE flag.
2- etc-update
3- don't forget to change 5M logfiles to 8M.
4- restart mysql

Everythin works.

Hope this helps.
_________________
Claude

[MasquedAvenger]

I just went ahead and wiped away my previous MySQL databases (I only had one that I had used for a test installation of MythTV; I didn't need it anymore). It's now working great I'm guessing that if I had re-merged it using latin1, that probably would have fixed it, although I decided to allow it to remain UTF-8.

James
_________________
"There are no uninteresting things; only uninterested people." --G.K. Chesterton

[flakzeus]

I re-emerged mysql with latin1 and it did not help. I still get the same error:

[flakzeus]

/bump

Anyone at all?
_________________
"I'm not a super genius...or are I?" - Homer Simpson

[lxg]

Just out of curiousity, no offense intended: What did you do when /etc-update asked you about /etc/mysql-xxx/my.cnf?

Btw, did you eselect your new MySQL version?
_________________
lxg.de – codebits and tech talk

[yamakawa]

[khantheripper]

I get the same message as icefarie no matter what I do:

[khantheripper]

As it turns out, I just had to execute the following, to set the (MySQL) root password and start the server:

[m4chine]

[n0n]