Troubleshooting

The current project's Python requirement (>=3.10) is not compatible with some of the required packages Python requirement

python --version
# or
python3 --version

# Ubuntu/Debian
sudo apt install python3.10

# macOS with Homebrew
brew install [email protected]

poetry env use python3.10
poetry install

# Clear Poetry cache
poetry cache clear pypi --all

# Update Poetry itself
poetry self update

# Use --no-cache option
poetry install --no-cache

# If still failing, try without dev dependencies first
poetry install --without dev

# Option 1: Virtual environment (recommended)
python -m venv chainbench-env
source chainbench-env/bin/activate  # On Windows: chainbench-env\Scripts\activate
pip install chainbench

# Option 2: User install
pip install --user chainbench

Target is required. If running in Web UI mode you may change it later but it is needed to initialize test data.

chainbench start --profile ethereum.general --target https://your-node.com

Profile ethereum.invalid could not be found in /path/to/profiles.
Use 'chainbench list profiles' to list available profiles.

# List built-in profiles
chainbench list profiles

# List profiles in custom directory
chainbench list profiles -d /path/to/custom/profiles

# Use correct profile name
chainbench start --profile ethereum.general --target https://your-node.com

Error occurred: Multiple test data types detected.
Specifying a directory that contains load profiles with same test data type is required

chainbench start \
  --profile ethereum.general \
  --target https://pruned-node.com \
  --use-latest-blocks \
  --size S \
  --headless --autoquit

Both start-block and end-block are required for specifying custom block range.

end-block must be greater than start-block.

chainbench start \
  --profile ethereum.general \
  --target https://node.com \
  --start-block 1000000 \
  --end-block 1001000 \
  --headless --autoquit

# Start with XS (10 blocks) for testing
chainbench start --profile ethereum.general --size XS --target https://node.com

# Move to S (100 blocks) for short tests
chainbench start --profile ethereum.general --size S --target https://node.com

# Use larger sizes only for extended tests
chainbench start --profile ethereum.general --size L --test-time 12h --target https://node.com

chainbench start \
  --profile ethereum.general \
  --target https://slow-node-to-test.com \
  --ref-url https://fast-reference-node.com \
  --size M \
  --headless --autoquit

HTTP Timeout Exception: ...

# Test with curl
curl -X POST https://your-node.com \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

# Check for authentication requirements
# Some endpoints need API keys in headers or URL
chainbench start \
  --target https://your-node.com/YOUR-API-KEY \
  --profile ethereum.general

# Verify port 5557 is available
lsof -i :5557
netstat -an | grep 5557

# Reduce worker count if system is constrained
chainbench start \
  --profile ethereum.general \
  --workers 2 \
  --target https://node.com

# Check for firewall issues (especially on cloud instances)
sudo ufw status
sudo firewall-cmd --list-all

# Option 1: Use different port
chainbench start \
  --profile ethereum.general \
  --port 5558 \
  --target https://node.com

# Option 2: Find and stop conflicting process
lsof -ti:5557 | xargs kill -9

# Option 3: Stop previous Chainbench instances
pkill -f chainbench

chainbench start \
  --profile ethereum.general \
  --test-time 1h \
  --headless \
  --autoquit \
  --target https://node.com

chainbench start \
  --profile ethereum.general \
  --target https://node.com \
  --monitor sync-lag-monitor \
  --headless \
  --autoquit

PG connection parameters are required when --timescale flag is used:
pg_host, pg_port, pg_username, pg_password

chainbench start \
  --profile ethereum.general \
  --target https://node.com \
  --timescale \
  --pg-host localhost \
  --pg-port 5432 \
  --pg-username postgres \
  --pg-password your_password \
  --headless --autoquit

# 1. Verify database is running
docker ps | grep timescale
# or
sudo systemctl status postgresql

# 2. Test connection manually
psql -h localhost -U postgres -c "SELECT 1;"

# 3. Check firewall
sudo ufw status
sudo firewall-cmd --list-all

# 4. Verify TimescaleDB extension
psql -d postgres -c "SELECT * FROM pg_extension WHERE extname = 'timescaledb';"

# 5. Check pg_hba.conf allows connections
sudo cat /etc/postgresql/*/main/pg_hba.conf | grep -v "^#"

# Check permissions
ls -la results/

# Fix permissions
chmod -R u+w results/

# Or specify different directory
chainbench start \
  --profile ethereum.general \
  --target https://node.com \
  --results-dir /tmp/chainbench-results

# Check results directory structure
ls -R results/

# Verify disk space
df -h .

# Check Chainbench logs
grep -i error results/*/locust.log

results/
  └── {profile_name}/
      └── {timestamp}/
          ├── stats.csv
          ├── stats_history.csv
          ├── failures.csv
          └── exceptions.csv

chainbench start \
  --profile ethereum.general \
  --debug-trace-methods \
  --users 10 \
  --target https://archive-node.com

# Format code
poetry run black .
poetry run isort .

# Check for issues
poetry run flake8
poetry run mypy .

# Or run all pre-commit hooks
poetry run pre-commit run --all-files