cschantz/Linux-Server-Management-Toolkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
233 Commits 2 Branches 0 Tags
723c30357d0fe4488130ff76e9ac1ef7a0d7cbf7
Commit Graph

2 Commits

Author SHA1 Message Date
cschantz 723c30357d Add server-wide memory capacity check (Option 9) - Critical OOM prevention 
NEW FEATURES:
- Menu Option 9: Check Server Memory Capacity (OOM Risk)
- Calculates total memory if ALL PHP-FPM pools hit max_children
- Identifies servers at risk of Out-Of-Memory (OOM) kills
- Provides balanced memory allocation recommendations

TWO NEW ANALYZER FUNCTIONS:

1. calculate_server_memory_capacity()
   - Iterates through all users/PHP-FPM pools
   - Calculates: max_children × avg_memory_per_process
   - Sums total across all pools
   - Compares to total RAM
   - Returns: total_required|total_ram|percentage|status

   Status Levels:
   - HEALTHY:  <60% RAM (safe)
   - CAUTION:  60-75% RAM (watch)
   - WARNING:  75-90% RAM (risky)
   - CRITICAL: >90% RAM (OOM likely!)

2. calculate_balanced_memory_allocation()
   - Analyzes traffic for each user (requests/minute)
   - Calculates proportional memory allocation
   - Reserves 20% of RAM for system (min 2GB)
   - Distributes remaining RAM based on traffic
   - Returns recommendations: REDUCE / INCREASE / OPTIMAL

   Example output:
   USER     CURRENT_MAX  AVG_MB  TRAFFIC_RPM  RECOMMENDED_MAX  REASON
   user1    50          45MB     120          75              INCREASE (traffic demands)
   user2    100         60MB     10           15              REDUCE (prevent OOM)

MENU OPTION 9 FEATURES:
- Shows total RAM vs required memory
- Displays percentage and color-coded status
- Optional per-user breakdown table
- Optional balanced recommendations
- Interactive: ask user what details to show

USE CASE:
Server has 16GB RAM. 10 users each with max_children=50, avg 50MB/process.
Total required: 10 × 50 × 50MB = 25GB
Percentage: 156% of RAM → CRITICAL!
Result: Server WILL run out of memory and kill processes!

This feature addresses user's request:
"calculating max children and memory allocation and then combining all the
 accounts to see if the memory will hit over the memory cap if at capacity"

CRITICAL for preventing OOM kills on shared hosting servers!

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-12-02 20:39:20 -05:00
cschantz 22fa5ad8b0 Phase 3: Add interactive PHP Performance Optimizer (modules/performance/php-optimizer.sh) 
COMPLETE INTERACTIVE MENU SYSTEM:
- 8 main menu options for comprehensive PHP optimization
- Domain selection with PHP version display
- Real-time analysis and recommendations
- Color-coded severity levels (CRITICAL/HIGH/MEDIUM/LOW)
- Safe implementation with cecho() helper

MENU OPTIONS:
1. Analyze Single Domain - Complete PHP analysis report
2. Analyze All Domains - Server-wide analysis with issue detection
3. Quick Health Check - Overall health score based on issues
4. Optimize Domain - Detect issues + show recommendations
5. Optimize Server-Wide - (Placeholder for future)
6. View OPcache Statistics - Hit rates, memory usage, cache efficiency
7. View PHP-FPM Process Stats - Memory usage, process counts, pool config
8. Check Configuration Issues - Grouped by severity with recommendations

FEATURES IMPLEMENTED:
- Domain selection with user/PHP version context
- Comprehensive analysis using lib/php-analyzer.sh
- Issue detection with 4 severity levels
- OPcache statistics with hit rate analysis
- PHP-FPM resource usage tracking
- Optimal max_children calculations
- Health scoring system (0-100)
- Color-coded output for readability

ANALYSIS CAPABILITIES:
- PHP version detection per domain
- Configuration hierarchy display (4 priority levels)
- Effective settings resolution
- PHP-FPM pool configuration parsing
- Resource usage statistics (processes, memory)
- OPcache performance metrics
- Traffic analysis (requests/min, peak concurrent)
- Error analysis (7-day history)

ISSUE DETECTION:
- Config mismatches (post_max_size < upload_max_filesize)
- Security risks (display_errors = On)
- Performance issues (low memory_limit, OPcache disabled)
- Capacity issues (max_children errors)
- Memory leaks (pm.max_requests = 0)
- Resource waste (pm=static on low traffic)

RECOMMENDATIONS ENGINE:
- Calculates optimal pm.max_children based on:
  * System memory (total - reserved)
  * Average memory per process
  * 20% safety buffer
- OPcache optimization suggestions
- Memory limit adjustments
- Process manager mode recommendations

SAFETY FEATURES:
- Read-only analysis (no modifications yet)
- Root user check
- PHP-FPM detection with warnings
- Graceful handling of missing data
- Clear "not yet implemented" placeholders for future features

DISPLAY FEATURES:
- Formatted banners and section separators
- Color-coded severity (RED=critical, YELLOW=high, BLUE=medium, GREEN=low)
- Progress indicators for multi-domain analysis
- Summary statistics and health scores
- Grouped issue display by severity

INTEGRATION:
- Uses lib/php-detector.sh for detection (Phase 1)
- Uses lib/php-analyzer.sh for analysis (Phase 2)
- Uses lib/system-detect.sh for system detection
- Uses lib/user-manager.sh for user/domain management

NOT YET IMPLEMENTED (Future):
- Automatic configuration changes (backup/apply/restore)
- Server-wide optimization in single action
- Backup/restore functionality
- Integration with live-attack-monitor (NOT requested by user)

USAGE:
bash /root/server-toolkit/modules/performance/php-optimizer.sh

All 3 phases complete! PHP optimizer ready for testing and refinement.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
 2025-12-02 20:30:44 -05:00