On Sun, Nov 26, 2023 at 6:51 AM Peter J. Holzer wrote:
[snip]
> > But is not explanatory. I want to see host names in the log file when
> > possible, not just IP addresses.
>
> So now that you have IP addresses again, are there any for which a
> reverse lookup doesn't work?
>
I've gone through
On 2023-11-24 16:39:57 -0500, Ron Johnson wrote:
> On Fri, Nov 24, 2023 at 4:26 PM David G. Johnston
> wrote:
>
> On Friday, November 24, 2023, Ron Johnson wrote:
>
>
> The second "way" sounds interesting, but what is it filled with?
With "???"
(which isn't very helpful. I would
On Fri, Nov 24, 2023 at 4:26 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Friday, November 24, 2023, Ron Johnson wrote:
>>
>>
>> The second "way" sounds interesting, but what is it filled with?
>>
>
> What does it matter? It’s an internal detail that apparently gets exposed
>
On Friday, November 24, 2023, Ron Johnson wrote:
>
>
> The second "way" sounds interesting, but what is it filled with?
>
What does it matter? It’s an internal detail that apparently gets exposed
as [unknown] appearing in your log file where the client ip address would
normally be.
>
> I
gt; > 18163 [unknown] 01000 WARNING: 01000:
> > pg_getnameinfo_all() failed: Temporary failure in name resolution
> > 2023-11-24 15:09:02.224 EST [unknown] [unknown]
> > 18163 [unknown] 01000 LOCATION: BackendInitialize,
&g
On 11/24/23 12:30, Ron Johnson wrote:
PG 9.6.24 (Yes, I know it's EOL.)
I'm seeing lots of these in the postgresql log file:
2023-11-24 15:09:02.224 EST [unknown] [unknown]
18163 [unknown] 01000 WARNING: 01000:
pg_getnameinfo_all() failed: Temporary
PG 9.6.24 (Yes, I know it's EOL.)
I'm seeing lots of these in the postgresql log file:
2023-11-24 15:09:02.224 EST [unknown] [unknown]
18163 [unknown] 01000 WARNING: 01000:
pg_getnameinfo_all() failed: Temporary failure in name resolution
2023-11-24 15:09
t;
> On Wed, Jun 5, 2019 at 11:08 AM Steve Crawford <
> scrawf...@pinpointresearch.com> wrote:
>
>> On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj wrote:
>>
>>> Hi All,
>>>
>>> We have recently noticed in our development environment pg_log with
with
>> flooded message.
>>
>> [64459]: [1-1] user=[unknown],db=[unknown],host= WARNING:
>> pg_getnameinfo_all() failed: Temporary failure in name resolution...
>>
>
> First thing I'd check is that DNS is functioning correctly (including
> local resolution settings or caching name resolvers).
>
> Cheers,
> Steve
>
>
On Wed, Jun 5, 2019 at 11:08 AM Steve Crawford <
scrawf...@pinpointresearch.com> wrote:
> On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj wrote:
>
>>
>> [64459]: [1-1] user=[unknown],db=[unknown],host= WARNING:
>> pg_getnameinfo_all() failed: Temporary failure in n
On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj wrote:
> Hi All,
>
> We have recently noticed in our development environment pg_log with
> flooded message.
>
> [64459]: [1-1] user=[unknown],db=[unknown],host= WARNING:
> pg_getnameinfo_all() failed: Temporary failure in name r
Hi All,
We have recently noticed in our development environment pg_log with flooded
message.
[64459]: [1-1] user=[unknown],db=[unknown],host= WARNING:
pg_getnameinfo_all() failed: Temporary failure in name resolution
[64463]: [1-1] user=[unknown],db=[unknown],host= WARNING:
pg_getnameinfo_all
12 matches
Mail list logo
