cb47cce074
- Organized 252 files across project - Root directory: 187 → 2 files (98.9% reduction) - Moved configuration guides to docs/04-configuration/ - Moved troubleshooting guides to docs/09-troubleshooting/ - Moved quick start guides to docs/01-getting-started/ - Moved reports to reports/ directory - Archived temporary files - Generated comprehensive reports and documentation - Created maintenance scripts and guides All files organized according to established standards.
94 lines
2.6 KiB
Markdown
94 lines
2.6 KiB
Markdown
# Blockscout Migration Status
|
|
|
|
**Date**: December 23, 2025
|
|
**Container**: VMID 5000 on pve2 (192.168.11.140)
|
|
**Status**: ⏳ **WAITING FOR AUTO-MIGRATIONS**
|
|
|
|
---
|
|
|
|
## Current Status
|
|
|
|
### Database State
|
|
- **Tables Count**: 0 (empty database)
|
|
- **PostgreSQL**: ✅ Running and healthy
|
|
- **Blockscout Container**: ✅ Running
|
|
- **Migrations**: ⏳ Waiting for auto-migration on startup
|
|
|
|
---
|
|
|
|
## Issue Analysis
|
|
|
|
Blockscout should automatically run database migrations when it starts for the first time. However, the database schema is still empty, indicating migrations haven't completed yet.
|
|
|
|
### Possible Reasons:
|
|
1. **First startup takes time**: Blockscout may take 3-5 minutes to complete all migrations
|
|
2. **Migration errors**: Silent failures or errors preventing migrations
|
|
3. **Application startup order**: Background workers may be starting before migrations complete
|
|
|
|
---
|
|
|
|
## Next Steps
|
|
|
|
### Option 1: Wait for Auto-Migration (Recommended)
|
|
Blockscout should automatically migrate on first startup. Wait 3-5 minutes and then check:
|
|
|
|
```bash
|
|
# Check if tables were created
|
|
docker exec blockscout-postgres psql -U blockscout -d blockscout -t -c "SELECT count(*) FROM information_schema.tables WHERE table_schema = 'public';"
|
|
|
|
# Check Blockscout logs for migration status
|
|
docker logs --tail 100 blockscout | grep -i migration
|
|
|
|
# Test API endpoint
|
|
curl http://localhost:4000/api/v2/status
|
|
```
|
|
|
|
### Option 2: Manual Migration (If Auto-Migration Fails)
|
|
If migrations don't run automatically after 5-10 minutes, we may need to run them manually. However, the typical approach is to let Blockscout handle it on startup.
|
|
|
|
---
|
|
|
|
## Configuration
|
|
|
|
The Blockscout container is configured with:
|
|
- `DISABLE_INDEXER=true` - Indexer disabled (reduces startup load)
|
|
- `DISABLE_WEBAPP=false` - Webapp enabled
|
|
- `ECTO_USE_SSL=false` - SSL disabled for database connection
|
|
- `POOL_SIZE=10` - Database connection pool size
|
|
|
|
---
|
|
|
|
## Monitoring Commands
|
|
|
|
```bash
|
|
# Check container status
|
|
docker ps | grep blockscout
|
|
|
|
# Follow logs in real-time
|
|
docker logs -f blockscout
|
|
|
|
# Check database tables
|
|
docker exec blockscout-postgres psql -U blockscout -d blockscout -c "\dt"
|
|
|
|
# Test API
|
|
curl http://localhost:4000/api/v2/status
|
|
|
|
# Test HTTPS
|
|
curl -k https://localhost/health
|
|
curl -k https://explorer.d-bis.org/health
|
|
```
|
|
|
|
---
|
|
|
|
## Expected Outcome
|
|
|
|
Once migrations complete, you should see:
|
|
- Database tables created (100+ tables including `blocks`, `transactions`, `addresses`, `schema_migrations`, etc.)
|
|
- Blockscout API responding with status
|
|
- Web interface accessible at `https://explorer.d-bis.org`
|
|
|
|
---
|
|
|
|
**Note**: First-time startup and migration for Blockscout typically takes 5-10 minutes. Be patient and monitor the logs.
|
|
|