Skip to content
This repository has been archived by the owner on Feb 23, 2021. It is now read-only.

SQL violation on startup #39

Open
FunkyLoiso opened this issue Apr 9, 2019 · 0 comments
Open

SQL violation on startup #39

FunkyLoiso opened this issue Apr 9, 2019 · 0 comments

Comments

@FunkyLoiso
Copy link

The containers are started with

sudo docker-compose down -v
sudo docker-compose up -d

Postgres log is the following

postgres_1       | The files belonging to this database system will be owned by user "postgres".
postgres_1       | This user must also own the server process.
postgres_1       | 
postgres_1       | The database cluster will be initialized with locale "en_US.utf8".
postgres_1       | The default database encoding has accordingly been set to "UTF8".
postgres_1       | The default text search configuration will be set to "english".
postgres_1       | 
postgres_1       | Data page checksums are disabled.
postgres_1       | 
postgres_1       | fixing permissions on existing directory /var/lib/postgresql/data/pgdata ... ok
postgres_1       | creating subdirectories ... ok
postgres_1       | selecting default max_connections ... 100
postgres_1       | selecting default shared_buffers ... 128MB
postgres_1       | selecting dynamic shared memory implementation ... posix
postgres_1       | creating configuration files ... ok
postgres_1       | running bootstrap script ... ok
postgres_1       | performing post-bootstrap initialization ... ok
postgres_1       | syncing data to disk ... ok
postgres_1       | 
postgres_1       | Success. You can now start the database server using:
postgres_1       | 
postgres_1       |     pg_ctl -D /var/lib/postgresql/data/pgdata -l logfile start
postgres_1       | 
postgres_1       | 
postgres_1       | WARNING: enabling "trust" authentication for local connections
postgres_1       | You can change this by editing pg_hba.conf or using the option -A, or
postgres_1       | --auth-local and --auth-host, the next time you run initdb.
postgres_1       | waiting for server to start....2019-04-09 09:04:06.075 UTC [43] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1       | 2019-04-09 09:04:06.185 UTC [44] LOG:  database system was shut down at 2019-04-09 09:04:00 UTC
postgres_1       | 2019-04-09 09:04:06.228 UTC [43] LOG:  database system is ready to accept connections
postgres_1       |  done
postgres_1       | server started
postgres_1       | 
postgres_1       | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
postgres_1       | 
postgres_1       | waiting for server to shut down...2019-04-09 09:04:06.323 UTC [43] LOG:  received fast shutdown request
postgres_1       | .2019-04-09 09:04:06.377 UTC [43] LOG:  aborting any active transactions
postgres_1       | 2019-04-09 09:04:06.379 UTC [43] LOG:  background worker "logical replication launcher" (PID 50) exited with exit code 1
postgres_1       | 2019-04-09 09:04:06.380 UTC [45] LOG:  shutting down
postgres_1       | 2019-04-09 09:04:06.684 UTC [43] LOG:  database system is shut down
postgres_1       |  done
postgres_1       | server stopped
postgres_1       | 
postgres_1       | PostgreSQL init process complete; ready for start up.
postgres_1       | 
postgres_1       | 2019-04-09 09:04:06.774 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres_1       | 2019-04-09 09:04:06.774 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres_1       | 2019-04-09 09:04:07.316 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres_1       | 2019-04-09 09:04:08.011 UTC [52] LOG:  database system was shut down at 2019-04-09 09:04:06 UTC
postgres_1       | 2019-04-09 09:04:08.012 UTC [54] LOG:  incomplete startup packet
postgres_1       | 2019-04-09 09:04:08.012 UTC [53] LOG:  incomplete startup packet
postgres_1       | 2019-04-09 09:04:08.012 UTC [55] LOG:  incomplete startup packet
postgres_1       | 2019-04-09 09:04:08.088 UTC [1] LOG:  database system is ready to accept connections
postgres_1       | 2019-04-09 09:06:06.929 UTC [64] ERROR:  duplicate key value violates unique constraint "pg_type_typname_nsp_index"
postgres_1       | 2019-04-09 09:06:06.929 UTC [64] DETAIL:  Key (typname, typnamespace)=(status_type, 2200) already exists.
postgres_1       | 2019-04-09 09:06:06.929 UTC [64] STATEMENT:  CREATE TYPE status_type AS ENUM ('pending', 'running', 'completed', 'reported', 'recovered', 'failed_analysis', 'failed_processing', 'failed_reporting')
postgres_1       | 2019-04-09 09:06:06.929 UTC [63] ERROR:  duplicate key value violates unique constraint "pg_type_typname_nsp_index"
postgres_1       | 2019-04-09 09:06:06.929 UTC [63] DETAIL:  Key (typname, typnamespace)=(status_type, 2200) already exists.
postgres_1       | 2019-04-09 09:06:06.929 UTC [63] STATEMENT:  CREATE TYPE status_type AS ENUM ('pending', 'running', 'completed', 'reported', 'recovered', 'failed_analysis', 'failed_processing', 'failed_reporting')

Whole log: https://pastebin.com/a7JNaBRC

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant