From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: peet.whittaker@gmail.com
Subject: BUG #16576: Creating a connection using psycopg2 results in "zombie" ccapiserver.exe processes on Windows
Date: Fri, 07 Aug 2020 15:52:52 +0000
Message-ID: <16576-0f02e224a1c2007b@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 16576
Logged by: Peet Whittaker
Email address: peet.whittaker@gmail.com
PostgreSQL version: 12.3
Operating system: Windows Server 2019
Description:
Originally reported here: https://github.com/psycopg/psycopg2/issues/1138
Running the following Python code (filling in the connection details)
results in a ccapiserver.exe process being spawned that persists even after
the Python session has ended.
import psycopg2
with psycopg2.connect(host='', dbname='', user='', password='') as conn:
pass
If the code is then re-run, no additional ccapiserver.exe process is spawned
(i.e. the total number of ccapiserver.exe processes stays at 1). However, if
the code is run via a scheduled task, it does spawn additional
ccapiserver.exe processes. This led to a huge number of these "zombie"
processes on one of our production servers (resulting in scheduled task
failures and general system slow-down).
The ccapiserver.exe process appears to be the "Kerberos Credentials Cache
API Server", although we are not using Kerberos authentication.
Is this a bug, or is there a way to avoid spawning the ccapiserver.exe
process?
Thanks
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, peet.whittaker@gmail.com
Subject: Re: BUG #16576: Creating a connection using psycopg2 results in "zombie" ccapiserver.exe processes on Windows
In-Reply-To: <16576-0f02e224a1c2007b@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox