Re: Problems when initdb on AIX 5.3

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Francesco Vecchio wrote:
> I have a problem with the command:
>
> # initdb -D /geasql/data
>
> which after displaying:
> selecting default max_connections …
> it stops and does not proceed.
>
> I tried on another server and the problem is the same.
> The ps command list initdb followed by the following process:
>
> /opt/freeware/bin/postgres --boot -x0 -F -c max_connections=100 -c shared_buffers=1000
>
> The following lines are the output of the initdb command:
>
> $ initdb –-debug -D /geasql/data. . . .
> The files belonging to this database system will be owned by user "postgres".
> This user must also own the server process.
> VERSION=9.3.5
> PGDATA=/geasql/data
> share_path=/opt/freeware/share/postgresql
> PGPATH=/opt/freeware/bin
> POSTGRES_SUPERUSERNAME=postgres
> POSTGRES_BKI=/opt/freeware/share/postgresql/postgres.bki
> POSTGRES_DESCR=/opt/freeware/share/postgresql/postgres.description
> POSTGRES_SHDESCR=/opt/freeware/share/postgresql/postgres.shdescription
> POSTGRESQL_CONF_SAMPLE=/opt/freeware/share/postgresql/postgresql.conf.sample
> PG_HBA_SAMPLE=/opt/freeware/share/postgresql/pg_hba.conf.sample
> PG_IDENT_SAMPLE=/opt/freeware/share/postgresql/pg_ident.conf.sample
> The database cluster will be initialized with locale "en_US".
> The default database encoding has accordingly been set to "LATIN1".
> The default text search configuration will be set to "english".
> Data page checksums are disabled.
> fixing permissions on existing directory /geasql/data ... ok
> creating subdirectories ... ok
> selecting default max_connections ...
> 
> ******
> Il server è IBM
> System Model: 7029-6E3
> Processor Type: PowerPC_POWER4
> CPU Type: 64-bit
> Kernel Type: 32-bit
> Memory Size: 2048 MB
> S.O. AIX 5.2
> Postgresql and dependences I downloaded from the site www.oss4aix.org strictly respecting the deps of the site.

You could use "truss" on or attach a debugger to the hanging "postgres"
process to see what it is doing.

You should *not* be using PostgreSQL 9.3.5.
Retry with 9.3.24 so you have all known bugs fixed.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com





[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux