9999b9deae
Some checks failed
- Removed redundant aitbc2 (via gitea-runner) section - Consolidated into gitea-runner section with aitbc2-specific commands - Clarifies that aitbc2 blockchain node runs on gitea-runner host - Simplifies SSH access documentation
1.6 KiB
1.6 KiB
SSH Access Patterns for AITBC Nodes
Purpose
Document SSH access patterns for all AITBC nodes in the infrastructure.
Node Access Patterns
aitbc (localhost)
Direct access - no SSH required.
# Run commands directly on localhost
echo "command"
systemctl restart service-name
aitbc1
Direct SSH access.
ssh aitbc1
# Or execute single command
ssh aitbc1 "command"
gitea-runner (hosts aitbc2 blockchain node)
Direct SSH access. The aitbc2 blockchain node runs on this same host.
ssh gitea-runner
# Or execute single command
ssh gitea-runner "command"
# aitbc2 blockchain node runs on this host
# Execute aitbc2-specific commands
ssh gitea-runner "/opt/aitbc/aitbc-cli blockchain info"
ssh gitea-runner "systemctl status aitbc-blockchain-node --no-pager"
Common Operations
Check service status on aitbc1
ssh aitbc1 "systemctl status aitbc-blockchain-node --no-pager"
Restart service on gitea-runner (aitbc2)
ssh gitea-runner "systemctl restart aitbc-blockchain-node"
Copy file to aitbc1
scp /path/to/file aitbc1:/path/to/destination
Execute script on gitea-runner
ssh gitea-runner "bash /path/to/script.sh"
Multi-Node Operations
Run command on all remote nodes
for node in aitbc1 gitea-runner; do
ssh "$node" "systemctl status aitbc-blockchain-node --no-pager"
done
Check block heights across all nodes
for node in aitbc1 gitea-runner; do
echo "=== $node ==="
ssh "$node" "curl -s http://localhost:8006/rpc/bestBlock | jq '.height'"
done