<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/" >

<channel>
	<title>Nagios Library</title>
	<atom:link href="https://library.nagios.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://library.nagios.com</link>
	<description>Complete Nagios monitoring resources and documentation</description>
	<lastBuildDate>Fri, 13 Nov 2026 18:33:48 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://library.nagios.com/wp-content/uploads/2024/11/Nagios-Blue-N.svg</url>
	<title>Nagios Library</title>
	<link>https://library.nagios.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Understanding And Using Device Inventory In Nagios Network Analyzer</title>
		<link>https://library.nagios.com/documentation/using-device-inventory-in-nagios-network-analyzer/</link>
		
		<dc:creator><![CDATA[Shamas Demoret]]></dc:creator>
		<pubDate>Fri, 13 Nov 2026 18:33:47 +0000</pubDate>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Network Monitoring]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71415</guid>

					<description><![CDATA[Overview Device Inventory in Nagios Network Analyzer 2026R2.1+ enables you to cultivate a directory of devices on your network, and optionally assign an Alias to them for easy identification. You can add devices to your inventory manually, or use the results of Nmap scans. There is also an ARP discovery daemon which can be used [&#8230;]]]></description>
										<content:encoded><![CDATA[
<h3 class="wp-block-heading">Overview</h3>



<p class="wp-block-paragraph"><strong>Device Inventory</strong> in Nagios Network Analyzer 2026R2.1+ enables you to cultivate a directory of devices on your network, and optionally assign an Alias to them for easy identification. You can add devices to your inventory manually, or use the results of Nmap scans. There is also an ARP discovery daemon which can be used to discover devices detect network changes, and alert on them.</p>



<p class="wp-block-paragraph">Your inventory can also be cross-referenced when viewing <a href="https://assets.nagios.com/downloads/nagios-network-analyzer/docs/Understanding-Sources-and-Groups-in-NNA-2026.pdf" target="_blank" rel="noopener">Sources</a>, <a href="https://assets.nagios.com/downloads/nagios-network-analyzer/docs/Using-Nmap-with-Nagios-Network-Analyzer-2026.pdf" target="_blank" rel="noopener">Nmap</a>, <a href="https://assets.nagios.com/downloads/nagios-network-analyzer/docs/Using-Suricata-with-Nagios-Network-Analyzer-2026.pdf" target="_blank" rel="noopener">Suricata</a>, and <a href="https://assets.nagios.com/downloads/nagios-network-analyzer/docs/Using-Wireshark-with-Nagios-Network-Analyzer-2026.pdf" target="_blank" rel="noopener">Wireshark</a> data (see the related guides for full details).</p>



<h3 class="wp-block-heading">Device Inventory Documentation</h3>



<p class="wp-block-paragraph">You can find full details on configuring and using Device Inventory here: </p>



<p class="wp-block-paragraph"><a href="https://assets.nagios.com/downloads/nagios-network-analyzer/docs/Using-Device-Inventory-in-Nagios-Network-Analyzer-2026R2.pdf" target="_blank" rel="noopener">Using Device Inventory in Nagios Network Analyzer 2026R2</a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Nagios Log Server Data Sources: What Else Can You Feed It?</title>
		<link>https://library.nagios.com/techtips/nagios-log-server-data-sources/</link>
		
		<dc:creator><![CDATA[Perry Broste]]></dc:creator>
		<pubDate>Fri, 13 Nov 2026 17:13:00 +0000</pubDate>
				<category><![CDATA[Techtips]]></category>
		<category><![CDATA[Log Data]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71424</guid>

					<description><![CDATA[Most people point Nagios Log Server at Windows Event Logs and Linux syslog and move on, but Log Server data sources can include almost anything that produces text. So it’s fair to ask: What else can you feed it? Short answer: anything you can get flowing into an input, whether it&#8217;s a standard log source [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Most people point Nagios Log Server at Windows Event Logs and Linux syslog and move on, but Log Server data sources can include almost anything that produces text. So it’s fair to ask: What else can you feed it? Short answer: anything you can get flowing into an input, whether it&#8217;s a standard log source or some creatively repurposed feed.&nbsp;</p>



<h2 class="wp-block-heading"><strong>Options for Incoming Log Server Data Sources</strong>&nbsp;</h2>



<h3 class="wp-block-heading"><strong>Event Logs</strong>&nbsp;</h3>



<p class="wp-block-paragraph">Start with the obvious: Windows Event Logs (via NXLog), security events, and application event streams. These are the bread and butter of correlation and compliance, and they are the easiest win for alerting on specific event IDs. You can find more information in the Admin Guide:</p>



<p class="wp-block-paragraph"><a href="https://assets.nagios.com/downloads/nagios-log-server/guides/administrator/generaluse.php#windowslogs" target="_blank" rel="noreferrer noopener">Sending Windows Logs To Nagios Log Server&nbsp;</a></p>



<h3 class="wp-block-heading"><strong>System Logs</strong>&nbsp;</h3>



<p class="wp-block-paragraph">Linux/UNIX syslog, network device logs from switches and firewalls, and OS-level messages. Pointing the rsyslog daemon at the Log Server TCP/UDP input is a one-line config change on the sending host.&nbsp;This section of the Admin Guide shows how to monitor a new log source:</p>



<p class="wp-block-paragraph"><a href="https://assets.nagios.com/downloads/nagios-log-server/guides/administrator/generaluse.php#source" target="_blank" rel="noreferrer noopener">Monitoring A New Log Source</a></p>



<h3 class="wp-block-heading"><strong>Get Creative With Custom Feeds</strong>&nbsp;</h3>



<p class="wp-block-paragraph">This is where thinking outside of the box comes in handy. Log Server data sources don’t have to be logs at all. You can use Log Server as a general-purpose event pipeline. Since Log Server indexes and stores any text that comes in, you can just script a small poller to pull RSS, HTTP, or JSON feeds and push them in as regular log events.</p>



<h4 class="wp-block-heading">Install Logstash RSS Plugin</h4>



<p class="wp-block-paragraph">Before adding an RSS feed, install the Logstash RSS input plugin from shell:</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>sudo /usr/local/nagioslogserver/logstash/bin/logstash-plugin install logstash-input-rss logstash-filter-xml</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">sudo /usr/local/nagioslogserver/logstash/bin/logstash-plugin install logstash-input-rss logstash-filter-xml</span></span></code></pre></div>



<h4 class="wp-block-heading">Configure Input</h4>



<p class="wp-block-paragraph">Next, log in to your Log Server and go to <strong>Admin &gt; Logstash Configuration &gt; Global Config</strong>, click the <strong>Add Input</strong> button, and add a new input with the feed URL and polling interval. Click <strong>Verify</strong> then <strong>Save</strong>.</p>



<p class="wp-block-paragraph">For detailed steps on configuring inputs, see <a href="https://library.nagios.com/docs/nagios-log-server/configuration/Nagios-Log-Server-Configuring-Inputs" target="_blank" rel="noreferrer noopener">Nagios Log Server Configuring Inputs</a>.</p>



<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="1024" height="704" src="https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-09_56_11-Instance-Configuration-·-Nagios-Log-Server-—-Mozilla-Firefox_input-e1794513256347-1024x704.png" alt="Nagios Log Server Global Config Inputs tab showing a custom RSS input that pulls a weather news feed" class="wp-image-71470" title="Nagios Log Server Data Sources: What Else Can You Feed It? 1" srcset="https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-09_56_11-Instance-Configuration-·-Nagios-Log-Server-—-Mozilla-Firefox_input-e1794513256347-1024x704.png 1024w, https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-09_56_11-Instance-Configuration-·-Nagios-Log-Server-—-Mozilla-Firefox_input-e1794513256347-300x206.png 300w, https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-09_56_11-Instance-Configuration-·-Nagios-Log-Server-—-Mozilla-Firefox_input-e1794513256347-768x528.png 768w, https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-09_56_11-Instance-Configuration-·-Nagios-Log-Server-—-Mozilla-Firefox_input-e1794513256347.png 1052w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Adding an RSS input to pull a national weather news feed.</figcaption></figure>



<p class="wp-block-paragraph">Logstash Input:</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>rss {
    id => "noaa-weather-obs"
    url => "https://forecast.weather.gov/xml/current_obs/KSTP.rss"
    interval => 200
    tags => &#91;"noaa", "weather", "data"&#93;
  }</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">rss {</span></span>
<span class="line"><span style="color: #D4D4D4">    id =&gt; &quot;noaa-weather-obs&quot;</span></span>
<span class="line"><span style="color: #D4D4D4">    url =&gt; &quot;https://forecast.weather.gov/xml/current_obs/KSTP.rss&quot;</span></span>
<span class="line"><span style="color: #D4D4D4">    interval =&gt; 200</span></span>
<span class="line"><span style="color: #D4D4D4">    tags =&gt; &#91;&quot;noaa&quot;, &quot;weather&quot;, &quot;data&quot;&#93;</span></span>
<span class="line"><span style="color: #D4D4D4">  }</span></span></code></pre></div>



<p class="wp-block-paragraph"><code>interval</code> sets how often, in seconds, Log Server checks the feed. <code>tags</code> labels the events so you can filter and search for them.</p>



<h4 class="wp-block-heading">Configure Filter</h4>



<p class="wp-block-paragraph">Next, set up a filter to parse the log data and turn it into something structured and queryable.</p>



<p class="wp-block-paragraph">For detailed steps on configuring filters, see <a href="https://library.nagios.com/docs/nagios-log-server/configuration/Nagios-Log-Server-Configuring-Input-Filters" target="_blank" rel="noreferrer noopener">Nagios Log Server Configuring Input Filters</a>.</p>



<figure class="wp-block-image size-full"><img decoding="async" width="972" height="715" src="https://library.nagios.com/wp-content/uploads/2026/11/CustomWeatherFilter.png" alt="Nagios Log Server Global Config Filters tab showing a custom weather filter" class="wp-image-71493" title="Nagios Log Server Data Sources: What Else Can You Feed It? 2" srcset="https://library.nagios.com/wp-content/uploads/2026/11/CustomWeatherFilter.png 972w, https://library.nagios.com/wp-content/uploads/2026/11/CustomWeatherFilter-300x221.png 300w, https://library.nagios.com/wp-content/uploads/2026/11/CustomWeatherFilter-768x565.png 768w" sizes="(max-width: 972px) 100vw, 972px" /><figcaption class="wp-element-caption">A filter that cleans up the feed data and extracts condition, temperature, and location fields.</figcaption></figure>



<p class="wp-block-paragraph">Logstash Filter:</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>mutate {
    gsub => [
      "message",
      '&lt;img&#91;^>&#93;*>.*?&lt;br\s*/?>\s*\n?',
      ''
    ]
  }

  grok {
    match => {
    "title" => "%{WORD:condition} and %{NUMBER:temperature} %{WORD:unit} at %{GREEDYDATA:location}"
  }
  }</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">mutate {</span></span>
<span class="line"><span style="color: #D4D4D4">    gsub =&gt; [</span></span>
<span class="line"><span style="color: #D4D4D4">      &quot;message&quot;,</span></span>
<span class="line"><span style="color: #D4D4D4">      &#39;&lt;img&#91;^&gt;&#93;*&gt;.*?&lt;br\s*/?&gt;\s*\n?&#39;,</span></span>
<span class="line"><span style="color: #D4D4D4">      &#39;&#39;</span></span>
<span class="line"><span style="color: #D4D4D4">    ]</span></span>
<span class="line"><span style="color: #D4D4D4">  }</span></span>
<span class="line"><span style="color: #D4D4D4"></span></span>
<span class="line"><span style="color: #D4D4D4">  grok {</span></span>
<span class="line"><span style="color: #D4D4D4">    match =&gt; {</span></span>
<span class="line"><span style="color: #D4D4D4">    &quot;title&quot; =&gt; &quot;%{WORD:condition} and %{NUMBER:temperature} %{WORD:unit} at %{GREEDYDATA:location}&quot;</span></span>
<span class="line"><span style="color: #D4D4D4">  }</span></span>
<span class="line"><span style="color: #D4D4D4">  }</span></span></code></pre></div>



<h4 class="wp-block-heading">Example Dashboard Results</h4>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="217" src="https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-10_11_32-Dashboard-·-Nagios-Log-Server-—-Mozilla-Firefox-e1794514534510-1024x217.png" alt="Nagios Log Server All Events list showing weather details from an RSS feed" class="wp-image-71472" title="Nagios Log Server Data Sources: What Else Can You Feed It? 3" srcset="https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-10_11_32-Dashboard-·-Nagios-Log-Server-—-Mozilla-Firefox-e1794514534510-1024x217.png 1024w, https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-10_11_32-Dashboard-·-Nagios-Log-Server-—-Mozilla-Firefox-e1794514534510-300x63.png 300w, https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-10_11_32-Dashboard-·-Nagios-Log-Server-—-Mozilla-Firefox-e1794514534510-768x162.png 768w, https://library.nagios.com/wp-content/uploads/2026/11/2026-11-12-10_11_32-Dashboard-·-Nagios-Log-Server-—-Mozilla-Firefox-e1794514534510.png 1527w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Nagios Log Server Results: All Events list showing weather details from an RSS feed</figcaption></figure>



<h2 class="wp-block-heading">Ideas to Poll and Why&nbsp;</h2>



<div class="wp-block-group is-layout-constrained wp-block-group-is-layout-constrained">
<ul class="wp-block-list">
<li><strong>Weather:</strong> Ingest NOAA or a local weather API on a schedule; alert when a storm cell or extreme temperature hits your data center ZIP code so the network operations center (NOC) is pre-warned before a power event.</li>



<li><strong>Sports</strong>: Pipe your team&#8217;s game feed into Log Server and build a dashboard that pings you on scores. Sounds silly, but it&#8217;s a great way to show a stakeholder that custom queries and dashboards actually work — without having to walk them through a dry infra demo.</li>



<li><strong>Tech</strong>: Pull a tech news RSS feed into the same index as your infra logs. Then when something breaks, you can search back and see what else was going on at the time, like a service outage or a known CVE that lines up with the incident window.</li>



<li><strong>Internal company data:</strong> Send company channel chats, Git bug reports, and support cases into Logstash so they&#8217;re searchable and can trigger alerts.&nbsp;Before indexing internal data, check with your security and compliance teams, and limit access to those indices to the users who need it.</li>



<li><strong>Alien sightings</strong>:&nbsp;The unusual one that makes the point: add a UFO-reporting RSS feed (e.g., a public sighting feed) to your Log Server data sources and you now have a fully indexed, queryable, alertable &#8220;extraterrestrial event&#8221; stream that can even be displayed on a world map. If Nagios Log Server can handle this type of data, it can handle your next unusual data source.</li>
</ul>
</div>



<h2 class="wp-block-heading"><strong>Conclusion</strong></h2>



<p class="wp-block-paragraph">Your Log Server data sources don’t have to stop at syslog. Nagios Log Server is a general-purpose ingestion and indexing engine, so anything with a text representation, such as structured logs, JSON, or RSS and Atom feeds, can become a queryable, alertable, archived stream. Those creative feeds aren’t a gimmick; they prove the input layer is genuinely open. Found an unusual data source that works? Share it with the Nagios Community on <a href="https://www.reddit.com/r/nagios/" target="_blank" rel="noreferrer noopener">r/nagios</a>, or tag us on <a href="https://www.linkedin.com/company/nagios-enterprises-llc" target="_blank" rel="noreferrer noopener">LinkedIn</a> or <a href="https://www.facebook.com/NagiosInc" target="_blank" rel="noreferrer noopener">Facebook</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Virtual Appliance Kernel Debt: How to Track Running Kernels</title>
		<link>https://library.nagios.com/industry-insights/virtual-appliance-kernel-debt-how-to-track-running-kernels/</link>
		
		<dc:creator><![CDATA[Sam Napier]]></dc:creator>
		<pubDate>Thu, 12 Nov 2026 21:16:10 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[VMware]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71335</guid>

					<description><![CDATA[An OVA (Open Virtualization Format Archive) is not only an application installer. It is a snapshot of a guest operating system, including the Linux kernel and every module that kernel can load. When a virtual appliance image remains in service for years, its guest-kernel security debt remains in service too—and most operations teams cannot immediately [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">An OVA (Open Virtualization Format Archive) is not only an application installer. It is a snapshot of a guest operating system, including the Linux kernel and every module that kernel can load. When a virtual appliance image remains in service for years, its guest-kernel security debt remains in service too—and most operations teams cannot immediately report which kernel versions or drivers are running across the appliances they have already deployed.</p>



<p class="wp-block-paragraph">That blind spot becomes acute whenever a kernel driver vulnerability is disclosed before a fix or affected-version range is available. The current example is ZDI-CAN-34068, a local privilege-escalation report in the Linux kernel&#8217;s <code>vmwgfx</code> driver that reached public mailing lists without an accompanying patch, CVE assignment, or affected-version list. Whether a patch is pending or already shipping upstream, the operational problem is the same: replacing a downloadable OVA does not update appliances already running in the field, and patching the hypervisor does not touch the guest kernel inside them.</p>



<h2 class="wp-block-heading">ZDI-CAN-34068 as the Current Example—and Why <code>vmwgfx</code> Is a Recurring Surface</h2>



<p class="wp-block-paragraph">On October 21, 2026, the Zero Day Initiative sent a report to the public Linux kernel mailing list titled “Linux Kernel vmwgfx Dirty Tracking Out-Of-Bounds Write Local Privilege Escalation Vulnerability.” The report is tracked as ZDI-CAN-34068. Greg Kroah-Hartman replied on October 22 that the report had reached public lists without a patch. ZDI&#8217;s upcoming-advisory page lists Linux as the vendor, CVSS 8.8, a report date of October 21, 2026, and a disclosure deadline of February 18, 2027.</p>



<p class="wp-block-paragraph">Contemporaneous reporting described the disclosure as one of several vulnerability reports posted before a mainline fix was available. TuxCare&#8217;s status table identifies <code>vmwgfx</code> and local privilege escalation, labels the entry “title only,” and states that no KernelCare action is planned until technical details exist.</p>



<p class="wp-block-paragraph">As of October 22, 2026, the public record supports these statements:</p>



<ul class="wp-block-list">
<li>The reported vulnerability is associated with the Linux kernel&#8217;s <code>vmwgfx</code> component.</li>



<li>Its published title describes dirty tracking, an out-of-bounds write, and local privilege escalation.</li>



<li>No upstream patch accompanied the public mailing-list report.</li>



<li>No affected-version range has been published.</li>



<li>No CVE tied to ZDI-CAN-34068 was found in current public search results.</li>
</ul>



<p class="wp-block-paragraph">The record does <strong>not</strong> support claims about a triggering operation, vulnerable data structure, reliable workaround, indicators of compromise, or which appliance releases are affected. Those questions remain open until maintainers or distribution vendors publish authoritative details.</p>



<p class="wp-block-paragraph">Even after ZDI-CAN-34068 receives an upstream fix, <code>vmwgfx</code> will remain a relevant case study for virtual appliance hygiene. Earlier disclosures in the same driver show that virtual graphics modules in Linux guests require routine kernel lifecycle management:</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Identifier</th><th>Reported area in <code>vmwgfx</code></th><th>Impact class</th><th>Operational takeaway</th></tr></thead><tbody><tr><td><strong>CVE-2022-36280</strong></td><td>Cursor snooper handling</td><td>Out-of-bounds write / local privilege escalation</td><td>In-guest driver flaws persist in older appliance kernels until the guest OS is patched</td></tr><tr><td><strong>ZDI-26-232 / CVE-2025-40277</strong></td><td><code>vmw_cmd_check</code> command validation</td><td>Local privilege escalation</td><td>Hypervisor updates do not remediate command-checking defects inside the guest kernel module</td></tr><tr><td><strong>CVE-2026-80700</strong></td><td><code>vmw_external_bo_copy</code> bounds checking</td><td>Out-of-bounds access</td><td>Requires verifying the exact running guest kernel package, not just the appliance version</td></tr><tr><td><strong>ZDI-CAN-34068</strong></td><td>Dirty tracking (title-only disclosure)</td><td>Out-of-bounds write / local privilege escalation (CVSS 8.8)</td><td>Demonstrates why operators need kernel and module inventory before affected versions are named</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">ZDI-CAN-34068 must not be conflated with those earlier flaws. Their mechanics do not explain this report, and their fixes do not remediate it. Together, however, they show that an in-guest virtual hardware driver is a recurring kernel patch surface.</p>



<p class="wp-block-paragraph">Sources: <a href="https://www.zerodayinitiative.com/advisories/upcoming/" target="_blank" rel="noopener">ZDI upcoming-advisory record</a>, <a href="https://lore.landau.one/lkml/2026102254-protector-seventy-6454@gregkh/T/" target="_blank" rel="noopener">Linux kernel mailing-list thread</a>, <a href="https://www.phoronix.com/news/LKML-New-Trend-Vulnerabilities" target="_blank" rel="noopener">Phoronix reporting</a>, and <a href="https://tuxcare.com/blog/zdi-ksmbd-bugs-cve/" target="_blank" rel="noopener">TuxCare status summary</a>.</p>



<h2 class="wp-block-heading"><strong>The Patch Belongs to the Guest Kernel, Not the Hypervisor</strong></h2>



<p class="wp-block-paragraph"><code>vmwgfx</code> is the Linux Direct Rendering Manager (DRM) driver for VMware&#8217;s virtual GPU. In a virtual appliance deployment, it is part of the Linux kernel running inside the guest virtual machine (VM) created from the OVA. ESXi or another hypervisor hosts that guest, but does not replace the guest&#8217;s kernel modules.</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>flowchart TB

  hypervisor&#91;Hypervisor&#93;

  guest&#91;Guest VM&#93;

  kernel&#91;Guest Linux kernel&#93;

  vmwgfx&#91;vmwgfx module&#93;

  flaw&#91;Driver vulnerability&#93;

  hypervisor --> guest

  guest --> kernel

  kernel --> vmwgfx

  vmwgfx --> flaw</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #C586C0">flowchart</span><span style="color: #D4D4D4"> </span><span style="color: #DCDCAA">TB</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">hypervisor</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Hypervisor</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">guest</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Guest VM</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">kernel</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Guest Linux kernel</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">vmwgfx</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">vmwgfx module</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">flaw</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Driver vulnerability</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">hypervisor </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">guest</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">guest </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">kernel</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">kernel </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">vmwgfx</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">vmwgfx </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">flaw</span></span></code></pre></div>



<p class="wp-block-paragraph">The remediation unit is therefore the guest kernel. Patching the hypervisor is necessary infrastructure maintenance, but it does not update a vulnerable guest kernel and should not be recorded as remediation for an in-guest driver flaw.</p>



<p class="wp-block-paragraph">Every published OVA should have a build manifest that names its kernel version, and vendors should record whether <code>vmwgfx</code> is present and expected to load. Without that record, neither a vendor nor an operator can quickly determine whether an upstream fix has reached a given appliance.</p>



<h2 class="wp-block-heading"><strong>Why Historical Appliance Images Preserve Guest-Kernel Debt</strong></h2>



<p class="wp-block-paragraph">When a vendor builds an OVA, the build freezes an application and operating-system stack into a single image. A download portal or image library distributes that file, and operators deploy running virtual machines from it. Replacing the download file later does not touch appliances that were already deployed.</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>flowchart LR

  build&#91;Appliance build&#93; --> ova&#91;Published OVA&#93;

  ova --> portal&#91;Download portal or template library&#93;

  portal --> deployed&#91;Deployed appliance in the field&#93;

  build --> replacement&#91;Replacement OVA with patched kernel&#93;

  replacement --> portal

  deployed -->|"In-place kernel update or migration"| replacement</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #C586C0">flowchart</span><span style="color: #D4D4D4"> </span><span style="color: #DCDCAA">LR</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">build</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Appliance build</span><span style="color: #C586C0">&#93;</span><span style="color: #D4D4D4"> </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">ova</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Published OVA</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">ova </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">portal</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Download portal or template library</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">portal </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">deployed</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Deployed appliance in the field</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">build </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">replacement</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Replacement OVA with patched kernel</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">replacement </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">portal</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">deployed </span><span style="color: #C586C0">--&gt;|</span><span style="color: #CE9178">&quot;In-place kernel update or migration&quot;</span><span style="color: #C586C0">|</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">replacement</span></span></code></pre></div>



<p class="wp-block-paragraph">This lifecycle creates a gap across almost every long-lived Linux appliance:</p>



<ul class="wp-block-list">
<li>Updating the file on a download page protects only future deployments.</li>



<li>Publishing a replacement OVA gives operators a clean image for new builds or migrations.</li>



<li>Appliances already running in the field still require an in-place kernel update (plus a reboot into the updated kernel) or migration to the replacement image.</li>



<li>A newer OVA is only a security fix once its guest kernel is verified to contain the upstream or distribution patch.</li>
</ul>



<p class="wp-block-paragraph">Image owners and infrastructure teams need to trace which build produced each OVA, where older images remain cached as internal templates, how many deployed instances exist in the field, and whether those instances can consume standard package updates.</p>



<h2 class="wp-block-heading"><strong>Compensating Controls Must Carry an Uncertainty Label</strong></h2>



<p class="wp-block-paragraph">Because the published impact of ZDI-CAN-34068 is local privilege escalation, the threat model starts with code already executing as a local user or service account inside the guest. A guest DRM device node is worth inspecting because DRM nodes normally mediate userspace access to the graphics subsystem, though the public record does not establish that a specific node or operation is required for this vulnerability.</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>flowchart LR

  workload&#91;Appliance workload&#93; --> localProcess&#91;Local user or service process&#93;

  localProcess --> drmNode&#91;DRM device node&#93;

  drmNode --> vmwgfx&#91;vmwgfx module&#93;

  vmwgfx --> kernelPrivileges&#91;Guest kernel privileges&#93;</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #C586C0">flowchart</span><span style="color: #D4D4D4"> </span><span style="color: #DCDCAA">LR</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">workload</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Appliance workload</span><span style="color: #C586C0">&#93;</span><span style="color: #D4D4D4"> </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">localProcess</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Local user or service process</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">localProcess </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">drmNode</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">DRM device node</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">drmNode </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">vmwgfx</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">vmwgfx module</span><span style="color: #C586C0">&#93;</span></span>
<span class="line"></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">vmwgfx </span><span style="color: #C586C0">--&gt;</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">kernelPrivileges</span><span style="color: #C586C0">&#91;</span><span style="color: #CE9178">Guest kernel privileges</span><span style="color: #C586C0">&#93;</span></span></code></pre></div>



<p class="wp-block-paragraph">This diagram represents a general reachability boundary, not a confirmed trigger path.</p>



<p class="wp-block-paragraph">Two precautions can reduce general exposure to <code>vmwgfx</code>:</p>



<ul class="wp-block-list">
<li>Restrict access to <code>/dev/dri/...</code> DRM device nodes to accounts that require virtual-GPU functionality.</li>



<li>Avoid loading <code>vmwgfx</code> when the appliance is verified not to require VMware SVGA acceleration.</li>
</ul>



<p class="wp-block-paragraph">Neither is a confirmed fix for ZDI-CAN-34068. The public record does not establish the exact reachability conditions, and disabling a graphics driver can affect virtual consoles, display management, support workflows, or vendor supportability. Test any module or permission change in a non-production clone, document the change, and keep a recovery path.</p>



<p class="wp-block-paragraph">Similarly, restricting shell access and removing unused local accounts shrinks the set of local processes that could attempt privilege escalation, while keeping management interfaces off untrusted networks reduces the chance that an application compromise yields local code execution inside the guest.</p>



<h2 class="wp-block-heading"><strong>What Operators and Vendors Should Do Before and After a Fix Lands</strong></h2>



<p class="wp-block-paragraph">Reducing virtual appliance kernel debt does not wait on a proof of concept.</p>



<h3 class="wp-block-heading"><strong>Before an Authoritative Patch or Version Range Exists</strong></h3>



<ol class="wp-block-list">
<li><strong>Inventory every deployed appliance.</strong> Record the appliance product and release, source OVA filename or template, <code>uname -r</code> output, distribution release, update channel, and whether a reboot is pending.</li>



<li><strong>Record driver state.</strong> Check whether <code>vmwgfx</code> is installed and currently loaded (<code>lsmod</code>, <code>modinfo vmwgfx</code>). Record its module filename, <code>vermagic</code>, and owning distribution package so the inventory can be matched against future advisories.</li>



<li><strong>Audit local execution paths and DRM permissions.</strong> Review interactive accounts, support credentials, service accounts, scheduled jobs, and plugins that execute inside the guest, and verify which users or groups can open <code>/dev/dri/card*</code> or <code>/dev/dri/renderD*</code>.</li>



<li><strong>Confirm update and reboot mechanics.</strong> Verify whether deployed appliances can take an in-place distribution kernel update or whether they must be migrated to a newly issued OVA.</li>
</ol>



<h3 class="wp-block-heading"><strong>When a Fix and Advisory Are Published</strong></h3>



<ol class="wp-block-list">
<li><strong>Map advisories to exact kernel packages.</strong> Compare the upstream or distribution advisory against the recorded kernel version of every supported OVA and deployed instance.</li>



<li><strong>Deliver both remediation paths.</strong> Vendors should publish an updated OVA through their normal build pipeline (naming the fixed kernel package in release notes), retire unpatched downloads, and provide an authenticated in-place update path where supported.</li>



<li><strong>Verify the running kernel after reboot.</strong> Operators should confirm that <code>uname -r</code> on each deployed appliance matches the fixed package after reboot, rather than checking only that an RPM or DEB package was installed on disk.</li>
</ol>



<h2 class="wp-block-heading"><strong>Tracking Appliance Kernel Versions and Drift With Monitoring Tooling</strong></h2>



<p class="wp-block-paragraph">The reason virtual appliance kernel debt accumulates silently is that appliance OS layers are rarely monitored with the same rigor as standard Linux servers. Once an OVA is imported, teams monitor the application service or web port, while the underlying guest kernel ages out of sight.</p>



<p class="wp-block-paragraph">Closing that gap requires continuous operational visibility across every deployed appliance. Regardless of which virtual appliances an organization runs, operators should track four data points across their fleet:</p>



<ul class="wp-block-list">
<li><strong>Running kernel release (<code>uname -r</code>):</strong> What kernel is active in memory right now on each appliance, and where does it diverge from the organization&#8217;s approved baseline?</li>



<li><strong>Installed versus running kernel drift:</strong> Has an appliance installed a security update on disk without rebooting into the new kernel?</li>



<li><strong>Kernel module state:</strong> Is a target module such as <code>vmwgfx</code> loaded (<code>lsmod</code>) on appliances that do not require virtual graphics acceleration?</li>



<li><strong>Fleet-wide version skew:</strong> Which older appliance instances are still running kernel generations from historical OVA templates after newer deployments have moved ahead?</li>
</ul>



<p class="wp-block-paragraph">Infrastructure monitoring tooling makes this inventory continuous rather than a one-off spreadsheet exercise during an advisory scramble. In Nagios, for example, operators can run scheduled agent-based or SSH checks across virtual appliances to collect <code>uname -r</code>, compare the running kernel against the latest installed kernel package to flag pending reboots, check whether specific kernel modules are loaded, and alert when an appliance drifts behind an expected kernel baseline. When an advisory such as ZDI-CAN-34068 is published—or when its eventual patch arrives—having live kernel and module outputs already collected in the monitoring system lets teams identify exposed appliances immediately and verify post-reboot remediation from the same dashboard.</p>



<h2 class="wp-block-heading"><strong>What This Article Intentionally Does Not Provide</strong></h2>



<p class="wp-block-paragraph">This article does not provide exploit theory, ioctl sequences, dirty-tracking trigger conditions, memory-layout analysis, proof-of-concept code, or a walkthrough for compromising an appliance. The public title of ZDI-CAN-34068 is not enough to infer those details responsibly.</p>



<p class="wp-block-paragraph">The operational conclusion does not depend on them: <code>vmwgfx</code> lives in the guest kernel; historical OVAs preserve the guest kernels they shipped with; replacing a download link or patching a hypervisor does not update appliances already running in the field; and continuous kernel inventory is what turns an opaque advisory into a manageable maintenance task.</p>



<h2 class="wp-block-heading"><strong>Glossary</strong></h2>



<ul class="wp-block-list">
<li><strong>OVA (Open Virtualization Format Archive):</strong> A single-file distribution archive (<code>.ova</code>) of an Open Virtualization Format package containing an OVF descriptor, virtual disks, and related metadata used to deploy a preconfigured virtual machine. Source: <a href="https://www.dmtf.org/sites/default/files/standards/documents/DSP0243_2.1.1.pdf" target="_blank" rel="noopener">DMTF, <em>*Open Virtualization Format Specification*</em> (DSP0243 §5)</a>.</li>



<li><strong>DRM node (Direct Rendering Manager device node):</strong> A character-device interface in Linux, such as <code>/dev/dri/card*</code> or <code>/dev/dri/renderD*</code>, through which user-space processes interact with the kernel&#8217;s Direct Rendering Manager subsystem and underlying GPU or virtual-GPU drivers. Source: <a href="https://docs.kernel.org/gpu/drm-uapi.html" target="_blank" rel="noopener">Linux Kernel Documentation, <em>*Userland interfaces (DRM)*</em></a>.</li>



<li><strong>Dirty tracking:</strong> A memory- and graphics-management mechanism used by kernel drivers (including virtual graphics drivers such as <code>vmwgfx</code>) to track which memory pages, buffer objects, or framebuffer regions have been modified so only updated regions are synchronized or rendered. Source: <a href="https://docs.kernel.org/gpu/drm-mm.html" target="_blank" rel="noopener">Linux Kernel Documentation, <em>*DRM Memory Management*</em></a>.</li>



<li><strong>SBOM (Software Bill of Materials):</strong> A formal, machine-readable inventory of software components, packages, dependencies, and their relationships used to track supply-chain provenance and vulnerability exposure across build artifacts such as virtual appliances. Source: <a href="https://www.cisa.gov/sites/default/files/2024-10/SBOM%20Framing%20Software%20Component%20Transparency%202024.pdf" target="_blank" rel="noopener">CISA, <em>*Framing Software Component Transparency*</em></a>.</li>
</ul>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>SolarWinds Price Increase 2026: What Changed, What It Costs, and Enterprise Alternatives</title>
		<link>https://library.nagios.com/industry-insights/solarwinds-price-increase-2026-what-changed-what-it-costs-and-enterprise-alternatives/</link>
		
		<dc:creator><![CDATA[Shota Kohno]]></dc:creator>
		<pubDate>Fri, 06 Nov 2026 20:43:28 +0000</pubDate>
				<category><![CDATA[Industry Insights]]></category>
		<category><![CDATA[Industry Updates]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71353</guid>

					<description><![CDATA[SolarWinds changed both its ownership and its licensing model in 2025. The company became privately held when Turn/River Capital completed its acquisition on April 16, 2025, at an enterprise value of about $4.4 billion.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">If your SolarWinds rep has called about a &#8220;new multi-year contract model,&#8221; and the renewal quote that followed is double or triple last year&#8217;s invoice for the same modules, you are not alone.</p>



<p class="wp-block-paragraph"><strong>Short answer:</strong> Since Turn/River Capital took SolarWinds private in April 2025, SolarWinds has stopped selling new perpetual licenses and moved to multi-year, subscription-only contracts billed annually. Customers report renewal increases of 100–300%. Organizations that want predictable costs can compare that against perpetual-license alternatives such as <a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noopener">Nagios XI</a>, which <a href="https://www.nagios.com/pricing-plans/" target="_blank" rel="noopener">publishes its prices</a>.</p>



<p class="wp-block-paragraph"><strong>Key takeaways</strong></p>



<ul class="wp-block-list">
<li>SolarWinds Observability Self-Hosted is subscription-only, sold on multi-year contracts. Published starting rates are $8, $14, and $17.50 per node per month.</li>



<li>Analysts report renewal increases of up to 300%. Across 14 renewal figures that customers shared in two public r/Solarwinds threads (April–June 2026), the median reported increase was about 166%.</li>



<li>Nagios XI is a perpetual license with optional annual Maintenance &amp; Support. If you stop paying for maintenance, your monitoring keeps running.</li>



<li>At 500 nodes, three years of Nagios XI Enterprise costs $26,400 at list price. Three years of SolarWinds Essentials costs $144,000 at its published starting rate.</li>
</ul>



<p class="wp-block-paragraph"></p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">What changed in SolarWinds pricing and licensing?</h2>



<p class="wp-block-paragraph">SolarWinds changed both its ownership and its licensing model in 2025. The company became privately held when Turn/River Capital <a href="https://www.solarwinds.com/company/newsroom/press-releases/turnriver-completes-acquisition-of-solarwinds" target="_blank" rel="noopener">completed its acquisition on April 16, 2025</a>, at an enterprise value of about $4.4 billion. The licensing shift followed within months.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Date</th><th>Event</th><th>Source</th></tr></thead><tbody><tr><td>April 16, 2025</td><td>Turn/River Capital completes its acquisition of SolarWinds, and SolarWinds stops trading on the NYSE.</td><td><a href="https://www.sec.gov/Archives/edgar/data/1739942/000119312525082231/d938698dex991.htm" target="_blank" rel="noopener">SEC Form 8-K</a></td></tr><tr><td>August 1, 2025</td><td>New perpetual license sales end, and a default three-year subscription term begins.</td><td><a href="https://www.manageengine.com/it-operations-management/cxo-focus/insights/sw-licensing.html" target="_blank" rel="noopener">ManageEngine</a>; <a href="https://faddom.com/understanding-solarwinds-pricing-and-recent-price-increases-2026/" target="_blank" rel="noopener">Faddom</a> (third-party reports)</td></tr><tr><td>August 26, 2025</td><td>Release notes for SolarWinds Engineer&#8217;s Toolset 2025.3 state that new customers are issued subscription licenses.</td><td><a href="https://documentation.solarwinds.com/en/success_center/ets-desk/content/release_notes/ets-desk_2025-3_release_notes.htm" target="_blank" rel="noopener">SolarWinds documentation</a></td></tr><tr><td>2026</td><td>SolarWinds&#8217; pricing page lists Observability Self-Hosted as subscription-only, sold on multi-year contracts and billed annually.</td><td><a href="https://www.solarwinds.com/hybrid-cloud-observability/pricing" target="_blank" rel="noopener">solarwinds.com</a> (accessed Nov 6, 2026)</td></tr></tbody></table></figure>



<h2 class="wp-block-heading">How much has SolarWinds pricing increased?</h2>



<p class="wp-block-paragraph">Most published reports put SolarWinds renewal increases between 100% and 300% since the acquisition. SolarWinds does not publish renewal pricing, so these figures come from customers and industry analysts rather than from the vendor.</p>



<ul class="wp-block-list">
<li><strong>Analyst reports:</strong> <a href="https://www.netdata.cloud/blog/solarwinds-price-increases-2026/" target="_blank" rel="noopener">Netdata</a> and <a href="https://thesamclub.co.uk/solarwinds-price-increases/" target="_blank" rel="noopener">The SAM Club</a> (a UK software licensing consultancy) report renewal increases of 100–300% for many customers. <a href="https://www.manageengine.com/blog/itom/solarwinds-is-now-forcing-3year-subscription-heres-what-it-means-for-your-it-stack.html" target="_blank" rel="noopener">ManageEngine</a> and Faddom cite increases of up to 300%. All stress that outcomes vary by product mix and contract. Netdata also reports annual escalators of roughly 10% built into the new multi-year contracts.</li>



<li><strong>Customer reports:</strong> We reviewed two public r/Solarwinds threads from April–June 2026 in which customers shared 14 specific renewal figures. The figures are a mix of initial quotes and final negotiated prices. The median reported increase was about 166%, the range was roughly 30% to 334%, and 9 of the 14 more than doubled.</li>



<li><strong>A documented case:</strong> In <a href="https://www.reddit.com/r/Solarwinds/comments/1ssotxe/has_anyone_been_contacted_by_their_solarwinds_rep/" target="_blank" rel="noopener">one r/Solarwinds thread</a>, a customer reported that a renewal for the same NPM and NCM modules rose from $7,900 to $19,936. The SolarWinds rep attributed the increase in writing to a licensing model change, not a standard annual uplift.</li>



<li><strong>Negotiation:</strong> Customers who showed a competing quote, or who said their legal team would not approve a three-year term, reported one-year renewals and smaller increases. In one case, a 50% increase on a three-year term became 15% on a one-year term.</li>
</ul>



<h2 class="wp-block-heading">What does SolarWinds cost now?</h2>



<p class="wp-block-paragraph">SolarWinds publishes starting prices for Observability Self-Hosted, the product that replaced the individual Orion modules (NPM, SAM, NTA, and others). The listed prices are starting rates, not quotes.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>SolarWinds edition</th><th>Published starting rate</th><th>What it adds</th></tr></thead><tbody><tr><td>Essentials</td><td>$8 per node per month</td><td>Network, server, and application monitoring; log monitoring; IP address management</td></tr><tr><td>Advanced</td><td>$14 per node per month</td><td>Essentials plus flow analysis, virtualization monitoring, ML-based alerting</td></tr><tr><td>Premier</td><td>$17.50 per node per month</td><td>Advanced plus storage and web performance monitoring, SaaS entitlements</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><em>All tiers: node-based, subscription only, multi-year contract billed annually. Source: <a href="https://www.solarwinds.com/hybrid-cloud-observability/pricing" target="_blank" rel="noopener">SolarWinds Observability Self-Hosted pricing</a>, accessed November 6, 2026.</em></p>



<p class="wp-block-paragraph">Two other details affect enterprise bills:</p>



<ul class="wp-block-list">
<li><strong>Enterprise editions.</strong> SolarWinds offers Enterprise editions for environments above 500 nodes and requires them above 1,500 nodes.</li>



<li><strong>Upgrades can change consumption.</strong> SolarWinds&#8217; <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-1_release_notes.htm" target="_blank" rel="noopener">2025.1</a> and <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-2_release_notes.htm" target="_blank" rel="noopener">2025.2</a> release notes warn that newly supported cloud entities may be monitored automatically after an upgrade, which can increase license consumption.</li>
</ul>



<h2 class="wp-block-heading">What happens to existing SolarWinds perpetual licenses?</h2>



<p class="wp-block-paragraph">Existing perpetual licenses keep working, but customers report being moved to multi-year subscriptions at renewal, often as Observability Self-Hosted bundles rather than the individual modules they bought before.</p>



<p class="wp-block-paragraph">The difference matters at the end of a term. A SolarWinds subscription that is not renewed <a href="https://thwack.solarwinds.com/discussion/92385/can-we-continue-use-npm-sam-and-ncm-or-any-orion-product-if-license-get-expired" target="_blank" rel="noopener">stops functioning</a>. A perpetual license keeps running at the version you own, without updates or support. Customers who have already converted say this bothers them most: under a subscription, everything stops working if you don&#8217;t renew, instead of just losing support.</p>



<h2 class="wp-block-heading">How is Nagios licensing different?</h2>



<p class="wp-block-paragraph"><strong>If you stop paying for Nagios maintenance, your monitoring keeps running.</strong> You only stop receiving updates and support.</p>



<p class="wp-block-paragraph">Nagios XI is sold as a <strong>perpetual license</strong>. You buy the software once. <a href="https://www.nagios.com/maintenance-support-plans/" target="_blank" rel="noopener">Maintenance &amp; Support</a> is a separate one-year plan, and the first year is included with a new license. It provides:</p>



<ul class="wp-block-list">
<li>version upgrades and security patches,</li>



<li>a dedicated Customer Success Manager,</li>



<li>up to 10 support cases with a one-business-day response,</li>



<li><a href="https://library.nagios.com/nagios-updates/nagios-xi-premium-features/">XI Premium Features</a> such as Azure AD single sign-on and the Nagios Mod-Gearman management interface.</li>
</ul>



<p class="wp-block-paragraph">Nagios publishes both prices.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Nagios XI license level</th><th>Standard (one-time)</th><th>Enterprise (one-time)</th><th>Annual maintenance (from year 2)</th></tr></thead><tbody><tr><td>100 nodes</td><td>$2,595</td><td>$4,690</td><td>$2,104 (+$1,066 Enterprise)</td></tr><tr><td>500 nodes</td><td>$8,295</td><td>$10,390</td><td>$6,939 (+$1,066 Enterprise)</td></tr><tr><td>1,000 nodes</td><td>$14,995</td><td>$17,090</td><td>$11,898 (+$1,066 Enterprise)</td></tr><tr><td>2,000+ nodes or Sitewide</td><td><a href="https://www.nagios.com/contact/" target="_blank" rel="noopener">Contact sales</a></td><td>Contact sales</td><td>Contact sales</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><em>Prices from <a href="https://www.nagios.com/pricing-plans/" target="_blank" rel="noopener">Nagios Pricing Plans</a> and <a href="https://www.nagios.com/maintenance-support-plans/" target="_blank" rel="noopener">Maintenance &amp; Support Plans</a>. Maintenance prices effective January 1, 2026, subject to change. Nagios defines a node as any unique IP address or web URL. Compare <a href="https://assets.nagios.com/handouts/nagiosxi/Nagios-XI-Edition-Comparison.pdf" target="_blank" rel="noopener">XI Standard and Enterprise features</a>.</em></p>



<p class="wp-block-paragraph">A monitoring server holds credentials for everything it monitors, so we recommend keeping maintenance active and applying security updates promptly. The difference from a subscription is that renewal is your choice, made one year at a time.</p>



<h2 class="wp-block-heading">Three-year cost comparison at published list prices</h2>



<p class="wp-block-paragraph">This comparison uses only prices each vendor publishes. It is an illustration, not a quote. SolarWinds figures are starting rates before volume discounts or escalators, and the two vendors define nodes differently.</p>



<p class="wp-block-paragraph"><strong>500 nodes, three years</strong></p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>Scenario</th><th>Three-year cost</th><th>Per node per month</th></tr></thead><tbody><tr><td>SolarWinds Essentials ($8 starting rate)</td><td>$144,000</td><td>$8.00</td></tr><tr><td>SolarWinds Advanced ($14 starting rate)</td><td>$252,000</td><td>$14.00</td></tr><tr><td>Nagios XI Enterprise</td><td>$26,400</td><td>$1.47</td></tr><tr><td>Nagios XI Enterprise + Network Analyzer + Log Server (3-instance)</td><td>$52,490</td><td>$2.92</td></tr></tbody></table></figure>



<p class="wp-block-paragraph">The Nagios figures are the one-time license plus two years of maintenance. For XI Enterprise at 500 nodes, that is $10,390 + 2 × ($6,939 + $1,066) = $26,400. To size your own environment, use the <a href="https://www.nagios.com/products/nagios-xi/xi-plan-calculator/" target="_blank" rel="noopener">Nagios XI Plan Calculator</a>.</p>



<p class="wp-block-paragraph">At 1,000 nodes, the same comparison is $288,000 for SolarWinds Essentials against $43,018 for Nagios XI Enterprise.</p>



<p class="wp-block-paragraph">The comparison excludes hardware, staff time, and migration effort, which apply to either vendor.</p>



<h2 class="wp-block-heading">Which Nagios products replace which SolarWinds modules?</h2>



<p class="wp-block-paragraph">Nagios products are licensed separately, so you buy only what you need.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><thead><tr><th>SolarWinds capability</th><th>Nagios equivalent</th><th>Notes</th></tr></thead><tbody><tr><td>Network Performance Monitor (NPM)</td><td><strong><a href="https://www.nagios.com/products/nagios-xi/" target="_blank" rel="noopener">Nagios XI</a></strong></td><td>SNMP monitoring and traps, a network switch and router wizard, auto-discovery</td></tr><tr><td>Server &amp; Application Monitor (SAM)</td><td><strong>Nagios XI</strong></td><td>Server, application, and database wizards; the NCPA agent</td></tr><tr><td>Virtualization Manager (VMAN)</td><td><strong>Nagios XI</strong></td><td>Premium Wizards for vSphere, Hyper-V, Docker, and Kubernetes</td></tr><tr><td>NetFlow Traffic Analyzer (NTA)</td><td><strong><a href="https://www.nagios.com/products/nagios-network-analyzer/" target="_blank" rel="noopener">Nagios Network Analyzer</a></strong></td><td>NetFlow, sFlow, J-Flow, and IPFIX analysis</td></tr><tr><td>Log Analyzer / Kiwi Syslog</td><td><strong><a href="https://www.nagios.com/products/nagios-log-server/" target="_blank" rel="noopener">Nagios Log Server</a></strong></td><td>Centralized log management and alerting; not a SIEM</td></tr><tr><td>Enterprise Operations Console (EOC)</td><td><strong><a href="https://www.nagios.com/products/nagios-fusion/" target="_blank" rel="noopener">Nagios Fusion</a></strong></td><td>A single view across Nagios XI, Log Server, Network Analyzer, and Core servers, with automatic sign-in to remote XI servers</td></tr><tr><td>Additional Polling Engines</td><td><strong>Nagios Mod-Gearman</strong> or <strong>XI Sitewide</strong></td><td>Remote workers run checks locally and connect outbound to the XI server, so remote sites need no inbound access</td></tr><tr><td>NCM, IPAM, UDT, SEM</td><td>No native equivalent</td><td>Pair Nagios with dedicated tools</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><strong>For large enterprises:</strong> Nagios XI Enterprise adds Service-Level Agreement (SLA) reports, capacity planning, Business Process Intelligence, scheduled reports, and audit logs. Nagios XI Sitewide covers large, distributed deployments. It includes multiple unlimited-node XI instances, Enterprise features, and a free Nagios Fusion license.</p>



<p class="wp-block-paragraph">Multi-site organizations can choose among four reference architectures: centralized, federated, Fusion-based, and Nagios Mod-Gearman distributed. Many combine elements of each. All four are described in <a href="https://assets.nagios.com/downloads/general/docs/Monitoring_Architecture_Solutions_For_Large_Organizations.pdf" target="_blank" rel="noopener">Nagios Monitoring Architecture Solutions for Large Organizations</a>.</p>



<p class="wp-block-paragraph">All Nagios products are self-hosted on your own infrastructure, and Nagios XI can run in air-gapped networks.</p>



<h2 class="wp-block-heading">Frequently asked questions</h2>



<p class="wp-block-paragraph"><strong>Did SolarWinds raise its prices in 2025 and 2026?</strong> Yes, according to customer and analyst reports. Since the April 2025 acquisition by Turn/River Capital, reported renewal increases range from 100% to 300%, driven largely by the move to multi-year subscriptions. SolarWinds does not publish renewal pricing.</p>



<p class="wp-block-paragraph"><strong>Does SolarWinds still sell perpetual licenses?</strong> No, not to new customers. Multiple industry reports state that SolarWinds ended new perpetual license sales on August 1, 2025, and its current pricing page lists Observability Self-Hosted as subscription-only. Existing perpetual licenses still work but are being moved toward subscriptions at renewal.</p>



<p class="wp-block-paragraph"><strong>How much does SolarWinds cost per node?</strong> SolarWinds lists Observability Self-Hosted starting at $8 per node per month for Essentials, $14 for Advanced, and $17.50 for Premier. These are starting rates on multi-year contracts as of November 2026, and actual quotes vary.</p>



<p class="wp-block-paragraph"><strong>Can you negotiate a SolarWinds renewal?</strong> Yes, according to customer reports. Customers who presented a competing quote, or who said legal would not approve a three-year term, reported one-year terms and smaller increases.</p>



<p class="wp-block-paragraph"><strong>Which network monitoring tools still offer perpetual licensing?</strong> Nagios XI, Nagios Log Server, Nagios Network Analyzer, and Nagios Fusion are all sold as perpetual licenses with optional annual maintenance. Nagios publishes license and maintenance prices on its website.</p>



<p class="wp-block-paragraph"><strong>What is the best SolarWinds NPM alternative for enterprises?</strong> For on-premises enterprise network monitoring with predictable costs, Nagios XI Enterprise covers SNMP device monitoring, traps, SLA reporting, and capacity planning. Add Nagios Network Analyzer to replace SolarWinds NTA for NetFlow analysis. For a full feature comparison, see <a href="https://www.nagios.com/nagios-vs-solarwinds/" target="_blank" rel="noopener">Nagios vs. SolarWinds</a>.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">Next steps</h2>



<ul class="wp-block-list">
<li><a href="https://www.nagios.com/products/nagios-xi/downloads/" target="_blank" rel="noopener">Start the 30-day Nagios XI trial</a></li>



<li><a href="https://www.nagios.com/nagios-vs-solarwinds/" target="_blank" rel="noopener">Compare your SolarWinds invoice with a Nagios cost review</a></li>



<li><a href="https://www.nagios.com/quickstart/" target="_blank" rel="noopener">Get expert setup with Nagios Quickstart</a></li>



<li><a href="https://www.nagios.com/contact/" target="_blank" rel="noopener">Talk to Nagios sales</a> about Sitewide and 2,000+ node environments</li>
</ul>



<h2 class="wp-block-heading">Sources</h2>



<ul class="wp-block-list">
<li>SolarWinds, <a href="https://www.solarwinds.com/company/newsroom/press-releases/turnriver-completes-acquisition-of-solarwinds" target="_blank" rel="noopener">&#8220;Turn/River Completes Acquisition of SolarWinds,&#8221;</a> April 16, 2025 (<a href="https://www.sec.gov/Archives/edgar/data/1739942/000119312525082231/d938698dex991.htm" target="_blank" rel="noopener">SEC Form 8-K, Exhibit 99.1</a>)</li>



<li>SolarWinds, <a href="https://www.solarwinds.com/hybrid-cloud-observability/pricing" target="_blank" rel="noopener">Observability Self-Hosted pricing and FAQ</a>, accessed November 6, 2026</li>



<li>SolarWinds documentation: <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-1_release_notes.htm" target="_blank" rel="noopener">2025.1 release notes</a>, <a href="https://documentation.solarwinds.com/en/success_center/orionplatform/content/release_notes/hco_2025-2_release_notes.htm" target="_blank" rel="noopener">2025.2 release notes</a>, <a href="https://documentation.solarwinds.com/en/success_center/ets-desk/content/release_notes/ets-desk_2025-3_release_notes.htm" target="_blank" rel="noopener">Engineer&#8217;s Toolset 2025.3 release notes</a></li>



<li>Netdata, <a href="https://www.netdata.cloud/blog/solarwinds-price-increases-2026/" target="_blank" rel="noopener">&#8220;SolarWinds Price Increases 2026: What Customers Need to Know,&#8221;</a> June 23, 2026</li>



<li>ManageEngine, <a href="https://www.manageengine.com/it-operations-management/cxo-focus/insights/sw-licensing.html" target="_blank" rel="noopener">&#8220;SolarWinds shift to 3-year subscriptions,&#8221;</a> November 27, 2025</li>



<li>Faddom, <a href="https://faddom.com/understanding-solarwinds-pricing-and-recent-price-increases-2026/" target="_blank" rel="noopener">&#8220;Understanding SolarWinds Pricing and Recent Price Increases (2026),&#8221;</a> updated November 1, 2026</li>



<li>The SAM Club, <a href="https://thesamclub.co.uk/solarwinds-price-increases/" target="_blank" rel="noopener">&#8220;SolarWinds Price Increases — What&#8217;s Changed and Why,&#8221;</a> July 14, 2026</li>



<li>r/Solarwinds, <a href="https://www.reddit.com/r/Solarwinds/comments/1ssotxe/has_anyone_been_contacted_by_their_solarwinds_rep/" target="_blank" rel="noopener">&#8220;Has anyone been contacted by their SolarWinds rep about a massive price increase for 2026?&#8221;</a> (about April 2026)</li>



<li>r/Solarwinds, <a href="https://www.reddit.com/r/Solarwinds/comments/1ucmw4y/solarwinds_lost_a_18_yr_customer_today/" target="_blank" rel="noopener">&#8220;Solarwinds lost a 18 yr customer today&#8221;</a> (about June 2026)</li>



<li>Nagios Enterprises, <a href="https://www.nagios.com/pricing-plans/" target="_blank" rel="noopener">Pricing Plans</a> and <a href="https://www.nagios.com/maintenance-support-plans/" target="_blank" rel="noopener">Maintenance &amp; Support Plans</a>, accessed November 6, 2026</li>



<li>Nagios Enterprises, <a href="https://assets.nagios.com/downloads/general/docs/Monitoring_Architecture_Solutions_For_Large_Organizations.pdf" target="_blank" rel="noopener">Monitoring Architecture Solutions for Large Organizations</a></li>
</ul>



<p class="wp-block-paragraph"><em>Disclaimer: SolarWinds pricing information comes from SolarWinds&#8217; published starting rates and from third-party customer and analyst reports as of November 2026. Actual SolarWinds pricing varies by customer, product, and contract terms. Nagios prices are list prices and are subject to change. Request formal quotes from both vendors before making a purchasing decision.</em></p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Managing Nagios Mod-Gearman in the Nagios XI User Interface</title>
		<link>https://library.nagios.com/tutorials/managing-nagios-mod-gearman-in-the-nagios-xi-user-interface/</link>
		
		<dc:creator><![CDATA[Shamas Demoret]]></dc:creator>
		<pubDate>Thu, 05 Nov 2026 15:42:47 +0000</pubDate>
				<category><![CDATA[Tutorials]]></category>
		<category><![CDATA[Configuration]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71293</guid>

					<description><![CDATA[Learn how to manage Nagios Mod Gearman for Nagios XI load reduction, load balancing, and distributed monitoring right from the user interface. ]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Nagios Mod-Gearman (NMG) is a Nagios Event Broker (NEB) module that can be used for a variety of purposes, including load reduction, load balancing, and distributed monitoring.</p>



<p class="wp-block-paragraph">NMG is pre-loaded in Nagios XI 2024R2.1+, and XI also includes<strong> Remote Workers</strong>, a UI-driven approach for managing the tool. This <a href="https://library.nagios.com/nagios-updates/nagios-xi-premium-features/">Premium</a> feature provides a way to manage your NMG Server configs and NMG Workers, including deployment and syncing changes, right from the XI web interface.</p>



<h3 class="wp-block-heading">Nagios Mod-Gearman UI Documentation<br></h3>



<p class="wp-block-paragraph">You can learn more about managing NMG from the web interface in this guide: </p>



<p class="wp-block-paragraph"><a href="https://assets.nagios.com/downloads/nagiosxi/docs/Managing-Nagios-Mod-Gearman-in-the-Nagios-XI-UI.pdf" target="_blank" rel="noreferrer noopener">Managing Nagios Mod-Gearman in the Nagios XI UI</a></p>



<h3 class="wp-block-heading">NMG Overview</h3>



<p class="wp-block-paragraph">You can find an overview of NMG&#8217;s features, functions, architecture, and benefits here:</p>



<p class="wp-block-paragraph"><a href="https://library.nagios.com/techtips/succeed-with-nagios-mod-gearman/" target="_blank" rel="noreferrer noopener">Gear Up With Nagios Mod-Gearman</a></p>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Nagios XI: Status Summary Dashlets Showing Zero (How to Fix)</title>
		<link>https://library.nagios.com/support-tips/nagios-xi-status-summary-dashlets-showing-zero/</link>
		
		<dc:creator><![CDATA[Tom Griep]]></dc:creator>
		<pubDate>Tue, 03 Nov 2026 19:25:59 +0000</pubDate>
				<category><![CDATA[Support Tips]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Crashed]]></category>
		<category><![CDATA[database]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Nagios XI]]></category>
		<category><![CDATA[Repair]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71009</guid>

					<description><![CDATA[If Nagios XI’s Status Summary dashlets show zero across the board, a corrupted MySQL table is usually the cause, here’s how to identify and repair it with Nagios’ built-in script.]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Purpose</h2>



<p class="wp-block-paragraph">This document describes how to repair issues with the Nagios XI database when encountering zero values in the Host Status Summary or the Service Status Summary dashlets.</p>



<h2 class="wp-block-heading">Identifying the Problem</h2>



<p class="wp-block-paragraph">After logging in to the Nagios XI web interface, if you see either the Host Status Summary or the Service Status Summary Dashlets displaying zero for all of the statuses (see screenshots below), it is most likely caused by a corrupted table in the MySQL database.</p>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="185" src="https://library.nagios.com/wp-content/uploads/2026/10/Host-Service-Status-Summary-1024x185.png" alt="Nagios XI Host Status Summary and Service Status Summary dashlets showing zero for all statuses." class="wp-image-71010" title="Nagios XI: Status Summary Dashlets Showing Zero (How to Fix) 4" srcset="https://library.nagios.com/wp-content/uploads/2026/10/Host-Service-Status-Summary-1024x185.png 1024w, https://library.nagios.com/wp-content/uploads/2026/10/Host-Service-Status-Summary-300x54.png 300w, https://library.nagios.com/wp-content/uploads/2026/10/Host-Service-Status-Summary-768x138.png 768w, https://library.nagios.com/wp-content/uploads/2026/10/Host-Service-Status-Summary.png 1104w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Nagios XI Host and Service Status Summary.</figcaption></figure>



<h2 class="wp-block-heading">Repairing the Database</h2>



<p class="wp-block-paragraph">Nagios included a new script, beginning with XI 2024R1.2, to repair the MySQL database, which will fix the above issue.</p>



<p class="wp-block-paragraph">Running this script can take up to an hour, which is normal. You will want to allow the script to fully complete. If it is interrupted, other issues with the database may develop and may not be repairable. </p>



<p class="wp-block-paragraph">Make sure to run this script in an SSH (Secure Shell) session as root user, to clean and repair the MySQL database of temporary data and to stop the old processes that should not be running. The script stops and restarts associated processes.</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>/usr/local/nagiosxi/scripts/repair_crashed_databases.sh</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">usr</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">local</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">nagiosxi</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">scripts</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">repair_crashed_databases</span><span style="color: #D4D4D4">.</span><span style="color: #9CDCFE">sh</span></span></code></pre></div>



<h3 class="wp-block-heading">Confirming the Fix</h3>



<p class="wp-block-paragraph">Wait 5–10 minutes after the script completes, then log back in to the XI interface and check whether the statuses are updating.</p>



<h3 class="wp-block-heading">Still Seeing Zero Values?</h3>



<p class="wp-block-paragraph">If the dashlets still display zero for all statuses, open a case through the support portal so a support engineer can help resolve the issue.</p>



<ul class="wp-block-list">
<li><a href="https://supportportal.nagios.com/" target="_blank" rel="noreferrer noopener">Nagios Customer Support Portal</a></li>



<li><a href="https://supportportal.nagios.com/s/article/Creating-a-Case" target="_blank" rel="noreferrer noopener">Creating a Case</a><br><br></li>
</ul>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Leveraging Your Nagios XI Disaster Recovery And Testing/Development Servers</title>
		<link>https://library.nagios.com/techtips/nagios-xi-disaster-recovery-and-test/</link>
		
		<dc:creator><![CDATA[Shamas Demoret]]></dc:creator>
		<pubDate>Fri, 30 Oct 2026 15:36:03 +0000</pubDate>
				<category><![CDATA[Techtips]]></category>
		<category><![CDATA[Disaster Recovery]]></category>
		<category><![CDATA[Testing/Development]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71122</guid>

					<description><![CDATA[Nagios XI license includes free testing/development and disaster recovery installations, in addition to your production instance. Leveraging these options can help ensure that changes are carefully tested before they hit production, and help you achieve monitoring continuity should issues arise with your production server.]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Did you know that your Nagios XI license includes free testing/development and disaster recovery installations, in addition to your production instance? Leveraging these options can help ensure that changes are carefully tested before they hit production, and help you achieve monitoring continuity should issues arise with your production server.</p>



<p class="wp-block-paragraph">In this article we&#8217;ll explore important guidelines and deployment options for both install types, and provide links to related resources to help you get the most out of them.</p>



<h3 class="wp-block-heading">Scheduled Backups Note</h3>



<p class="wp-block-paragraph">In the following sections you&#8217;ll find guidance on using Nagios XI&#8217;s backup/restore capability to facilitate both your testing/development and disaster recovery servers. </p>



<p class="wp-block-paragraph">If you choose the Local option for your Scheduled Backups, we recommend that you use a mount point on a remote mount, rather than a local directory path on your production XI server itself. This will ensure that you will still have access to the backups in the event of production server failure. Enter the mount point in the <strong>Location</strong> field of the <strong>Local</strong> tab of the <strong>Scheduled Backups </strong>menu to set this up.</p>



<p class="wp-block-paragraph">We also recommend that you create a mount point to the same remote mount on your DR server so that you can access it for regular disaster recovery testing, and in the event your production server goes down.</p>



<h2 class="wp-block-heading">Testing &amp; Development</h2>



<h3 class="wp-block-heading">Purpose and Guidelines</h3>



<p class="wp-block-paragraph">Your testing and development (T&amp;D) install enables you to test things like new Nagios XI versions, scripts, plugins, and wizards, as well as operating system or OS component updates (such as <code>dnf update</code> or a <a href="https://library.nagios.com/documentation/nagios-php-upgrade-what-to-know/" target="_blank" rel="noreferrer noopener">PHP upgrade</a>), before rolling them into production.</p>



<p class="wp-block-paragraph">Your T&amp;D server must not be used for production host and service monitoring or notifications.</p>



<h3 class="wp-block-heading">Deployment Options</h3>



<p class="wp-block-paragraph">There are a variety of approaches you could take to duplicate your Production environment in T&amp;D, such as:</p>



<h4 class="wp-block-heading">1. Back Up Production, Restore to T&amp;D</h4>



<p class="wp-block-paragraph">To create the T&amp;D instance using this approach, back up your production system and restore it on your test server to ensure it is similar or identical to your production system. Refer to the following documents in the Nagios XI Admin Guide for full installation and backup/restore instructions:</p>



<ul class="wp-block-list">
<li><a href="https://assets.nagios.com/downloads/nagiosxi/guides/administrator/installation.php#manualinstallation" target="_blank" rel="noreferrer noopener">Manual Installation Instructions</a></li>



<li><a href="https://assets.nagios.com/downloads/nagiosxi/guides/administrator/sysmgmt.php#backuprestore" target="_blank" rel="noreferrer noopener">How To Back Up &amp; Restore Your Nagios XI Server</a></li>
</ul>



<h4 class="wp-block-heading">2. VM Cloning</h4>



<p class="wp-block-paragraph">If you are using a hypervisor such as VMware or Proxmox, another option is to clone your production system to make an exact copy. The exact steps will vary depending on your hypervisor, so you&#8217;ll need to check your vendor documentation or coordinate with your hypervisor admins if you&#8217;re uncertain of how to proceed. </p>



<h3 class="wp-block-heading">Important: Disabling Checks</h3>



<p class="wp-block-paragraph">Regardless of the approach you choose, it is critical that your T&amp;D system is <strong>not</strong> being used for any checks or notifications unless you are actively testing a specific potential change or scenario for a short time.</p>



<p class="wp-block-paragraph">To disable checks and notifications on your T&amp;D server, navigate to:</p>



<p class="wp-block-paragraph"><strong>Admin &gt; Monitoring Engine Status</strong></p>



<p class="wp-block-paragraph">In the <strong>Monitoring Engine Process</strong> dashlet, click on the “X” to the right of the following Processes:</p>



<ul class="wp-block-list">
<li>Active Service Checks</li>



<li>Active Host Checks</li>



<li>Notifications</li>
</ul>



<p class="wp-block-paragraph">The Value icon for all three will change from green to red. Once they are red, the XI instance will no longer perform host/service checks or send notifications.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="822" height="545" src="https://library.nagios.com/wp-content/uploads/2026/10/disable-check-notifications-for-xi-test-server.png" alt="Disabling host/service checks and notifications in your XI test server." class="wp-image-71133" title="Leveraging Your Nagios XI Disaster Recovery And Testing/Development Servers 5" srcset="https://library.nagios.com/wp-content/uploads/2026/10/disable-check-notifications-for-xi-test-server.png 822w, https://library.nagios.com/wp-content/uploads/2026/10/disable-check-notifications-for-xi-test-server-300x199.png 300w, https://library.nagios.com/wp-content/uploads/2026/10/disable-check-notifications-for-xi-test-server-768x509.png 768w" sizes="(max-width: 822px) 100vw, 822px" /><figcaption class="wp-element-caption">Disabling checks and notifications on your XI Testing server is easy. </figcaption></figure>



<h2 class="wp-block-heading">Disaster Recovery</h2>



<h3 class="wp-block-heading">Purpose and Guidelines</h3>



<p class="wp-block-paragraph">The disaster recovery (DR) instance is used to take over production monitoring in the event that your production XI fails.</p>



<p class="wp-block-paragraph">The DR instance must be in non-operational mode except when it assumes production operation. The <strong>only</strong> exception to this important policy is that your DR instance can be used to actively monitor your production XI server and notify you of problems.</p>



<h3 class="wp-block-heading">Deployment Options</h3>



<h4 class="wp-block-heading">1. Hot DR Spare</h4>



<p class="wp-block-paragraph">To create a “hot” disaster recovery spare, install a fresh version of XI on a new, clean Linux installation, making sure the XI version is the same as the production instance. </p>



<ul class="wp-block-list">
<li>Use the DR instance to check that the production XI is running. The <a href="https://assets.nagios.com/downloads/nagiosxi/docs/Monitoring-a-Nagios-XI-Server-2024.pdf" target="_blank" rel="noopener">Nagios XI Server Wizard</a> is an excellent option for this. Make sure that your production XI server is the <strong>only</strong> thing being checked and notified on unless you&#8217;ve switched DR to production during a production XI outage. </li>



<li>Ensure that you maintain the same version of XI on the DR and production instances. If your production instance fails, you can recover the most <a href="https://assets.nagios.com/downloads/nagiosxi/guides/administrator/sysmgmt.php#backuprestore" target="_blank" rel="noopener">current backup</a> to your DR server and change the IP address (if using passive checks, since they are configured to send to the address of your production server specifically). </li>



<li>You’ll regain your production checks and notifications while Nagios Support helps you recover your production instance. </li>



<li>Make sure you <a href="https://assets.nagios.com/downloads/nagiosxi/guides/administrator/updates.php#upgradingxi" target="_blank" rel="noreferrer noopener">upgrade</a> your DR instance when you upgrade Production so that they are the same version, enabling you to apply your backup to DR in the event of a Production XI issue</li>
</ul>



<h4 class="wp-block-heading">2. High Availability</h4>



<p class="wp-block-paragraph">Depending on your business continuity and disaster recovery needs, simply having a DR server in place and recovering from a backup may be enough. Or, you may decide to pursue a High Availability (HA) solution. Define what is important to you in a disaster recovery scenario. Once you have clearly defined goals and outcomes, you can plan appropriately and test. You can find additional details in this guide:<br><a href="https://assets.nagios.com/downloads/nagiosxi/guides/administrator/advanced.php#highavailability" target="_blank" rel="noopener">High Availability Options for Nagios XI</a><br></p>



<p class="wp-block-paragraph">We also have a network of global partners, known as the Nagios Partner Network, who offer professional services. If you would like help <a href="https://www.nagios.com/find-a-partner/" target="_blank" rel="noopener">finding a partner</a> to assist with your HA requirements and implementation, just let us know.</p>



<p class="wp-block-paragraph">You can contact us directly at <a href="mailto:sales@nagios.com">sales@nagios.com</a>, we&#8217;d be happy to answer questions and help connect you<br>with a Partner.</p>



<h2 class="wp-block-heading">Further Reading</h2>



<p class="wp-block-paragraph">You can find further details on the three included installation types, license activation, and license benefits here:</p>



<p class="wp-block-paragraph"><a href="https://assets.nagios.com/downloads/nagiosxi/docs/Nagios-XI-License-Information.pdf" target="_blank" rel="noopener">Nagios XI License Information</a></p>



<p class="wp-block-paragraph"><a href="https://assets.nagios.com/downloads/nagiosxi/docs/Nagios-XI-2024-Best-Practices.pdf" target="_blank" rel="noopener">Nagios XI Best Practices</a></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Troubleshooting Nagios Log Server Migration Issues</title>
		<link>https://library.nagios.com/documentation/troubleshooting-nagios-log-server-migration-issues/</link>
		
		<dc:creator><![CDATA[Rumed Arafa]]></dc:creator>
		<pubDate>Tue, 27 Oct 2026 16:16:42 +0000</pubDate>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Support Tips]]></category>
		<category><![CDATA[Command Line]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[Troubleshooting]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71002</guid>

					<description><![CDATA[If your Nagios Log Server migration isn’t completing as expected, this guide will help you find the cause using migration logs, command-line tools, and example output. Due to architectural changes introduced in Nagios Log Server 2024R2, an in-place upgrade from 2024R1.x is not supported. Instead, deploy a new Nagios Log Server 2026R2 Cluster and migrate [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">If your Nagios Log Server migration isn’t completing as expected, this guide will help you find the cause using migration logs, command-line tools, and example output.</p>



<p class="wp-block-paragraph">Due to architectural changes introduced in Nagios Log Server 2024R2, an in-place upgrade from 2024R1.x is not supported. Instead, deploy a new Nagios Log Server 2026R2 Cluster and migrate data using the included migration utility.</p>



<p class="wp-block-paragraph">During this migration, you may run into issues you can resolve on your own before contacting Nagios Support. This article covers how to review migration logs, run the migration manually, and identify common errors.</p>



<p class="wp-block-paragraph">For migration instructions, see the <a href="https://assets.nagios.com/downloads/nagios-log-server/docs/Migrating-to-Nagios-Log-Server-2026.pdf" target="_blank" rel="noreferrer noopener">Migrating to Nagios Log Server 2026</a> document.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading"><strong>Verify Versions</strong></h2>



<p class="wp-block-paragraph">Before troubleshooting, confirm that you have used supported versions for the source and destination clusters:</p>



<ul class="wp-block-list">
<li>Source Cluster: <strong>Nagios Log Server 2024R1.3.8</strong></li>



<li>Destination Cluster: <strong>At least Nagios Log Server 2026R2</strong></li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:0px;margin-bottom:0px"/>



<h2 class="wp-block-heading"><strong>Common Migration Issues</strong></h2>



<p class="wp-block-paragraph">Many issues can be resolved based on the log output, without the need to contact Nagios Support. For example, if you see that the logs show connectivity issues, it could be related to network connectivity problems.</p>



<p class="wp-block-paragraph">Here is a list of common migration issues:</p>



<ul class="wp-block-list">
<li>Network connectivity problems </li>



<li>Authentication failures</li>



<li>OpenSearch indexing errors</li>



<li>Data mapping conflicts</li>



<li>Permission issues</li>



<li>Dashboard or settings migration failures</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:0px;margin-bottom:0px"/>



<h2 class="wp-block-heading"><strong>Review Migration Logs</strong></h2>



<p class="wp-block-paragraph">On the target instance, you can grep the logs to find all the messages generated by the migration, to isolate issues:</p>



<h3 class="wp-block-heading">RHEL-Based Systems</h3>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>cat /var/log/messages | grep "Nagios Log Server Migration"</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #9CDCFE">cat</span><span style="color: #D4D4D4"> /</span><span style="color: #569CD6">var</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">log</span><span style="color: #D4D4D4">/messages | grep </span><span style="color: #CE9178">&quot;Nagios Log Server Migration&quot;</span></span></code></pre></div>



<h3 class="wp-block-heading">Debian-Based Systems</h3>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>cat /var/log/syslog | grep "Nagios Log Server Migration"</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #9CDCFE">cat</span><span style="color: #D4D4D4"> /</span><span style="color: #569CD6">var</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">log</span><span style="color: #D4D4D4">/syslog | grep </span><span style="color: #CE9178">&quot;Nagios Log Server Migration&quot;</span></span></code></pre></div>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:0px;margin-bottom:0px"/>



<h2 class="wp-block-heading"><strong>Run the Migration From the Command Line</strong></h2>



<p class="wp-block-paragraph">Another option is to run the migration from the command line which gives you more flexibility and control, and shows actual errors on the console. You can isolate a specific index, migrate only the log data, or restart the previous migration. Run the following migration script from the command line on the target instance:</p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>php /usr/local/nagioslogserver/scripts/migrate_data.php -s &lt;source_ip></textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #9CDCFE">php</span><span style="color: #D4D4D4"> /</span><span style="color: #9CDCFE">usr</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">local</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">nagioslogserver</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">scripts</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">migrate_data</span><span style="color: #D4D4D4">.</span><span style="color: #9CDCFE">php</span><span style="color: #D4D4D4"> -</span><span style="color: #9CDCFE">s</span><span style="color: #D4D4D4"> &lt;</span><span style="color: #9CDCFE">source_ip</span><span style="color: #D4D4D4">&gt;</span></span></code></pre></div>



<p class="wp-block-paragraph"><strong>Example:</strong></p>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>php /usr/local/nagioslogserver/scripts/migrate_data.php -s 192.168.55.101 -i logstash-2026.07.30 -r</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #9CDCFE">php</span><span style="color: #D4D4D4"> /</span><span style="color: #9CDCFE">usr</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">local</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">nagioslogserver</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">scripts</span><span style="color: #D4D4D4">/</span><span style="color: #9CDCFE">migrate_data</span><span style="color: #D4D4D4">.</span><span style="color: #9CDCFE">php</span><span style="color: #D4D4D4"> -</span><span style="color: #9CDCFE">s</span><span style="color: #D4D4D4"> </span><span style="color: #B5CEA8">192.168</span><span style="color: #D4D4D4">.</span><span style="color: #B5CEA8">55.101</span><span style="color: #D4D4D4"> -</span><span style="color: #9CDCFE">i</span><span style="color: #D4D4D4"> </span><span style="color: #9CDCFE">logstash</span><span style="color: #D4D4D4">-</span><span style="color: #B5CEA8">2026.07</span><span style="color: #D4D4D4">.</span><span style="color: #B5CEA8">30</span><span style="color: #D4D4D4"> -</span><span style="color: #9CDCFE">r</span></span></code></pre></div>



<p class="wp-block-paragraph">This command will migrate the index named <code>logstash-2026.07.30</code> and restart the previous migration using <code>192.168.55.101</code> as the source instance.</p>



<h3 class="wp-block-heading">Common Parameters:</h3>



<ul class="wp-block-list">
<li><code>-s &lt;source_ip&gt;</code>&nbsp;The IP address of the source cluster. This is required.</li>



<li><code>-i &lt;index_name&gt;</code>&nbsp;Migrates the specified index.</li>



<li><code>-l</code> Migrates log data.</li>



<li><code>-r</code> Restarts previous migration.</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:0px;margin-bottom:0px"/>



<h2 class="wp-block-heading">Reading Migration Outputs</h2>



<p class="wp-block-paragraph">The following examples show what to look for in the log files or on the console, if performed manually.</p>



<h3 class="wp-block-heading">Failed Migration Example</h3>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>{
  "failures": &#91;
    {
      "cause": {
        "type": "mapper_parsing_exception",
        "reason": "object mapping conflict"
      },
      "status": 400
    }
  &#93;
}</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">{</span></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">&quot;failures&quot;</span><span style="color: #D4D4D4">: &#91;</span></span>
<span class="line"><span style="color: #D4D4D4">    {</span></span>
<span class="line"><span style="color: #D4D4D4">      </span><span style="color: #9CDCFE">&quot;cause&quot;</span><span style="color: #D4D4D4">: {</span></span>
<span class="line"><span style="color: #D4D4D4">        </span><span style="color: #9CDCFE">&quot;type&quot;</span><span style="color: #D4D4D4">: </span><span style="color: #CE9178">&quot;mapper_parsing_exception&quot;</span><span style="color: #D4D4D4">,</span></span>
<span class="line"><span style="color: #D4D4D4">        </span><span style="color: #9CDCFE">&quot;reason&quot;</span><span style="color: #D4D4D4">: </span><span style="color: #CE9178">&quot;object mapping conflict&quot;</span></span>
<span class="line"><span style="color: #D4D4D4">      },</span></span>
<span class="line"><span style="color: #D4D4D4">      </span><span style="color: #9CDCFE">&quot;status&quot;</span><span style="color: #D4D4D4">: </span><span style="color: #B5CEA8">400</span></span>
<span class="line"><span style="color: #D4D4D4">    }</span></span>
<span class="line"><span style="color: #D4D4D4">  &#93;</span></span>
<span class="line"><span style="color: #D4D4D4">}</span></span></code></pre></div>



<p class="wp-block-paragraph">A <code>mapper_parsing_exception</code> indicates a data mapping conflict during migration. If you see this, please open a Support Case.</p>



<h3 class="wp-block-heading">Successful Migration Example</h3>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>{
  "created": 1,
  "version_conflicts": 0,
  "failures": []
}</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">{</span></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">&quot;created&quot;</span><span style="color: #D4D4D4">: </span><span style="color: #B5CEA8">1</span><span style="color: #D4D4D4">,</span></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">&quot;version_conflicts&quot;</span><span style="color: #D4D4D4">: </span><span style="color: #B5CEA8">0</span><span style="color: #D4D4D4">,</span></span>
<span class="line"><span style="color: #D4D4D4">  </span><span style="color: #9CDCFE">&quot;failures&quot;</span><span style="color: #D4D4D4">: []</span></span>
<span class="line"><span style="color: #D4D4D4">}</span></span></code></pre></div>



<p class="wp-block-paragraph">An empty <code>failures</code> array indicates the migration completed without errors.</p>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:0px;margin-bottom:0px"/>



<h2 class="wp-block-heading">Before Opening a Support Case</h2>



<p class="wp-block-paragraph">If you still need help, collect the following and upload them to your Support Case:</p>



<ul class="wp-block-list">
<li>Source and destination Log Server versions</li>



<li>Migration log output</li>



<li>Any output from the migration script</li>



<li>Screenshots of reported errors</li>



<li>Full <a href="https://supportportal.nagios.com/s/article/Generating-the-Log-Server-Diagnostic-Profile" target="_blank" rel="noreferrer noopener">diagnostic profiles</a> of both instances</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:0px;margin-bottom:0px"/>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">Migrating to the latest Nagios Log Server version is a significant step. If you worked through these troubleshooting steps and still see errors, <a href="https://supportportal.nagios.com/s/" target="_blank" rel="noopener">open a Support Case</a> and include the items listed above so our team can review your migration as quickly as possible.</p>



<h3 class="wp-block-heading">Additional Resources</h3>



<ul class="wp-block-list">
<li><a href="https://assets.nagios.com/downloads/nagios-log-server/guides/administrator/updates.php#migrate-to-r2" target="_blank" rel="noreferrer noopener">Migrating from 2024R1 to 2026</a></li>



<li><a href="https://assets.nagios.com/downloads/nagios-log-server/guides/administrator/generaluse.php#backup-and-restore" target="_blank" rel="noreferrer noopener">Backing Up and Restoring Nagios Log Server</a></li>



<li><a href="https://assets.nagios.com/downloads/nagios-log-server/guides/administrator/" target="_blank" rel="noopener">Nagios Log Server Admin Guide</a></li>



<li><a href="https://library.nagios.com/docs" target="_blank" rel="noreferrer noopener">Nagios Log Server Documentation</a></li>



<li><a href="https://support.nagios.com/forum" target="_blank" rel="noopener">Nagios Support Forum</a></li>
</ul>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Nagios PHP Upgrade: What to Know Before You Start</title>
		<link>https://library.nagios.com/documentation/nagios-php-upgrade-what-to-know/</link>
		
		<dc:creator><![CDATA[Andy Fried]]></dc:creator>
		<pubDate>Thu, 22 Oct 2026 16:38:05 +0000</pubDate>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Support Tips]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[PHP]]></category>
		<category><![CDATA[Upgrade]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=71054</guid>

					<description><![CDATA[On October 21, 2026, the PHP project released urgent security fixes, addressing two vulnerabilities, CVE-2026-109618 and CVE-2026-109619, known as PHP2Shell. Both carry a critical 9.2 CVSS v4.0 score, meaning an unauthorized user could remotely execute code on a vulnerable web server without logging in. As a result, many organizations are planning a PHP upgrade. This [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">On October 21, 2026, the PHP project released urgent security fixes, addressing two vulnerabilities, <a href="https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w" target="_blank" rel="noopener">CVE-2026-109618</a> and <a href="https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp" target="_blank" rel="noopener">CVE-2026-109619</a>, known as PHP2Shell. Both carry a critical 9.2 CVSS v4.0 score, meaning an unauthorized user could remotely execute code on a vulnerable web server without logging in.</p>



<p class="wp-block-paragraph">As a result, many organizations are planning a PHP upgrade. This article describes what you need to consider before a PHP upgrade, so your Nagios software keeps working properly.</p>



<div role="note" style="border-left:6px solid #e5484d;background:rgba(229,72,77,0.12);padding:16px 22px;margin:28px 0;">
  <p style="margin:0 0 4px;font-size:1.1em;font-weight:600;color:#e5484d;text-transform:uppercase;letter-spacing:0.04em;">Important</p>
  <p style="margin:0;font-size:1em;line-height:1.5;">Do not upgrade PHP 7.x to PHP 8.x on an existing Nagios server. Migrate to a newer OS release instead.</p>
</div>



<h2 class="wp-block-heading">What This Means for Nagios Monitoring Solutions </h2>



<p class="wp-block-paragraph">Nagios XI and our other web-based products (including Nagios Fusion) run on the PHP version installed on your server, so applying your Linux vendor’s PHP security updates is important.</p>



<p class="wp-block-paragraph">When Nagios software is initially installed, it relies on the base version of PHP that the OS vendor installs. The following is mostly geared towards Nagios XI, but it is applicable to our other software as well.&nbsp;</p>



<p class="wp-block-paragraph">For example, RHEL 8 installs PHP 7.2, RHEL 9 installs PHP 8.0, and Ubuntu 24.04 LTS installs PHP 8.3.&nbsp;</p>



<p class="wp-block-paragraph">As of October 1, 2026, the current versions of our software require a minimum of PHP 7.4 and have been developed and tested to run on PHP 8.4.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<h2 class="wp-block-heading">How to Check Your System</h2>



<p class="wp-block-paragraph">Check whether your PHP packages include the PHP2Shell fixes.</p>



<h3 class="wp-block-heading">RHEL-Based Systems</h3>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>rpm -q --changelog php-common | grep -i CVE-2026-1096</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">rpm -q --changelog php-common | grep -i CVE-2026-1096</span></span></code></pre></div>



<p class="wp-block-paragraph">If the command returns CVE-2026-109618 and CVE-2026-109619, your PHP packages include the fixes. If it returns nothing, apply your Linux vendor’s latest PHP updates, then check again.</p>



<h3 class="wp-block-heading">Debian Systems</h3>



<h4 class="wp-block-heading">Debian 12</h4>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>apt list | grep php8.2-common</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">apt list | grep php8.2-common</span></span></code></pre></div>



<p class="wp-block-paragraph">If they have this version, they have the patch: 8.2.35-1~deb12u1</p>



<h4 class="wp-block-heading">Debian 13</h4>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>apt list | grep php8.4-common</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">apt list | grep php8.4-common</span></span></code></pre></div>



<p class="wp-block-paragraph">If they have this version, they have the patch: 8.4.27-1~deb13u1</p>



<h3 class="wp-block-heading">Ubuntu Systems</h3>



<h4 class="wp-block-heading">Ubuntu 22</h4>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>apt list | grep php8.1-common</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">apt list | grep php8.1-common</span></span></code></pre></div>



<p class="wp-block-paragraph">If they have this version, they have the patch: 8.1.2-1ubuntu2.28</p>



<h4 class="wp-block-heading">Ubuntu 24.04</h4>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><span role="button" tabindex="0" style="color:#D4D4D4;display:none" aria-label="Copy" class="code-block-pro-copy-button"><pre class="code-block-pro-copy-button-pre" aria-hidden="true"><textarea class="code-block-pro-copy-button-textarea" tabindex="-1" aria-hidden="true" readonly>apt list | grep php8.3-common</textarea></pre><svg xmlns="http://www.w3.org/2000/svg" style="width:24px;height:24px" fill="none" viewBox="0 0 24 24" stroke="currentColor" stroke-width="2"><path class="with-check" stroke-linecap="round" stroke-linejoin="round" d="M4.5 12.75l6 6 9-13.5"></path><path class="without-check" stroke-linecap="round" stroke-linejoin="round" d="M16.5 8.25V6a2.25 2.25 0 00-2.25-2.25H6A2.25 2.25 0 003.75 6v8.25A2.25 2.25 0 006 16.5h2.25m8.25-8.25H18a2.25 2.25 0 012.25 2.25V18A2.25 2.25 0 0118 20.25h-7.5A2.25 2.25 0 018.25 18v-1.5m8.25-8.25h-6a2.25 2.25 0 00-2.25 2.25v6"></path></svg></span><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">apt list | grep php8.3-common</span></span></code></pre></div>



<p class="wp-block-paragraph">If they have this version, they have the patch: 8.3.6-0ubuntu0.24.04.13</p>



<h3 class="wp-block-heading">Example Output (RHEL 9)</h3>



<div class="wp-block-kevinbatdorf-code-block-pro" data-code-block-pro-font-family="Code-Pro-Geist-Mono" style="font-size:.875rem;font-family:Code-Pro-Geist-Mono,ui-monospace,SFMono-Regular,Menlo,Monaco,Consolas,monospace;line-height:1.5rem;--cbp-tab-width:2;tab-size:var(--cbp-tab-width, 2)"><pre class="shiki dark-plus" style="background-color: #1E1E1E" tabindex="0"><code><span class="line"><span style="color: #D4D4D4">&#91;root@nagios-xi ~&#93;# php --version</span></span>
<span class="line"><span style="color: #D4D4D4"> PHP 8.0.30 (cli) (built: Oct 21 2026 15:47:44) ( NTS gcc x86_64 )</span></span>
<span class="line"><span style="color: #D4D4D4"> Copyright (c) The PHP Group</span></span>
<span class="line"><span style="color: #D4D4D4"> Zend Engine v4.0.30, Copyright (c) Zend Technologies</span></span>
<span class="line"><span style="color: #D4D4D4">    with Zend OPcache v8.0.30, Copyright (c), by Zend Technologies</span></span>
<span class="line"><span style="color: #D4D4D4">&#91;root@nagios-xi ~&#93;# rpm -q --changelog php-common | grep -i CVE-2026-10961</span></span>
<span class="line"><span style="color: #D4D4D4">  CVE-2026-109618, CVE-2026-109619</span></span></code></pre></div>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:16px;margin-bottom:0px"/>



<h2 class="wp-block-heading">Options to Safeguard Your Installations </h2>



<p class="wp-block-paragraph">Choose the option that fits your situation. For most PHP2Shell concerns, applying your Linux vendor’s security updates is the fastest and safest path.</p>



<h3 class="wp-block-heading">If You Need a PHP Upgrade for Security or Vulnerability Concerns</h3>



<p class="wp-block-paragraph">Keep in mind that Linux vendors backport security fixes into the PHP versions they ship, so an older version number does not always mean your system is vulnerable. Use the check above, or check with your Linux distribution vendor, to see if you need to upgrade your version of PHP.&nbsp;</p>



<p class="wp-block-paragraph">Contact your Linux distribution vendor for the proper method to update your version of PHP and stay inside the parameters listed in this article.&nbsp;</p>



<h3 class="wp-block-heading">If You Need a PHP Upgrade Within the Same Major Version</h3>



<p class="wp-block-paragraph">Nagios strongly recommends that you do not upgrade from one major version of PHP to another (for example, from PHP 7.x to PHP 8.x).</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">For example, if you are running Nagios XI on RHEL 8, with PHP 7.2, you can upgrade to anything from version 7.4 through the highest, available version of PHP 7.x, but do not upgrade to PHP 8.0 or above.</p>
</blockquote>



<p class="wp-block-paragraph">When Nagios performs the initial software installation, it depends on the major version of all the components that ship with that distribution. A PHP upgrade to a different major version can cause issues with the software, as well as with the OS itself.</p>



<h2 class="wp-block-heading">If You Need a PHP Upgrade to a Higher Major Version</h2>



<p class="wp-block-paragraph">To maintain the integrity of your installed version of Nagios software, migrate your XI instance to a newer release of your Linux distribution that installs the major PHP version you need.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">For example, if you are on RHEL 8, running PHP 7.4 and wish to upgrade to PHP 8.3, back up your XI instance and restore it to a new RHEL 9 or RHEL 10 system. Then perform the PHP upgrade on the new instance to PHP 8.3. </p>



<p class="wp-block-paragraph">Related Reading: <a href="https://assets.nagios.com/downloads/nagiosxi/guides/administrator/sysmgmt.php#backuprestore" target="_blank" rel="noreferrer noopener">Backing Up And Restoring XI</a></p>
</blockquote>



<hr class="wp-block-separator has-alpha-channel-opacity" style="margin-top:24px;margin-bottom:0px"/>



<h2 class="wp-block-heading">Before Any PHP Upgrade&nbsp;</h2>



<p class="wp-block-paragraph">It is important to perform all PHP upgrades in your test environment before your production environment and take a snapshot or clone of your virtual machine so you can roll back if you encounter any problems.&nbsp;</p>



<p class="wp-block-paragraph">After making a PHP upgrade, make sure to install the latest SourceGuardian loaders for the new version. See: <a href="https://library.nagios.com/docs/nagios-xi/installation/Nagios-XI-Installing-Latest-SourceGuardian-Loaders" target="_blank" rel="noopener">Nagios XI – Installing Latest SourceGuardian Loaders</a>.&nbsp;</p>



<p class="wp-block-paragraph">We are monitoring this situation and will provide updates as more information becomes available.</p>



<h3 class="wp-block-heading">Additional Resources</h3>



<ul class="wp-block-list">
<li><a href="https://assets.nagios.com/downloads/nagiosxi/guides/administrator/systemconfig.php#bestpractices" target="_blank" rel="noopener">Nagios XI Best Practices</a></li>



<li><a href="https://library.nagios.com/docs" target="_blank" rel="noreferrer noopener">Nagios Documentation Hub</a></li>



<li><a href="https://support.nagios.com/forum" target="_blank" rel="noopener">Nagios Support Forum</a></li>
</ul>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>How to Switch Nagios XI to the Faster Compiled check_ncpa Plugin</title>
		<link>https://library.nagios.com/support-tips/switch-nagios-xi-to-check-ncpa-plugin/</link>
		
		<dc:creator><![CDATA[Craig Dienger]]></dc:creator>
		<pubDate>Tue, 13 Oct 2026 18:05:47 +0000</pubDate>
				<category><![CDATA[Support Tips]]></category>
		<category><![CDATA[CCM]]></category>
		<category><![CDATA[Command Line]]></category>
		<category><![CDATA[NCPA]]></category>
		<category><![CDATA[Plugins]]></category>
		<category><![CDATA[Python]]></category>
		<guid isPermaLink="false">https://library.nagios.com/?p=70777</guid>

					<description><![CDATA[As of Nagios XI 2026R1.7, there is an option to use either the legacy Python version of check_ncpa.py or a new compiled version of check_ncpa, the plugin Nagios XI uses to run checks against the Nagios Cross-Platform Agent (NCPA). The new binary version has been shown to execute much faster, should be a command-line match [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">As of <a href="https://www.nagios.com/changelog/nagios-xi/2026r1-7/" target="_blank" rel="noopener">Nagios XI 2026R1.7</a>, there is an option to use either the legacy Python version of check_ncpa.py or a new compiled version of check_ncpa, the plugin Nagios XI uses to run checks against the Nagios Cross-Platform Agent (NCPA). The new binary version has been shown to execute much faster, should be a command-line match with the Python version, and should work as a drop-in replacement.</p>



<h2 class="wp-block-heading">Performance Comparison</h2>



<p class="wp-block-paragraph">Below are screenshots of the top output of a lab machine configured with approximately 13,000 checks running <code>check_ncpa.py</code>:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="975" height="397" src="https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa.py_.png" alt="Screenshot of the top output of a lab machine configured with approximately 13,000 checks running check_ncpa.py" class="wp-image-70825" title="How to Switch Nagios XI to the Faster Compiled check_ncpa Plugin 6" srcset="https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa.py_.png 975w, https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa.py_-300x122.png 300w, https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa.py_-768x313.png 768w" sizes="(max-width: 975px) 100vw, 975px" /><figcaption class="wp-element-caption">Screenshot of the top output of check_ncpa.py</figcaption></figure>



<p class="wp-block-paragraph">And the same machine running the compiled version of <code>check_ncpa</code>:</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="975" height="364" src="https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa.png" alt="Screenshot of the top output of compiled version of check_ncpa" class="wp-image-70828" title="How to Switch Nagios XI to the Faster Compiled check_ncpa Plugin 7" srcset="https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa.png 975w, https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa-300x112.png 300w, https://library.nagios.com/wp-content/uploads/2026/10/top-output_check_ncpa-766x286.png 766w" sizes="(max-width: 975px) 100vw, 975px" /><figcaption class="wp-element-caption">Screenshot of the top output of compiled version of check_ncpa</figcaption></figure>



<h2 class="wp-block-heading">Before You Begin</h2>



<p class="wp-block-paragraph">The new binary version is being configured by default on new installations of XI 2026R1.7. Upgraded systems keep the Python version by default so that customers can decide to opt in if they have not made any customizations to the Python version of the plugin.</p>



<p class="wp-block-paragraph">If you want to test the new version of check_ncpa on your upgraded system or switch back to using the Python version, please use the steps below.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
<p class="wp-block-paragraph">As always, we recommend testing the script in your test environment prior to using it in production.</p>
</blockquote>



<p class="wp-block-paragraph">Please note that if you are running Nagios Mod-Gearman (NMG) checks, we recommend waiting for&nbsp;a future version as the current version does not work properly with NMG.</p>



<h2 class="wp-block-heading">Switching to the Compiled check_ncpa Plugin</h2>



<ol class="wp-block-list">
<li>Before making changes, back up your current configuration. Navigate to <strong>Core Configuration Manager (CCM)</strong> <strong>&gt; Quick Tools &gt;</strong> <strong>Configuration Snapshots</strong> and confirm a recent snapshot is listed. If the switch causes problems, you can restore this snapshot to return to your previous configuration.</li>



<li>Navigate to&nbsp;<strong>Configure &gt; Core Config Manager</strong> <strong>&gt; Commands &gt; Commands</strong>&nbsp;in the Nagios XI web interface.</li>



<li>Search for&nbsp;<code>check_xi_ncpa</code> and click the <strong>Edit</strong> icon.</li>
</ol>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="1430" height="461" src="https://library.nagios.com/wp-content/uploads/2026/10/XI-Commands.png" alt="XI Commands" class="wp-image-70829" title="How to Switch Nagios XI to the Faster Compiled check_ncpa Plugin 8" srcset="https://library.nagios.com/wp-content/uploads/2026/10/XI-Commands.png 1430w, https://library.nagios.com/wp-content/uploads/2026/10/XI-Commands-300x97.png 300w, https://library.nagios.com/wp-content/uploads/2026/10/XI-Commands-1024x330.png 1024w, https://library.nagios.com/wp-content/uploads/2026/10/XI-Commands-766x247.png 766w" sizes="(max-width: 1430px) 100vw, 1430px" /><figcaption class="wp-element-caption">Screenshot of the Commands page in Nagios XI searching for check_xi_ncpa and editing the command.</figcaption></figure>



<ol start="4" class="wp-block-list">
<li>Change the <strong>Command Line</strong> from <code>$USER1$/check_ncpa.py</code> to&nbsp;<code>$USER1$/check_ncpa</code>, leaving the remainder of the command intact.</li>
</ol>



<p class="wp-block-paragraph">This will force the checks to use the new version of check_ncpa.</p>



<figure class="wp-block-image size-full"><img loading="lazy" decoding="async" width="624" height="359" src="https://library.nagios.com/wp-content/uploads/2026/10/CommandManagement-CommandLine.png" alt="Command Management screen in Nagios XI." class="wp-image-70830" title="How to Switch Nagios XI to the Faster Compiled check_ncpa Plugin 9" srcset="https://library.nagios.com/wp-content/uploads/2026/10/CommandManagement-CommandLine.png 624w, https://library.nagios.com/wp-content/uploads/2026/10/CommandManagement-CommandLine-300x173.png 300w" sizes="(max-width: 624px) 100vw, 624px" /><figcaption class="wp-element-caption">Command Management screen in Nagios XI.</figcaption></figure>



<ol start="5" class="wp-block-list">
<li>Click <strong>Save</strong>, then click <strong>Apply Configuration</strong>.</li>
</ol>



<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" width="1024" height="192" src="https://library.nagios.com/wp-content/uploads/2026/10/Commands-ApplyConfiguration-1024x192.png" alt="Commands ApplyConfiguration" class="wp-image-70831" title="How to Switch Nagios XI to the Faster Compiled check_ncpa Plugin 10" srcset="https://library.nagios.com/wp-content/uploads/2026/10/Commands-ApplyConfiguration-1024x192.png 1024w, https://library.nagios.com/wp-content/uploads/2026/10/Commands-ApplyConfiguration-300x56.png 300w, https://library.nagios.com/wp-content/uploads/2026/10/Commands-ApplyConfiguration-767x144.png 767w, https://library.nagios.com/wp-content/uploads/2026/10/Commands-ApplyConfiguration.png 1428w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption class="wp-element-caption">Apply Configuration Commands page in Nagios XI. </figcaption></figure>



<h2 class="wp-block-heading">Switching Back to the Python Version</h2>



<p class="wp-block-paragraph">To switch back to the Python version, repeat steps 2-5 and change <code>$USER1$/check_ncpa</code> back to&nbsp;<code>$USER1$/check_ncpa.py</code>.</p>



<h2 class="wp-block-heading">Conclusion</h2>



<p class="wp-block-paragraph">The compiled check_ncpa plugin lets your Nagios XI server run the same NCPA checks with significantly less overhead, freeing capacity to monitor more of your environment on existing hardware. Because the change applies to every service using the check_xi_ncpa command, validate it in a test environment and take a configuration snapshot before switching production systems. If you need to return to the original plugin, switching back takes only a single command edit.</p>



<p class="wp-block-paragraph">Looking for more ways to get the most out of Nagios XI? Browse the <a href="https://library.nagios.com/" target="_blank" rel="noreferrer noopener">Nagios Library</a> for documentation and how-to guides, or visit <a href="https://support.nagios.com/" target="_blank" rel="noreferrer noopener">Nagios Support</a> if you have questions about switching to the compiled plugin.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
