Scalix 11 Installation on Debian Etch / Testing

[nenad]

yes , it works that way:

Code: Select all

root@scalix:~# host=$(hostname)
root@scalix:~# short=${host:0:1}${host: -1:1}
root@scalix:~# echo $short
sx
root@scalix:~#


[nenad]

Code: Select all

root@scalix:~# ps xa|grep postmaster
 2055 ?        S      0:00 /usr/lib/postgresql/7.4/bin/postmaster -D /var/lib/postgresql/7.4/main
 2984 pts/0    R+     0:00 grep postmaster
root@scalix:~#

This is output as you requested

Thank you very much for your help and your time.

[christoph.lukas]

Code: Select all

root@scalix:~# ps xa|grep postmaster
 2055 ?        S      0:00 /usr/lib/postgresql/7.4/bin/postmaster -D /var/lib/postgresql/7.4/main
 2984 pts/0    R+     0:00 grep postmaster
root@scalix:~#

This is output as you requested

Thank you very much for your help and your time.

Hm. This is only your standard postgresql running. Your Scalix postgresql is not running.

Does it start if you manually do a

Code: Select all

/etc/init.d/scalix-postgres start

Normally it should be running just after the installation of the scalix-postgresql package. Could you try to purge all packages and run the script step by step by copy and pasting one instruction after another?
When you execute the installation of the scalix-postgres package check for any error message from the postinstall script. And just afterwards check if the scalix postgres is running.

If everything is ok, the command:

Code: Select all

ps xa|grep postmaster

should show one postmaster process similar to this:

Code: Select all

/usr/lib/postgresql/7.4/bin/postmaster -i -h your-hostname -p 5733 -D /var/opt/scalix/xx/postgres/data -k /var/opt/scalix/xx/postgres/data


Regards,
Christoph

[nenad]

Code: Select all

root@scalix:~# /etc/init.d/scalix-postgres start
Starting scalix-postgres service (scalix): ok

root@scalix:~# ps xa|grep postmaster
 2067 ?        S      0:00 /usr/lib/postgresql/7.4/bin/postmaster -D /var/lib/postgresql/7.4/main
 2732 pts/0    R+     0:00 grep postmaster
root@scalix:~#


It seems that /etc/init.d/scalix-postgres start
starts scalix-postgres service.
But once when it is checked with ps xa|grep postmaster
it shows that it is running here /var/lib/postgresql/7.4/main

I think that error occurs here:

Code: Select all

root@scalix:/opt/scalix-postgres/bin# ./sxpsql-setpwd $dbpwd
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/opt/scalix/sx/postgres/data/.s.PGSQL.5733"?


Code: Select all

root@scalix:~# locate PGSQL
/var/run/postgresql/.s.PGSQL.5432
/var/run/postgresql/.s.PGSQL.5432.lock
root@scalix:~#


It seems that postgres is running on one socket and scalix-postgres is expecting to find it on another socket?

I will try to change settings in postgresql.conf for port and for directory in /var/lib/postgresql/7.4/main

Code: Select all

#port = 5432
port = 5733
#unix_socket_directory = '/var/run/postgresql'
unix_socket_directory = '/var/opt/scalix/sx/postgres"
#unix_socket_group = ''


Hmmm, this was a failure. I changed port but postgres won't accept /var/opt/scalix/sx/postgres for a socket directory. Mybie should I then change settings in scalix-postgres and make it expect unix socket on /var/run/postgresq instead of /var/opt/scalix/sx/postgres ??

Note: postgresql server is restarting with: /etc/init.d/postgresql-7.4 restart instead of /etc/init.d/postgresql restart

Anyway, if this brings no results I will erase server, and perform clean OS install and then I will execute your script line by line, and I will notify you about each error.[/code]

[christoph.lukas]

The scalix-postgres package installs a second postgres database in /var/opt/scalix/xx/postgres/data.
So in a normal setup there should be two postmaster processes running. One from the normal debian postgres package, one from the scalix-postgres package.

