· 6 years ago · Mar 14, 2020, 12:30 AM
1For pg-2
2
3dusky-installer: Installing dusky tools.
4dusky-installer: Installing dusky agent.
5dusky-installer: Starting dusky agent.
62020-03-13T23:57:16 INFO: Loading 'Postgres' database engine DLL.
72020-03-13T23:57:16 INFO: Instantiating database engine.
82020-03-13T23:57:16 INFO: Opening V1ConfigMap watch.
92020-03-13T23:57:16 INFO: Configuring REST API.
102020-03-13T23:57:16 INFO: Starting database engine.
112020-03-13T23:57:16 INFO: Running usermod -d /var/lib/postgresql/data/home postgres...
122020-03-13T23:57:16 INFO: Starting Postgres...
132020-03-13T23:57:16 INFO: Running /bin/sh -c "exec /bin/su -c \"exec pg_autoctl run\" postgres"...
142020-03-13T23:57:16 INFO: Waiting for Postgres to finish starting up...
152020-03-13T23:57:16 INFO: Starting REST API.
162020-03-13T23:57:16 WARN: No XML encryptor configured. Key {c8ad083b-36e5-4c27-9222-51c7aae9ba2c} may be persisted to storage in unencrypted form.
1723:57:16 INFO The version of extension "pgautofailover" is "1.1" on the monitor
1823:57:16 INFO pg_autoctl service is running, current state is "single"
1923:57:16 INFO Postgres is not running, starting postgres
2023:57:16 INFO /usr/lib/postgresql/11/bin/pg_ctl --pgdata /var/lib/postgresql/data/data --options "-p 5432" --options "-h *" --wait start
212020-03-13T23:57:16 WARN: Unable to bind to http://localhost:8000 on the IPv6 loopback interface: 'Cannot assign requested address'.
22Hosting environment: Production
23Content root path: /
24Now listening on: http://localhost:8000
2523:57:16 WARN PostgreSQL was not running, restarted with pid 3419
262020-03-13T23:57:16 INFO: Waiting for database engine to shut down.
272020-03-13T23:57:38 INFO: Request GET /health/ready completed with status OK after 122.9ms.
2823:57:42 INFO Monitor assigned new state "wait_primary"
2923:57:42 INFO FSM transition from "single" to "wait_primary": A new secondary was added
3023:57:42 INFO Preparing replication for standby node 2 (pg-1.pg-svc.default.svc.cluster.local:5432)
3123:57:42 INFO Transition complete: current state is now "wait_primary"
322020-03-13T23:57:48 INFO: Request GET /health/ready completed with status OK after 4.8ms.
332020-03-13T23:57:58 INFO: Request GET /health/ready completed with status OK after 0.5ms.
342020-03-13T23:58:08 INFO: Request GET /health/ready completed with status OK after 0.3ms.
352020-03-13T23:58:18 INFO: Request GET /health/ready completed with status OK after 0.3ms.
362020-03-13T23:58:28 INFO: Request GET /health/ready completed with status OK after 0.3ms.
372020-03-13T23:58:38 INFO: Request GET /health/ready completed with status OK after 0.6ms.
38
39
40
41
42
43
44For pg-1
45
46dusky-installer: Installing dusky tools.
47dusky-installer: Installing dusky agent.
48dusky-installer: Starting dusky agent.
492020-03-14T00:03:50 INFO: Loading 'Postgres' database engine DLL.
502020-03-14T00:03:50 INFO: Instantiating database engine.
512020-03-14T00:03:50 INFO: Opening V1ConfigMap watch.
522020-03-14T00:03:51 INFO: Configuring REST API.
532020-03-14T00:03:51 INFO: Starting database engine.
542020-03-14T00:03:51 INFO: Creating Postgres directories.
552020-03-14T00:03:51 INFO: Running usermod -d /var/lib/postgresql/data/home postgres...
562020-03-14T00:03:51 INFO: Initializing pg_auto_failover...
572020-03-14T00:03:51 INFO: Running /bin/sh -c "exec /bin/su -c \"exec pg_autoctl create coordinator --pgctl `which pg_ctl` --nodename pg-1.pg-svc.default.svc.cluster.local --monitor postgres://autoctl_node@pg-0.pg-svc.default.svc.cluster.local/pg_auto_failover\" postgres"...
5800:03:51 INFO Continuing from a previous `pg_autoctl create` failed attempt
5900:03:51 INFO PostgreSQL state at registration time was: PGDATA does not exists
6000:03:51 INFO FSM transition from "wait_standby" to "catchingup": The primary is now ready to accept a standby
6100:03:51 INFO Initialising PostgreSQL as a hot standby
6200:03:51 INFO Running /usr/lib/postgresql/11/bin/pg_basebackup -w -h pg-2.pg-svc.default.svc.cluster.local -p 5432 --pgdata /var/lib/postgresql/data/backup/pg-1.pg-svc.default.svc.cluster.local -U pgautofailover_replicator --write-recovery-conf --max-rate 100M --wal-method=stream --slot pgautofailover_standby_2 ...
6300:03:51 ERROR pg_basebackup: could not connect to server: could not translate host name "pg-2.pg-svc.default.svc.cluster.local" to address: Name or service not known
64
6500:03:51 ERROR Failed to run pg_basebackup: exit code 1
6600:03:51 ERROR Failed initialise standby server, see above for details
6700:03:51 ERROR Failed to transition from state "wait_standby" to state "catchingup", see above.
682020-03-14T00:03:51 ERROR: The engine terminated unexpectedly. Exception - pg_autoctl create failed with status 3.
69System.Exception: pg_autoctl create failed with status 3.
70 at Dusky.Agent.Engine.Postgres.PostgresEngine.Run(CancellationToken cancelToken) in /home/kothapavan35/aris-ha/projects/dusky/dotnet/agent/engines/Postgres/PostgresEngine.cs:line 86
712020-03-14T00:03:51 INFO: Shutting down.
722020-03-14T00:03:51 INFO: Starting REST API.
732020-03-14T00:03:51 WARN: No XML encryptor configured. Key {67d6eec0-3f64-4c00-9b24-08592c4b396a} may be persisted to storage in unencrypted form.
742020-03-14T00:03:51 WARN: Unable to bind to http://localhost:8000 on the IPv6 loopback interface: 'Cannot assign requested address'.
75Hosting environment: Production
76Content root path: /
77Now listening on: http://localhost:8000
782020-03-14T00:03:51 INFO: Waiting for database engine to shut down.