Update Problem 8.1.1 -> 8.2.0 MySQl Problem

[SauerRam]

First of all, excuse me if my english isn't the very best.

I tried to handle the Update from 8.1.1 to 8.2.0, but it seems it dislikes my updated MySQL server version.

When I first tried to Update, i got following error in my email response

The following could cause the installation failure: Packages "mysql-client-4.1.10a-3.x86_64" and "MySQL-server-5.0.37-0.glibc23.x86_64" cannot be installed at the same time

Detailed Status Report:
http://www.sauerram.net/docs/error1.txt

The next Update trials brought back some different error reasons, but they are all connected with problems starting MySQL server.

At the Moment my Updatelist shows only version 8.2.0, which isn't completely installed. Over all Plesk seems to work, never the less Update isn't finished, not even Base packages of Plesk is up to date.

Has somebody any kind of solution to fix my problem and get the update working?

SauerRam

Edit:

There are some troubles occured:

ERROR: PleskMainDBException
MySQL query failed: Unknown column 'uid' in 'field list'

Additionally, an exception has occurred while trying to report this error: PleskMainDBException
MySQL query failed: Unknown column 'uid' in 'field list'

0: /usr/local/psa/admin/plib/common_func.php3:216
db_query(string 'select `id`,`cr_date`,`cname`,`pname`,`login`,`account_id`,`status`,`phone`,`fax`,`email`,`address`,`city`,`state`,`pcode`,`country`,`locale`,`limits_id`,`params_id`,`perm_id`,`pool_id`,`logo_id`,`tmpl_id`,`sapp_pool_id`,`uid`,`ownership` from clients where `id`=6')
1: /usr/local/psa/admin/plib/class.Table.php:180
Table->select()
2: /usr/local/psa/admin/plib/class.cObject.php:443
cObject->fetchAttrsFromTable_()
3: /usr/local/psa/admin/plib/class.Client.php3:74
Client->Client(integer '6')
4: /usr/local/psa/admin/plib/common_func.php3:2867
objectMaker(string 'Client', integer '6')
5: /usr/local/psa/admin/plib/class.Manager.php:679
Manager->createMainObject(integer '2')
6: /usr/local/psa/admin/plib/class.Manager.php:126
Manager->Manager(integer '3', integer '6')
7: /usr/local/psa/admin/htdocs/domains/domains.php3:64

 

[Angels]

Which exact OS do you run?

 

[SauerRam]

SUSE 9.3 64-Bit

 

[Angels]

So its a different problem to the one i solved (debian sarge).

It seems, that you want to install a new SERVER over an old CLIENT. Either you install the SERVER matching the CLIENT Version (or was it other way arround *shrug) or you deinstall the old version first

Hope this helps a bit - i am not that familiar with plesk + suse

 

[SauerRam]

This is exactly what i wanted to avoid...

Now I've installed mysql-client verion 5.0.45
mysql-server 5.0.37 is still running.
I hope this little different version may help, or do i have to upgrade server to same version to?

In the meantime a new problem occured...
Plesk is saying my partition named 'none' which, i believe, doesn't exist is 100% full.

Here the Plesk Output:

Filesystem all used available capacity
/dev/md5 4 767.00 MB 2 259.12 MB 2 507.88 MB 47.39%

/dev/md6 4 767.00 MB 512.69 MB 4 254.31 MB 10.75%

/dev/md8 121 047.93 MB 23 157.12 MB 97 890.81 MB 19.13%

/dev/md1 949.49 MB 457.81 MB 443.45 MB 48.22%

proc 0.00 MB 0.00 MB 0.00 MB 0%
sysfs 0.00 MB 0.00 MB 0.00 MB 0%
tmpfs 492.79 MB 0.00 MB 492.79 MB 0%
devpts 0.00 MB 0.00 MB 0.00 MB 0%
/dev/md7 19 074.94 MB 35.82 MB 19 039.11 MB 0.19%
none 492.79 MB 492.79 MB 0.00 MB 100%