The scalix postgres db is started on port 5733, the debian postgres db is running on port 5432.

Code: Select all

root@scalix:~# /etc/init.d/scalix-postgres start
Starting scalix-postgres service (scalix): ok

root@scalix:~# ps xa|grep postmaster
 2067 ?        S      0:00 /usr/lib/postgresql/7.4/bin/postmaster -D /var/lib/postgresql/7.4/main
 2732 pts/0    R+     0:00 grep postmaster
root@scalix:~#


This postmaster process is the one from the normal debian package, not the scalix one.
This is a little bit strange as the init script does not give any error but the scalix postgres db is not running afterwards.

Please run:

Code: Select all

ls -la /var/opt/scalix/sx/postgres/data/

to check if the database files have been created.

It seems that /etc/init.d/scalix-postgres start
starts scalix-postgres service.
But once when it is checked with ps xa|grep postmaster
it shows that it is running here /var/lib/postgresql/7.4/main

I think that error occurs here:

Code: Select all

root@scalix:/opt/scalix-postgres/bin# ./sxpsql-setpwd $dbpwd
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/opt/scalix/sx/postgres/data/.s.PGSQL.5733"?


This error occurs because the scalix postgres db is not running and the sxpsql-setpwd command is trying to connect to the scalix posgres db!

It seems that postgres is running on one socket and scalix-postgres is expecting to find it on another socket?

Anyway, I will erase server, and perform clean OS install and then I will execute your script line by line, and I will notify you about each error.

Hope this will make things more clear.

Regards,
Christoph

[nenad]

Thank you.

Code: Select all

root@scalix:~# ls -la /var/opt/scalix/sx/postgres/data/
total 52
drwx------ 6 postgres postgres 4096 2007-03-29 14:01 .
drwxr-xr-x 3 postgres postgres 4096 2007-03-29 01:38 ..
drwx------ 4 postgres postgres 4096 2007-03-29 01:38 base
drwx------ 2 postgres postgres 4096 2007-03-29 01:38 global
drwx------ 2 postgres postgres 4096 2007-03-29 01:38 pg_clog
-rw------- 1 postgres postgres 3481 2007-03-29 02:09 pg_hba.conf
-rw------- 1 postgres postgres 1441 2007-03-29 01:38 pg_ident.conf
-rw------- 1 postgres postgres    4 2007-03-29 01:38 PG_VERSION
drwx------ 2 postgres postgres 4096 2007-03-29 01:38 pg_xlog
-rw------- 1 postgres postgres 7900 2007-03-29 14:00 postgresql.conf
-rw------- 1 root     root     7882 2007-03-29 14:00 postgresql.conf~


I still don't get it why there is no second instance running?

Code: Select all

root@scalix:~# /etc/init.d/scalix-postgres start
Starting scalix-postgres service (scalix): ok

root@scalix:~# ps xa|grep postmaster
 3065 ?        S      0:00 /usr/lib/postgresql/7.4/bin/postmaster -c unix_socket_directory=/var/run/postgresql -D /var/lib/postgresql/7.4/main
 3181 pts/0    R+     0:00 grep postmaster
root@scalix:~#


Should I reinstall OS and install scalix executing your script line by line ?
( I will become semi-automatic debbuger application )

[nenad]

Have a look at this:

Code: Select all

root@scalix:~# /etc/init.d/scalix-postgres start
Starting scalix-postgres service (scalix): ok

root@scalix:~# /etc/init.d/scalix-postgres stop
Stopping scalix-postgres service (scalix): failed

root@scalix:~#


That means that scalix-postgres actually didn't startted, because if it is then

/etc/init.d/scalix-postgres stop wouldn't give as result:

Stopping scalix-postgres service (scalix): failed

