Updating MySQL and PSA with ART's yum

[iMedia]

I used PSA's Updater last month to updgrade from 7.5.1 to 7.5.3, had one hitch of PSA commenting-out a eithernet config line (and) the infamous ioncube/PHP glitch. All else went well...

However, I'm in desperate need to upgrade MySQL to 4.x for use of sub-selects and GROUP BY modifiers. I also want to patch PSA-hotfix.

I just discovered the wonders of ART's yum updates and have been experimenting with them (check-update, list, info, and search).

I found two issues that concern me:
1) #yum list mysql shows installed package
mysql i386 3.23.58-9.1 db

and Availabe Packages:
mysql i386 4.0.24-2.rhfc2.art atomic

More concerning...
2)#yum list psa
shows installed package:
psa i586 7.5.2-fc2.build75050128.11db

and Available package:
psa i586 7.5.3-fc2.build75050506.13psa-7.1

I thought it WAS an upgrade to 7.5.3, not 7.5.2 I'm guessing that the first Update, using PSA's Updater, didn't complete the install --- or that I needed to run it again to finalize the 7.5.3 upgrade --- or I missed something alltogether.

So my questions:
A) Why is my PSA Installed Package from "db" and the Available Package from "7.1". Is this ok, or do I have $distroverpkg set wrong?

1) if I run #yum update psa... will it conflict with PSA's Updater LAST run?

2) do I need to run #yum update psa before updating MySQL to 4.x???

3) the yum.conf is concerning me because I do not see a [PSA-7.2] channel. Is [PSA-7.1] good for all PSA 7.x versions?

4) extra: is there a Horder/IMP update via ART's yum?

5) extra: what's the recommended way to proceed, where my primary concern is upgrading MySQL?

...sorry to pick your brains like this

yum.conf:
[main]
cachedir=/var/cache/yum
debuglevel=2
logfile=/var/log/yum.log
pkgpolicy=newest
distroverpkg=redhat-release <-- is this line correct?
tolerant=1
exactarch=1

[atomic]
name=Atomic Rocket Turtle - $releasever - Atomic PSA-Compatible RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/art/$releasever/
baseurl=http://www.atomicrocketturtle.com/atomic/art/$releasever/

[psa-7.1]
name=Atomic Rocket Turtle - $releasever - SW-Soft PSA 7.5 RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/psa-7.5/$releasever/
baseurl=http://archive.atomicrocketturtle.com/atomic/psa-7.5/$releasever/
baseurl=http://www.atomicrocketturtle.com/atomic/psa-7.5/$releasever/

[atomic-app-vault]
name=Atomic Rocket Turtle - $releasever - Atomic PSA App Vault RPMS
baseurl=http://3es.atomicrocketturtle.com/atomic/app-vault/

[base]
name=Atomic Rocket Turtle - $releasever - Base OS RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-party/base/$releasever/

[updates]
name=Atomic Rocket Turtle - $releasever - OS Update RPMS mirror
baseurl=http://3es.atomicrocketturtle.com/3rd-party/updates/$releasever/

OS:
P4 3.06GHz
Version psa v7.5.2_build75050204.17 os_FedoraCore 2
OS Linux 2.6.9-041221

 

[iMedia]

I fixed yum.conf to:
[psa-7.5]

...but I still have my concerns.

 

[atomicturtle]

first for the FC2 (yum 2.1 users) I've got repo files for you here:
http://3es.atomicrocketturtle.com/yum/repos/

Just drop the repo's you want into /etc/yum.repos.d/ no further modifications should be required.


From the information Ive seen, I would say that your upgrade to 7.5.3 failed, or it just didnt even start as you expected.

I personally avoid upgrading specific packages, and go with a system wide "yum update". You'll have to run that eventually just to get your regular OS bug and security fixes, however if you did want to restrict an update to a specific package you could define, a la yum update php, or yum update mysql.

Order in regard to PSA doesnt really matter

 

[iMedia]

yum update

Ok, bit the bullet and launched #yum update!

It went well and I'm extreemly satisfied, but wanted to make note, in case others have same issues.

1) MySQL wasn't running after update completing.
#/sbin/service mysqld start

no problems!

Horde/IMP Webmail ran away!

#yum install psa-horde
#yum install psa-imp

Apache stopped after this.

I'm accustomed to #apachectl -k start|graceful|restart
etc... but received sock error
(sorry) didn't note it, was in slight panic.
so, I checked PSA Admin Panel, which was fine on httpsd and restarted Apache there.

All was well again and now happily on PSA 7.5.3, with updated services.

Thank's atomicturtle for the great service! We will be donating.

 

[iMedia]

just another note:

some of my clients use the Address Book features in Horde/IMP and it was gone after the upgrade .... just a simple install of the seperate features.

#yum install psa-kronolith.noarch psa-turba.noarch

previous address book entries were preserved.

PS: psa-kronolith.noarch is the calendar feature and psa-turnba.norach is the Address Book feature.

 

[dennysp]

Do these instructions work with RHEL3 and Plesk 7.5.3 ?

 

[dennysp]

I'm getting this error after doing
#yum update

retrygrab() failed for:
  [url]http://3es.atomicrocketturtle.com/3rd-party/updates/3ES//RPMS/initscripts-7.31.18.EL-1.centos.1.i386.rpm[/url]
  Executing failover method
