scalix-postgres failed after upgrade to 11.4.2

[daniel]

Hello,

After upgrade to version 11.4.2 scalix-postgres failed by startup and manually. In the pgstartup.log I get the following error:

FATAL: unbekannter Konfigurationsparameter Ä>>redirect_stderrÄ<<

Any idea what's wrong here?

[schmoe90]

What did you upgrade from?

Babelfish makes the error "unknown quantity configuration parameter", so I'd make sure that you have the right /etc/init.d/scalix-postgres file - I have:

# Version 8.1 Devrim Gunduz <devrim@PostgreSQL.org>

in the header.

It seems to be complaining about redirecting stderr, but the only redirects I can find are to /dev/null and $PGLOG

PGLOG=$INST_DIR/pgstartup.log

so I don't think that's quite right. Any more information in the log?

[daniel]

I upgrade from SUSE 10.2 to SUSE 11.0 and then from scalix 11.2.0 to 11.4.2.



That is all, what is written to the /var/opt/scalix/ml/postgres/pgstartup.log:

FATAL: unbekannter Konfigurationsparameter »redirect_stderr«

For every startup test one line.



That is all, what is written at this date to the /var/opt/scalix/ml/s/logs/fatal:

SERIOUS ERROR CDA Server (CDA Server ) Sun Nov 9 20:29:04 2008
[OM 28664] There is already a CDA server process running
Pid of logging process: 3055


ERROR Administration(Scalix Admin C) Sun Nov 9 21:42:02 2008
[SYS 2] No such file or directory
Pid of logging process: 12580
Current errno value: 2


ERROR Administration(Scalix Admin C) Sun Nov 9 21:44:38 2008
[SYS 2] No such file or directory
Pid of logging process: 13717
Current errno value: 2



Show the following output of the commands omstat -a and omstat -s:

mail:~ # omstat -a
PC Monitor Started NON-STOP 0
Directory Relay Server Started 11:52:50
Notification Server Started 11:52:50 0
Shared memory daemon Started NON-STOP
Notification Monitor Started NON-STOP
Session Monitor Started NON-STOP
Indexer Started NON-STOP
Stats Daemon Started NON-STOP
Container Access Monitor Started NON-STOP
Item Structure Server Stopped 11.09.08
Database Monitor Started 11:52:50
Licence Monitor Daemon Started NON-STOP
LDAP Daemon Started 11:52:50
Queue Manager Started NON-STOP
Item Delete Daemon Started NON-STOP
IMAP Server Daemon Started 11:52:50
SMTP Relay Started 11:52:50
Mime Browser Controller Started 11:52:50
Event Server Started 11:52:50


mail:~ # omstat -s
Service Router Started 11:52:51 0
Local Delivery Started 11:52:51 0
Internet Mail Gateway Started 11:52:51 0
Local Client Interface Enabled 11:52:51 0
Remote Client Interface Enabled 11:52:51 2
Test Server Started 11:52:51 0
Request Server Started 11:52:51 0
Print Server Started 11:52:52 0
Bulletin Board Server Started 11:52:52 0
Background Search Service Started 11:52:52 0
CDA Server Started 11:52:52 0
POP3 interface Started 11:52:52 0
Omscan Server Started 11:52:52 0
Proxy Folder Service Started 11:52:52 0


Any idea?

[LeslieW]

That error message is not very helpful, unfortunately

I'd first check to see if postgres is running:
service postgres status

If it is, I'd shut down Scalix:
omshut

Then I'd run the scalix-installer and remove the DB component.

Then I'd remove
/var/opt/scalix/??/postgres
if it is still there

Then re-install the DB component.

[marcust]

Hello,

I had the same error when upgrading scalix, the redirect_stderr directive is no longer valid with postgres 8.3, also the data store cannot be used any further. I would think a migration of the data from postgres 8.1 to 8.3 would be needed.

Does the removal of the database component have any impact on the mailstore or any other components? Then this would be a good idea.

Regards,

Marcus

[Valerion]

The PostgreSQL database stores cache data used by SWA, Scalix Mobile Client and CalDAV. You should be able to recreate it without a issue, the system can rebuild the contents over time. Not having it installed does affect the components mentioned earlier.

[daniel]

Scalix support deinstalls and installs the datebase with scalix installer and recreates the database data with sxapiprep.py.