• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

CentOS Updates

T

theywill

Basic Pleskian
I am running Plesk 9.5.2 on CentOS 5.4. Recently some security updates have been released for CentOS, and I wanted to install these. I can do this via yum, but I wanted to see if anyone had advice about maintaining Plesk while using yum to update the OS. I wouldn't want to break Plesk or install an update that would keep Plesk from updating later.

Any specific advice?

Thanks so much.
 
hi,

I'm new to plesk and I'd like to know if there is a special order for updates??
Do I have to do a YUM then the plesk updates, or shall I start with updating plesk and then YUM???

I tried first to update plesk to 9.5.2 and then to update with yum update, mysql got ****ed and psa refuses to start!

Now I started to do a yum update first and it sounds OK at the moment ;)
SQL is updated (to 5.0.77) but not php! Then I do a yum update php and php is now updated to 5.2.13

Now I'm updating plesk from 9.0 to 9.5.2 step by step with the update manager in plesk admin
- After update 9.2.1, I met a bug with open_ssl but I found the solution here (SOLUTION => http://kb.odin.com/en/8338)
- After update 9.3, when I restart apache, I have a message saying "mod_ssl already loaded"! I don't really know what this is about??
- Then updates to 9.5.2 are well done and everything seemed to work !
- Then when I tried to redo a yum update, and I could find a new version of mysql 5.1.48 but when I installed it my psa service refuse to start now!
What can I do to update properly centos + plesk + php + mysql??
Thanks for help ;)
 
Last edited by a moderator:
Thanks for your link ;)
Can you tell me if there is a special order for updates ?
Plesk first or YUM first??
Thanks
 
Hi,

thanks for your answer ;)
sorry for my english but there might be a misunderstanding!
I don't want to install plesk through yum! Basically, I have a dedicated server at 1&1 with centos and plesk already installed. I just want to update my server!

If I understand well, I can update centos through yum and I can update plesk with the plesk admin.
I wanted to know

1/ Update Centos
# yum update
Update ok => mysql 5.0.77 updated but not php (version 5.1.6 still installed)

2/ Update php
#wget -q -O - http://www.atomicorp.com/installers/atomic.sh | sh
#yum update php
#/etc/init.d/httpd restart
Update ok =>php = 5.2.13

3/ Install plesk update
3.1/ Version 9.0.1 => update OK
• Base packages of Plesk
• Plesk Updater
• Apache ASP support
• Plesk Firewall module
• Watchdog (System monitoring module)

3.2/ Version 9.2.1 => update NOT OK because of a bug with openssl update (PSA don’t start anymore after plesk update 9.2.1)
SOLUTION => http://kb.odin.com/en/8338
#wget -c http://kb.odin.com/Attachments/12669/Attachments/sw-cp-server-1.0-6.201004011130.centos5.x86_64.rpm
#rpm -Uhv sw-cp-server-1.0-6.201004011130.centos5.x86_64.rpm
• Base packages of Plesk
• Plesk Updater
• Plesk API [former Plesk Agent]
• Plesk migration manager
• Plesk Firewall module
• Watchdog (System monitoring module)
• Plesk Backup Manager
• French language pack
• Horde webmail support

3.3/ Version 9.2.2 => update OK
• Base packages of Plesk
• Plesk Updater
• Plesk API [former Plesk Agent]
• Plesk migration manager
• Plesk Firewall module
• Watchdog (System monitoring module)
• Plesk Backup Manager
• French language pack
• Horde webmail support

3.4/ Version 9.2.3 => update OK
• Base packages of Plesk
• Plesk Updater
• Plesk API [former Plesk Agent]
• Plesk migration manager
• Plesk Firewall module
• Watchdog (System monitoring module)
• Plesk Backup Manager
• French language pack
• Horde webmail support

3.5/ Version 9.5.1 => update OK but message mod_ssl already loaded after restarting apache !!!
SOLUTION : http://www.atomicorp.com/forums/viewtopic.php?f=3&t=4078
Plesk apparently added a LoadModule ssl_module statement to /etc/httpd/conf/httpd.conf at some point, while this module is also being loaded in /etc/httpd/conf.d/ssl.conf (from the mod_ssl package). So comment out this line : LoadModule ssl_module statement in /etc/httpd/conf/httpd.conf
• Base packages of Plesk
• Plesk Updater
• Plesk API [former Plesk Agent]
• Plesk migration manager
• Plesk Firewall module
• Watchdog (System monitoring module)
• Plesk Backup Manager
• French language pack
• Horde webmail support

3.6/ Version 9.5.2 => update OK
• Base packages of Plesk
• Plesk Updater
• Plesk API [former Plesk Agent]
• Plesk migration manager
• Plesk Firewall module
• Watchdog (System monitoring module)
• Plesk Backup Manager
• French language pack
• Horde webmail support
• PHP5 support

