Skip to content
Remnawave Telegram Shop Bot
v3.5.6 261

Logs & Debugging

Viewing Logs

Section titled “Viewing Logs”

Real-time Logs

Section titled “Real-time Logs”
Terminal window
# Follow bot logs (live)
docker compose logs -f remnawave-telegram-shop-bot


# Follow database logs
docker compose logs -f postgres


# Both simultaneously
docker compose logs -f

Historical Logs

Section titled “Historical Logs”
Terminal window
# Last 100 lines
docker compose logs --tail 100 remnawave-telegram-shop-bot


# Specific time range
docker compose logs \
  --since 2024-11-10T10:00:00 \
  --until 2024-11-10T11:00:00 \
  remnawave-telegram-shop-bot


# All available logs
docker compose logs remnawave-telegram-shop-bot > /tmp/bot-logs.txt

Log Levels

Section titled “Log Levels”

Error Logs

Section titled “Error Logs”
Terminal window
# Show only errors
docker compose logs remnawave-telegram-shop-bot | grep -i error


# With context
docker compose logs remnawave-telegram-shop-bot | grep -A 5 -B 5 "error"

Common errors:

  • connection refused - Service unavailable
  • permission denied - Access issue
  • timeout - Slow response
  • invalid token - Auth failed

Warning Logs

Section titled “Warning Logs”
Terminal window
docker compose logs remnawave-telegram-shop-bot | grep -i warning

Info Logs

Section titled “Info Logs”
Terminal window
docker compose logs remnawave-telegram-shop-bot | grep -i "info\|started"

Common Log Patterns

Section titled “Common Log Patterns”

On Startup

Section titled “On Startup”
[INFO] Starting bot
[INFO] Connecting to database
[INFO] Database connection established
[INFO] Loading configuration
[INFO] Bot ready for commands

Payment Processing

Section titled “Payment Processing”
[INFO] Payment received from user 123456789
[INFO] Processing payment via yookassa
[INFO] Activating subscription for user
[INFO] Subscription activated successfully

Errors

Section titled “Errors”
[ERROR] Failed to connect to database: connection refused
[ERROR] Invalid API token
[ERROR] User not found in Remnawave
[ERROR] Webhook signature verification failed

Filtering Logs

Section titled “Filtering Logs”

By Component

Section titled “By Component”
Terminal window
# Database related
docker compose logs remnawave-telegram-shop-bot | grep -i "database\|db\|postgres"


# Payment related
docker compose logs remnawave-telegram-shop-bot | grep -i "payment\|yookassa\|crypto\|stars"


# User related
docker compose logs remnawave-telegram-shop-bot | grep -i "user\|subscription"


# API related
docker compose logs remnawave-telegram-shop-bot | grep -i "api\|remnawave"

By Severity

Section titled “By Severity”
Terminal window
# Errors
docker compose logs remnawave-telegram-shop-bot | grep ERROR


# Warnings
docker compose logs remnawave-telegram-shop-bot | grep WARNING


# Info
docker compose logs remnawave-telegram-shop-bot | grep INFO

By User

Section titled “By User”
Terminal window
# Specific user ID
docker compose logs remnawave-telegram-shop-bot | grep "123456789"


# Recent activity
docker compose logs remnawave-telegram-shop-bot | grep -i "user" | tail -20

Debugging Specific Issues

Section titled “Debugging Specific Issues”

Database Debugging

Section titled “Database Debugging”
Terminal window
# Connect directly
docker compose exec postgres \
  psql -U remnawave -d remnawave


# Check connections
SELECT * FROM pg_stat_activity;


# List tables
\dt


# Check specific table
SELECT COUNT(*) FROM subscriptions;

Payment Debugging

Section titled “Payment Debugging”
Terminal window
# View payment logs
docker compose logs remnawave-telegram-shop-bot | grep -A 10 "payment"


# Check transaction status
docker compose logs remnawave-telegram-shop-bot | grep "transaction\|order"


# API responses
docker compose logs remnawave-telegram-shop-bot | grep "response\|status"

