Thread: postgresql11-devel RPM is missing from "Direct RPM downloads"
Hi, Where can I find postgresq11-devel RPM ? It is missing from direct RPM download page : https://yum.postgresql.org/11/redhat/rhel-7-x86_64/repoview/ or https://yum.postgresql.org/11/redhat/rhel-7-x86_64/repoview/postgresqldbserver11.group.html Thanks, Dmitry
Hi Dimiry, On 04/06/2019 23:49, Dmitry O Litvintsev wrote: > Where can I find postgresq11-devel RPM ? > [...] > https://yum.postgresql.org/11/redhat/rhel-7-x86_64/repoview/ have you looked under the letter "P" in your first link? There you can find the -devel package. https://yum.postgresql.org/11/redhat/rhel-7-x86_64/repoview/letter_p.group.html Cheers! Jakub
D'oh. Thanks! /----------------------------------------------------------\ | Tel: (630) 840 5005 | | FAX: (630) 840 2968 | | (630) 840 2783 | | office: FCC 240 | | E-mail: litvinse@fnal.gov | \----------------------------------------------------------/ On Wed, 5 Jun 2019, Jakub Olczyk wrote: > Hi Dimiry, > > On 04/06/2019 23:49, Dmitry O Litvintsev wrote: >> Where can I find postgresq11-devel RPM ? >> [...] >> https://urldefense.proofpoint.com/v2/url?u=https-3A__yum.postgresql.org_11_redhat_rhel-2D7-2Dx86-5F64_repoview_&d=DwICaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=7PHi3TDlwkvpc07MjENbOxVFl0u_sEurf250JnUFWCU&m=x0FsGjpFkd074Owr0TbLitPaA8Y3iFdjJIgsUZQKx4Q&s=64-qFF0vgct9WdlN14qDUr3Dx58YQv0sWwCFLg2D8M4&e= > > have you looked under the letter "P" in your first link? > There you can find the -devel package. > > https://urldefense.proofpoint.com/v2/url?u=https-3A__yum.postgresql.org_11_redhat_rhel-2D7-2Dx86-5F64_repoview_letter-5Fp.group.html&d=DwICaQ&c=gRgGjJ3BkIsb5y6s49QqsA&r=7PHi3TDlwkvpc07MjENbOxVFl0u_sEurf250JnUFWCU&m=x0FsGjpFkd074Owr0TbLitPaA8Y3iFdjJIgsUZQKx4Q&s=9BjL2HUlWfddhgpV1vnwDsRjRXNO4d1DNN0USk3J1uE&e= > > Cheers! > Jakub > >
Flood Warning message : user=[iso-8859-1],db=[iso-8859-1],host= WARNING:pg_getnameinfo_all() failed: Temporary failure in name resolution
From
Perumal Raj
Date:
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() failed: Temporary failure in name resolution
[64464]: [1-1] user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
[64548]: [1-1] user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
[64551]: [1-1] user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
[64553]: [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() failed: Temporary failure in name resolution
[64464]: [1-1] user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
[64548]: [1-1] user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
[64551]: [1-1] user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
[64553]: [1-1] user=[unknown],db=[unknown],host= WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
Not sure , How to address this message ,
Much appreciated if some one give light on this.
Version . : 9.2.23
Regards,
Raj
Re: Flood Warning message : user=[iso-8859-1],db=[iso-8859-1],host=WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
From
Steve Crawford
Date:
On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj <perucinci@gmail.com> 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 resolution...
First thing I'd check is that DNS is functioning correctly (including local resolution settings or caching name resolvers).
Cheers,
Steve
Re: Flood Warning message : user=[iso-8859-1],db=[iso-8859-1],host=WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
From
bricklen
Date:
On Wed, Jun 5, 2019 at 11:08 AM Steve Crawford <scrawford@pinpointresearch.com> wrote:
On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj <perucinci@gmail.com> wrote:[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).
In addition to what Steve mentioned, I've a vague recollection from running into this several years ago that this is triggered by having "log_hostname" enabled in your postgresql.conf.
Re: Flood Warning message : user=[iso-8859-1],db=[iso-8859-1],host=WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
From
Perumal Raj
Date:
Thanks Steve for the response, Yes we had DNS server change.
But conf file updated with right DNS server and its resolving when i crosscheck with nslookup against clinet_addr
By the way , What is the right syntax for LDAP configuration ,
I am using the one below, and getting LDAP authentication error though i was able to login to server with same password.
host all all 0.0.0.0/0 ldap ldapserver=ldap.xxx.com ldapport=389 ldaptls=1 ldapbasedn="dc=domain,dc=com" ldapbinddn="cn=auth_user,dc=domain,dc=com" ldapbindpasswd=encrypted_password ldapsearchattribute=uid
Version :9..2
Regards,
Raju
On Wed, Jun 5, 2019 at 11:08 AM Steve Crawford <scrawford@pinpointresearch.com> wrote:
On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj <perucinci@gmail.com> 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 resolution...First thing I'd check is that DNS is functioning correctly (including local resolution settings or caching name resolvers).Cheers,Steve
Re: Flood Warning message : user=[iso-8859-1],db=[iso-8859-1],host=WARNING: pg_getnameinfo_all() failed: Temporary failure in name resolution
From
Perumal Raj
Date:
Hi All,
We are using the following format for LDAP authentication,
host all all 0.0.0.0/0 ldap ldapserver=ldap.xxx.com ldapport=389 ldaptls=1 ldapbasedn="dc=domain,dc=com" ldapbinddn="cn=auth_user,dc=domain,dc=com" ldapbindpasswd=encrypted_password ldapsearchattribute=uid
1. It successfully retrieved user information when we do ldapsearch "ldapsearch -H "ldaps://ldap.xxxx.com" -W -D "cn=auth_user,ou=people,dc=domain,dc=com" -b "dc=domain,dc=com" "uid=ldap_user"
2. Same LDAP server is authenticating while ssh / sudo successfully.
But issue is while connecting DB
-bash-4.1$ psql -h dbhost.domain.com -Atc "select 'success'" -Uldap_user postgres
Password for user ldap_user:
psql: FATAL: LDAP authentication failed for user "ldap_user"
-bash-4.1$
Is there any way to validate ldap_user password using ldapsearch ?
Or is there any specific format in pg_hba.conf to configure LDAP.
Regards,
Raj
On Wed, Jun 5, 2019 at 4:56 PM Perumal Raj <perucinci@gmail.com> wrote:
Thanks Steve for the response, Yes we had DNS server change.But conf file updated with right DNS server and its resolving when i crosscheck with nslookup against clinet_addrBy the way , What is the right syntax for LDAP configuration ,I am using the one below, and getting LDAP authentication error though i was able to login to server with same password.host all all 0.0.0.0/0 ldap ldapserver=ldap.xxx.com ldapport=389 ldaptls=1 ldapbasedn="dc=domain,dc=com" ldapbinddn="cn=auth_user,dc=domain,dc=com" ldapbindpasswd=encrypted_password ldapsearchattribute=uidVersion :9..2Regards,RajuOn Wed, Jun 5, 2019 at 11:08 AM Steve Crawford <scrawford@pinpointresearch.com> wrote:On Wed, Jun 5, 2019 at 10:13 AM Perumal Raj <perucinci@gmail.com> 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 resolution...First thing I'd check is that DNS is functioning correctly (including local resolution settings or caching name resolvers).Cheers,Steve