3.7/ yum update
If I do one more yum update, mysql is updated to 5.1 and then plesk refuses to start! I guess I have to apply this mysql patch here http://www.atomicorp.com/wiki/index.php/Mysql. I will try and tell here ;)

Can anybody see any mistake in my procedure?? Or any advice??

Thanks
 
Some news...
I followed the procedure to update mysql 5.1 and it's workin ;)
I had some error at the step 4 for the plesk users (mysql_upgrade -u admin -p) but plesk was still workin (like my site) with the lastest mysql 5.1.48...

I now have to redo the procedure on my prod server... Hope its gonna work too...
 
It sounds like there are some troubles. It's not that simple... I tried to redo the procedure and I have a problem with step 4 (mysql_upgrade -u admin -p)!
I cannot apply this task. I just can apply step 4 in 6th position (after step 5 = restarting mysql service)

STEP 4 : mysql_upgrade -u admin -p => FAILED
[root@s15236251 ~]# mysql_upgrade -u admin -p
Enter password:
Looking for 'mysql' as: mysql
Looking for 'mysqlcheck' as: mysqlcheck
Running 'mysqlcheck with default connection arguments
mysqlcheck: Got error: 2002: Can't connect to local MySQL server through socket
FATAL ERROR: Upgrade failed
Click to expand...

STEP 5 : /etc/init.d/mysqld restart => OK
Then if I try to restart mysql, mysql failed to reload: I have to stop first and then start mysql service! So plesk can load back OK

STEP 6 : mysql_upgrade -u admin -p
And then if I try to run this command again, it is accepted and I have lots of information....
I guess I have to repair the tables....and some other table like plesk ones probably don't have to be changed and/or cannot be repaired..!!??? I'm getting lost and don't know what to do.... My sites and plesk are working good but what do I have to do?? To skip those messages??? Any advice??? Thanks ;)

.....................................................!!!!!!!!!!!!probably lots of errors before!!!!!!!!!
psa.mn_param
error : Table upgrade required. Please do "REPAIR TABLE `mn_param`" or dump/reload to fix it!
psa.module_firewall_objects OK
psa.module_firewall_rules OK
psa.module_watchdog_disk OK
psa.module_watchdog_disk_event OK
psa.module_watchdog_param OK
psa.module_watchdog_report OK
psa.module_watchdog_service
error : Table upgrade required. Please do "REPAIR TABLE `module_watchdog_service`" or dump/reload to fix it!
psa.module_watchdog_service_event OK
psa.module_watchdog_sys_stat OK
psa.password_secrets
error : Table upgrade required. Please do "REPAIR TABLE `password_secrets`" or dump/reload to fix it!
psa.pd_users OK
psa.protected_dirs OK
psa.report OK
psa.report_auto OK
psa.report_section OK
psa.resp_attach OK
psa.resp_forward OK
psa.resp_freq
error : Table upgrade required. Please do "REPAIR TABLE `resp_freq`" or dump/reload to fix it!
psa.secret_keys
error : Table upgrade required. Please do "REPAIR TABLE `secret_keys`" or dump/reload to fix it!
psa.sessions OK
psa.siteapppackages_apscategories OK
psa.slave_params OK
psa.slaves
error : Table upgrade required. Please do "REPAIR TABLE `slaves`" or dump/reload to fix it!
psa.smtp_poplocks
error : Table upgrade required. Please do "REPAIR TABLE `smtp_poplocks`" or dump/reload to fix it!
psa.spamfilter
error : Table upgrade required. Please do "REPAIR TABLE `spamfilter`" or dump/reload to fix it!
psa.spamfilter_preferences
error : Table upgrade required. Please do "REPAIR TABLE `spamfilter_preferences`" or dump/reload to fix it!
psa.subdomains
error : Table upgrade required. Please do "REPAIR TABLE `subdomains`" or dump/reload to fix it!
psa.suspend_handler_history OK
psa.sys_users
error : Table upgrade required. Please do "REPAIR TABLE `sys_users`" or dump/reload to fix it!
psa.tts_cats OK
psa.tts_conf OK
psa.tts_priorities OK
psa.tts_queues OK
psa.tts_reporters OK
psa.tts_slave_info OK
psa.tts_ticket_events OK
psa.tts_tickets OK
psa.upgrade_history OK
psa.web_users OK
psa.webalizer_group_referrer OK
psa.webalizer_hidden_referrer OK

