Emergency procedures: Difference between revisions

From VoIPmonitor.org
(Create new page for emergency recovery procedures)
 
(Review: použití šablon {{Note}} a {{Warning}} místo prostého textu)
(11 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{DISPLAYTITLE:Emergency Procedures & System Recovery}}
= Diagnosing Database Bottlenecks Using Sensor RRD Charts =


'''This guide covers emergency procedures for recovering your VoIPmonitor system from critical failures, including runaway processes, high CPU usage, and system unresponsiveness.'''
If your VoIPmonitor GUI becomes unresponsive or PHP processes are being terminated by the OOM (Out of Memory) killer, the root cause may be a '''database performance bottleneck''', not a PHP configuration issue.


== Emergency: VoIPmonitor Process Consuming Excessive CPU or System Unresponsive ==
This guide explains how to use the sensor's RRD (Round-Robin Database) charts to identify whether the database server is the limiting factor.


When a VoIPmonitor process consumes excessive CPU (e.g., ~3000% or more) or causes the entire system to become unresponsive, follow these immediate steps:
== Symptoms of Database Bottlenecks affecting the GUI ==


=== Immediate Action: Force-Terminate Runaway Process ===
* GUI becomes extremely slow or unresponsive during peak hours
* PHP processes are killed by the OOM killer on the GUI server
* Dashboard and CDR views take a long time to load
* Alerts and reports fail during high traffic periods
* System appears fine during off-peak hours but degrades during peak usage


If the system is still minimally responsive via SSH or requires out-of-band management (iDRAC, IPMI, console):
{{Note|These symptoms often occur when the GUI server is waiting for database queries to complete, causing PHP processes to pile up and consume excessive memory.}}


;1. Identify the Process ID (PID):
== Understanding Sensor RRD Charts ==
<syntaxhighlight lang="bash">
# Using htop (if available)
htop


# Or using ps
The VoIPmonitor sensor generates performance charts (RRD files) that track system metrics over time. These charts are accessible through the GUI and provide visual indicators of where bottlenecks are occurring.
ps aux | grep voipmonitor
</syntaxhighlight>


Look for the voipmonitor process consuming the most CPU resources. Note down the PID (process ID number).
To access sensor RRD charts:
# Navigate to '''Settings > Sensors''' in the GUI
# Click the graph icon next to the sensor
# Select the time range covering the problematic peak hours


;2. Forcefully terminate the process:
== Diagnostic Flowchart ==
<syntaxhighlight lang="bash">
kill -9 <PID>
</syntaxhighlight>


Replace <PID> with the actual process ID number identified in step 1.
<kroki lang="mermaid">
flowchart TD
    A[GUI Unresponsive / OOM Errors] --> B{Check Sensor RRD Charts}
    B --> C{SQL Cache Growing<br/>During Peak Hours?}
    C -->|No| D[Issue is NOT<br/>database bottleneck]
    C -->|Yes| E[Database Bottleneck<br/>Confirmed]
    E --> F{Identify<br/>Bottleneck Type}
    F --> G{mysqld CPU<br/>near 100%?}
    G -->|Yes| H[CPU Bottleneck]
    H --> I[Add CPU cores<br/>or upgrade CPU]
    G -->|No| J{Buffer pool full?<br/>Swap usage?}
    J -->|Yes| K[Memory Bottleneck]
    K --> L[Add RAM<br/>Tune innodb_buffer_pool_size]
    J -->|No| M{High iowait?<br/>Magnetic disks?}
    M -->|Yes| N[Storage I/O Bottleneck]
    N --> O[Upgrade to SSD/NVMe]


;3. Verify system recovery:
    style A fill:#f9f,stroke:#333
<syntaxhighlight lang="bash">
    style E fill:#ff9,stroke:#333
# Check CPU usage has returned to normal
    style H fill:#f96,stroke:#333
top
    style K fill:#f96,stroke:#333
    style N fill:#f96,stroke:#333
</kroki>


