Skip to content

SASL: Last message was not SASLResponse #3222

@gdaybrice

Description

@gdaybrice

Hi, I'm using node-pg in a serverless environment and I often see the following error:

Unhandled Rejection: Error: SASL: Last message was not SASLResponse
at /var/task/apps/lawy/.next/server/chunks/9840.js:1:2550
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async a.acquireConnection (/var/task/apps/lawy/.next/server/chunks/9840.js:1:58997)

I can see in code that it gets called in finalizeSession

throw new Error('SASL: Last message was not SASLResponse')

When would this error happen?

Thanks for your help.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions