Hi all -- I have seen this pop up on my self-manag...
# ask-community
t
Hi all -- I have seen this pop up on my self-managed prefect server. Any idea on what it means?
Copy code
AttributeError: 'NoneType' object has no attribute 'backend_pid'
16:28:53.312 | WARNING | prefect.server.services.cancellationcleanup - CancellationCleanup took 20.650677 seconds to run, which is longer than its loop interval of 20.0 seconds.
16:30:32.442 | ERROR   | asyncio - Future exception was never retrieved
future: <Future finished exception=TimeoutError()>
TimeoutError
16:30:32.444 | ERROR   | asyncio - Future exception was never retrieved
future: <Future finished exception=AttributeError("'NoneType' object has no attribute 'backend_pid'")>
Traceback (most recent call last):
  File "/home/gal16b/miniforge3/envs/prefect3.11/lib/python3.11/site-packages/asyncpg/connection.py", line 1586, in _cancel
    backend_pid=self._protocol.backend_pid,
                ^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'backend_pid'
n
hi @Tim Galvin - hmmm no I'm not sure any chance there's more of that stack trace to share?
t
I will go looking (I restarted the service some hours ago), but it didn't seem to be much. This error was thrown / repeated a lot in the persistent screen session I have it running under
If it is treiggered again I will have a deeper look (which really means scrolling up a lot more!!)
Not clear to me if the issue was postgres either. As in the postgres database is placed in a downed state, which causes a bubble of connection errors in other connected services, like in prefect