3.1.2 Matrix Server Upgrade Guide

Chapter 3: Single Upgrade Procedures 27

The following message then appears:

Stopping PolyServe Matrix Server

This server needs to be rebooted before the product removal

can proceed.

/etc/init.d/pmxs has been moved to /etc/init.d/Pmxs to avoid

PolyServe Matrix Server from starting automatically on boot.

error: %preun(pmxs-<ver>-release) scriptlet failed, exit status 1

Reboot the server and run the rpm -e command again. Matrix Server

will now be uninstalled.

NOTE: When the uninstall is complete, you will see a message listing

files and directories that could not be removed. Do not

manually remove any of these files.

8. Uninstall the Management Console:

# rpm -e mxconsole

9. Upgrade to RHEL4 or SLES9 or do a fresh installation of the operating

system. See Appendix A (RHEL4) or B (SLES9) for information about

files that need to be modified.

10. Install the Matrix Server Support RPM if necessary and install the

kernel as described in Appendix A (RHEL4) or B (SLES9).

11. If you did a fresh installation of the operating system, extract the

backup tar files saved in step 1 to /etc/opt/polyserve and /var/

optpolyserve.

12. Install Matrix Server 3.1.2 from the Matrix Server product CD or the

location where you have downloaded the software. Be sure to install

the RPM that corresponds to your architecture (i586 for 32-bit or

x86_64 for 64-bit).

# rpm -i <mountpoint>/pmxs-3.1.2-<xxxx>.<arch>.rpm

13. If you saved any Matrix Server configuration files in step 3, compare

the saved files with the new versions of the files that were installed

with Matrix Server 3.1. (The new versions were installed in the

directory /etc/opt/polyserve.) You will need to migrate your customized

values from the old files to the new files as necessary.