When i now try running autoinstaller in Command line, it tells me, there is not enough space, and asks me if i want to use a standard certificate
Maybe because of this unknown full partition.
When i checked my fstab in yast, i couldn't find a partition with a sice of 492.79MB how plesk is telling me.
There only thing i could believe is, that this unknown partition is a cd, but i haven't checked it yet.
Why should there be a cd listed in Plesk?

ATM I'm really helpless.

Greez SauerRam

Edit:

s15244998:/dev # mount
/dev/md1 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /dev/shm type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/md5 on /usr type xfs (rw)
/dev/md6 on /var type xfs (rw,usrquota)
/dev/md7 on /home type xfs (rw,usrquota)
/dev/md8 on /srv type xfs (rw,usrquota)
none on /tmp type tmpfs (rw)

maybe i should clean up my tmp directory?

Edit2:
Now I checked out my tmp dir, and found a about 400MB large plesk backup file, i tried to make today, and after deleting it, I try now to update Plesk again, lets look what happens.
Now I know at least where my backup got lost^^

 

[SauerRam]

I think I finally found the reason.
Now i have installed mysql server and client both with version 5.0.37, and get to the same result.

Autoinstaller works fine, till he gets to a package using mysql, i believe.

Autoinstaller Output:

Paket wird installiert psa-spamassassin-8.2.0-suse9.3.build82070706.15.x86_64
Trying to start MySQL server...
ERROR while trying to start MySQL server
Check the error reason(see log file: /tmp/psa-spamassassin_8.2.0_suse9.3.build82070706.15_upgrade.070712.21.21.log), fix and try again

Aborting...

error: %pre(psa-spamassassin-8.2.0-suse9.3.build82070706.15) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping psa-spamassassin-8.2.0-suse9.3.build82070706.15
ERROR: An error occurred during installation of packages.
Achtung! Ihre Software ist vielleicht nicht betriebsbereit.
Bitte kontaktieren Sie den technischen Produktsupport.

Errorlog looks like this:

START psa-spamassassin-8.2.0-suse9.3.build82070706.15 upgrading AT Do Jul 12 21:21:52 CEST 2007
Usage: /etc/init.d/mysql {start|stop|restart|reload} [ MySQL server options ]
Trying to start MySQL server... Usage: /etc/init.d/mysql {start|stop|restart|reload} [ MySQL server options ]
Starting MySQL..done
Usage: /etc/init.d/mysql {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysql {start|stop|restart|reload} [ MySQL server options ]
...
The same s*** about 50 times
...
Usage: /etc/init.d/mysql {start|stop|restart|reload} [ MySQL server options ]
Usage: /etc/init.d/mysql {start|stop|restart|reload} [ MySQL server options ]

ERROR while trying to start MySQL server

Aborting...

STOP psa-spamassassin-8.2.0-suse9.3.build82070706.15 upgrading AT Thu Jul 12 21:22:58 CEST 2007

The question is, why can't mysql be started?
mysql-server works
mysql-client works
both same versions...
mysql startscript is present at /etc/init.d/

Thanks to everyone who can help solving this problem.
Greez SauerRam

 

[shall]

The question is, why can't mysql be started?

It's not that MySQL isn't getting started, but that the MySQL init script doesn't support the 'status' verb, which the Plesk installer is using to determine if the MySQL service is running okay. The version of MySQL you (and I) have installed does not support it - only "{start|stop|restart|reload}", so it is returning an error with a syntax suggestion.

My next chore is to go digging into the installer to find out if I can prevent this, or skip it or something, so I can get Plesk up and running and Watchdog back.

 

[shall]

Okay, I fudged the init script to enable the status verb. This MUST be done individually on each of your systems, since there's no way to ensure that there isnt something else in the existing init script that might be harmed by just overwriting it.

Your mileage may vary, of course, but this should give you an idea of how to toy with the init script to make it compatible with Plesk 8.2.

BEFORE DOING ANYTHING, BACK UP ANY FILES YOU PLAN TO TOUCH!


Now let's get dirty.

Edit this file:
/etc/rc.d/init.d/mysqld
Which may actually be this file, depending on your config:
/etc/rc.d/init.d/mysql

Find a few lines like this in it:

    ;;

  'restart')