User Action Debugging

Section titled “User Action Debugging”
Terminal window
# User starts bot
docker compose logs remnawave-telegram-shop-bot | grep "user.*start\|/start"


# User makes payment
docker compose logs remnawave-telegram-shop-bot | grep "user.*payment"


# User subscribes
docker compose logs remnawave-telegram-shop-bot | grep "subscription.*created"

Advanced Debugging

Section titled “Advanced Debugging”

Increase Log Level

Section titled “Increase Log Level”

Edit docker-compose.yaml:

environment:
  LOG_LEVEL: DEBUG

Restart:

Terminal window
docker compose up -d

Log to File

Section titled “Log to File”
Terminal window
# Continuous logging
docker compose logs -f remnawave-telegram-shop-bot > /var/log/bot.log 2>&1 &


# Monitor file
tail -f /var/log/bot.log

Log Rotation

Section titled “Log Rotation”
Terminal window
# Create logrotate config
sudo tee /etc/logrotate.d/remnawave-bot > /dev/null <<EOF
/var/log/bot.log {
    daily
    rotate 7
    compress
    delaycompress
    missingok
    notifempty
}
EOF

Save Logs for Analysis

Section titled “Save Logs for Analysis”
Terminal window
# Create log archive
docker compose logs remnawave-telegram-shop-bot > logs_$(date +%Y%m%d).txt
gzip logs_*.txt


# Save to external storage
scp logs_*.txt.gz backup@server:/backups/

Log Analysis Tools

Section titled “Log Analysis Tools”

Search for Errors

Section titled “Search for Errors”
Terminal window
docker compose logs remnawave-telegram-shop-bot | \
  grep -E "ERROR|FATAL|failed" | \
  wc -l  # Count errors

Timeline Analysis

Section titled “Timeline Analysis”
Terminal window
# Group by hour
docker compose logs remnawave-telegram-shop-bot | \
  grep ERROR | \
  awk '{print $1}' | \
  sort | uniq -c

Performance Analysis

Section titled “Performance Analysis”
Terminal window
# Find slow operations
docker compose logs remnawave-telegram-shop-bot | \
  grep "duration\|time" | \
  sort -k3 -nr | head -10
Section titled “Related Logs”

Docker System Logs

Section titled “Docker System Logs”
Terminal window
# Docker daemon logs
docker logs $(docker compose ps -q remnawave-telegram-shop-bot) -f


# Container events
docker events --filter type=container

System Logs

Section titled “System Logs”
Terminal window
# Linux system logs
journalctl -u docker -f


# Check disk space
df -h

Log Security

Section titled “Log Security”

⚠️ Important: Logs may contain:

  • User IDs
  • Transaction details
  • API keys (if misconfigured)
  • Sensitive system info

Best Practices:

  • ✅ Restrict log access
  • ✅ Rotate logs regularly
  • ✅ Archive old logs
  • ✅ Never share logs publicly with keys
  • ❌ Don’t log passwords/tokens

Troubleshooting with Logs

Section titled “Troubleshooting with Logs”

Problem: Bot not responding

Section titled “Problem: Bot not responding”
Terminal window
docker compose logs remnawave-telegram-shop-bot | grep -E "ERROR|failed|starting"

Problem: Payments not working

Section titled “Problem: Payments not working”
Terminal window
docker compose logs remnawave-telegram-shop-bot | grep -i "payment\|yookassa"

Problem: Slow performance

Section titled “Problem: Slow performance”
Terminal window
docker compose logs remnawave-telegram-shop-bot | grep "duration\|slow\|timeout"

Problem: Database issues

Section titled “Problem: Database issues”
Terminal window
docker compose logs postgres | grep -E "ERROR|failed"

When to Collect Logs

Section titled “When to Collect Logs”

Before opening issue/support:

  1. Reproduce the problem
  2. Collect logs: docker compose logs > issue.log
  3. Include last 50-100 lines
  4. Remove any sensitive data
  5. Describe steps taken
  6. Include configuration (no secrets)