Troubleshooting
Troubleshooting guide for S3 Migration Scheduler - common issues, solutions, and debugging tips.
Troubleshooting S3 Migration Scheduler
Having issues with S3 Migration Scheduler? This guide will help you resolve common problems and get back to migrating your data efficiently.
Quick Fixes
Most Common Issues
- Connection Problems
- Verify your AWS credentials are correct
- Check network connectivity to AWS S3
- Ensure proper IAM permissions
- Performance Issues
- Adjust concurrent transfer settings
- Check available bandwidth
- Monitor system resources (CPU, memory)
- Migration Failures
- Review error logs for specific issues
- Verify source and destination bucket permissions
- Check file path and naming conventions
Complete Troubleshooting Guide
For detailed troubleshooting steps, error codes, and advanced debugging techniques, please refer to our comprehensive troubleshooting documentation:
📖 Official Troubleshooting Guide
The complete troubleshooting guide is maintained in our GitHub repository and includes:
- Detailed error code explanations
- Step-by-step debugging procedures
- Performance optimization tips
- Common configuration issues
- Log analysis techniques
Getting Help
If you can’t find a solution in the troubleshooting guide, here are additional resources:
Community Support
- GitHub Issues - Report bugs or request features
- GitHub Discussions - Community Q&A
- Documentation - Complete user guides
Before Reporting an Issue
To help us help you faster, please include:
- Version Information
s3-migration-scheduler --version
- System Information
- Operating system and version
- Available memory and disk space
- Network configuration
- Error Details
- Complete error messages
- Relevant log entries
- Steps to reproduce the issue
- Configuration
- Migration configuration (sanitized)
- AWS region and service endpoints
- Any custom settings
Common Error Codes
Error Code | Description | Quick Fix |
---|---|---|
AUTH_001 |
Invalid AWS credentials | Check AWS access key and secret key |
CONN_002 |
Network connection timeout | Verify internet connection and AWS endpoints |
PERM_003 |
Insufficient permissions | Review IAM policy for required S3 permissions |
RATE_004 |
API rate limit exceeded | Reduce concurrent transfers or add delays |
For complete error code documentation, see the official troubleshooting guide.
Log Files
S3 Migration Scheduler creates detailed logs to help diagnose issues:
Default Log Locations
- Windows:
%APPDATA%\S3MigrationScheduler\logs\
- Linux:
~/.s3-migration-scheduler/logs/
- Docker:
/app/logs/
(inside container)
Log Levels
ERROR
- Critical issues that stop migrationWARN
- Potential problems that don’t stop migrationINFO
- General migration progress informationDEBUG
- Detailed debugging information
Performance Optimization
If you’re experiencing slow migration speeds:
- Increase Concurrent Transfers
- Adjust the
--concurrent
parameter - Monitor system resources
- Adjust the
- Optimize Network Settings
- Use AWS Transfer Acceleration if available
- Consider running closer to AWS regions
- System Resources
- Ensure adequate RAM and CPU
- Use SSD storage for temporary files
For detailed performance tuning, see the complete troubleshooting guide.