MySQL help after "Yum Upgrade" [solved]

Support/Development for PHP
blogchex
Forum User
Forum User
Posts: 6
Joined: Mon Jan 08, 2007 5:10 am

MySQL help after "Yum Upgrade" [solved]

Unread post by blogchex »

I have a FC3 server running Plesk 7.5.4.

Yesterday I did a yum upgrade on mysql and moved to 4.1 with no problems. I wanted to upgrade PHP as well so I did a Yum Upgrade.

The install went smooth except for one or two lines with ioncube errors. I gnored those and it completed.

I had a few problems with the php.conf and mysqlconnect errors so I read the notes on the manual changes I had to make and took care of that as well.

Now I got the mysql connect errors to go away and the database won't work. When I try to login or do anything that needs db access, nothing happens. try here: crm.tribis.net

Any ideas?
Last edited by blogchex on Tue Jan 09, 2007 3:34 am, edited 2 times in total.
scott
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin
Posts: 8355
Joined: Wed Dec 31, 1969 8:00 pm
Location: earth
Contact:

Unread post by scott »

Try running php from the command line on one of your mysql related scripts, it could be that the mysql php module isn't loading correctly, because of a missing library, etc.
blogchex
Forum User
Forum User
Posts: 6
Joined: Mon Jan 08, 2007 5:10 am

Unread post by blogchex »

where can I look for hints....php and mysql error logs give no clues.

We had some errors before we changed all the config files from PHP4 to PHP5, but since then, nothing.
blogchex
Forum User
Forum User
Posts: 6
Joined: Mon Jan 08, 2007 5:10 am

Unread post by blogchex »

this is the only error I see:

070108 09:21:16 mysqld ended

070108 09:21:16 mysqld started
070108 9:21:18 InnoDB: Started; log sequence number 0 712829830
070108 9:21:18 [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them
/usr/libexec/mysqld: ready for connections.
Version: '4.1.21' socket: '/var/lib/mysql/mysql.sock' port: 3306 Source distribution
blogchex
Forum User
Forum User
Posts: 6
Joined: Mon Jan 08, 2007 5:10 am

Unread post by blogchex »

This was not a Yum problem at all. It was a configuration problem and problem with our code on our server when upgrading to PHP5. Old statements were invalid, etc.

Thank you Scott and Jason for all the hard work.

CS
Post Reply