From 8df7da07d0f28f8be17c61b65fc5cbebe99a82d7 Mon Sep 17 00:00:00 2001
From: mehmetyavuzz43 <147098445+mehmetyavuzz43@users.noreply.github.com>
Date: Thu, 18 Dec 2025 20:04:20 +0100
Subject: [PATCH] docs: add local logging troubleshooting guide

Added short instructions for checking services, logs, and RPC health of the local Base node.
---
 docs/LOCAL_LOGGING_TROUBLESHOOTING.md | 31 +++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 docs/LOCAL_LOGGING_TROUBLESHOOTING.md

diff --git a/docs/LOCAL_LOGGING_TROUBLESHOOTING.md b/docs/LOCAL_LOGGING_TROUBLESHOOTING.md
new file mode 100644
index 00000000..d82bb245
--- /dev/null
+++ b/docs/LOCAL_LOGGING_TROUBLESHOOTING.md
@@ -0,0 +1,31 @@
+# Local Logging & Troubleshooting Guide
+
+This document describes a few small helpers for working with a local Base node.
+
+## 1. Check running services
+
+To see which services are up, run:
+
+    docker compose ps
+
+This helps you confirm that the node and execution clients are running.
+
+## 2. Tail node logs
+
+Use the helper script to follow logs:
+
+    ./scripts/tail_node_logs.sh
+
+Or tail a specific service only (for example, the op-node):
+
+    ./scripts/tail_node_logs.sh op-node
+
+## 3. Quick RPC health check
+
+You can verify that the JSON-RPC endpoint is responding with a simple script:
+
+    ./scripts/check_node_health.sh
+    ./scripts/check_node_health.sh http://localhost:8545
+
+If the script prints a latest block number, your node is responding to `eth_blockNumber`.
+If it reports an HTTP error or empty result, check your environment variables and Docker logs.