This is the end and beginning of a new code block in the verb variable checks.

Change it to look like this:

    ;;

  'status')
    status mysqld
    ;;

  'restart')

Now scroll WAY up. We want to be right under the comments and main variable assignments, so this is VERY subjective. On mine this was at line 78 (right above a variable assignment to "lsb_functions=". Make sure the line we're adding does NOT already exist in the file. Add this code (again, this might be different for different systems, but it's unlikely):

# Source function library.
. /etc/rc.d/init.d/functions

That adds the ability for the init script to access some native functions (like "pidof" which is the one actually used to check status, again, at least on my system)


Now save it and try it at a prompt with:

# service mysqld status

Mine returned something like:

mysqld (pid 12345) is running...

Now I'm off to try it with the Plesk autoinstaller - let's hope it just works.

 

[shall]

It worked!

Name                                    Version        Rel
----------------------------------------------------------
psa-firewall                            1.0.1          rhel4.build82070706.15i586
psa-watchdog                            2.0.2          rhel4.build82070706.15i586


Testing package set / solving RPM inter-dependencies...
psa-firewall-1.0.1-rhel4.bu  Retrieved.
psa-watchdog-2.0.2-rhel4.bu  Retrieved.
Preparing               Trying to establish test connection... connected
done
===> Checking database

Installing /var/spool/up2date/psa-watchdog-2.0.2-rhel4.build82070706.15.i586.rpm...
 Trying to establish test connection... connected
done
===> Setting up file owners
===> Installing database
===> Registering module
 Trying to establish test connection... connected
done
===> Checking database
===> Checking kernel support for iptables

Installing /var/spool/up2date/psa-firewall-1.0.1-rhel4.build82070706.15.i586.rpm...
warning: /etc/init.d/psa-firewall saved as /etc/init.d/psa-firewall.rpmorig
warning: /etc/init.d/psa-firewall-forward saved as /etc/init.d/psa-firewall-forward.rpmorig
 Trying to establish test connection... connected
done
===> Setting up file owners
===> Installing database
===> Installing configuration files
===> Registering services
 Trying to register service psa-firewall...  using /sbin/chkconfig
done
===> Registering module
[COLOR=red][B]The packages were installed successfully.[/B][/COLOR]

 

[Angels]

congratulations

 

[SauerRam]

Thanks for that issue, it worked, but now theres a new problem... i cant start plesk...

/etc/init.d/psa status
psa dead but subsys locked

I tried 'psa stopall', delete syslog and start it again, didn't work...
First it failed to start postgresql, and because I didn't need it, I changed /etc/init.d/psa.
Now i get the following

s15244998:/etc/init.d # ./psa stopall
Stopping Plesk... done
Stopping named service... done
Stopping mysql service... done
Stopping qmail service... done
Stopping courier-imap service... done
Stopping psa-spamassassin service... done
Stopping drwebd service... done
Stopping tomcat5 service... done
Stopping apache2 service... done
s15244998:/etc/init.d # ./psa startall
Starting xinetd service... done
Starting named service... done
Starting mysql service... done
Starting qmail service... done
Starting courier-imap service... done
Starting psa-spamassassin service... done
s15244998:/etc/init.d # ./psa start
Starting xinetd service... done
Starting named service... done
Starting mysql service... done
Starting qmail service... done
Starting courier-imap service... done
Starting psa-spamassassin service... done
Starting Plesk... done
Starting drwebd service... done
s15244998:/etc/init.d # ./psa status
psa dead but subsys locked
s15244998:/etc/init.d #

I believe drwebd wasn't started correctly...
any reason?

 

[mortal]

Hi. for suse 10 users. i found through plesk support that

it had to be

'status')
#status mysqld
;;


instead of

'status')
status mysqld
;;

im not really sure if it then has any effect.

in file /etc/init.d/mysql status line 236 in my case. the functions line did not have to be implemented. after this mod. plesk support ran the update with no problems. but i dont know how they did it


