OperationalError: FATAL: no pg_hba.conf entry for replication connection from host












0















I'm trying to build a Postgres HA Cluster with Postgres 11, patroni and etcd.
I have it pretty much working other than the error in the title.



The patroni config section for the pg_hba.conf looks like this,



pg_hba:
- host all postgres all md5


No other entries appear to be needed as the ETCD cluster takes care of the configuration and role of each node.
I have tested this with the node entries of the servers in the pg_hba section but still get the same error.
I built an example of a patroni PG cluster on one server running 2 instances of Postgres 11 and it worked fine. No issues when switching.



I have 2 nodes so when I restart the master and it becomes the secondary, it throws this error



"return self.gen.next() File
"/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1249,
in _get_replication_connection_cursor connect_timeout=3, options='-c
statement_timeout=2000') as cur: File
"/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return
self.gen.next() File
"/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1238,
in _get_connection_cursor with psycopg2.connect(**kwargs) as conn:
File "/usr/lib64/python2.7/site-packages/psycopg2/__init__.py", line
130, in connect conn = _connect(dsn,
connection_factory=connection_factory, **kwasync) OperationalError:
FATAL: no pg_hba.conf entry for replication connection from host
"my private ip", user "replusr", SSL off"


"my private ip" being the IP of the node it is throwing the error on.



Databases replicate across ok so the DB switching works despite this error.



My investigations now suspect its something to do with the ETCD cluster which reports back as healthy and the entries for the nodes appear to be ok.



Has anyone come across this before?










share|improve this question













migrated from superuser.com Dec 20 '18 at 18:16


This question came from our site for computer enthusiasts and power users.




















    0















    I'm trying to build a Postgres HA Cluster with Postgres 11, patroni and etcd.
    I have it pretty much working other than the error in the title.



    The patroni config section for the pg_hba.conf looks like this,



    pg_hba:
    - host all postgres all md5


    No other entries appear to be needed as the ETCD cluster takes care of the configuration and role of each node.
    I have tested this with the node entries of the servers in the pg_hba section but still get the same error.
    I built an example of a patroni PG cluster on one server running 2 instances of Postgres 11 and it worked fine. No issues when switching.



    I have 2 nodes so when I restart the master and it becomes the secondary, it throws this error



    "return self.gen.next() File
    "/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1249,
    in _get_replication_connection_cursor connect_timeout=3, options='-c
    statement_timeout=2000') as cur: File
    "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return
    self.gen.next() File
    "/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1238,
    in _get_connection_cursor with psycopg2.connect(**kwargs) as conn:
    File "/usr/lib64/python2.7/site-packages/psycopg2/__init__.py", line
    130, in connect conn = _connect(dsn,
    connection_factory=connection_factory, **kwasync) OperationalError:
    FATAL: no pg_hba.conf entry for replication connection from host
    "my private ip", user "replusr", SSL off"


    "my private ip" being the IP of the node it is throwing the error on.



    Databases replicate across ok so the DB switching works despite this error.



    My investigations now suspect its something to do with the ETCD cluster which reports back as healthy and the entries for the nodes appear to be ok.



    Has anyone come across this before?










    share|improve this question













    migrated from superuser.com Dec 20 '18 at 18:16


    This question came from our site for computer enthusiasts and power users.


















      0












      0








      0








      I'm trying to build a Postgres HA Cluster with Postgres 11, patroni and etcd.
      I have it pretty much working other than the error in the title.



      The patroni config section for the pg_hba.conf looks like this,



      pg_hba:
      - host all postgres all md5


      No other entries appear to be needed as the ETCD cluster takes care of the configuration and role of each node.
      I have tested this with the node entries of the servers in the pg_hba section but still get the same error.
      I built an example of a patroni PG cluster on one server running 2 instances of Postgres 11 and it worked fine. No issues when switching.



      I have 2 nodes so when I restart the master and it becomes the secondary, it throws this error



      "return self.gen.next() File
      "/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1249,
      in _get_replication_connection_cursor connect_timeout=3, options='-c
      statement_timeout=2000') as cur: File
      "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return
      self.gen.next() File
      "/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1238,
      in _get_connection_cursor with psycopg2.connect(**kwargs) as conn:
      File "/usr/lib64/python2.7/site-packages/psycopg2/__init__.py", line
      130, in connect conn = _connect(dsn,
      connection_factory=connection_factory, **kwasync) OperationalError:
      FATAL: no pg_hba.conf entry for replication connection from host
      "my private ip", user "replusr", SSL off"


      "my private ip" being the IP of the node it is throwing the error on.



      Databases replicate across ok so the DB switching works despite this error.



      My investigations now suspect its something to do with the ETCD cluster which reports back as healthy and the entries for the nodes appear to be ok.



      Has anyone come across this before?










      share|improve this question














      I'm trying to build a Postgres HA Cluster with Postgres 11, patroni and etcd.
      I have it pretty much working other than the error in the title.



      The patroni config section for the pg_hba.conf looks like this,



      pg_hba:
      - host all postgres all md5


      No other entries appear to be needed as the ETCD cluster takes care of the configuration and role of each node.
      I have tested this with the node entries of the servers in the pg_hba section but still get the same error.
      I built an example of a patroni PG cluster on one server running 2 instances of Postgres 11 and it worked fine. No issues when switching.



      I have 2 nodes so when I restart the master and it becomes the secondary, it throws this error



      "return self.gen.next() File
      "/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1249,
      in _get_replication_connection_cursor connect_timeout=3, options='-c
      statement_timeout=2000') as cur: File
      "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__ return
      self.gen.next() File
      "/usr/lib/python2.7/site-packages/patroni/postgresql.py", line 1238,
      in _get_connection_cursor with psycopg2.connect(**kwargs) as conn:
      File "/usr/lib64/python2.7/site-packages/psycopg2/__init__.py", line
      130, in connect conn = _connect(dsn,
      connection_factory=connection_factory, **kwasync) OperationalError:
      FATAL: no pg_hba.conf entry for replication connection from host
      "my private ip", user "replusr", SSL off"


      "my private ip" being the IP of the node it is throwing the error on.



      Databases replicate across ok so the DB switching works despite this error.



      My investigations now suspect its something to do with the ETCD cluster which reports back as healthy and the entries for the nodes appear to be ok.



      Has anyone come across this before?







      linux






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 20 '18 at 3:23









      inkedinked

      11




      11




      migrated from superuser.com Dec 20 '18 at 18:16


      This question came from our site for computer enthusiasts and power users.






      migrated from superuser.com Dec 20 '18 at 18:16


      This question came from our site for computer enthusiasts and power users.
























          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "2"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f946172%2foperationalerror-fatal-no-pg-hba-conf-entry-for-replication-connection-from-ho%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Server Fault!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f946172%2foperationalerror-fatal-no-pg-hba-conf-entry-for-replication-connection-from-ho%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Сан-Квентин

          8-я гвардейская общевойсковая армия

          Алькесар