failover: out of servers to try
Error getting file [url]http://3es.atomicrocketturtle.com/3rd-party/updates/3ES//RPMS/initscripts-7.31.18.EL-1.centos.1.i386.rpm[/url]
[Errno 4] IOError: HTTP Error 404: Not Found


Getting bind-utils-9.2.4-7_EL3.i386.rpm
retrygrab() failed for:
  [url]http://3es.atomicrocketturtle.com/3rd-party/updates/3ES//RPMS/bind-utils-9.2.4-7_EL3.i386.rpm[/url]
  Executing failover method
failover: out of servers to try
Error getting file [url]http://3es.atomicrocketturtle.com/3rd-party/updates/3ES//RPMS/bind-utils-9.2.4-7_EL3.i386.rpm[/url]
[Errno 4] IOError: HTTP Error 404: Not Found

Can I skip these packages safely?
EDIT: My server has RHEL 3 and plesk 7.5.3

 

[dennysp]

I'm getting this error now:

ERROR: Unable to query: Can't find file: 'misc.MYI' (errno: 2) 0: /usr/local/psa/admin/plib/common_func.php3:177 psaerror(string "Unable to query: 
Can't find file: 'misc.MYI' (errno: 2)") 1: /usr/local/psa/admin/plib/common_func.php3:365 db_query(string "select param, val from misc") 2: 
/usr/local/psa/admin/plib/class.Session.php:99 get_param(string "login_timeout") 3: /usr/local/psa/admin/auto_prepend/auth.php3:114 session->session()

and this when I try to start PSA

[root@bigkitty /]# service psa startall
Starting named:                                            [  OK  ]
Starting qmail:                                            [  OK  ]
Starting Courier-IMAP server:
   Starting imapd                                          [  OK  ]
   Starting imap-ssl                                       [  OK  ]
   Starting pop3                                           [  OK  ]
   Starting pop3-ssl                                       [  OK  ]

Unable to fetch SpamAssassin config from database: Can't find file: 'sa_conf.MYI' (errno: 2)
Starting psa-spamassassin service:                         [FAILED]
ERROR 1017 at line 1: Can't find file: 'DomainServices.MYI' (errno: 2)
[root@bigkitty /]#

 

[dennysp]

Can someone please help? I need to get this fixed. Now my webmail also doesn't work, I get "Login failed" when trying to login. Something got screwed big time. I checked my psa database backup for these MYI files, and they are not there either!!
Is there a way to tell plesk not to load spamassassing at start up???

EDIT: I'm willing to pay to someone who fixes this issue, as I need to get the server back up.


Thanks
-d

 

[serve-you.net]

There shouldn't be MYI files for the PSA db. That is a table index for MyISAM type tables. PSA does not use MyISAM tables, so I'm not sure why it's looking for those, unless you are on an old build of Plesk.

Need a bit more information to help you.
Is your MySQL server starting up properly? What version of Plesk do you have installed? What OS? What's in your yum.conf?

 

[serve-you.net]

Actually, now that I look closer, it sounds like you may have partially upgraded Plesk from something prior to 7.5.3. I looked at an old mysql backup from 7.5.2, and there were in fact MyISAM tables in the psa db.

 

[dennysp]

Thanks for replying, however, I had someone fix it for me. I couldn't afford to have the system down.
The problem was the mysql 4 configuration had messed up the psa db. Also my spamassassin got upgraded to version 3 which doesn't work with plesk and that in turn corrupted mailfiles.

Thanks a bunch to Andrew @ Transnexis for his quick and effective resolution.

-d

 

[dennysp]

I seem to be having another problem now. Every day I get a rogue httpd process that causes my CPU usage to sky rocket.
I have noticed though that I'm no longer running the RHEL version of apache, but insted a CentOS version (from ART yum repo). I would like to know how I can go back to the original redhat RPM, since I never had this problem with that one. BTW, my up2date no longer checks for RHEL packages, but instead it looks at centos channels, can this be fixed?

Thanks in advance
-d

 

[serve-you.net]

Well, if you are getting cent packages from up2date, it would probably be because someone aither changed your /etc/redhat-release file, or added the cent repos to your /etc/sysconfig/rhn/sources file. As for the version of apache, you can force a "downgrade" to the version RH supplies by downloading it, and doing rpm -Uvh --oldpackage file1.rpm file2.rpm

 

[dennysp]

Thanks, I found the yum channels added to the sources files, and commented them out.
Now, my problem is that when I try to do a "downgrade", I get the error

 file /usr/share/doc/httpd-2.0.46/migration.html conflicts between attempted installs of httpd-2.0.46-46.highfd.rhel3.art and httpd-2.0.46-25.ent

on a lot of files. I alsot tried to uninstall the existing apache version but I get a lot of warnings about dependencies. Can I ignore dependencies and then install the RHEL version of apache from the rhel cd ?

thanks in advance
-d

 

[serve-you.net]

If you are feeling brave, you can do the following with the RPM's from RH:
rpm -Uvh --force httpd httpd-devel

However, this is probably not necessary at all. The only difference in the RH ROM's and ART's, are that Scott added in support for 1024 file descriptors vs the default limit of (I believe 512). If you have an apache process that's running away, then you have a poorly coded site somewhere. Probably a CGI or PHP script thats buggy.

 

[dennysp]

You were right, I found the script that was causing this Thank you much

 

[atomicturtle]

I think I did 8192 on those

 

[serve-you.net]

That's much higher than I can count!