#Dagger server sometimes not sshable due to network namespace

1 messages · Page 1 of 1 (latest)

ripe obsidian
#

I am getting this errors quite often with dagger engine 0.11.9
DeadlineExceeded: failed to get main client caller: no active session for
and when i checked logs after sometimes(when server become sshable), i see engine logs like this
level=warning msg="failed to release network namespace \"4putf26xs0qfx52e8rgstwcbh\" left over from previous run: plugin type=\"loopback\" failed (delete): unknown FS magic on

I believe dagger uses network namespace a lot and somehow its not able to release. I am not sure about casue of actaul problem but could be related.

Could you please help?

glossy frigate
ripe obsidian
#

We don't have immediate plan to upgrade, but we will consider it for sure. But I wanted to check if it's something that you are/were aware of this issue before

glossy frigate
#

not sure I've seen that before. Could also be something within your servers as well depending the kernel version.

#

silentnly tagging @slim cave and @thorn vortex which might have seen that before

#

seems like the warning message particularly doesn't seem to be related to the main error reported here as I've found the message "unknown FS magic on " in the Discord server history a few times.

#

@ripe obsidian I'd try upgrading to v0.12.4 when possible to check if that fixes it

#

particularly because we're currently backporting any fixes into minor releases

ripe obsidian
#

i have seen this error before even before upgrade to 0.11.9, so not sure if upgrading might fix this, for some reason dagger session is dropped

glossy frigate
#

@ripe obsidian IIRC you have this custom setup with a reverse proxy in the middle right?

ripe obsidian
#

that proxy is still a problem which we removed it(we have to fix that as well) but for now server address are directly via tcp server url

glossy frigate
#

can you reproduce in your local machine? or does it happen only with the remote engine?

ripe obsidian
#

these build are little big, so running it via gitlab runner is only solution

#

also i am little afraid for directly upgrading to latest version, i have seen some breaking feature when upgrade(like gc issue in previous version), so i am little hesitant to go to latest version for now

#

but if you are confident about stability i can plan for upgradation🙂

glossy frigate