(I didn't noticd that you informed me about this in your previous post)

What I don't get it is where is defined that second instance of postgresql will run on port 5733 and in unix socket directory /var/opt/scalix/sx/postgres/data/.s.PGSQL.5733 ?

Is there any meaning in this:

Code: Select all

PGVERSION=8.1.4

?

there are two packages for Debian Etch, postgresql-8.1 and postgresql-7.4, but with apt-get install postgresql by default postgresql-7.4 is installed...

I found that within /etc/init.d/scalix-postgres ?
Is the distribution (Debian) also recognised properly? In one another software package there was script like this one which was failing to recognise Debian properly ?

[nenad]

This error occured during the initial install of packages

Code: Select all

Setting up make (3.81-2) ...
Setting up postgresql-client-common (71) ...
Setting up postgresql-client-7.4 (7.4.16-1)

Setting up ssl-cert (1.0.12) ...

Setting up postgresql-common (71) ...
adduser: Warining: that home directory does not belong to the user you are currently reating


Code: Select all

Setting up sendmail-base (8.13.8-3) ...
adduser: Warning: that home directory does not belong to the user you are
currently creating.
adduser: Warning: that home directory does not belong to the user you are
currently creating

Setting up sendmail-bin (8.13.8-3) ...


[nenad]

Here we go:

I completely reinstalled server (Debian Etch OS)

I ma executing every single line by hand, even all of the packages in aptitude install section of your script:

1. What should I answer for a question about Kerberos realm?
"Enetr the hostname for Kerberos servers in web-hosting.co.yu. kerberos servers for your realm?"

I answered "scalix"

1.a. Enter the hostname of administrative server "Administrative server for your kerberos realm?"

I answered "scalix"

2. It seems that:

aptitude install libkadm55 is surplus
aptitude install libkrb53 is surplus

as

aptitude install krb5-user

installs them both.

3. And this is happening with aptitude install postgresq

Code: Select all

scalix:~# aptitude install postgresql
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Writing extended state information... Done
Reading task descriptions... Done
Building tag database... Done
The following NEW packages will be automatically installed:
  libperl5.8 openssl postgresql-7.4 postgresql-client postgresql-client-7.4 postgresql-client-common
  postgresql-common postgresql-plperl-7.4 postgresql-plpython-7.4 postgresql-pltcl-7.4 python2.4
  python2.4-minimal ssl-cert tcl8.4
The following NEW packages will be installed:
  libperl5.8 openssl postgresql postgresql-7.4 postgresql-client postgresql-client-7.4
  postgresql-client-common postgresql-common postgresql-plperl-7.4 postgresql-plpython-7.4
  postgresql-pltcl-7.4 python2.4 python2.4-minimal ssl-cert tcl8.4
0 packages upgraded, 15 newly installed, 0 to remove and 0 not upgraded.
Need to get 11.4MB of archives. After unpacking 31.9MB will be used.
Do you want to continue? [Y/n/?]
Writing extended state information... Done
Get:1 http://ftp.de.debian.org etch/main libperl5.8 5.8.8-7 [527kB]
Get:2 http://ftp.de.debian.org etch/main openssl 0.9.8c-4 [1004kB]
Get:3 http://ftp.de.debian.org etch/main postgresql-client-common 71 [40.2kB]
Get:4 http://ftp.de.debian.org etch/main postgresql-client-7.4 1:7.4.16-1 [1076kB]
Get:5 http://ftp.de.debian.org etch/main ssl-cert 1.0.14 [11.1kB]
Get:6 http://ftp.de.debian.org etch/main postgresql-common 71 [102kB]
Get:7 http://ftp.de.debian.org etch/main postgresql-7.4 1:7.4.16-1 [3375kB]
Get:8 http://ftp.de.debian.org etch/main postgresql-client 7.5.22 [4784B]
Get:9 http://ftp.de.debian.org etch/main postgresql 7.5.22 [7024B]
Get:10 http://ftp.de.debian.org etch/main postgresql-plperl-7.4 1:7.4.16-1 [118kB]
Get:11 http://ftp.de.debian.org etch/main python2.4-minimal 2.4.4-2 [900kB]
Get:12 http://ftp.de.debian.org etch/main python2.4 2.4.4-2 [2849kB]
Get:13 http://ftp.de.debian.org etch/main postgresql-plpython-7.4 1:7.4.16-1 [120kB]
Get:14 http://ftp.de.debian.org etch/main tcl8.4 8.4.12-1.1 [1144kB]
Get:15 http://ftp.de.debian.org etch/main postgresql-pltcl-7.4 1:7.4.16-1 [122kB]
Fetched 11.4MB in 55s (205kB/s)
Preconfiguring packages ...
Selecting previously deselected package libperl5.8.
(Reading database ... 14867 files and directories currently installed.)
Unpacking libperl5.8 (from .../libperl5.8_5.8.8-7_i386.deb) ...
Selecting previously deselected package openssl.
Unpacking openssl (from .../openssl_0.9.8c-4_i386.deb) ...
Creating directory /etc/ssl
Selecting previously deselected package postgresql-client-common.
Unpacking postgresql-client-common (from .../postgresql-client-common_71_all.deb) ...
Selecting previously deselected package postgresql-client-7.4.
Unpacking postgresql-client-7.4 (from .../postgresql-client-7.4_1%3a7.4.16-1_i386.deb) ...
Selecting previously deselected package ssl-cert.
Unpacking ssl-cert (from .../ssl-cert_1.0.14_all.deb) ...
Selecting previously deselected package postgresql-common.
Unpacking postgresql-common (from .../postgresql-common_71_all.deb) ...
Selecting previously deselected package postgresql-7.4.
Unpacking postgresql-7.4 (from .../postgresql-7.4_1%3a7.4.16-1_i386.deb) ...
Selecting previously deselected package postgresql-client.
Unpacking postgresql-client (from .../postgresql-client_7.5.22_all.deb) ...
Selecting previously deselected package postgresql.
Unpacking postgresql (from .../postgresql_7.5.22_all.deb) ...
Selecting previously deselected package postgresql-plperl-7.4.
Unpacking postgresql-plperl-7.4 (from .../postgresql-plperl-7.4_1%3a7.4.16-1_i386.deb) ...
Selecting previously deselected package python2.4-minimal.
Unpacking python2.4-minimal (from .../python2.4-minimal_2.4.4-2_i386.deb) ...
Selecting previously deselected package python2.4.
Unpacking python2.4 (from .../python2.4_2.4.4-2_i386.deb) ...
Selecting previously deselected package postgresql-plpython-7.4.
Unpacking postgresql-plpython-7.4 (from .../postgresql-plpython-7.4_1%3a7.4.16-1_i386.deb) ...
Selecting previously deselected package tcl8.4.
Unpacking tcl8.4 (from .../tcl8.4_8.4.12-1.1_i386.deb) ...
Selecting previously deselected package postgresql-pltcl-7.4.
Unpacking postgresql-pltcl-7.4 (from .../postgresql-pltcl-7.4_1%3a7.4.16-1_i386.deb) ...
Setting up libperl5.8 (5.8.8-7) ...

Setting up openssl (0.9.8c-4) ...

Setting up postgresql-client-common (71) ...
Setting up postgresql-client-7.4 (7.4.16-1) ...

Setting up ssl-cert (1.0.14) ...

Setting up postgresql-common (71) ...
dpkg: error processing postgresql-common (--configure):
 subprocess post-installation script returned error exit status 255
dpkg: dependency problems prevent configuration of postgresql-7.4:
 postgresql-7.4 depends on postgresql-common (>= 24); however:
  Package postgresql-common is not configured yet.
dpkg: error processing postgresql-7.4 (--configure):
 dependency problems - leaving unconfigured
Setting up postgresql-client (7.5.22) ...
dpkg: dependency problems prevent configuration of postgresql:
 postgresql depends on postgresql-7.4; however:
  Package postgresql-7.4 is not configured yet.
 postgresql depends on postgresql-common (>= 40); however:
  Package postgresql-common is not configured yet.
dpkg: error processing postgresql (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of postgresql-plperl-7.4:
 postgresql-plperl-7.4 depends on postgresql-7.4; however:
  Package postgresql-7.4 is not configured yet.
dpkg: error processing postgresql-plperl-7.4 (--configure):
 dependency problems - leaving unconfigured
Setting up python2.4-minimal (2.4.4-2) ...
adduser: Warning: that home directory does not belong to the user you are currently creating.
Linking and byte-compiling packages for runtime python2.4...

Setting up python2.4 (2.4.4-2) ...

dpkg: dependency problems prevent configuration of postgresql-plpython-7.4:
 postgresql-plpython-7.4 depends on postgresql-7.4; however:
  Package postgresql-7.4 is not configured yet.
dpkg: error processing postgresql-plpython-7.4 (--configure):
 dependency problems - leaving unconfigured
Setting up tcl8.4 (8.4.12-1.1) ...

dpkg: dependency problems prevent configuration of postgresql-pltcl-7.4:
 postgresql-pltcl-7.4 depends on postgresql-7.4; however:
  Package postgresql-7.4 is not configured yet.
dpkg: error processing postgresql-pltcl-7.4 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 postgresql-common
 postgresql-7.4
 postgresql
 postgresql-plperl-7.4
 postgresql-plpython-7.4
 postgresql-pltcl-7.4
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up postgresql-common (71) ...

Setting up postgresql-7.4 (7.4.16-1) ...
Creating new cluster (configuration: /etc/postgresql/7.4/main, data: /var/lib/postgresql/7.4/main)...
Moving configuration file /var/lib/postgresql/7.4/main/postgresql.conf to /etc/postgresql/7.4/main...
Moving configuration file /var/lib/postgresql/7.4/main/pg_hba.conf to /etc/postgresql/7.4/main...
Moving configuration file /var/lib/postgresql/7.4/main/pg_ident.conf to /etc/postgresql/7.4/main...
Configuring postgresql.conf to use port 5432...
Starting PostgreSQL 7.4 database server: main.

Setting up postgresql-pltcl-7.4 (7.4.16-1) ...
Setting up postgresql (7.5.22) ...

Setting up postgresql-plperl-7.4 (7.4.16-1) ...
Setting up postgresql-plpython-7.4 (7.4.16-1) ...
scalix:~#
scalix:~#


Is there any problems with it? Should I continue with installation of script ?

[nenad]

Code: Select all

scalix:/tmp# cd $scalix11dir
scalix:/tmp/scalix-debian-11.0.2.1-GA/software/scalix_server# dpkg -i scalix-postgres_*.deb
Selecting previously deselected package scalix-postgres.
(Reading database ... 19877 files and directories currently installed.)
Unpacking scalix-postgres (from scalix-postgres_11.0.2.23_all.deb) ...
Setting up scalix-postgres (11.0.2.23) ...
The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.

creating directory /var/opt/scalix/sx/postgres/data... ok
creating directory /var/opt/scalix/sx/postgres/data/base... ok
creating directory /var/opt/scalix/sx/postgres/data/global... ok
creating directory /var/opt/scalix/sx/postgres/data/pg_xlog... ok
creating directory /var/opt/scalix/sx/postgres/data/pg_clog... ok
selecting default max_connections... 100
selecting default shared_buffers... 1000
creating configuration files... ok
creating template1 database in /var/opt/scalix/sx/postgres/data/base/1... ok
initializing pg_shadow... ok
enabling unlimited row size for system tables... ok
initializing pg_depend... ok
creating system views... ok
loading pg_description... ok
creating conversions... ok
setting privileges on built-in objects... ok
creating information schema... ok
vacuuming database template1... ok
copying template1 to template0... ok

Success. You can now start the database server using:

    /usr/lib/postgresql/7.4/bin/postmaster -D /var/opt/scalix/sx/postgres/data
or
    /usr/lib/postgresql/7.4/bin/pg_ctl -D /var/opt/scalix/sx/postgres/data -l logfile start

Starting scalix-postgres service (sx): ok

Starting scalix-postgres service (scalix): ok

invoke-rc.d: initscript scalix-postgres, action "start" failed.

scalix:/tmp/scalix-debian-11.0.2.1-GA/software/scalix_server#


[christoph.lukas]

What I don't get it is where is defined that second instance of postgresql will run on port 5733 and in unix socket directory /var/opt/scalix/sx/postgres/data/.s.PGSQL.5733 ?

This is in: /var/opt/scalix/sx/postgres/data/postmaster.opts

Is there any meaning in this:

Code: Select all

PGVERSION=8.1.4

?

there are two packages for Debian Etch, postgresql-8.1 and postgresql-7.4, but with apt-get install postgresql by default postgresql-7.4 is installed...

This is ok, I have scalix 11.0.2 running with postgres 7.4.

I found that within /etc/init.d/scalix-postgres ?
Is the distribution (Debian) also recognised properly? In one another software package there was script like this one which was failing to recognise Debian properly ?

Please do a:

Code: Select all

tail -f /var/opt/scalix/cz/postgres/pgstartup.log

and in another console a:

Code: Select all

/etc/init.d/scalix-postgres start

This should shed some light into why the scalix postgres is not starting.

[christoph.lukas]

Here we go:

I completely reinstalled server (Debian Etch OS)

[..]

Setting up postgresql-common (71) ...
dpkg: error processing postgresql-common (--configure):
subprocess post-installation script returned error exit status 255
dpkg: dependency problems prevent configuration of postgresql-7.4:
postgresql-7.4 depends on postgresql-common (>= 24); however:
Package postgresql-common is not configured yet.
dpkg: error processing postgresql-7.4 (--configure):
dependency problems - leaving unconfigured

[..]

Is there any problems with it? Should I continue with installation of script ?

This is pretty strange and does not happen on a fresh etch install here. Checked it a few minutes ago.

Regards,
Christoph

[christoph.lukas]

Code: Select all

scalix:/tmp# cd $scalix11dir

[..]

creating information schema... ok
vacuuming database template1... ok
copying template1 to template0... ok

Success. You can now start the database server using:

    /usr/lib/postgresql/7.4/bin/postmaster -D /var/opt/scalix/sx/postgres/data
or
    /usr/lib/postgresql/7.4/bin/pg_ctl -D /var/opt/scalix/sx/postgres/data -l logfile start
[/quote]
Looks correct up to here.
[quote]
Starting scalix-postgres service (sx): ok

Starting scalix-postgres service (scalix): ok

invoke-rc.d: initscript scalix-postgres, action "start" failed.

scalix:/tmp/scalix-debian-11.0.2.1-GA/software/scalix_server#


This is strange. The init script is trying to start two additional postgres instances (sx and scalix). If I find the time I will try to install scalix 11.0.2 myself to see what is happening there.

Will keep you updated,
Christoph[/quote]

[nenad]

console 1:

Code: Select all

scalix:~# /etc/init.d/scalix-postgres start
Starting scalix-postgres service (scalix): ok

scalix:~#


console 2:

Code: Select all

scalix:~# tail -f /var/opt/scalix/sx/postgres/pgstartup.log
FATAL:  could not create listen socket for "scalix"
LOG:  could not bind IPv4 socket: Cannot assign requested address
HINT:  Is another postmaster already running on port 5733? If not, wait a few seconds and retry.
FATAL:  could not create listen socket for "scalix"
LOG:  could not bind IPv4 socket: Cannot assign requested address
HINT:  Is another postmaster already running on port 5733? If not, wait a few seconds and retry.
FATAL:  could not create listen socket for "scalix"
LOG:  could not bind IPv4 socket: Cannot assign requested address
HINT:  Is another postmaster already running on port 5733? If not, wait a few seconds and retry.
FATAL:  could not create listen socket for "scalix"
LOG:  could not bind IPv4 socket: Cannot assign requested address
HINT:  Is another postmaster already running on port 5733? If not, wait a few seconds and retry.
FATAL:  could not create listen socket for "scalix"



[nenad]

I definitely think that something must be wrong in 11.0.2 deb packages