# Check if the process was terminated
== Diagnostic Step 1: Look for Growing SQL Cache ==
ps aux | grep voipmonitor
</syntaxhighlight>


The system should become responsive again immediately after the process is killed. CPU utilization should drop significantly.
The most critical indicator of a database bottleneck is '''growing SQL cache''' or '''SQL cache files''' during peak hours.


=== Optional: Stop and Restart the Service (for persistent issues) ===
{| class="wikitable"
|-
! Metric !! What to Look For !! Indicates
|-
| '''SQL Cache''' || Consistently increasing during peak hours, never decreasing || Database cannot keep up with insert rate
|-
| '''SQL Cache Files''' || Growing over time during peak usage || Database buffer pool too small or storage too slow
|-
| '''CPU Load (mysqld)''' || Near 100% during peak hours || CPU bottleneck on database server
|-
| '''Disk I/O (mysql)''' || High or saturated during peak hours || Storage bottleneck (magnetic disks instead of SSDs)
|}


If the problem persists or the service needs to be cleanly restarted:
If you see SQL cache or SQL cache files growing consistently during peak traffic periods, the database server is the bottleneck.


<syntaxhighlight lang="bash">
== Diagnostic Step 2: Determine the Bottleneck Type ==
# Stop the voipmonitor service
systemctl stop voipmonitor


# Verify no zombie processes remaining
After identifying that the database is the issue, determine which resource is the limiting factor:
killall voipmonitor


# Restart the service
=== CPU Bottleneck ===
systemctl start voipmonitor
* Check database CPU usage during peak hours
* If mysqld is at or near 100% CPU, you need more CPU cores or faster CPUs


# Verify service status
=== Memory Bottleneck ===
systemctl status voipmonitor
* Check if SQL cache grows because buffer pool is too small
</syntaxhighlight>
* Database runs out of RAM for caching, forcing disk reads
* The SQL cache chart shows a pattern of filling up and staying full


'''Caution:''' When using <code>systemd</code> service management, avoid using the deprecated <code>service</code> command as it can cause systemd to lose track of the daemon. Always use <code>systemctl</code> commands or direct process commands like <code>killall</code>.
=== Storage I/O Bottleneck (Most Common) ===
* High disk I/O wait times for mysqld process
* Disk latency (iowait) increases during peak hours
* Database storage on magnetic disks (e.g., 10K SAS) instead of SSD/NVMe
* SQL cache grows because data cannot be written/read fast enough


=== Root Cause Analysis: Why Did the CPU Spike? ===
== Solutions for Database Performance Bottlenecks ==


After recovering the system, investigate the root cause to prevent recurrence. Common causes include:
=== Solution 1: Add More RAM to the Database Server ===


;SIP REGISTER Flood / Spaming Attack
This is often the most effective fix for memory-related bottlenecks.
Massive volumes of SIP REGISTER messages from malicious IPs can overwhelm the VoIPmonitor process.


