INFO: You need to start mysql after upgrade to 4.0.24-1

[niel]

Hi,

I've successfully upgraded to mysql 4.0.24-1 in FC2 and FC3, thanks scott.

The only think I'd like to say is that I needed to start the service again, as my mail accounts were failing (and everything that uses mysql).

I did it this way:

/etc/init.d/mysqld start

but in Fedora (and RedHat) you can do it also this way:

service mysqld start

[Brent]

Yes you do have to do this

[scott]

yeah, ran into this on a couple other systems too, Im not sure what it is exactly, but I suspect that its a one-time thing. Although the mysql init procedure has always been kind of wierd like this. Im wondering if its regenerating some kind of table on startup after an initial upgrade.

[niel]

Hi,

I have upgraded my FC2 and FC3 boxes to:

Code: Select all

mysql.i386 0:4.0.24-2.rhfc3.art
mysql-compat.i386 0:4.0.24-2.rhfc3.art
mysql-devel.i386 0:4.0.24-2.rhfc3.art
mysql-server.i386 0:4.0.24-2.rhfc3.art

In FC3, I had to re-start mysqld after upgrade. I recommend you to upgrade this way:

Code: Select all

# yum install mysql mysql-compat mysql-devel mysql-server && /etc/init.d/mysqld condrestart

In FC2, I had some more trouble with mysql-compat due to the same issue (mysqld not running after upgrade):

Code: Select all

packagemng: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
packagemng: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
packagemng: Unable to connect to the mysql database

System error 2: No such file or directory
packagemng: Unable to connect to the mysql database

System error 2: No such file or directory
error: %trigger(psa-7.5.2-fc2.build75050128.11) scriptlet failed, exit status 1
packagemng: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
packagemng: db_connect: failed to connect to database: Error: Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)
packagemng: Unable to connect to the mysql database

...

System error 2: No such file or directory
error: %trigger(psa-7.5.2-fc2.build75050128.11) scriptlet failed, exit status 1

So I recommend you to upgrade this way:

Code: Select all

# yum install mysql mysql-devel mysql-server && /etc/init.d/mysqld condrestart

# yum install mysql-compat && /etc/init.d/mysqld condrestart

Regards

[scott]

You know whats wierd, in -2 I pulled out the conrestart piece in %post, and its STILL stopping the server. I wonder if this is something internal in the mysql daemon thats causing it to happen.

[niel]

Hi scott,

I've found 2 references to the issue, the first one is about pretty the same:

http://listman.redhat.com/archives/fedo ... 00074.html

The second one goes a bit further, but the comment from 'commander' also remarks what we are talking about:

http://www.linuxquestions.org/questions ... did=260505

So knowing that yum does so, I'd recommend to upgrade this way:

Code: Select all

# yum install mysql mysql-compat mysql-devel mysql-server && /etc/init.d/mysqld condrestart

[scott]

yep, I know exactly what those are talking about, specifically that rpm runs a conrestart in %post, which is exactly what I disabled in -2. Meaning there is nothing in the rpm itself that would cause mysql to restart. My guess at this point is that the old rpm is triggering the restart, before the new one is installed.

[JLChafardet]

it seems to be a one time issue only, it happened to me with the 2 latest mysql upgrades, but when i started mysql by hand, then stoped all psa and restarted it it worked good, i think we can handle this little issue

regards,

JLChafardet