Mike Swanson
e4392afce9
Investigation and Documentation: - Discovered and documented test database system on AD2 server - Created comprehensive TEST_DATABASE_ARCHITECTURE.md with full system details - Retrieved all key database files from AD2 (import.js, schema.sql, server configs) - Documented data flow: DOS machines → NAS → AD2 → SQLite → Web interface - Verified database health: 1,027,517 records, 1075 MB, dates back to 1990 Database System Architecture: - SQLite database with Node.js/Express.js web server (port 3000) - Automated import via Sync-FromNAS.ps1 (runs every 15 minutes) - 8 log types supported: DSCLOG, 5BLOG, 7BLOG, 8BLOG, PWRLOG, SCTLOG, VASLOG, SHT - FTS5 full-text search, comprehensive indexes for performance - API endpoints: search, stats, export, datasheet generation Troubleshooting Scripts Created: - Database diagnostics: check-db-simple.ps1, test-db-directly.ps1 - Server status checks: check-node-running.ps1, check-db-server.ps1 - Performance analysis: check-db-performance.ps1, check-wal-files.ps1 - API testing: test-api-endpoint.ps1, test-query.js - Import monitoring: check-new-records.ps1 - Database optimization attempts: api-js-optimized.js, api-js-fixed.js - Deployment scripts: deploy-db-optimization.ps1, deploy-db-fix.ps1, restore-original.ps1 Key Findings: - Database file healthy and queryable (verified with test-query.js) - Node.js server not running (port 3000 closed) - root cause of web interface issues - Database last updated 8 days ago (01/13/2026) - automated sync may be broken - Attempted performance optimizations (WAL mode) incompatible with readonly connections - Original api.js restored from backup after optimization conflicts Retrieved Documentation: - QUICKSTART-retrieved.md: Quick start guide for database server - SESSION_NOTES-retrieved.md: Complete session notes from database creation - Sync-FromNAS-retrieved.ps1: Full sync script with database import logic - import-js-retrieved.js: Node.js import script (12,774 bytes) - schema-retrieved.sql: SQLite schema with FTS5 triggers - server-js-retrieved.js: Express.js server configuration - api-js-retrieved.js: API routes and endpoints - package-retrieved.json: Node.js dependencies Action Items Identified: 1. Start Node.js server on AD2 to restore web interface functionality 2. Investigate why automated sync hasn't updated database in 8 days 3. Check Windows Task Scheduler for Sync-FromNAS.ps1 scheduled task 4. Run manual import to catch up on 8 days of test data if needed Technical Details: - Database path: C:\Shares\testdatadb\database\testdata.db - Web interface: http://192.168.0.6:3000 (when running) - Database size: 1075.14 MB (1,127,362,560 bytes) - Total records: 1,027,517 (slight variance from original 1,030,940) - Pass rate: 99.82% (1,029,046 passed, 1,888 failed) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
48 lines
2.1 KiB
PowerShell
48 lines
2.1 KiB
PowerShell
# Check if Node.js server is running on AD2
|
|
Write-Host "[OK] Checking Node.js server status..." -ForegroundColor Green
|
|
|
|
# Test 1: Check port 3000
|
|
Write-Host "`n[TEST 1] Testing port 3000..." -ForegroundColor Cyan
|
|
$portTest = Test-NetConnection -ComputerName 192.168.0.6 -Port 3000 -WarningAction SilentlyContinue -InformationLevel Quiet
|
|
|
|
if ($portTest) {
|
|
Write-Host " [OK] Port 3000 is OPEN" -ForegroundColor Green
|
|
} else {
|
|
Write-Host " [ERROR] Port 3000 is CLOSED" -ForegroundColor Red
|
|
Write-Host " [INFO] Node.js server is not running" -ForegroundColor Yellow
|
|
}
|
|
|
|
# Test 2: Check Node.js processes (via SMB)
|
|
Write-Host "`n[TEST 2] Checking for Node.js processes..." -ForegroundColor Cyan
|
|
$password = ConvertTo-SecureString 'Paper123!@#' -AsPlainText -Force
|
|
$cred = New-Object System.Management.Automation.PSCredential('INTRANET\sysadmin', $password)
|
|
|
|
try {
|
|
$nodeProcs = Invoke-Command -ComputerName 192.168.0.6 -Credential $cred -ScriptBlock {
|
|
Get-Process node -ErrorAction SilentlyContinue | Select-Object Id, ProcessName, @{Name='Memory(MB)';Expression={[math]::Round($_.WorkingSet64/1MB,2)}}, Path
|
|
} -ErrorAction Stop
|
|
|
|
if ($nodeProcs) {
|
|
Write-Host " [OK] Node.js process(es) found:" -ForegroundColor Green
|
|
$nodeProcs | Format-Table -AutoSize
|
|
} else {
|
|
Write-Host " [ERROR] No Node.js process found" -ForegroundColor Red
|
|
}
|
|
} catch {
|
|
Write-Host " [WARNING] WinRM check failed: $($_.Exception.Message)" -ForegroundColor Yellow
|
|
Write-Host " [INFO] Cannot verify via WinRM, but port test is more reliable" -ForegroundColor Cyan
|
|
}
|
|
|
|
Write-Host "`n[SUMMARY]" -ForegroundColor Cyan
|
|
if (!$portTest) {
|
|
Write-Host " Node.js server is NOT running" -ForegroundColor Red
|
|
Write-Host "`n [ACTION] Start the server on AD2:" -ForegroundColor Yellow
|
|
Write-Host " cd C:\Shares\testdatadb" -ForegroundColor Cyan
|
|
Write-Host " node server.js" -ForegroundColor Cyan
|
|
} else {
|
|
Write-Host " Node.js server appears to be running" -ForegroundColor Green
|
|
Write-Host " But API endpoints are not responding - check server logs" -ForegroundColor Yellow
|
|
}
|
|
|
|
Write-Host "`n[OK] Done" -ForegroundColor Green
|