OS Support request.

[nvehommes]

I meant run omscan before you upgrade. The upgrade doesn't run omscan before it upgrades packages, and afterwards what you see running is not what i mean by a full omscan run in fix mode. And you want to be clean before upgrade.

To run a full fix mode omscan before upgrade.....

omscan -Aafvx

/opt/scalix/bin/sxmaint will do this for you regularly, check the scalix wiki for instructions.

This is very good, thanks a lot!

would have been nice to try and pinpoint exactly what was causing the slowness, but you've gone past that point now. I cant imagine it would have been anything permanent.

This is on my test machine, so I could give it another try and redo a migration to a freshly installed 11.4. Only problem is that I have no idea what to look for.

[nvehommes]

Hi all!

A follow-up to let the world know that the migration of our server (Scalix 11.3 on openSUSE 10.3 to Scalix 11.4 on SLES10SP2) was done today without major difficulties.
The procedure, described in detail earlier in this thread, consists of three main steps:
1. install SLES10SP2, then Scalix 11.3
2. add the message store (directories sx/s and sx/indexes, saved as tar-file) from the old server to /var/opt/scalix/sx
3. upgrade Scalix to 11.4

A few points are worth mentioning:

1. it helps to have an extra ethernet interface available: you can set up the main (eth0) interface with server name and IP, but only connect it when you are sure that everything is OK and still have network access through the second interface.
2. before starting, run sxmaint -weekly.
3. when the tar-file of /var/opt/scalix is unpacked, tar automagically sets the right UID and GID for the user "scalix". No need to force UID and GID to those of the original installation.
4. mail domains apparently are not defined in the message store. When updating the server, no maildomains except the default domain are listed. Add them during the upgrade or mail may be rejected.
5. this time, logging in on the administrative console didn't work after the upgrade. Reboot and everything was fine.


Some "first experiences":

With Scalix 11.4, the administrative console works fine with Safari 3.1.1 under MacOS X 10.5.3 (I tried several actions and everything worked as expected). Compared to Firefox 2.0.0.14, Safari feels faster.
Would be great if webmail worked under Safari as well.

After the migration, omshowlog still displays "interesting" error messages like:

Code: Select all

ERROR                          Internet Mail (Incoming      ) 06.14.08 16:06:11
[OM 3102] A Built-in Converter encountered a serious error.

ERROR                          Browser       (Index_Browser ) 06.14.08 16:06:21
[OM 3102] A Built-in Converter encountered a serious error.
  Last Msg Id: 3a1157aa9e31e8be1540651a8a675847(a)localhost.localdomain
  Last Msg DirectRef: 00018ae717ec28c4


The times correspond quite well to those of Chinese spams I see listed on the mail gateway, so I don't expect anything important to be lost. Nevertheless, more informative error messages would be nice. No error would be even better.

Mails addressed to "name" instead of "name@domain.com" still get the FQDN of the server instead of the default mail domain appended.