<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Splunk caused a kernel panic!  What do I do?? in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9779#M6329</link>
    <description>&lt;P&gt;It is unlikely that Splunk is at fault for a kernel panic.  Even though a kernel panic may be triggered by a Splunk installation and/or the error points to splunkd, the kernel panic is an indication of a bug in the kernel, not a bug in the installation software.&lt;/P&gt;

&lt;P&gt;You can take the information from the error to investigate.  For example, from the above, I performed the following search using Google.com:&lt;/P&gt;

&lt;P&gt;kernel panic 2.6.9-788.Elsmp&lt;/P&gt;

&lt;P&gt;The first url returned is the following RedHat article regarding a sys_times bug in the kernel &lt;/P&gt;

&lt;P&gt;"Bug 456993 -  kernel panic with kernel version 2.6.9-78.ELsmp"
&lt;A href="https://bugzilla.redhat.com/show_bug.cgi?id=456993" rel="nofollow"&gt;https://bugzilla.redhat.com/show_bug.cgi?id=456993&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Thu, 18 Feb 2010 03:17:27 GMT</pubDate>
    <dc:creator>the_wolverine</dc:creator>
    <dc:date>2010-02-18T03:17:27Z</dc:date>
    <item>
      <title>Splunk caused a kernel panic!  What do I do??</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9778#M6328</link>
      <description>&lt;P&gt;I tried installing Splunk today and it appears to have caused a kernel panic. See the kernel panic below:&lt;/P&gt;
&lt;PRE&gt;Pid: 23986, comm: splunkd Not tainted 2.6.9-78.ELsmp
RIP: 0010: [] (next_thread+12)
RAX: ...
RDX: ...



Process splunkd (pid: 23986, threadinfo 00000102e1e54000, task 0000010193d027f0)
Stack: ...

Call Trace:{sys_times+103} {sys_futex+203}
       {do_gettimeofday+77} {system_call+126}
}

Code: ...
RIP 
  Kernel panic - not syncing: Oops
&lt;/PRE&gt;
&lt;P&gt;Now what?&lt;/P&gt;</description>
      <pubDate>Tue, 23 Jun 2020 22:21:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9778#M6328</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2020-06-23T22:21:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk caused a kernel panic!  What do I do??</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9779#M6329</link>
      <description>&lt;P&gt;It is unlikely that Splunk is at fault for a kernel panic.  Even though a kernel panic may be triggered by a Splunk installation and/or the error points to splunkd, the kernel panic is an indication of a bug in the kernel, not a bug in the installation software.&lt;/P&gt;

&lt;P&gt;You can take the information from the error to investigate.  For example, from the above, I performed the following search using Google.com:&lt;/P&gt;

&lt;P&gt;kernel panic 2.6.9-788.Elsmp&lt;/P&gt;

&lt;P&gt;The first url returned is the following RedHat article regarding a sys_times bug in the kernel &lt;/P&gt;

&lt;P&gt;"Bug 456993 -  kernel panic with kernel version 2.6.9-78.ELsmp"
&lt;A href="https://bugzilla.redhat.com/show_bug.cgi?id=456993" rel="nofollow"&gt;https://bugzilla.redhat.com/show_bug.cgi?id=456993&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Feb 2010 03:17:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9779#M6329</guid>
      <dc:creator>the_wolverine</dc:creator>
      <dc:date>2010-02-18T03:17:27Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk caused a kernel panic!  What do I do??</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9780#M6330</link>
      <description>&lt;P&gt;I had a similar issue today on: Linux ip-10-166-215-67 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 x86_64 x86_64 GNU/Linux  with splunkforwarder-5.0.2-149561-Linux-x86_64.tgz.  &lt;/P&gt;

&lt;P&gt;$SPLUNK_HOME/bin/splunk start&lt;BR /&gt;&lt;BR /&gt;
Checking prerequisites...&lt;BR /&gt;&lt;BR /&gt;
        Checking mgmt port [8089]: open&lt;/P&gt;

&lt;P&gt;Message from syslogd@domU-12-31-38-04-18-9C at May 28 19:59:08 ...&lt;BR /&gt;
 kernel:[17884.833628] alignment check: 0000 [#7] SMP&lt;/P&gt;

&lt;P&gt;/var/log/dmesg shows... "splunk tainted"&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 14:00:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9780#M6330</guid>
      <dc:creator>rroberts</dc:creator>
      <dc:date>2020-09-28T14:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk caused a kernel panic!  What do I do??</title>
      <link>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9781#M6331</link>
      <description>&lt;P&gt;I also encountered similar issue with splunk 6.1.3 upgrade,  2.6.18-308.el5&lt;/P&gt;</description>
      <pubDate>Fri, 19 Sep 2014 03:57:13 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Splunk-caused-a-kernel-panic-What-do-I-do/m-p/9781#M6331</guid>
      <dc:creator>ppathik</dc:creator>
      <dc:date>2014-09-19T03:57:13Z</dc:date>
    </item>
  </channel>
</rss>

