April 15, 2026, 10:04pm 1

After clicking Restart the server and monitoring logs through Output > rust-analyzer Language Server, the following message appears:

[Error - 6:53:42 PM] Server process exited with code 0.

The same issue occurred in both VSCode and Antigravity. I don't know how to fix this behavior. Can anyone help?

Using Ubuntu 24.04 LTS

~$ tree .rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/
.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/
├── cargo
├── cargo-clippy
├── cargo-fmt
├── clippy-driver
├── rust-analyzer
├── rustc
├── rustdoc
├── rustfmt
├── rust-gdb
├── rust-gdbgui
└── rust-lldb

~$ tree .vscode/extensions/rust-lang.rust-analyzer-0.3.2862-linux-x64/
.vscode/extensions/rust-lang.rust-analyzer-0.3.2862-linux-x64/
├── icon.png
├── language-configuration.json
├── LICENSE.txt
├── node_modules
│   ├── d3
│   │   └── dist
│   │       └── d3.min.js
│   └── d3-graphviz
│       └── build
│           └── d3-graphviz.min.js
├── out
│   └── main.js
├── package.json
├── package-lock.json
├── ra_syntax_tree.tmGrammar.json
├── readme.md
├── server
│   └── rust-analyzer
└── walkthrough-setup-tips.md

{
    "rust-analyzer.trace.server": "verbose",
    "rust-analyzer.server.path": "[PATH TO THE BINARY]",
    "rust-analyzer.check.command": "clippy",
    "cSpell.words": [
        "Clippy",
        "println"
    ]
}

1 Like

The process exited with code 0 is expected if you restart the server. That is the old server exiting. If the new server exited, it would automatically get restarted a couple of times and if that still fails you get a notification and the rust analyzer status turns red.

It is also expected that the logs don't show every keystroke.

2 Likes