API tools faq
paste
Advertisement
Guest User

Log repmgr

a guest
Aug 21st, 2019
190
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
SystemVerilog 8.79 KB | None | 0 0
raw download clone embed print report
  1. Aug 21 13:45:35 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:35] [WARNING] unable to reconnect to node 1 after 6 attempts
  2. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] 1 active sibling nodes registered
  3. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] primary and this node have the same location ("default")
  4. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] local node's last receive lsn: 3/42000098
  5. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] checking state of sibling node "server-c" (ID: 2)
  6. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] node "server-c" (ID: 2) reports its upstream is node 1, last seen 76 second(s) ago
  7. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] node 2 last saw primary node 76 second(s) ago
  8. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] last receive LSN for sibling node "server-c" (ID: 2) is: 3/42000098
  9. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] node "server-c" (ID: 2) has same LSN as current candidate "server-f" (ID: 3)
  10. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] node "server-c" (ID: 2) has same priority but lower node_id than current candidate "server-f" (ID: 3)
  11. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] visible nodes: 2; total nodes: 2; no nodes have seen the primary within the last 4 seconds
  12. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [NOTICE] promotion candidate is "server-c" (ID: 2)
  13. Aug 21 13:45:36 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:36] [INFO] follower node awaiting notification from a candidate node
  14. Aug 21 13:45:43 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:43] [INFO] local node 3 can attach to follow target node 2
  15. Aug 21 13:45:43 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:43] [DETAIL] local node's recovery point: 3/42000098; follow target node's fork point: 3/42000098
  16. Aug 21 13:45:43 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:43] [NOTICE] setting node 3's upstream to node 2
  17. Aug 21 13:45:43 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:43] [NOTICE] restarting server using "sudo systemctl restart postgresql-11"
  18. Aug 21 13:45:43 postgre-percona-zeljkom systemd: Created slice User Slice of root.
  19. Aug 21 13:45:43 postgre-percona-zeljkom systemd: Started Session c23 of user root.
  20. Aug 21 13:45:43 postgre-percona-zeljkom systemd: Stopping PostgreSQL 11 database server...
  21. Aug 21 13:45:43 postgre-percona-zeljkom systemd: Stopped PostgreSQL 11 database server.
  22. Aug 21 13:45:43 postgre-percona-zeljkom systemd: Starting PostgreSQL 11 database server...
  23. Aug 21 13:45:43 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:43.416 UTC [19239] LOG:  listening on IPv4 address "0.0.0.0", port 5432
  24. Aug 21 13:45:43 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:43.416 UTC [19239] LOG:  listening on IPv6 address "::", port 5432
  25. Aug 21 13:45:43 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:43.481 UTC [19239] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  26. Aug 21 13:45:43 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:43.681 UTC [19239] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
  27. Aug 21 13:45:43 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:43.729 UTC [19239] LOG:  redirecting log output to logging collector process
  28. Aug 21 13:45:43 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:43.729 UTC [19239] HINT:  Future log output will appear in directory "log".
  29. Aug 21 13:45:45 postgre-percona-zeljkom systemd: Started PostgreSQL 11 database server.
  30. Aug 21 13:45:45 postgre-percona-zeljkom systemd: Removed slice User Slice of root.
  31. Aug 21 13:45:45 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:45] [NOTICE] STANDBY FOLLOW successful
  32. Aug 21 13:45:45 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:45] [DETAIL] standby attached to upstream node "server-c" (ID: 2)
  33. Aug 21 13:45:46 postgre-percona-zeljkom systemd: Stopping PostgreSQL 11 database server...
  34. Aug 21 13:45:46 postgre-percona-zeljkom systemd: Stopped PostgreSQL 11 database server.
  35. Aug 21 13:45:46 postgre-percona-zeljkom systemd: Starting PostgreSQL 11 database server...
  36. Aug 21 13:45:46 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:46.148 UTC [19289] LOG:  listening on IPv4 address "0.0.0.0", port 5432
  37. Aug 21 13:45:46 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:46.148 UTC [19289] LOG:  listening on IPv6 address "::", port 5432
  38. Aug 21 13:45:46 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:46.308 UTC [19289] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
  39. Aug 21 13:45:46 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:46.356 UTC [19289] LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
  40. Aug 21 13:45:46 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:46.371 UTC [19289] LOG:  redirecting log output to logging collector process
  41. Aug 21 13:45:46 postgre-percona-zeljkom postmaster: 2019-08-21 11:45:46.371 UTC [19289] HINT:  Future log output will appear in directory "log".
  42. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Created slice User Slice of root.
  43. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Started Session c24 of user root.
  44. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Stopping A replication manager, and failover management tool for PostgreSQL...
  45. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [NOTICE] TERM signal received
  46. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [ERROR] unable to determine if server is in recovery
  47. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [DETAIL]
  48. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: FATAL:  terminating connection due to administrator command
  49. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: server closed the connection unexpectedly
  50. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: This probably means the server terminated abnormally
  51. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: before or while processing the request.
  52. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [DETAIL] query text is:
  53. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: SELECT pg_catalog.pg_is_in_recovery()
  54. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [INFO] repmgrd terminating...
  55. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Stopped A replication manager, and failover management tool for PostgreSQL.
  56. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Started PostgreSQL 11 database server.
  57. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Starting A replication manager, and failover management tool for PostgreSQL...
  58. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [NOTICE] using provided configuration file "/etc/repmgr/11/repmgr.conf"
  59. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [NOTICE] repmgrd (repmgrd 4.4) starting up
  60. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [INFO] connecting to database "host=192.168.120.3 user=repmgr dbname=repmgr port=5432 connect_timeout=7"
  61. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Started A replication manager, and failover management tool for PostgreSQL.
  62. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: INFO:  set_repmgrd_pid(): provided pidfile is /run/repmgr/repmgrd-11.pid
  63. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [NOTICE] starting monitoring of node "server-f" (ID: 3)
  64. Aug 21 13:45:49 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:49] [INFO] "connection_check_type" set to "ping"
  65. Aug 21 13:45:49 postgre-percona-zeljkom systemd: Removed slice User Slice of root.
  66. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:52] [ERROR] connection to database failed
  67. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:52] [DETAIL]
  68. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: could not connect to server: No route to host
  69. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: Is the server running on host "192.168.120.7" and accepting
  70. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: TCP/IP connections on port 5432?
  71. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:52] [DETAIL] attempted to connect using:
  72. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: user=repmgr connect_timeout=7 dbname=repmgr host=192.168.120.7 port=5432 fallback_application_name=repmgr
  73. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:52] [ERROR] unable connect to upstream node (ID: 1), terminating
  74. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:52] [HINT] upstream node must be running before repmgrd can start
  75. Aug 21 13:45:52 postgre-percona-zeljkom repmgrd: [2019-08-21 13:45:52] [INFO] repmgrd terminating...
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!