Upgrade 11.0.2 to 11.0.3 fails.

[joaster]

Hi,

When upgrading 11.0.2 to 11.0.3 the proces fails at:

-> Please specify comma-separated list of IP addresses where Scalix Messaging Services is or will be installed [xxx.yyy.zzz.aaa]:
Configuring PostgreSQL...
Fatal error occured: Msg: An error occurred configuring Web applications -- check the log for errors.

I remebered I had the same problem upgrading from 11.0.1 to 11.0.2. However when I continue to restart all the services I can use the Scalix machine.

But today I noticed that SWA and SAC are still displaying versions 11.0.1.22 on the logon screen. Does this mean SWA and SAC are not upgraded at all (both upgrades)?

However SAC \ Server Info tells me everything is upgraded (11.0.3.31), which information is displayed correctly? And how can I avoid the fatal error that occurs?

I am a little bit lost here. Who can help me make a consistent installation again.

Regards,
Joost.

[joaster]

Found the log file of the upgrade...

The fatal error is cause because the password cannot be set?

2007-04-12 01:43:18,665 ERROR Operation failed: Failed to set password for the 'scalix' database user.

How can I resolve this?

Regards,
Joost.

[ScalixSupport]

Hi Joost!

Follow the link below:
viewtopic.php?t=6219

See if this helps.

Thanks,
Subir

[joaster]

Subir, thanks for the link.

I got it working (all version 11.0.3 now).

Regards, Joost

[swordfish]

Did you try to change your postgress database password from the old one during the upgrade for this problem to happen or it's some sort of "bug" with the upgarde?

[joaster]

Swordfish,

I don't think it is a bug in the upgrade (I had it before when upgrading from 11.0.1 to 11.0.2). However from the notes of the two upgrades I noticed that before the upgrade I did shutdown several services including 'scalix-postgres'. Turning on this last service before running the installer solved my problem.

The installer however could be improved by checking which services should and should not not running during the upgrade!

Regards,
Joost.

[newbiez]

hi.. I'm having similar problem. But I did upgrade manually by rpm -Uvh scalix-xxxxx
I also have tried to re-configure the database (postgres), but somehow, all the web pages are still displaying old version. But if I check from the sac server info, all of the scalix component are already upgraded. Any idea?

thanks.

[newbiez]

hi..

it works now. all I have to do is just reconfigure the whole stuff using scalix_installer.

[PedanticAss]

Hi,
(Ubuntu 6.06.1 lts & scalix 11.0.3 upgrade from 11.0.2.21 running in a vmware session)
I'm having a *similar* problem - my postgres looks fine, but my version numbers are off for both sac & webmail.

The general feel is the next step is to "reconfigure the whole stuff using scalix_installer" or "Reconfiguring the Scalix DB component with the Scalix installer this should configure PostgreSQL now.".

As I'm on the debian base I have no installer - anyone any ideas?

Thanks in advance.

[ScalixSupport]

Hi PedanticAss!

Try to redo the steps mentioned under step # 10 Setting up Scalix-Postgres and step # 11.4
Configuring Scalix Messaging Services API Platform, restart scalix, scalix-tomcat and
scalix-postgres services, keep a track of the postgres logs at location:

Code: Select all

/var/opt/scalix/??/postgres/pgstartup.log

If installer still fail to work, get back to me with the non-commented lines from the file:

Code: Select all

/var/opt/scalix/??/postgres/data/pg_hba.conf

Feel free to reply here?

Thanks,
Subir

[PedanticAss]

Hi and thanks for the response

I looked at the files mentioned in the setup, but they look like my original 11.0.2.21 and didn't need any tweaking

A quick checkpoint ( echo . > ./pgstartup.log) of the pgstartup.log followed by a scalix-postgres restart.

Code: Select all

.
LOG:  received fast shutdown request
LOG:  shutting down
LOG:  database system is shut down
LOG:  database system was shut down at 2007-04-27 11:25:36 BST
LOG:  checkpoint record is at 0/33B1DC
LOG:  redo record is at 0/33B1DC; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 571; next OID: 16386
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system is ready
LOG:  transaction ID wrap limit is 2147484146, limited by database "postgres"


I have not seen anything that looks like errors in this file since I followed ;

Code: Select all

http://www.scalix.com/forums/viewtopic.php?p=27995#27995

Uncommented parts of pg_hba.conf :

Code: Select all

host    scalix      scalix      10.250.253.251/32   md5
local   all         all                               trust
host    all         all         127.0.0.1/32          trust
host    all         all         ::1/128               trust


All that seems to be wrong is the version number reported by both sac and webmail.

Thanks again for the assist.

[ScalixSupport]

Hi!

Could you tell me the value within the file, /var/opt/scalix/??/s/sys/version?
Also, tell us the value for:
1. res.version= in the file /var/opt/scalix/??/res/config/res.properties
2. ubermanager.version= in the file /var/opt/scalix/??/caa/scalix.res/config/ubermanager.properties
3. swa.version= in the file /var/opt/scalix/??/webmail/swa.properties

Thanks,
Subir

[PedanticAss]

Hi

/var/opt/scalix/??/s/sys/version

Code: Select all

11.0.3.10719

res.properties

Code: Select all

res.version=@MAJOR@.@MINOR@.@PATCH@

ubermanager.properties

Code: Select all

ubermanager.version=@MAJOR@.@MINOR@.@PATCH@

swa.properties

Code: Select all

swa.version=11.0

Thanks again

[ScalixSupport]

Hi!

Set the value "11.0.3" for both res.version and ubermanager.version in files res.properties
and ubermanager.properties respectively. Restart tomcat and check the version again.

Thanks,
Subir

[PedanticAss]

Firstly an admission:

The version I am upgrading from is NOT 11.0.2.21 it is 11.0.2.23 !

My bad - sorry for the wrong info.

Thanks again for the assist.

I have made those changes and done a scalix-tomcat restart and an apache2 restart for luck.

Sadly sac and webmail still show version 11.0.2.23 on their respective logon pages.