Skip to content

Getting issue when running postgres container on ppc64le #789

Closed
@ShubhamKale

Description

@ShubhamKale

Below are logs when tried to run postgres image on Linux PPC machine.

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.utf8".
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 /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.
syncing data to disk ... ok
Success. You can now start the database server using:
pg_ctl -D /var/lib/postgresql/data -l logfile start
waiting for server to start....2020-11-23 04:42:58.848 UTC [45] LOG: starting PostgreSQL 13.0 (Debian 13.0-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-23 04:42:58.852 UTC [45] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-23 04:42:58.871 UTC [46] LOG: database system was shut down at 2020-11-23 04:42:55 UTC
2020-11-23 04:42:58.882 UTC [45] LOG: database system is ready to accept connections
done
server started
2020-11-23 04:42:59.150 UTC [47] PANIC: could not flush dirty data: Operation not permitted
2020-11-23 04:43:00.006 UTC [45] LOG: checkpointer process (PID 47) was terminated by signal 6: Aborted
2020-11-23 04:43:00.006 UTC [45] LOG: terminating any other active server processes
2020-11-23 04:43:00.006 UTC [50] WARNING: terminating connection because of crash of another server process
2020-11-23 04:43:00.006 UTC [50] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-11-23 04:43:00.006 UTC [50] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-11-23 04:43:00.013 UTC [61] WARNING: terminating connection because of crash of another server process
2020-11-23 04:43:00.013 UTC [61] DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2020-11-23 04:43:00.013 UTC [61] HINT: In a moment you should be able to reconnect to the database and repeat your command.
2020-11-23 04:43:00.016 UTC [45] LOG: all server processes terminated; reinitializing
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
connection to server was lost

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions