ResolvedFunctionsCloud

[SOLVED] My CLoud function suddenly not working

Mar 9, 2024, 01:00

View on Discord

Votes

Replies

Participants

Unknown

Messages

Mosh OntongOriginal post

Quality

Feb 29, 2024, 00:41

An internal curl error has occurred while starting runtime! Error Msg: Docker Error: docker: Error response from daemon: Conflict. The container name "/exc5-65c5df06933e47ebdec4-65db2b1e57482e06673b" is already in use by container "af988d3c2da9426f5f2a4444cb0fcc723676efa41a671d4aded842d0f47cf3ee". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
\nError Code: 500

Summary

Cloud function stopped working suddenly due to a conflict with a container name. Redeploying the function resolved the issue.

Steven

Admin

Feb 29, 2024, 00:45

for now, best if you redeployed

Mosh Ontong

Quality

Feb 29, 2024, 00:45

ohh I see I will try

Mosh Ontong

Quality

Feb 29, 2024, 00:53

thanks steve the function is working right now

Steven

Admin

Feb 29, 2024, 00:56

[SOLVED] My CLoud function suddenly not working

Steven

Admin

Mar 9, 2024, 00:38

The underlying problem is the executor thinks the runtime container doesn't exist but it does. We keep track of the active runtimes in memory table but for some reason there's an error adding the entry in the table

[SOLVED] My CLoud function suddenly not working

Need support?_