| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Ray O'Donnell <ray(at)rodonnell(dot)ie>, Yessica Brinkmann <brinkmann(dot)yessica(at)gmail(dot)com> |
| Cc: | Dave Cramer <davecramer(at)postgres(dot)rocks>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Pg_hba.conf problem after unexpected IP change |
| Date: | 2021-11-14 20:16:32 |
| Message-ID: | d6d7746b-18a4-5582-fba9-ca97de08d407@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/14/21 11:55, Ray O'Donnell wrote:
> On 14/11/2021 19:46, Yessica Brinkmann wrote:
>> Hello.
>> Thank you very much for your answer.
>> The configuration actually works for me.After restarting my computer,
>> I went to test again and it was already working. I assume that perhaps
>> because they are virtual machines it was not only enough to restart
>> the server, I think you also had to restart the computer.
>> It's what I think, or I don't know what else could have happened, but
>> now it's working for me.
>
> Restarting the entire computer shouldn't be necessary... On the Debian
> servers I look after, it's enough to do:
>
> systemctl restart postgresql
>
> (or whatever the name of the particular service is).
Actually that was already done:
The problems seems to have stemmed from this(per OP):
"Well, it turns out that at one point when I was using my virtual
machines, suddenly and unexpectedly, the IP of one of the virtual
machines changed."
Something to do with the networking between host and VM's I presume.
>
> Ray.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ray O'Donnell | 2021-11-14 20:17:38 | Re: Pg_hba.conf problem after unexpected IP change |
| Previous Message | Ray O'Donnell | 2021-11-14 19:55:35 | Re: Pg_hba.conf problem after unexpected IP change |