That file just generates the postgres configs. Here is what is generated:
-bash-4.2$ cat postgresql.conf # Do not edit this file manually! # It will be overwritten by Patroni! include 'postgresql.base.conf' cluster_name = 'postgres' hot_standby = 'on' listen_addresses = '192.168.0.124' max_connections = '100' max_locks_per_transaction = '64' max_prepared_transactions = '0' max_replication_slots = '10' max_wal_senders = '10' max_worker_processes = '8' port = '5432' track_commit_timestamp = 'off' unix_socket_directories = '.' wal_keep_segments = '8' wal_level = 'replica' wal_log_hints = 'on' hba_file = '/data/patroni/pg_hba.conf' ident_file = '/data/patroni/pg_ident.conf' -bash-4.2$ cat /data/patroni/pg_hba.conf # PostgreSQL Client Authentication Configuration File # =================================================== # # Refer to the "Client Authentication" section in the PostgreSQL # documentation for a complete description of this file. A short # synopsis follows. # # This file controls: which hosts are allowed to connect, how clients # are authenticated, which PostgreSQL user names they can use, which # databases they can access. Records take one of these forms: # # local DATABASE USER METHOD [OPTIONS] # host DATABASE USER ADDRESS METHOD [OPTIONS] # hostssl DATABASE USER ADDRESS METHOD [OPTIONS] # hostnossl DATABASE USER ADDRESS METHOD [OPTIONS] # # (The uppercase items must be replaced by actual values.) # # The first field is the connection type: "local" is a Unix-domain # socket, "host" is either a plain or SSL-encrypted TCP/IP socket, # "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a # plain TCP/IP socket. # # DATABASE can be "all", "sameuser", "samerole", "replication", a # database name, or a comma-separated list thereof. The "all" # keyword does not match "replication". Access to replication # must be enabled in a separate record (see example below). # # USER can be "all", a user name, a group name prefixed with "+", or a # comma-separated list thereof. In both the DATABASE and USER fields # you can also write a file name prefixed with "@" to include names # from a separate file. # # ADDRESS specifies the set of hosts the record matches. It can be a # host name, or it is made up of an IP address and a CIDR mask that is # an integer (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that # specifies the number of significant bits in the mask. A host name # that starts with a dot (.) matches a suffix of the actual host name. # Alternatively, you can write an IP address and netmask in separate # columns to specify the set of hosts. Instead of a CIDR-address, you # can write "samehost" to match any of the server's own IP addresses, # or "samenet" to match any address in any subnet that the server is # directly connected to. # # METHOD can be "trust", "reject", "md5", "password", "scram-sha-256", # "gss", "sspi", "ident", "peer", "pam", "ldap", "radius" or "cert". # Note that "password" sends passwords in clear text; "md5" or # "scram-sha-256" are preferred since they send encrypted passwords. # # OPTIONS are a set of options for the authentication in the format # NAME=VALUE. The available options depend on the different # authentication methods -- refer to the "Client Authentication" # section in the documentation for a list of which options are # available for which authentication methods. # # Database and user names containing spaces, commas, quotes and other # special characters must be quoted. Quoting one of the keywords # "all", "sameuser", "samerole" or "replication" makes the name lose # its special character, and just match a database or username with # that name. # # This file is read on server startup and when the server receives a # SIGHUP signal. If you edit the file on a running system, you have to # SIGHUP the server for the changes to take effect, run "pg_ctl reload", # or execute "SELECT pg_reload_conf()". # # Put your actual configuration here # ---------------------------------- # # If you want to allow non-local connections, you need to add more # "host" records. In that case you will also need to make PostgreSQL # listen on a non-local interface via the listen_addresses # configuration parameter, or via the -i or -h command line switches. # CAUTION: Configuring the system for local "trust" authentication # allows any local user to connect as any PostgreSQL user, including # the database superuser. If you do not trust all your local users, # use another authentication method. # TYPE DATABASE USER ADDRESS METHOD # "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: host all all ::1/128 trust # Allow replication connections from localhost, by a user with the # replication privilege. local replication all trust host replication all 127.0.0.1/32 trust host replication all ::1/128 trust host replication replicator 127.0.0.1/32 md5 host replication replicator 192.168.0.108/0 md5 host replication replicator 192.168.0.124/0 md5 host replication replicator 192.168.0.118/0 md5 host all all 0.0.0.0/0 md5 -bash-4.2$ pwd /data/patroni -bash-4.2$ -bash-4.2$ cat postgresql.base.conf|grep -v "#"|sed -e "/^$/d" log_timezone = 'Canada/Eastern' datestyle = 'iso, mdy' timezone = 'Canada/Eastern' default_text_search_config = 'pg_catalog.english' -bash-4.2$ On Sat, Jun 1, 2019 at 8:36 PM Adrian Klaver <adrian.kla...@aklaver.com> wrote: > On 6/1/19 5:21 PM, Tom K wrote: > > > > > > On Sat, Jun 1, 2019 at 7:34 PM Adrian Klaver <adrian.kla...@aklaver.com > > <mailto:adrian.kla...@aklaver.com>> wrote: > > > > On 6/1/19 4:22 PM, Tom K wrote: > > > > > > > > > > > > > > Looks like this crash was far more catastrophic then I thought. > > By the > > > looks of things, thinking on psql02 would be my best bet. > > > > > > > The more I look at it the more I think the replication was not doing > > what you thought it was doing. That psql02 was the primary and that > > psql01 and psql03 where out of sync and/or defunct standbys. > > > > > > Now that I look at the files myself, that's the conclusion I was coming > > to myself. Sample config: > > The below would be for someone that uses and understands Patroni. That > would not be me:) > > > > > [root@psql02 base]# cat /etc/patroni.yml > > scope: postgres > > namespace: /db/ > > name: postgresql1 > > > > restapi: > > listen: 192.168.0.124:8008 <http://192.168.0.124:8008> > > connect_address: 192.168.0.124:8008 <http://192.168.0.124:8008> > > > > > Or perhaps when the system crashed, the filesystem check simply moved > > the folders out due to corruption. > > That would leave the cluster in an inconsistent state and you would not > have been able to start the one you got going. > > -- > Adrian Klaver > adrian.kla...@aklaver.com >
