Failure of initdb

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Failure of initdb

Bruce Rindahl
Building postgresql-from source on Debian Buster.  At version 67422.  Bug happened at a previous version but not sure exactly where.
Source build with no errors.  Install with no errors.  Brand new build with no previous installs of postgresql.
Attempted to initialize cluster with initdb.  Received the following:

pi@pi364B0:~$ sudo chown postgres /usr/local/pgsql
pi@pi364B0:~$ sudo chgrp postgres /usr/local/pgsql
pi@pi364B0:~$ sudo su postgres
postgres@pi364B0:/home/pi$ mkdir /usr/local/pgsql/data
postgres@pi364B0:/home/pi$ /usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
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".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /usr/local/pgsql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default timezone ... US/Pacific
creating configuration files ... ok
running bootstrap script ... 2019-04-09 18:02:14.010 PDT [6358] FATAL:  could not open file "base/1/1255": No such file or directory
2019-04-09 18:02:14.010 PDT [6358] PANIC:  cannot abort transaction 1, it was already committed
Aborted
child process exited with exit code 134
initdb: removing contents of data directory "/usr/local/pgsql/data"

Any help would be appreciated.  This error can be repeated on different but identical machines.