The build was successful, but there is no runtime log output.
ForumForumThe build was successful, but there is no runtime log output.
Hello, we have checked your service (feishu-mcp-percid, deployment ID 69d47d484b28ea4c377fafd5) and observed the following:
The combination of "Build successful + No runtime logs + Deployment FAILED" is most commonly caused not by your application itself, but by the state of the dedicated server node: usually, the CPU/memory is exhausted, or k3s has become unresponsive, causing the Pod to be cleared immediately upon scheduling before it can produce any stdout.
We recommend the following steps (Note: The owner of this server is elonehoo, so steps 1 and 2 need to be performed by him):
lolm-roll, issueflow, api-proxy, etc.) to bring the node to an idle state.feishu-mcp-percid individually and observe if it starts normally and produces runtime logs.If there are still no runtime logs after restarting, please reply, and I will check the K8s events for this Pod from the backend for you.
This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.
New replies are disabled for resolved issues.