* '''Detection:''' Check recent alert triggers in the VoIPmonitor GUI > Alerts > Sent Alerts for SIP REGISTER flood alerts
{| class="wikitable"
* '''Immediate mitigation:''' Block attacker IPs at the network edge (SBC, firewall, iptables)
|-
* '''Long-term prevention:''' Configure anti-fraud rules with custom scripts to auto-block, see [[Anti-fraud#SIP REGISTER Flood/Attack|SIP REGISTER Flood Mitigation]]
! Current RAM !! Recommended Upgrade !! Expected Impact
|-
| 32GB || 64GB or 128GB || Significantly reduces cache growth
|-
| 64GB || 128GB or 256GB || Handles much higher peak loads
|-
| 128GB || 256GB || Suitable for large deployments
|}


;Packet Capture Overload (pcapcommand)
After adding RAM, tune <code>innodb_buffer_pool_size</code> in your MySQL configuration:
The <code>pcapcommand</code> feature forks a program for ''every'' call, which can generate up to 500,000 interrupts per second.


* '''Detection:''' Check <code>/etc/voipmonitor.conf</code> for a <code>pcapcommand</code> line
<syntaxhighlight lang="ini">
* '''Immediate fix:''' Comment out or remove the <code>pcapcommand</code> directive and restart the service
# /etc/mysql/my.cnf
* '''Alternative:''' Use the built-in cleaning spool functionality (<code>maxpoolsize</code>, <code>cleanspool</code>) instead
# Set to 50-70% of total RAM on dedicated database server
 
innodb_buffer_pool_size = 128G
;Excessive RTP Processing Threads
</syntaxhighlight>
High concurrent call volumes can overload RTP processing threads.
 
* '''Detection:''' Check performance logs for high <code>tRTP_CPU</code> values (sum of all RTP threads)
* '''Mitigation:'''
  <pre>callslimit = 2000  # Limit max concurrent calls</pre>
 
;Audio Feature Overhead
Silence detection and audio conversion are CPU-intensive operations.
 
* '''Detection:''' Check if <code>silencedetect</code> or <code>saveaudio</code> are enabled
* '''Mitigation:'''
  <pre>
  silencedetect = no
  # saveaudio = wav  # Comment out if not needed
  </pre>


See [[Scaling|Scaling and Performance Tuning]] for detailed performance optimization strategies.
For more tuning guidance, see [[Scaling#Optimizing_Database_Performance_.28MySQL.2FMariaDB.29|Scaling - Database Performance]].


=== Preventive Measures ===
{{Warning|1=Do NOT reduce <code>innodb_buffer_pool_size</code> on the GUI server when the database is the bottleneck. This will make the problem worse.}}


Once the root cause is identified, implement these preventive configurations:
=== Solution 2: Upgrade Database Storage to SSD/NVMe ===


;Monitor CPU Trends:
If your database storage is on magnetic disks (e.g., 10K SATA or SAS), upgrading to SSDs is often the single most effective improvement.
Use [[Collectd_installation|collectd]] or your existing monitoring system to track CPU usage over time and receive alerts before critical thresholds are reached.


;Anti-Fraud Auto-Blocking:
{| class="wikitable"
Configure [[Anti-fraud|Anti-Fraud rules]] with custom scripts to automatically block attacker IPs when a flood is detected. See the [[Anti-fraud|Anti-Fraud documentation]] for PHP script examples using iptables or ipset.
|-
! Current Storage !! Recommended Upgrade !! Expected Speedup
|-
| 10K RPM SATA HDD || NVMe SSD array || 10-50x faster I/O
|-
| 10K RPM SAS HDD || Enterprise SSD (SAS/SATA) || 5-20x faster I/O
|-
| Older SSD || Modern NVMe (PCIe 4.0+) || 2-5x faster I/O
|}


;Network Edge Protection:
For high-traffic deployments, '''NVMe storage is recommended for the database host'''.
Block SIP REGISTER spam and floods at your network edge (SBC, firewall) before traffic reaches VoIPmonitor. This provides better performance and reduces CPU load on the monitoring system.


== Emergency: System Freezes on Every Update Attempt ==
See [[Hardware#Database_Storage|Hardware - Storage Selection]] for detailed recommendations.


If the VoIPmonitor sensor becomes unresponsive or hangs each time you attempt to update it through the Web GUI:
=== Solution 3: Temporary Mitigation - Schedule Alerts/Reports Outside Peak Hours ===


;1. SSH into the sensor host
If you cannot immediately upgrade the database server hardware, temporarily reduce the load by scheduling intensive tasks during off-peak hours.
;2. Execute the following commands to forcefully stop and restart:
<syntaxhighlight lang="bash">
killall voipmonitor
systemctl stop voipmonitor
systemctl start voipmonitor
</syntaxhighlight>


This sequence ensures zombie processes are terminated, systemd is fully stopped, and a clean service restart occurs. Verify the sensor status in the GUI to confirm it is responding correctly.
'''1. Disable or reduce alert frequency''' during peak hours:
* Navigate to '''GUI > Alerts'''
* Temporarily disable high-frequency alerts
* Set alerts to run during off-peak periods (e.g., 2am-4am)


== Emergency: Binary Not Found After Crash ==
'''2. Schedule reports outside peak usage:'''
* Navigate to '''GUI > Reports'''
* Configure scheduled reports for off-peak hours
* Avoid generating reports during the busiest part of the day


If the VoIPmonitor service fails to start after a crash with error "Binary not found" for <code>/usr/local/sbin/voipmonitor</code>:
'''3. Reduce dashboard complexity''' during peak hours:
* Simplify dashboards that query large ranges of data
* Avoid "All time" statistics during peak loads
* Use cached dashboards or static displays when possible


;1. Check for a renamed binary:
=== Solution 4: Consider Component Separation ===
<syntaxhighlight lang="bash">
ls -l /usr/local/sbin/voipmonitor_*
</syntaxhighlight>


The crash recovery process may have renamed the binary with an underscore suffix.
If the database server is a bottleneck and upgrading is not feasible, consider moving to a dedicated database architecture.


;2. If found, rename it back:
In a component separation deployment (see [[Scaling#Scaling_Through_Component_Separation|Scaling - Component Separation]]):
<syntaxhighlight lang="bash">
* '''Host 1:''' Dedicated database server with maximum RAM and SSD/NVMe storage
mv /usr/local/sbin/voipmonitor_ /usr/local/sbin/voipmonitor
* '''Host 2:''' GUI web server
</syntaxhighlight>
* '''Host 3:''' Sensor(s)
 
;3. Restart the service:
<syntaxhighlight lang="bash">
systemctl start voipmonitor
systemctl status voipmonitor
</syntaxhighlight>


Verify the service starts correctly.
This allows you to independently scale the database with more powerful hardware without affecting the GUI.


== Out-of-Band Management Scenarios ==
== Common Pitfalls to Avoid ==


When the system is completely unresponsive and cannot be accessed via SSH:
{| class="wikitable" style="background:#fff3cd; border:1px solid #ffc107;"
|-
! colspan="2" style="background:#ffc107;" | Incorrect Solutions When Database is the Bottleneck
|-
| style="vertical-align: top;" | '''Reducing PHP memory_limit'''
| This does NOT fix the root cause. PHP waits for the database; less memory means processes crash sooner.
|-
| style="vertical-align: top;" | '''Tuning PHP-FPM worker counts'''
| More workers will pile up waiting for slow database queries, consuming even more memory.
|-
| style="vertical-align: top;" | '''Reducing innodb_buffer_pool_size'''
| This makes the database slower, not faster. It causes more disk I/O and longer query times.
|-
| style="vertical-align: top;" | '''Adding RAM to the GUI server'''
| If the bottleneck is the database, adding RAM to the GUI won't help. The database is the limiting factor.
|}


* '''Use your server's out-of-band management system:'''
== Verification Checklist ==
  * Dell iDRAC
  * HP iLO
  * Supermicro IPMI
  * Other vendor-specific BMC/management tools


* '''Actions available via OBM:'''
After implementing a database upgrade to fix the bottleneck:
  * Access virtual console (KVM-over-IP)
  * Send NMI (Non-Maskable Interrupt) for system dump
  * Force power cycle
  * Monitor hardware health


See [[Sniffer_troubleshooting|Sniffer Troubleshooting]] for more diagnostic procedures.
1. Monitor SQL cache charts during the next peak traffic period
2. Check that SQL cache does not grow uncontrollably
3. Verify GUI responsiveness during peak hours
4. Confirm no OOM killer events
5. Check database query latency (slow queries should be minimal)


== Related Documentation ==
== Related Documentation ==


* [[Scaling|Scaling and Performance Tuning Guide]] - For performance optimization
* [[Scaling]] - General performance tuning and scaling guide
* [[Anti-fraud|Anti-Fraud Rules]] - For attack detection and mitigation
* [[Scaling#Optimizing_Database_Performance_.28MySQL.2FMariaDB.29|Optimizing Database Performance]] - MySQL tuning parameters
* [[Sniffer_troubleshooting|Sniffer Troubleshooting]] - For systematic diagnostic procedures
* [[Hardware]] - Hardware sizing recommendations for different deployment sizes
* [[High-Performance_VoIPmonitor_and_MySQL_Setup_Manual|High-Performance Setup]] - For optimizing high-traffic deployments
* [[Scaling#Scaling_Through_Component_Separation|Component Separation]] - Dedicated database architecture
* [[Systemd_for_voipmonitor_service_management|Systemd Service Management]] - For service management best practices


== AI Summary for RAG ==
== AI Summary for RAG ==


'''Summary:''' This article provides emergency procedures for recovering VoIPmonitor from critical failures. It covers steps to force-terminate runaway processes consuming excessive CPU (including kill -9 and systemctl commands), root cause analysis for CPU spikes (SIP REGISTER floods, pcapcommand, RTP threads, audio features), preventive measures (monitoring, anti-fraud auto-blocking, network edge protection), recovery procedures for system freezes during updates and binary issues after crashes, and out-of-band management scenarios.
'''Summary:''' Guide for diagnosing database bottlenecks affecting VoIPmonitor GUI using sensor RRD charts. Symptoms: GUI unresponsive during peak hours, OOM killer terminating PHP processes, slow dashboard/CDR views. KEY DIAGNOSTIC: Check sensor RRD charts (Settings > Sensors > graph icon) for growing SQL cache during peak hours - primary indicator of database bottleneck. Bottleneck types: CPU (mysqld at 100%), Memory (buffer pool too small), Storage I/O (most common - high iowait, magnetic disks). Solutions: (1) Add RAM to database server and tune innodb_buffer_pool_size to 50-70% of RAM; (2) Upgrade storage from HDD to SSD/NVMe (10-50x speedup); (3) Schedule alerts/reports outside peak hours; (4) Component separation with dedicated database server. INCORRECT solutions: Do NOT reduce PHP memory_limit, do NOT tune PHP-FPM workers, do NOT reduce innodb_buffer_pool_size, do NOT add RAM to GUI server instead of database.


'''Keywords:''' emergency recovery, high CPU, system unresponsive, runaway process, kill process, kill -9, systemctl, SIP REGISTER flood, pcapcommand, performance optimization, out-of-band management, iDRAC, iLO, IPMI, crash recovery
'''Keywords:''' database bottleneck, RRD charts, sensor performance, SQL cache, SQL cache files, peak hours, OOM killer, GUI unresponsive, dashboard slow, RAM upgrade, SSD upgrade, NVMe, iowait, innodb_buffer_pool_size, component separation, dedicated database


'''Key Questions:'''
'''Key Questions:'''
* What to do when VoIPmonitor consumes 3000% CPU or system becomes unresponsive?
* How do I diagnose database bottlenecks in VoIPmonitor?
* How to forcefully terminate a runaway VoIPmonitor process?
* What do growing SQL cache files in RRD charts indicate?
* What are common causes of CPU spikes in VoIPmonitor?
* Why is my VoIPmonitor GUI slow during peak hours?
* How to mitigate SIP REGISTER flood attacks causing high CPU?
* How to fix OOM killer terminating PHP processes?
* How to restart VoIPmonitor service after a crash?
* Should I upgrade RAM on GUI server or database server?
* What to do if service binary is not found after crash?
* What storage is recommended for VoIPmonitor database?
* How to prevent VoIPmonitor from freezing during GUI updates?
* How to access sensor RRD charts in VoIPmonitor GUI?
* What tools can help diagnose VoIPmonitor performance issues?
* What are incorrect solutions for database bottlenecks?
* How much RAM should innodb_buffer_pool_size be set to?
* When should I consider component separation for VoIPmonitor?

Revision as of 18:00, 6 January 2026

Diagnosing Database Bottlenecks Using Sensor RRD Charts

If your VoIPmonitor GUI becomes unresponsive or PHP processes are being terminated by the OOM (Out of Memory) killer, the root cause may be a database performance bottleneck, not a PHP configuration issue.

This guide explains how to use the sensor's RRD (Round-Robin Database) charts to identify whether the database server is the limiting factor.

Symptoms of Database Bottlenecks affecting the GUI

  • GUI becomes extremely slow or unresponsive during peak hours
  • PHP processes are killed by the OOM killer on the GUI server
  • Dashboard and CDR views take a long time to load
  • Alerts and reports fail during high traffic periods
  • System appears fine during off-peak hours but degrades during peak usage

ℹ️ Note: These symptoms often occur when the GUI server is waiting for database queries to complete, causing PHP processes to pile up and consume excessive memory.

Understanding Sensor RRD Charts

The VoIPmonitor sensor generates performance charts (RRD files) that track system metrics over time. These charts are accessible through the GUI and provide visual indicators of where bottlenecks are occurring.

To access sensor RRD charts:

  1. Navigate to Settings > Sensors in the GUI
  2. Click the graph icon next to the sensor
  3. Select the time range covering the problematic peak hours

Diagnostic Flowchart

Diagnostic Step 1: Look for Growing SQL Cache

The most critical indicator of a database bottleneck is growing SQL cache or SQL cache files during peak hours.

Metric What to Look For Indicates
SQL Cache Consistently increasing during peak hours, never decreasing Database cannot keep up with insert rate
SQL Cache Files Growing over time during peak usage Database buffer pool too small or storage too slow
CPU Load (mysqld) Near 100% during peak hours CPU bottleneck on database server
Disk I/O (mysql) High or saturated during peak hours Storage bottleneck (magnetic disks instead of SSDs)

If you see SQL cache or SQL cache files growing consistently during peak traffic periods, the database server is the bottleneck.

Diagnostic Step 2: Determine the Bottleneck Type

After identifying that the database is the issue, determine which resource is the limiting factor:

CPU Bottleneck

  • Check database CPU usage during peak hours
  • If mysqld is at or near 100% CPU, you need more CPU cores or faster CPUs

Memory Bottleneck

  • Check if SQL cache grows because buffer pool is too small
  • Database runs out of RAM for caching, forcing disk reads
  • The SQL cache chart shows a pattern of filling up and staying full

Storage I/O Bottleneck (Most Common)

  • High disk I/O wait times for mysqld process
  • Disk latency (iowait) increases during peak hours
  • Database storage on magnetic disks (e.g., 10K SAS) instead of SSD/NVMe
  • SQL cache grows because data cannot be written/read fast enough

Solutions for Database Performance Bottlenecks

Solution 1: Add More RAM to the Database Server

This is often the most effective fix for memory-related bottlenecks.

Current RAM Recommended Upgrade Expected Impact
32GB 64GB or 128GB Significantly reduces cache growth
64GB 128GB or 256GB Handles much higher peak loads
128GB 256GB Suitable for large deployments

After adding RAM, tune innodb_buffer_pool_size in your MySQL configuration: 

# /etc/mysql/my.cnf
# Set to 50-70% of total RAM on dedicated database server
innodb_buffer_pool_size = 128G

For more tuning guidance, see Scaling - Database Performance.

⚠️ Warning: Do NOT reduce innodb_buffer_pool_size on the GUI server when the database is the bottleneck. This will make the problem worse.

Solution 2: Upgrade Database Storage to SSD/NVMe

If your database storage is on magnetic disks (e.g., 10K SATA or SAS), upgrading to SSDs is often the single most effective improvement.

Current Storage Recommended Upgrade Expected Speedup
10K RPM SATA HDD NVMe SSD array 10-50x faster I/O
10K RPM SAS HDD Enterprise SSD (SAS/SATA) 5-20x faster I/O
Older SSD Modern NVMe (PCIe 4.0+) 2-5x faster I/O

For high-traffic deployments, NVMe storage is recommended for the database host.

See Hardware - Storage Selection for detailed recommendations.

Solution 3: Temporary Mitigation - Schedule Alerts/Reports Outside Peak Hours

If you cannot immediately upgrade the database server hardware, temporarily reduce the load by scheduling intensive tasks during off-peak hours.

1. Disable or reduce alert frequency during peak hours:

  • Navigate to GUI > Alerts
  • Temporarily disable high-frequency alerts
  • Set alerts to run during off-peak periods (e.g., 2am-4am)

2. Schedule reports outside peak usage:

  • Navigate to GUI > Reports
  • Configure scheduled reports for off-peak hours
  • Avoid generating reports during the busiest part of the day

3. Reduce dashboard complexity during peak hours:

  • Simplify dashboards that query large ranges of data
  • Avoid "All time" statistics during peak loads
  • Use cached dashboards or static displays when possible

Solution 4: Consider Component Separation

If the database server is a bottleneck and upgrading is not feasible, consider moving to a dedicated database architecture.

In a component separation deployment (see Scaling - Component Separation):

  • Host 1: Dedicated database server with maximum RAM and SSD/NVMe storage
  • Host 2: GUI web server
  • Host 3: Sensor(s)

This allows you to independently scale the database with more powerful hardware without affecting the GUI.

Common Pitfalls to Avoid

Incorrect Solutions When Database is the Bottleneck
Reducing PHP memory_limit This does NOT fix the root cause. PHP waits for the database; less memory means processes crash sooner.
Tuning PHP-FPM worker counts More workers will pile up waiting for slow database queries, consuming even more memory.
Reducing innodb_buffer_pool_size This makes the database slower, not faster. It causes more disk I/O and longer query times.
Adding RAM to the GUI server If the bottleneck is the database, adding RAM to the GUI won't help. The database is the limiting factor.

Verification Checklist

After implementing a database upgrade to fix the bottleneck:

1. Monitor SQL cache charts during the next peak traffic period 2. Check that SQL cache does not grow uncontrollably 3. Verify GUI responsiveness during peak hours 4. Confirm no OOM killer events 5. Check database query latency (slow queries should be minimal)

Related Documentation

AI Summary for RAG

Summary: Guide for diagnosing database bottlenecks affecting VoIPmonitor GUI using sensor RRD charts. Symptoms: GUI unresponsive during peak hours, OOM killer terminating PHP processes, slow dashboard/CDR views. KEY DIAGNOSTIC: Check sensor RRD charts (Settings > Sensors > graph icon) for growing SQL cache during peak hours - primary indicator of database bottleneck. Bottleneck types: CPU (mysqld at 100%), Memory (buffer pool too small), Storage I/O (most common - high iowait, magnetic disks). Solutions: (1) Add RAM to database server and tune innodb_buffer_pool_size to 50-70% of RAM; (2) Upgrade storage from HDD to SSD/NVMe (10-50x speedup); (3) Schedule alerts/reports outside peak hours; (4) Component separation with dedicated database server. INCORRECT solutions: Do NOT reduce PHP memory_limit, do NOT tune PHP-FPM workers, do NOT reduce innodb_buffer_pool_size, do NOT add RAM to GUI server instead of database.

Keywords: database bottleneck, RRD charts, sensor performance, SQL cache, SQL cache files, peak hours, OOM killer, GUI unresponsive, dashboard slow, RAM upgrade, SSD upgrade, NVMe, iowait, innodb_buffer_pool_size, component separation, dedicated database

Key Questions:

  • How do I diagnose database bottlenecks in VoIPmonitor?
  • What do growing SQL cache files in RRD charts indicate?
  • Why is my VoIPmonitor GUI slow during peak hours?
  • How to fix OOM killer terminating PHP processes?
  • Should I upgrade RAM on GUI server or database server?
  • What storage is recommended for VoIPmonitor database?
  • How to access sensor RRD charts in VoIPmonitor GUI?
  • What are incorrect solutions for database bottlenecks?
  • How much RAM should innodb_buffer_pool_size be set to?
  • When should I consider component separation for VoIPmonitor?
Retrieved from "https://www.voipmonitor.org/doc/index.php?title=Emergency_procedures&oldid=9007"