Post 11.0.4 Upgrade Issues/Topics Here

[wolf7901]

Please post all topics and issues related to version 11.0.4 in this thread. Thanks.

[wirtsi]

I had a problem installing the new debian packages, the scalix-tomcat_5.5.16-263_all.deb wouldn't install because of an error in the postinst script ...

To fix this

cp scalix-tomcat_5.5.16-263_all.deb /tmp
ar x scalix-tomcat_5.5.16-263_all.deb
tar xfz control.tar.gz
nano postinst ... remove ) in line 21 .. after tomcat-create-instace ""
mkdir debian
mv data.tar.gz debian
cd debian
tar xfz data.tar.gz
mkdir DEBIAN
cd ..
cp control debian/DEBIAN
dpkg-deb -b debian
mv debian.deb scalix-tomcat_5.5.16-263_all.deb

and you're sorted

wirtsi

[friedmar]

No problem!

SUSE 10.1 Upgrade from 11.0.2.1

[florian]

wirtsi,

thanks for finding this...

http://bugzilla.scalix.com/show_bug.cgi?id=15319

and I already fixed in myself for the next release, so you will get a proper package without the problem next month. This must have slipped our testing and release process, apologies.

Florian.

[eddieedwards]

I ran the installer script to upgrade from 11.0.2 to 11.0.4 and first got an error and the scalix-DB wasn't upgraded. I ran omshut and tried the installer again. This time, I only had the option of upgrading Scalix-DB, and it upgraded fine. Then, when I went to start Scalix, I got an error: "Inconsistency found between version files in sys and lib" Based on this thread: viewtopic.php?t=6575&highlight=inconsistency+sys+lib, I hacked the /var/opt/scalix/xx/s/sys/version file to match what omvers was reporting, and Scalix started OK. (I think this happened when I upgraded from 11.0.1 to 11.0.2 as well.) My only issue now, is that SWA and SAC are both still reporting themselves to be version 11.0.2.23. I can't tell if that's a glitch, intended, or if I'm not fully upgraded to 11.0.4 yet....

[florian]

i think the first check is to see what rpms are on.... rpm -qa | grep scalix should tell you that.

you shouldn't hack the version file.

the way to get to a correct match of binaries and database is to run ompatchom which will update the db to whatever the software is. your current setup is presumably inconsistent and will most likely fail again with the next upgrade; based on what you say about that systems history, this might have been induced by previous similar action. I don't think that the specific 11.0.4 upgrade code is responsible for it.

OK, let's first check the versions of the RPMs.

... Florian.

[eddieedwards]

Here are my results...

# rpm -qa|grep scalix
scalix-res-11.0.4.25-1
scalix-sis-11.0.4.25-1
scalix-postgres-11.0.4.25-1
scalix-sac-11.0.4.25-1
scalix-server-11.0.4.10790-1.rhel4
scalix-tomcat-5.5.16-263
scalix-swa-11.0.4.25-1
scalix-tomcat-connector-11.0.4.25-1.rhel4
scalix-platform-11.0.4.25-1
scalix-mobile-11.0.4.25-1

[florian]

well, that's something.

next, shutdown the server (omshut), undo you manual patch to the version file and run ompatchom and see if you can bring the server up again (omrc)

Florian.

[eddieedwards]

Hmmm... That seems to have worked, but SAC is still reporting itself as 11.0.2.23 and we get an error when using SWA: "The server failed to send back a valid XML response." (I'm trying to run down this latter problem by searching the forums. I do have e-mail support, but don't want to burn one if I can find the answer here! )

[florian]

next step...

1. shutdown tomcat (/etc/init.d/scalix-tomcat stop - check no java procs running afterwards)
2. Remove tomcat temp files

Code: Select all

cd /var/opt/scalix/<instance>/tomcat
rm -rf webapps/* work/*

3. start tomat (/etc/init.d/scalix-tomcat start)

You might also want to make sure that your browser cache is cleaned.

Florian.

[eddieedwards]

OK! That seems to be working now. Thanks! I still get the nagging problem where the "Item Structure Server" never starts up on its own. I have to implicitly start it "by hand".

[florian]

unless you want to do a specific type of single user restore (see the knowledgebase) you don't really need it, so this is the default configuration and not what i would call a problem.

if you wanted to, you could use the omsetsvc command to set it to autostart. please see the manpage for details.

Florian.