Repairing tables
mysql.help_category OK
mysql.help_keyword OK
mysql.help_topic OK
mysql.proc OK
mysql.time_zone_name OK
nom_base_sql.jos_categories OK
nom_base_sql.jos_components OK
psa.BackendCache
note : The storage engine for the table doesn't support repair
psa.BackupsRunning
note : The storage engine for the table doesn't support repair
psa.DashboardPreset
note : The storage engine for the table doesn't support repair
psa.DatabaseServers
note : The storage engine for the table doesn't support repair
psa.IP_Addresses
note : The storage engine for the table doesn't support repair
psa.Limits
note : The storage engine for the table doesn't support repair
psa.ListsParams
note : The storage engine for the table doesn't support repair
psa.PMMDefault
note : The storage engine for the table doesn't support repair
psa.Parameters
note : The storage engine for the table doesn't support repair
psa.Permissions
note : The storage engine for the table doesn't support repair
psa.PersistentCache
note : The storage engine for the table doesn't support repair
psa.PleskPagesStat
note : The storage engine for the table doesn't support repair
psa.SBResellers
note : The storage engine for the table doesn't support repair
psa.SSOBranding
note : The storage engine for the table doesn't support repair
psa.SiteAppsHitsStat
note : The storage engine for the table doesn't support repair
psa.Skins
note : The storage engine for the table doesn't support repair
psa.TmplData
note : The storage engine for the table doesn't support repair
psa.Webmails
note : The storage engine for the table doesn't support repair
psa.actions
note : The storage engine for the table doesn't support repair
psa.badmailfrom
note : The storage engine for the table doesn't support repair
psa.cl_param
note : The storage engine for the table doesn't support repair
psa.clients
note : The storage engine for the table doesn't support repair
psa.dom_param
note : The storage engine for the table doesn't support repair
psa.domainaliases
note : The storage engine for the table doesn't support repair
psa.domains
note : The storage engine for the table doesn't support repair
psa.key_history_params
note : The storage engine for the table doesn't support repair
psa.lockout
note : The storage engine for the table doesn't support repair
psa.log_components
note : The storage engine for the table doesn't support repair
psa.longtaskparams
note : The storage engine for the table doesn't support repair
psa.mail
note : The storage engine for the table doesn't support repair
psa.mail_aliases
note : The storage engine for the table doesn't support repair
psa.mail_resp
note : The storage engine for the table doesn't support repair
psa.mass_mail
note : The storage engine for the table doesn't support repair
psa.mn_param
note : The storage engine for the table doesn't support repair
psa.module_watchdog_service
note : The storage engine for the table doesn't support repair
psa.password_secrets
note : The storage engine for the table doesn't support repair
psa.resp_freq
note : The storage engine for the table doesn't support repair
psa.secret_keys OK
psa.slaves
note : The storage engine for the table doesn't support repair
psa.smtp_poplocks
note : The storage engine for the table doesn't support repair
psa.spamfilter
note : The storage engine for the table doesn't support repair
psa.spamfilter_preferences
note : The storage engine for the table doesn't support repair
psa.subdomains
note : The storage engine for the table doesn't support repair
psa.sys_users
note : The storage engine for the table doesn't support repair
Running 'mysql_fix_privilege_tables'...
OK
Click to expand...
 
Delete those 2 lines 11 & 20 ???? (skip-bdb)

In the original tutorial to update Mysql, I just noticed that this line "skip-bdb" is actually written twice (line 11& 20) in the file /etc/my.cnf I guess we have to delete (or comment) those 2 lines!!!!??? It's workin but just to be sure, can someone confirm this???
Step 3) MySQL 5.1 removed the BERKLEY storage engine. Since it was not commonly used, to save resources it was recommended this be turned off. You must comment the following out or remove it from /etc/my.cnf or MySQL 5.1 will not start!
 
I found some troubles with HORDE...

1/ HORDE PROBLEM WHEN CHECK SQL : Just one thing I don't understand is when I try to check the sql database, I got an error with horde
mysqlcheck -u admin -p --check /var/lib/mysql/*/*.MYI
mysqlcheck: Got error: 1049: Unknown database '/var/lib/mysql/horde/horde_datatree.MYI' when selecting the database
Click to expand...

2/ HORDE LANGUE PROBLEM : "Sent folder" cannot be created (after replying to an e-mail) because of the special caracter é used in french (Envoyés) I have found the solution but I cannot find the file on my server... http://lists.horde.org/archives/bugs/Week-of-Mon-20081117/041047.html
 
You must log in or register to reply here.

Similar threads

K
Question How does Plesk handle OS updates?
Replies
0
Views
117
Kroptokin
K
D
Issue IPV6 issue after yum update CentOS 7.9
Replies
0
Views
493
Deagan
D
H
Question Best Practice for Upgrading OpenSSL on CentOS 7.9 - Obsidian v18.0.54
Replies
2
Views
5K
IAR
IAR
D
Resolved Unable to update due to proftpd?
Replies
3
Views
944
Peter Debik
P
dotdev
Question Upgrade to openssl 1.1.1 on centOS 7 / Plesk Onyx 17.8.11
Replies
1
Views
1K
IAR
IAR
Back
Top