-
Notifications
You must be signed in to change notification settings - Fork 75
Bug: JSON-RPC API service stops silently without any log output #772
Copy link
Copy link
Open
Labels
Description
🙂 Expected behavior
When the JSON-RPC API service stops (either gracefully or due to a failure), a log message should be emitted so operators can observe the shutdown lifecycle in node logs, consistent with how other services in the node behave.
🫠 Actual behavior
I see nothing in the logs for the jsonrpc-api service.
For other services, it works:
2026-04-01T18:12:24.357 INF Shutting down inspect HTTP server service=advancer
2026-04-01T18:12:24.357 INF Closing machine manager service=advancer
2026-04-01T18:12:24.358 INF Stop service=advancer force=false duration=451.17µs
2026-04-01T18:12:28.950 INF Stop service=claimer force=false duration=281.67µs
2026-04-01T18:12:31.551 INF Stop service=validator force=false duration=257.28µs
2026-04-01T18:12:34.761 INF Stop service=evm-reader force=false duration=156.91µs
🧪 Minimal test case
Start the cartesi-rollupa-jsonrpc-api
Trigger a graceful shutdown (e.g., send SIGTERM).
Inspect the node logs — no "Stop service=jsonrpc-api" message appears
🌎 Environment
Rollups Node version: 2.0.0-alpha.11
Running cartesi-rollups-jsonrpc-api individually without the cartesi-rollups-node supervisor.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Todo