> On Feb 24, 2017, at 1:37 PM, Tom Ekberg <tekberg@uw.edu> wrote:
>
> I'm running postgres 9.6.2 (also happened on 9.3.14) and have a cron job that runs hourly that runs a program that
doesmostly postgres SELECTs on a different host. Occasionally I get email (not hourly) from the cron daemon that
containsa stack trace that ends with this:
>
> sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not translate host name "db3.labmed.uw.edu" to
address:Name or service not known
>
> It has happened about 9 times so far this month. I have one of our network people look into this but there is no real
answer.I could use the IP address but I'd rather not. This problem only happens on one host. I moved the data from db2
todb3. I was getting similar emails regarding db2 which runs the older postgres.
>
> Any ideas on how to proceed?
It looks like a DNS issue. That hostname authoritatively doesn't exist, according to any of UW's nameservers.
If it works sometimes then you have some sort of internal name resolution hack, and it's not reliable.
Cheers,
Steve
>
> Tom Ekberg
> Senior Computer Specialist, Lab Medicine
> University of Washington Medical Center
> 1959 NE Pacific St, MS 357110
> Seattle WA 98195
> work: (206) 598-8544
> email: tekberg@uw.edu
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general