New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting issue when running postgres container on ppc64le #789
Comments
I'm not able to reproduce -- is your server perhaps running out of resources such as memory or disk space? $ docker images postgres:13
REPOSITORY TAG IMAGE ID CREATED SIZE
postgres 13 ff7c5eb3b0b0 5 days ago 373MB
$ docker run -it --rm --name test -e POSTGRES_PASSWORD=foo postgres:13
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
syncing data to disk ... 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.
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 19:29:33.448 UTC [46] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-23 19:29:33.711 UTC [46] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-23 19:29:33.822 UTC [47] LOG: database system was shut down at 2020-11-23 19:29:31 UTC
.2020-11-23 19:29:34.658 UTC [46] LOG: database system is ready to accept connections
done
server started
/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
waiting for server to shut down....2020-11-23 19:29:35.042 UTC [46] LOG: received fast shutdown request
2020-11-23 19:29:35.087 UTC [46] LOG: aborting any active transactions
2020-11-23 19:29:35.091 UTC [46] LOG: background worker "logical replication launcher" (PID 53) exited with exit code 1
2020-11-23 19:29:35.094 UTC [48] LOG: shutting down
....2020-11-23 19:29:39.643 UTC [46] LOG: database system is shut down
done
server stopped
PostgreSQL init process complete; ready for start up.
2020-11-23 19:29:41.013 UTC [1] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on powerpc64le-unknown-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-23 19:29:41.014 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2020-11-23 19:29:41.014 UTC [1] LOG: listening on IPv6 address "::", port 5432
2020-11-23 19:29:41.615 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-23 19:29:41.733 UTC [55] LOG: database system was shut down at 2020-11-23 19:29:39 UTC
2020-11-23 19:29:44.308 UTC [1] LOG: database system is ready to accept connections |
docker run -d -e POSTGRES_PASSWORD=Test@db2 -e POSTGRES_USER=testuser -e POSTGRES_DB=testdb -v testDbVolume:/var/lib/postgresql/data -p 54322:5432 postgres this command i used |
I'm (still) not able to reproduce -- is your server perhaps running out of resources such as memory or disk space? $ docker pull postgres
Using default tag: latest
latest: Pulling from library/postgres
Digest: sha256:839d6212e7aadb9612fd216374279b72f494c9c4ec517b8e98d768ac9dd74a15
Status: Image is up to date for postgres:latest
docker.io/library/postgres:latest
$ docker run -d -e POSTGRES_PASSWORD=Test@db2 -e POSTGRES_USER=testuser -e POSTGRES_DB=testdb -v testDbVolume:/var/lib/postgresql/data -p 54322:5432 postgres
dbe59c1d6f6ededd2a217da6bd595c687c90c5d1f85571fd6b8527e8e3a85c92
$ docker logs dbe59c1d6f6ededd2a217da6bd595c687c90c5d1f85571fd6b8527e8e3a85c92
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
syncing data to disk ... 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.
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-25 16:26:04.037 UTC [46] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-25 16:26:04.038 UTC [46] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-25 16:26:04.043 UTC [47] LOG: database system was shut down at 2020-11-25 16:26:03 UTC
2020-11-25 16:26:04.046 UTC [46] LOG: database system is ready to accept connections
done
server started
CREATE DATABASE
/usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
2020-11-25 16:26:04.279 UTC [46] LOG: received fast shutdown request
waiting for server to shut down....2020-11-25 16:26:04.280 UTC [46] LOG: aborting any active transactions
2020-11-25 16:26:04.281 UTC [46] LOG: background worker "logical replication launcher" (PID 53) exited with exit code 1
2020-11-25 16:26:04.281 UTC [48] LOG: shutting down
2020-11-25 16:26:04.290 UTC [46] LOG: database system is shut down
done
server stopped
PostgreSQL init process complete; ready for start up.
2020-11-25 16:26:04.418 UTC [1] LOG: starting PostgreSQL 13.1 (Debian 13.1-1.pgdg100+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 8.3.0-6) 8.3.0, 64-bit
2020-11-25 16:26:04.418 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432
2020-11-25 16:26:04.418 UTC [1] LOG: listening on IPv6 address "::", port 5432
2020-11-25 16:26:04.421 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2020-11-25 16:26:04.424 UTC [64] LOG: database system was shut down at 2020-11-25 16:26:04 UTC
2020-11-25 16:26:04.428 UTC [1] LOG: database system is ready to accept connections |
no i checked memory and space is available. |
For further help, I suggest trying a dedicated support forum, such as the Docker Community Forums, the Docker Community Slack, or Stack Overflow. |
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
The text was updated successfully, but these errors were encountered: