Scribd
Upload
32 views2 pages

Postgresql Log

The document details the initialization and configuration process of a PostgreSQL instance with Replication Manager (repmgr). It includes logs of various steps such as validating environment variables, preparing configurations, and starting the PostgreSQL server in standby mode. Additionally, it captures errors related to executing write operations in a read-only transaction.

Uploaded by

Eduardo Ortiz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
32 views2 pages

Postgresql Log

The document details the initialization and configuration process of a PostgreSQL instance with Replication Manager (repmgr). It includes logs of various steps such as validating environment variables, preparing configurations, and starting the PostgreSQL server in standby mode. Additionally, it captures errors related to executing write operations in a read-only transaction.

Uploaded by

Eduardo Ortiz
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].

35 #[0m
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].35 #[0m#[1mWelcome to the Bitnami
postgresql-repmgr container#[0m
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].35 #[0mSubscribe to project updates by
watching #[1m[Link]
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].35 #[0mSubmit issues and feature
requests at #[1m[Link]
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].36 #[0m
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].36 #[0m#[38;5;2mINFO #[0m ==> **
Starting PostgreSQL with Replication Manager setup **
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].39 #[0m#[38;5;2mINFO #[0m ==>
Validating settings in REPMGR_* env vars...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].39 #[0m#[38;5;2mINFO #[0m ==>
Validating settings in POSTGRESQL_* env vars..
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].39 #[0m#[38;5;2mINFO #[0m ==> Querying
all partner nodes for common upstream node...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].47 #[0m#[38;5;2mINFO #[0m ==> Node
configured as standby
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].48 #[0m#[38;5;2mINFO #[0m ==>
Preparing PostgreSQL configuration...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].48 #[0m#[38;5;2mINFO #[0m ==>
[Link] file not detected. Generating it...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].66 #[0m#[38;5;2mINFO #[0m ==>
Preparing repmgr configuration...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].68 #[0m#[38;5;2mINFO #[0m ==>
Initializing Repmgr...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].69 #[0m#[38;5;2mINFO #[0m ==> Waiting
for primary node...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].78 #[0m#[38;5;2mINFO #[0m ==>
Rejoining node...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].78 #[0m#[38;5;2mINFO #[0m ==> Cloning
data from primary node...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].83 #[0m#[38;5;2mINFO #[0m ==>
Initializing PostgreSQL database...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].84 #[0m#[38;5;2mINFO #[0m ==> Custom
configuration /opt/bitnami/postgresql/conf/[Link] detected
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].84 #[0m#[38;5;2mINFO #[0m ==> Custom
configuration /opt/bitnami/postgresql/conf/pg_hba.conf detected
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].89 #[0m#[38;5;2mINFO #[0m ==>
Deploying PostgreSQL with persisted data...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].94 #[0m#[38;5;2mINFO #[0m ==>
Configuring replication parameters
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].99 #[0m#[38;5;2mINFO #[0m ==>
Configuring fsync
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].02 #[0m#[38;5;2mINFO #[0m ==> Setting
up streaming replication slave...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].06 #[0m#[38;5;2mINFO #[0m ==> Starting
PostgreSQL in background...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].02 #[0m#[38;5;2mINFO #[0m ==>
Unregistering standby node...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].07 #[0m#[38;5;2mINFO #[0m ==>
Registering Standby node...
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].13 #[0m#[38;5;2mINFO #[0m ==> Stopping
PostgreSQL...
waiting for server to shut down.... done
server stopped
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].34 #[0m#[38;5;2mINFO #[0m ==> **
PostgreSQL with Replication Manager setup finished! **
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].37 #[0m#[38;5;2mINFO #[0m ==> Starting
PostgreSQL in background...
waiting for server to start....2024-12-18 [Link].418 GMT [221] LOG: pgaudit
extension initialized
2024-12-18 [Link].626 GMT [221] LOG: redirecting log output to logging collector
process
2024-12-18 [Link].626 GMT [221] HINT: Future log output will appear in directory
"/opt/bitnami/postgresql/logs".
2024-12-18 [Link].626 GMT [221] LOG: starting PostgreSQL 14.7 on x86_64-pc-
linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2024-12-18 [Link].627 GMT [221] LOG: listening on IPv4 address "[Link]", port
5432
2024-12-18 [Link].627 GMT [221] LOG: listening on IPv6 address "::", port 5432
2024-12-18 [Link].631 GMT [221] LOG: listening on Unix socket
"/tmp/.[Link].5432"
2024-12-18 [Link].655 GMT [223] LOG: database system was shut down in recovery
at 2024-12-18 [Link] GMT
2024-12-18 [Link].657 GMT [223] LOG: entering standby mode
2024-12-18 [Link].706 GMT [223] LOG: redo starts at 0/6000028
2024-12-18 [Link].708 GMT [223] LOG: consistent recovery state reached at
0/7000858
2024-12-18 [Link].708 GMT [223] LOG: invalid record length at 0/7000858: wanted
24, got 0
2024-12-18 [Link].708 GMT [221] LOG: database system is ready to accept read-
only connections
2024-12-18 [Link].719 GMT [227] LOG: started streaming WAL from primary at
0/7000000 on timeline 1
done
server started
#[38;5;6mpostgresql-repmgr #[38;5;5m[Link].83 #[0m#[38;5;2mINFO #[0m ==> **
Starting repmgrd **
[2024-12-18 [Link] [NOTICE] repmgrd (repmgrd 5.3.3) starting up
INFO: set_repmgrd_pid(): provided pidfile is /tmp/[Link]
[2024-12-18 [Link] [NOTICE] starting monitoring of node "events-db-postgresql-
ha-postgresql-2" (ID: 1002)
2024-12-19 [Link].600 GMT [51494] ERROR: cannot execute UPDATE in a read-only
transaction
2024-12-19 [Link].600 GMT [51494] STATEMENT: UPDATE "events_eventstatus" SET
"name" = 'Pending', "created" = '2022-05-24T[Link]+00:00'::timestamptz, "updated"
= '2022-05-24T[Link]+00:00'::timestamptz WHERE "events_eventstatus"."id" = 1
2024-12-19 [Link].906 GMT [51543] ERROR: cannot execute CREATE TABLE in a read-
only transaction
2024-12-19 [Link].906 GMT [51543] STATEMENT: CREATE TABLE "auditlog_logentry"
("id" serial NOT NULL PRIMARY KEY, "object_pk" text NOT NULL, "object_id" integer
NULL CHECK ("object_id" >= 0), "object_repr" text NOT NULL, "action" smallint NOT
NULL CHECK ("action" >= 0), "changes" text NOT NULL, "timestamp" timestamp with
time zone NOT NULL, "actor_id" integer NULL, "content_type_id" integer NOT NULL)
2024-12-19 [Link].381 GMT [60942] ERROR: cannot execute UPDATE in a read-only
transaction
2024-12-19 [Link].381 GMT [60942] STATEMENT: UPDATE "events_eventstatus" SET
"name" = 'Pending', "created" = '2022-05-24T[Link]+00:00'::timestamptz, "updated"
= '2022-05-24T[Link]+00:00'::timestamptz WHERE "events_eventstatus"."id" = 1
2024-12-19 [Link].594 GMT [60954] ERROR: cannot execute UPDATE in a read-only
transaction
2024-12-19 [Link].594 GMT [60954] STATEMENT: UPDATE "events_eventstatus" SET
"name" = 'Pending', "created" = '2022-05-24T[Link]+00:00'::timestamptz, "updated"
= '2022-05-24T[Link]+00:00'::timestamptz WHERE "events_eventstatus"."id" = 1

You might also like