Skip to content

Latest commit

 

History

History
177 lines (150 loc) · 4.1 KB

TROUBLESHOOTING.md

File metadata and controls

177 lines (150 loc) · 4.1 KB

Troubleshooting Guide

Common Issues and Solutions

Twitter Integration

Authentication Issues

Login Failed
Error: Failed to verify Twitter login status

Solution:

  1. Verify credentials in .env
  2. Check for rate limiting (wait 15 minutes)
  3. Clear cookies and retry: 
    rm -rf .cache/twitter-cookies
ACID Challenge Error (Code 399)
Twitter anti-automation check triggered (ACID challenge)

Important Note: The ACID challenge (Error Code 399) is part of Twitter's normal authentication flow and does not indicate a failure. This is expected behavior when using the agent-twitter-client implementation.

Solution:

  1. No immediate action required - the system handles this automatically:

    • Implements exponential backoff retry strategy
    • Default 3 retry attempts with increasing delays
    • Automatic session recovery after successful challenge

  2. If persisting beyond 30 minutes:

    # Check authentication logs
tail -f logs/social.log | grep "ACID"

# Verify retry configuration
grep TWITTER_MAX_RETRIES .env

  3. Adjust retry settings if needed:

    TWITTER_MAX_RETRIES=5        # Increase retry attempts
TWITTER_RETRY_DELAY=10000    # Increase delay between retries
Suspicious Login Notifications
Received "Suspicious login attempt detected" from Twitter

Important Note: This is normal and expected behavior when using the agent-twitter-client implementation. A successful login may trigger Twitter's suspicious login notification system.

Solution:

  1. No action required - this indicates successful authentication

  2. System will proceed with normal operation

  3. Monitor logs for actual authentication status:

    tail -f logs/social.log | grep "authentication"

  4. If concerned, verify session status:

    pnpm run check:twitter-session

Rate Limiting

Error: Too many requests

Solution:

  1. Check current limits: 
    grep "rate limit" logs/social.log
  2. Wait 15 minutes before retrying
  3. Adjust intervals in .env: 
    CONTENT_GENERATION_INTERVAL=300000
MARKET_MONITORING_INTERVAL=60000

Development Issues

Mock Mode

Enable mock mode for development and testing:

TWITTER_MOCK_MODE=true     # Enable Twitter mock mode
MOCK_MARKET_DATA=true      # Enable market data mocking

Use Cases:

  1. Development without Twitter credentials
  2. Testing content generation
  3. CI/CD environments
  4. Rate limit avoidance during testing

Verification:

  1. Check mock mode status:

    grep "Running in mock mode" logs/social.log

  2. Verify mock tweets:

    tail -f logs/mock_tweets.log

  3. Test content generation:

    pnpm test src/services/social/__tests__/

Important Notes:

  • Mock mode simulates all Twitter operations
  • Tweets are logged but not posted
  • Rate limits are not enforced
  • Perfect for development and testing

Database Issues

Redis Connection Failed

Error: NOAUTH Authentication required

Solution:

  1. Verify Redis is running: 
    sudo systemctl status redis-server
  2. Check Redis credentials in .env: 
    REDIS_HOST=127.0.0.1
REDIS_PORT=6379
REDIS_PASSWORD=your_password
  3. Test connection: 
    redis-cli -a your_password ping

PostgreSQL Connection Failed

Error: connect ECONNREFUSED 127.0.0.1:5432

Solution:

  1. Check PostgreSQL service: 
    sudo systemctl status postgresql
  2. Verify database exists: 
    sudo -u postgres psql -c '\l' | grep meme_agent_db
  3. Test connection: 
    psql -h localhost -U meme_agent_user -d meme_agent_db -c '\conninfo'

Debug Commands

# Check service status
sudo systemctl status redis-server postgresql

# View logs
tail -f logs/social.log
tail -f logs/app.log

# Test database connections
redis-cli -a $REDIS_PASSWORD ping
psql -h localhost -U $POSTGRES_USER -d $POSTGRES_DB -c '\conninfo'

# Run specific tests
pnpm test src/services/social/auth/__tests__/twitterAuth.test.ts