custom script failed with psycopg.OperationalError

[llamafilm]

One of my custom scripts failed with the following traceback. This sounds like maybe a temporary connection issue to Postgres. I'm wondering if Netbox has any configurable options to make it more resilient against issues like this?
My Postgres cluster is running in RDS Aurora in the same availability zone. RDS metrics show a small spike in throughput around this time but it doesn't seem to be hitting any limits.

An exception occurred: OperationalError: consuming input failed: SSL SYSCALL error: EOF detected

Traceback (most recent call last):
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 105, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/psycopg/cursor.py", line 97, in execute
    raise ex.with_traceback(None)
psycopg.OperationalError: consuming input failed: SSL SYSCALL error: EOF detected

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/opt/netbox-4.0.8/netbox/extras/scripts.py", line 662, in _run_script
    script.output = script.run(data, commit)
                    ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox-4.0.8/netbox/scripts/import_serraview.py", line 53, in run
    included_space_types = list(CustomFieldChoiceSet.objects.get(name='space_types').values)
                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/models/manager.py", line 87, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/models/query.py", line 645, in get
    num = len(clone)
          ^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/models/query.py", line 382, in __len__
    self._fetch_all()
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/models/query.py", line 1928, in _fetch_all
    self._result_cache = list(self._iterable_class(self))
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/models/query.py", line 91, in __iter__
    results = compiler.execute_sql(
              ^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/models/sql/compiler.py", line 1562, in execute_sql
    cursor.execute(sql, params)
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 79, in execute
    return self._execute_with_wrappers(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 92, in _execute_with_wrappers
    return executor(sql, params, many, context)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 100, in _execute
    with self.db.wrap_database_errors:
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/utils.py", line 91, in __exit__
    raise dj_exc_value.with_traceback(traceback) from exc_value
  File "/opt/netbox/venv/lib/python3.12/site-packages/django/db/backends/utils.py", line 105, in _execute
    return self.cursor.execute(sql, params)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/netbox/venv/lib/python3.12/site-packages/psycopg/cursor.py", line 97, in execute
    raise ex.with_traceback(None)
django.db.utils.OperationalError: consuming input failed: SSL SYSCALL error: EOF detected

[candlerb]

One of my custom scripts failed with the following traceback. This sounds like maybe a temporary connection issue to Postgres. I'm wondering if Netbox has any configurable options to make it more resilient against issues like this?

No (AFAIK).

My Postgres cluster is running in RDS Aurora

You are using either RDS or Aurora. Which one is it?

If it's Aurora, it's very unlikely to work. Aurora is an AWS proprietary database. It claims to be Postgres "compatible", i.e. it implements the Postgres wire protocol, but it's not Postgres and Netbox is not developed or tested against it (AFAIK).

What you need is RDS, which runs an actual Postgres cluster for you.

[brianou7]

I hope this could be helpfully for someone...

@llamafilm according what @candlerb say, may be you would like to use Amazon Aurora DSQL > Using Aurora DSQL to build an application with Django instead of PostgreSQL databse backend for Django.