@hvt thanks for reporting this issue! The error message occurs if devspace somehow loses connection to the pods where the logs are streamed from. Losing the connection could have several reasons:

• The pod is restarting for some reason (you can verify this via kubectl get pods)
• Some kubernetes api servers have a timeout for idle connections and will kill the connection if this timeout is reached
• There is an issue with the network which causes the connection loss

Having multiple devspace dev running shouldn't cause any issues with log streaming usually, are these projects running in the same namespace or have mutual deployments?

The projects are running in the same namespace.

Mmm, I will see what kubectl get pods gives, around the time this is happening. Will get back once it appears again :].

Hey @FabianKramm, this indeed happens when the pod is getting terminated and restarted because of failing liveness or readiness checks (your first point) because hey, we're developing and stuff breaks ;], or when I have a really long lasting devspace dev session that probably triggers a timeout at the Kubernetes API (your second point).

Is there anything that can be done about this? I.e. find the new deployed pod? Or is there missing metadata since the pod is not explicitly started by devspace itself, but by Kubernetes itself?