the exact mail

Hello,

I found that there was something wrong with /etc/init.d/mysql script. It got failed on "status" option:

w2wdomain:~ # /etc/init.d/mysql status
/etc/init.d/mysql: line 236: status: command not found
w2wdomain:~ #

I patched the script and then I updated Plesk fine.

Please let us know if something goes wrong.

 

[shall]

Originally posted by SauerRam
Thanks for that issue, it worked, but now theres a new problem... i cant start plesk...

/etc/init.d/psa status
psa dead but subsys locked

The EXACT same thing happened to me. I spent an hour or more futzing with it when my colo finally managed to get Plesk to look into the system.

From the logs, it looks like they created a new MySQL backup, removed and reinstalled Plesk, and then restored their backup to re-engage the settings. A couple modules still didn't work (firewall and watchdog), so they removed and reinstalled those again, and they worked.

Plesk 8.2 is working for me now.

From this I think the best I can surmise is, run a full PSA backup, remove and reinstall (make sure you have your keyfiles so you can re-register if necessary), and you'll have it working again. A failed Plesk install doesn't leave significant garbage, but it will need completely removed and reinstalled in order to be reliable. Again, MAKE THE BACKUPS. This was the absolutely first thing they did upon logging in. Before even testing to see if Plesk was working. That's the best thing they did. Most people might "fiddle" a bit first.

I just gotta wonder if the whole process was automated. Making backups, removing Plesk (and all it's components), reinstalling and restoring the backup has gotta be only a couple dozen consistent lines of code for each platform.

 

[SauerRam]

I feared I've to do this... especially because i've never done this before... maybe someone can give me a hint?

 

[dredding]

There are some troubles occured:

quote:ERROR: PleskMainDBException
MySQL query failed: Unknown column 'uid' in 'field list'

Additionally, an exception has occurred while trying to report this error: PleskMainDBException
MySQL query failed: Unknown column 'uid' in 'field list'

0: /usr/local/psa/admin/plib/common_func.php3:216
db_query(string 'select `id`,`cr_date`,`cname`,`pname`,`login`,`account_id
`,`status`,`phone`,`fax`,`email`,`address`,`city`,
`state`,`pcode`,`country`,`locale`,`limits_id`,`pa
rams_id`,`perm_id`,`pool_id`,`logo_id`,`tmpl_id`,`
sapp_pool_id`,`uid`,`ownership` from clients where `id`=6')
1: /usr/local/psa/admin/plib/class.Table.php:180
Table->select()
2: /usr/local/psa/admin/plib/class.cObject.php:443
cObject->fetchAttrsFromTable_()
3: /usr/local/psa/admin/plib/class.Client.php3:74
Client->Client(integer '6')
4: /usr/local/psa/admin/plib/common_func.php3:2867
objectMaker(string 'Client', integer '6')
5: /usr/local/psa/admin/plib/class.Manager.php:679
Manager->createMainObject(integer '2')
6: /usr/local/psa/admin/plib/class.Manager.php:126
Manager->Manager(integer '3', integer '6')
7: /usr/local/psa/admin/htdocs/domains/domains.php3:64

To correct this, run these statements in mysql:

use psa;
ALTER TABLE clients ADD uid VARCHAR(36);
ALTER TABLE clients ADD ownership ENUM('true','false') default "true";

 

[shall]

To correct this, run these statements in mysql:

use psa;
ALTER TABLE clients ADD uid VARCHAR(36);
ALTER TABLE clients ADD ownership ENUM('true','false') default "true";

When I went through this same experience, I went through every table within the server that was messed up and the one that worked (I had two RHEL5 servers with almost every setting the same; one updated flawlessly, the other was hosed), migrating database schema changes between them.

The two changes above are only a small sampling of the changes that were made - and it will *not* fix the problem. It will make the one error go away, but the error is only a symptom of an incomplete update. There are files that are still out of sync, and if you just try to migrate the database changes your server will get screwed up even worse once you try manipulating user accounts.