Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lcJid-000415-Mo for pgsql-admin@arkaria.postgresql.org; Fri, 30 Apr 2021 03:21:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lcJic-0006jg-JF for pgsql-admin@arkaria.postgresql.org; Fri, 30 Apr 2021 03:21:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lcJic-0006jX-7R for pgsql-admin@lists.postgresql.org; Fri, 30 Apr 2021 03:21:30 +0000 Received: from mail-oi1-x236.google.com ([2607:f8b0:4864:20::236]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lcJiY-0006CF-8M for pgsql-admin@lists.postgresql.org; Fri, 30 Apr 2021 03:21:29 +0000 Received: by mail-oi1-x236.google.com with SMTP id e25so38721047oii.2 for ; Thu, 29 Apr 2021 20:21:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=3Oht556E830rOi/PtETN9EYxxueP0Qiee6DFbRJD6IQ=; b=EguT3Zlt45xRnzgPTHqfxL8X7xRRXPjs0srw1BxpqtYvBa+9UP/VbcZx1o0i3Dyhov ahzRd0mFMY0zDAWggpwNnA0hkrUZHh/cCp15gubGrE5PL7fWN5lfMrCwxOdgA6GRaUd5 WeyL6jwdAOBxVP8YKOnwA1/kPUCcxWhjwc/EIkhSCcDWdHoKM5sXAI/2niB1BMdBxvDZ Z4x+FXXJ9X80lnZ9PIMzVWHhYYjvjZAjcxKehK56z+LO1G18ughtbNmPXKdccAGpK8/2 O0YCRKTsTvGDXz6F3En3n5Sy/5jJwgRRUboo6ILB1x4hCCS2LqTgyI1dSrcZjmcmMalT /z0A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=3Oht556E830rOi/PtETN9EYxxueP0Qiee6DFbRJD6IQ=; b=pMdovytbyoNfnhn7aedNhl6hReyoOKvd8XejhHZfvjsGE4NfXEwSyippHGxp2Lluv8 J6WOSL5Ac59H78kyrIvhbnwgF69icJwx2Ej+vqBX0HmMyMmDqB5iouIYSdB+ujGUCyas kQAM+zFUkFGLppNyXfsjveDssvWkrSbEpzkH0nw6Qmdg0Twk8b9H3+E/LECtF1n7YRlH uYNhOJFXwcqZ42ve5gOI98sbdy/bAfm8eLQkENrwlW9F5/0viefZPMH1jbcn1vCwOe7t hgRZOdXn8Oy9IANjCMPeKAwV7zjb989eIG/IYitbeupnPgdbnp93/FEyOYJiEdVAwRRp m+Ug== X-Gm-Message-State: AOAM532G2fT3AXpTG8xzDyHPBXT8qAvZ+V9HPK3P575by0sfFrX8c0eD 6GFQzZ1CWMmWKomUkFpT8UvuRTpOX0k= X-Google-Smtp-Source: ABdhPJzFCy9uAIAJFInaK+TxlDkGzBORu5x4E/5N52Ea945aeqcqJKehAXs192rqskBODmlRpdm/jg== X-Received: by 2002:aca:c206:: with SMTP id s6mr2282311oif.177.1619752883998; Thu, 29 Apr 2021 20:21:23 -0700 (PDT) Received: from [192.168.88.10] (ip174-67-141-204.no.no.cox.net. [174.67.141.204]) by smtp.googlemail.com with ESMTPSA id u126sm491132oig.4.2021.04.29.20.21.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 29 Apr 2021 20:21:23 -0700 (PDT) Subject: Re: FATAL error in logs: no pb_hba.conf entry To: pgsql-admin@lists.postgresql.org References: <1566938499.2834154.1619746776214.ref@mail.yahoo.com> <1566938499.2834154.1619746776214@mail.yahoo.com> From: Ron Message-ID: Date: Thu, 29 Apr 2021 22:21:22 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <1566938499.2834154.1619746776214@mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------053647E3ADA0B4B769C67CA2" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------053647E3ADA0B4B769C67CA2 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit On 4/29/21 8:39 PM, james terris wrote: > Hello, > I have a postgres version 9.6 server running on and old Windows Server > 2008 R2 server. An *EOL* Windows Server...  Don't feel too bad: I've got to manage SQL Server 2005 on Win 2008 R2; earlier this year, we just migrated SQL Server 2000 to 2016. > I noticed this message in the logs: > > FATAL: no pg_hba.conf entry for host "::1", user "APPSERVER$", database > "postgres", SSL off > > > It's true that I don't have a row for the the "APPSERVER$" user but I'm > not really sure where that user is coming from. It's the server name and > it's only trying to log in via IPv6 ? > > If someone could give me some more details about why is causing that log > line that would be great. I have other servers configured without that > line in pg_hba.conf and they don't have that FATAL message. It means exactly what it says: some process is trying to log in as user APPSERVER$ from the IPv6 loopback device.  This is a security concern.  Look in the Windows Event logs for that user, ask the Windows sysadmins, and the end users who care about this. > My pg_hba.conf looks like this: > > host    all   postgres 127.0.0.1/32   md5 > host anotherDB   anotherUser    127.0.0.1/32   md5 > host all   postgres    ::1/128   md5 > host anotherDB anotherUser ::1/128  md5 -- Angular momentum makes the world go 'round. --------------053647E3ADA0B4B769C67CA2 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit On 4/29/21 8:39 PM, james terris wrote:
Hello,
I have a postgres version 9.6 server running on and old Windows Server 2008 R2 server.

An EOL Windows Server...  Don't feel too bad: I've got to manage SQL Server 2005 on Win 2008 R2; earlier this year, we just migrated SQL Server 2000 to 2016.


I noticed this message in the logs:

FATAL: no pg_hba.conf entry for host "::1", user "APPSERVER$", database "postgres", SSL off


It's true that I don't have a row for the the "APPSERVER$" user but I'm not really sure where that user is coming from. It's the server name and it's only trying to log in via IPv6 ?

If someone could give me some more details about why is causing that log line that would be great. I have other servers configured without that line in pg_hba.conf and they don't have that FATAL message.

It means exactly what it says: some process is trying to log in as user APPSERVER$ from the IPv6 loopback device.  This is a security concern.  Look in the Windows Event logs for that user, ask the Windows sysadmins, and the end users who care about this.

My pg_hba.conf looks like this:

host    all   postgres    127.0.0.1/32   md5
host    anotherDB   anotherUser    127.0.0.1/32   md5
host    all   postgres    ::1/128   md5
host    anotherDB    anotherUser    ::1/128   md5

--
Angular momentum makes the world go 'round.
--------------053647E3ADA0B4B769C67CA2--