Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Lagoon API Error: No channels left to allocate

See original GitHub issue

Describe the bug Watching at api logs, today I got this error several times:

[api-100-4bgkx] error: Error: No channels left to allocate 
[api-100-4bgkx]     at Connection.C.freshChannel (/app/node_modules/amqplib/lib/connection.js:451:11) 
[api-100-4bgkx]     at Channel.C.allocate (/app/node_modules/amqplib/lib/channel.js:53:29) 
[api-100-4bgkx]     at tryCatcher (/app/node_modules/bluebird/js/release/util.js:16:23) 
[api-100-4bgkx]     at Function.Promise.attempt.Promise.try (/app/node_modules/bluebird/js/release/method.js:39:29) 
[api-100-4bgkx]     at Channel.C.open (/app/node_modules/amqplib/lib/channel_model.js:68:21) 
[api-100-4bgkx]     at ChannelModel.CM.createChannel (/app/node_modules/amqplib/lib/channel_model.js:48:12) 
[api-100-4bgkx]     at /app/node_modules/rabbitmq-pub-sub/dist/main.js:425:61 
[api-100-4bgkx]     at tryCatcher (/app/node_modules/bluebird/js/release/util.js:16:23) 
[api-100-4bgkx]     at Promise._settlePromiseFromHandler (/app/node_modules/bluebird/js/release/promise.js:517:31) 
[api-100-4bgkx]     at Promise._settlePromise (/app/node_modules/bluebird/js/release/promise.js:574:18) 
[api-100-4bgkx]     at Promise._settlePromiseCtx (/app/node_modules/bluebird/js/release/promise.js:611:10) 
[api-100-4bgkx]     at _drainQueueStep (/app/node_modules/bluebird/js/release/async.js:142:12) 
[api-100-4bgkx]     at _drainQueue (/app/node_modules/bluebird/js/release/async.js:131:9) 
[api-100-4bgkx]     at Async._drainQueues (/app/node_modules/bluebird/js/release/async.js:147:5) 
[api-100-4bgkx]     at Immediate.Async.drainQueues [as _onImmediate] (/app/node_modules/bluebird/js/release/async.js:17:14) 
[api-100-4bgkx]     at runCallback (timers.js:705:18) 'failed to recieve message from queue \'%s\'' 'api.event.deployment.added'

Issue Analytics

State:
Created 4 years ago
Comments:6 (6 by maintainers)

Top GitHub Comments

1reaction

Schnitzelcommented, Jun 29, 2020

I think just restarting all api pods solves this issue as well, as the issue is that the api creates a new channel for every GraphQL Subscription that is created, if you restart the api, all channels are closed and the cycle starts again.

0reactions

tobybellwoodcommented, Nov 10, 2022

lets address subscriptions

Top Results From Across the Web

Lagoon API Error: No channels left to allocate #1344 - GitHub

Describe the bug Watching at api logs, today I got this error several times: [api-100-4bgkx] error: Error: No channels left to allocate ......

Rabbit MQ amqplib error "No channels left to allocate"

The maximum number of channels you can allocate is negotiated with rabbitmp server. In my server, this value is 2047.

No channels left to allocate error - Google Groups

Iam getting `No channels left to allocate error` after few messages. I'm not able find the root cause for this error. Thanks for...

Troubleshoot Dataflow errors - Google Cloud

This error occurs if the Dataflow service account doesn't have access to the Data Catalog API. To resolve this issue, enable the Data...

Critical Issues Addressed in PAN-OS Releases

Bugs Affected Platform(if any). /Affected Version Description (release note) PAN‑92564 8.0.0‑8.0‑8, 8.1.0 PAN‑86882 8.0.0‑8.0.7. and all older Mainlines PAN‑81990 PA‑5220,PA‑5250. /. 8.0.4 Multiple DP restarts by...