Ugrading 3.16.6 to 3.18coupled with move to new machine

Squiz Matrix Installation
1

Hi,


I'm trying to upgrade from 3.16.6 to 3.18. The 3.16.6 machine is running RHEL4, the 3.18 machine is running RHEL5.1, fully patched. I've made sure that the PEAR requirements are met.



I've made a backup of the matrix installation on the 3.16 site using scripts/backup.sh



I then restore this onto the new machine. Same path and system root URL - if the upgrade works I can move the IP address to the new machine instantly on a spare network card.



Once I reach step03 though, I get the following error:



±-----------------------------------------------------------------+

| MySource Warning |

|------------------------------------------------------------------|

| Asset #12 does not exist [SYS0087] |

±-----------------------------------------------------------------+



Fatal error: Argument 1 passed to MySource::setCurrentUser() must not be null, called in /<path_removed>/mysource_matrix/install/install.inc on line 351 and defined in /<path_removed/mysource_matrix/core/include/mysource.inc on line 1445



and so cannot carry on.



Asset 12 is the Root User - found in System Administrators



I'm not going to do an OS upgrade on the RHEL4 machine in place as I can't be sure this problem won't arise further down the line.



Any advice appreciated.



M.

2

Part of that backup is a dump of the PostgreSQL database. Once you unpack the tarball on the new server, you will need to recreate the database and restore the data from the original server. You should ensure that PostgreSQL creates the database with the correct encoding (SQL_ASCII) as the default on 5.1 is now UTF8. Otherwise, the data probably won't restore properly.
3

Ah - that's right - I'll try again now. Many thanks for that suggestion - I'll let you know if that's it.

4

It's solved the issue.


For future reference, the full command is:



createdb -U postgres -O matrix mysource_matrix -E SQL_ASCII



to get that coding.



Many thanks.



M.

5

Hi Folks,


I have a different problem… testing the upgrade on a backup machine…



  • restored a copy of the 3.16.6 DB
    [*] unpacked 3.18
    [*] copied in the data folder from unpacked 3.16.6 backup (did get asked about overwriting some CVS files - but tried it saying yes and saying no - both times same error below)
    [*] ran all the upgrade scripts / SQL etc
    [*] startup httpd


When I try to login I get 'Login Key incorrect' - the second time I hadn't looked the the new site til I cleared the browser of all cookies etc

Any Ideas?

K
6

You've added the new db.inc configuration in v3.18? You're sure Apache is pointing to the new, upgraded version?
7

If the backup machine uses a different URL, is the URL(s) for that server in your main.inc configuration file, or has it been updated to include them? One major reason for "Login Key Incorrect" errors is that your browser cannot save the cookies required to keep you logged in, because it's trying to save the cookies to one of the URLs set for Matrix to use, and browsers generally won't allow that for security reasons.

8

Thanks - I did have that in but took out a the original server's IP address and then it started working... dunno why that would effect it.

K