toml
Verified User
Of course within an hour of me upgrading to 4.1.13, a new version 4.1.14 was released. I just upgraded to 4.1.14, the update seemed to work fine. No problems yet after doing some initial testing.
MySQL 4.1.14 Released
- Thread starter toml
- Start date
toml
Verified User
That just means that you didn't recompile php, that should not be a problem. The API did not change between those versions.thastudio said:
toml
Verified User
It will not automatically recompile. When you update php next it will pick up the latest libmysqlclient.so. The only time you really have to recompile is when the API changes, that should only really happen if a major version changes. So, if the version number goes from 4.1 to 4.2, then I would assume that a recompile would be necessary, same goes for 4.x to 5.x. That is what happened when 4.0 went to 4.1.thastudio said:
toml
Verified User
Shark said:
Here is the script that I used to do my upgrade, someone here posted it, I just added the deletes that the end, since DA uses mysqld as the init scripts:
Code:
#!/bin/sh
cd $HOME
echo -e "\n\n\033[1;37mUpgrade to what version? (e.g. 4.1.15 )\033[0m"
read INSTALL_VER
echo -e "\n\n\033[1;37mUpgrading to MySQL ${INSTALL_VER}\033[0m\n\n";
wget [url]http://mysql.he.net/Downloads/MySQL-4.1/MySQL-server-[/url]${INSTALL_VER}-0.i386.rpm
wget [url]http://mysql.he.net/Downloads/MySQL-4.1/MySQL-client-[/url]${INSTALL_VER}-0.i386.rpm
wget [url]http://mysql.he.net/Downloads/MySQL-4.1/MySQL-devel-[/url]${INSTALL_VER}-0.i386.rpm
rpm -Uvh ./MySQL-server-${INSTALL_VER}-0.i386.rpm ./MySQL-client-${INSTALL_VER}-0.i386.rpm ./MySQL-devel-${INSTALL_VER}-0.i386.rpm
rm -fr ./MySQL-server-${INSTALL_VER}-0.i386.rpm ./MySQL-client-${INSTALL_VER}-0.i386.rpm ./MySQL-devel-${INSTALL_VER}-0.i386.rpm
service mysql restart
echo -e "\n\n\033[1;37mSuccessfully upgraded to MySQL ${INSTALL_VER}\033[0m\n\n";
rm -f /etc/init.d/mysql
rm -f /etc/rc?.d/*mysql
exit 0;Thanks for the script toml, upgraded to 4.1.14. The installation brought up 2 additional questions:
[Warning] Asked for 196608 thread stack, but got 126976
[Warning] Asked for 196608 thread stack, but got 126976
Are these warnings OK to ignore?
Also,
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h doamin.com password 'new-password'
running the 1st one above I get:
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: NO)'
Sorry to be such a newbie as I currently have limited knowledge with mysql but soon to change
DaveR~
[Warning] Asked for 196608 thread stack, but got 126976
[Warning] Asked for 196608 thread stack, but got 126976
Are these warnings OK to ignore?
Also,
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h doamin.com password 'new-password'
running the 1st one above I get:
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: NO)'
Sorry to be such a newbie as I currently have limited knowledge with mysql but soon to change
DaveR~
toml
Verified User
Shark said:Thanks for the script toml, upgraded to 4.1.14. The installation brought up 2 additional questions:
[Warning] Asked for 196608 thread stack, but got 126976
[Warning] Asked for 196608 thread stack, but got 126976
Are these warnings OK to ignore?
Also,
PLEASE REMEMBER TO SET A PASSWORD FOR THE MySQL root USER !
To do so, start the server, then issue the following commands:
/usr/bin/mysqladmin -u root password 'new-password'
/usr/bin/mysqladmin -u root -h doamin.com password 'new-password'
running the 1st one above I get:
/usr/bin/mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'@'localhost' (using password: NO)'
Sorry to be such a newbie as I currently have limited knowledge with mysql but soon to change
DaveR~
I'm not 100% sure about the thread stack warning, but I think it is safe to ignore, unless you really need to debug a core dump.
You don't need to run the password stuff after doing an upgrade. That is only needed when installing MySQL fresh. Your old root password is still intact.
@how@
Verified User
toml said:
is this right or not (cent4/RH4)
Code:
#!/bin/sh
service mysql stop
cd $HOME
echo -e "\n\n\033[1;37mUpgrade to what version? 4.1.12\033[0m"
read INSTALL_VER
echo -e "\n\n\033[1;37mUpgrading to MySQL ${INSTALL_VER}\033[0m\n\n";
wget [url]http://mysql.he.net/Downloads/MySQL-4.1/MySQL-server-standard-4.1.12-0.rhel4.i386.rpm[/url]
wget [url]http://mysql.he.net/Downloads/MySQL-4.1/MySQL-client-standard-4.1.12-0.rhel4.i386.rpm[/url]
wget [url]http://mysql.he.net/Downloads/MySQL-4.1/MySQL-devel-standard-4.1.12-0.rhel4.i386.rpm[/url]
rpm -Uvh ./MySQL-server-standard-4.1.12-0.rhel4.i386.rpm ./MySQL-client-standard-4.1.12-0.rhel4.i386.rpm ./MySQL-devel-standard-4.1.12-0.rhel4.i386.rpm
rm -fr ./MySQL-server-standard-4.1.12-0.rhel4.i386.rpm ./MySQL-client-standard-4.1.12-0.rhel4.i386.rpm ./MySQL-devel-standard-4.1.12-0.rhel4.i386.rpm
service mysql restart
echo -e "\n\n\033[1;37mSuccessfully upgraded to MySQL 4.1.12\033[0m\n\n";
rm -f /etc/init.d/mysql
rm -f /etc/rc?.d/*mysql