<?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: Unable to start splunk, failed with crash report in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-start-splunk-failed-with-crash-report/m-p/240769#M188839</link>
    <description>&lt;P&gt;Seeing anything in splunkd.log?&lt;/P&gt;

&lt;P&gt;This appears to be an issue with threads being unable to be opened from your crash report.&lt;/P&gt;

&lt;P&gt;42/45 doesn't seem inordinately high, but i would recommend opening a support ticket to see if there isn't something bigger wrong.&lt;/P&gt;

&lt;P&gt;one other thing you may want to look at is your ulimits for processes and files for the user splunk is running as.&lt;/P&gt;</description>
    <pubDate>Sat, 26 Sep 2015 20:47:59 GMT</pubDate>
    <dc:creator>scruse</dc:creator>
    <dc:date>2015-09-26T20:47:59Z</dc:date>
    <item>
      <title>Unable to start splunk, failed with crash report</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-start-splunk-failed-with-crash-report/m-p/240768#M188838</link>
      <description>&lt;P&gt;[build aa7d4b1ccb80] 2015-09-26 11:27:52&lt;BR /&gt;
Received fatal signal 6 (Aborted).&lt;BR /&gt;
 Cause:&lt;BR /&gt;
   Signal sent by PID 1039871 running under UID 1838232.&lt;BR /&gt;
 Crashing thread: PipelineAllocatorThread&lt;BR /&gt;
 Registers:&lt;BR /&gt;
    RIP:  [0x00000033F9432625] gsignal + 53 (/lib64/libc.so.6)&lt;BR /&gt;
    RDI:  [0x00000000000FDDFF]&lt;BR /&gt;
    RSI:  [0x00000000000FDE71]&lt;BR /&gt;
    RBP:  [0x0000000001F2DDA0]&lt;BR /&gt;
    RSP:  [0x00007FE0405FDAD8]&lt;BR /&gt;
    RAX:  [0x0000000000000000]&lt;BR /&gt;
    RBX:  [0x00007FE03FC2C178]&lt;BR /&gt;
    RCX:  [0xFFFFFFFFFFFFFFFF]&lt;BR /&gt;
    RDX:  [0x0000000000000006]&lt;BR /&gt;
    R8:  [0x000000000000000A]&lt;BR /&gt;
    R9:  [0x00007FE0405FE700]&lt;BR /&gt;
    R10:  [0x0000000000000008]&lt;BR /&gt;
    R11:  [0x0000000000000206]&lt;BR /&gt;
    R12:  [0x00007FE03FC3E040]&lt;BR /&gt;
    R13:  [0x00007FE03FC1E2B8]&lt;BR /&gt;
    R14:  [0x00000000018100CC]&lt;BR /&gt;
    R15:  [0x00007FE0510A4950]&lt;BR /&gt;
    EFL:  [0x0000000000000206]&lt;BR /&gt;
    TRAPNO:  [0x0000000000000000]&lt;BR /&gt;
    ERR:  [0x0000000000000000]&lt;BR /&gt;
    CSGSFS:  [0x0000000000000033]&lt;BR /&gt;
    OLDMASK:  [0x0000000000000000]&lt;/P&gt;

&lt;P&gt;OS: Linux&lt;BR /&gt;
 Arch: x86-64&lt;/P&gt;

&lt;P&gt;Backtrace:&lt;BR /&gt;
  [0x00000033F9432625] gsignal + 53 (/lib64/libc.so.6)&lt;BR /&gt;
  [0x00000033F9433E05] abort + 373 (/lib64/libc.so.6)&lt;BR /&gt;
  [0x00000000017FD12D] &lt;EM&gt;ZN9&lt;/EM&gt;&lt;EM&gt;gnu_cxx27&lt;/EM&gt;&lt;EM&gt;verbose_terminate_handlerEv + 285 (splunkd)&lt;BR /&gt;
  [0x00000000017B76D6] _ZN10&lt;/EM&gt;&lt;EM&gt;cxxabiv111&lt;/EM&gt;_terminateEPFvvE + 6 (splunkd)&lt;BR /&gt;
  [0x00000000017B7703] ? (splunkd)&lt;BR /&gt;
  [0x00000000017B898E] ? (splunkd)&lt;BR /&gt;
  [0x00000000010A016A] ? (splunkd)&lt;BR /&gt;
  [0x000000000109FCCC] _ZN6ThreadC2EPKcz + 588 (splunkd)&lt;BR /&gt;
[0x0000000000DB0B17] _ZN8PipelineC2ERK3StrRK15PluginProcessorPK7XmlNodeP13InThreadActorP11PipelineSet + 87 (splunkd)&lt;BR /&gt;
  [0x0000000000DB5775] _ZN23PipelineAllocatorThread4mainEv + 85 (splunkd)&lt;BR /&gt;
  [0x000000000109F0EE] _ZN6Thread8callMainEPv + 62 (splunkd)&lt;BR /&gt;
  [0x00000033F98079D1] ? (/lib64/libpthread.so.0)&lt;BR /&gt;
  [0x00000033F94E88DD] clone + 109 (/lib64/libc.so.6)&lt;BR /&gt;
 Linux / xxx.prod.sin2.secureserver.net / 2.6.32-531.29.2.lve1.3.11.10.el6.x86_64 / #1 SMP Fri Jun 12 15:09:02 EDT 2015 / x86_64&lt;BR /&gt;
 Last few lines of stderr (may contain info on assertion failure, but also could be old):&lt;BR /&gt;
    2015-09-26 11:26:07.692 -0700 splunkd started (build aa7d4b1ccb80)&lt;BR /&gt;
    terminate called after throwing an instance of 'ThreadException'&lt;BR /&gt;
      what():  Main Thread: about to throw a ThreadException: pthread_create: Resource temporarily unavailable; 45 threads active&lt;BR /&gt;
    2015-09-26 11:27:51.646 -0700 splunkd started (build aa7d4b1ccb80)&lt;BR /&gt;
    terminate called after throwing an instance of 'ThreadException'&lt;BR /&gt;
      what():  PipelineAllocatorThread: about to throw a ThreadException: pthread_create: Resource temporarily unavailable; 42 threads active&lt;/P&gt;

&lt;P&gt;glibc version: 2.12&lt;BR /&gt;
 glibc release: stable&lt;BR /&gt;
Last errno: 12&lt;BR /&gt;
Threads running: 42&lt;BR /&gt;
Runtime: 0.864909s&lt;BR /&gt;
argv: [splunkd -p 8089 start]&lt;BR /&gt;
Thread: "PipelineAllocatorThread", did_join=1, ready_to_run=Y, main_thread=N&lt;BR /&gt;
First 8 bytes of Thread token @0x7fff28fe9080:&lt;BR /&gt;
00000000  00 e7 5f 40 e0 7f 00 00                           |&lt;A href="mailto:.._@" target="_blank"&gt;.._@&lt;/A&gt;....|&lt;BR /&gt;
00000008&lt;/P&gt;

&lt;P&gt;x86 CPUID registers:&lt;BR /&gt;
         0: 0000000D 756E6547 6C65746E 49656E69&lt;BR /&gt;
         1: 000306E4 00200800 7FBEE3FF BFEBFBFF&lt;BR /&gt;
         2: 76036301 00F0B2FF 00000000 00CA0000&lt;BR /&gt;
         3: 00000000 00000000 00000000 00000000&lt;BR /&gt;
         4: 00000000 00000000 00000000 00000000&lt;BR /&gt;
         5: 00000040 00000040 00000003 00001120&lt;BR /&gt;
         6: 00000077 00000002 00000009 00000000&lt;BR /&gt;
         7: 00000000 00000000 00000000 00000000&lt;BR /&gt;
         8: 00000000 00000000 00000000 00000000&lt;BR /&gt;
         9: 00000001 00000000 00000000 00000000&lt;BR /&gt;
         A: 07300403 00000000 00000000 00000603&lt;BR /&gt;
         B: 00000000 00000000 000000FD 00000000&lt;BR /&gt;
 C: 00000000 00000000 00000000 00000000&lt;BR /&gt;
         &lt;span class="lia-unicode-emoji" title=":anguished_face:"&gt;😧&lt;/span&gt; 00000000 00000000 00000000 00000000&lt;BR /&gt;
  80000000: 80000008 00000000 00000000 00000000&lt;BR /&gt;
  80000001: 00000000 00000000 00000001 2C100800&lt;BR /&gt;
  80000002: 20202020 746E4920 52286C65 65582029&lt;BR /&gt;
  80000003: 52286E6F 50432029 35452055 3336322D&lt;BR /&gt;
  80000004: 76204C30 20402032 30342E32 007A4847&lt;BR /&gt;
  80000005: 00000000 00000000 00000000 00000000&lt;BR /&gt;
  80000006: 00000000 00000000 01006040 00000000&lt;BR /&gt;
  80000007: 00000000 00000000 00000000 00000100&lt;BR /&gt;
  80000008: 0000302E 00000000 00000000 00000000&lt;BR /&gt;
terminating...&lt;/P&gt;

&lt;P&gt;Any help!!&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:22:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unable-to-start-splunk-failed-with-crash-report/m-p/240768#M188838</guid>
      <dc:creator>jitsinha</dc:creator>
      <dc:date>2020-09-29T07:22:44Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to start splunk, failed with crash report</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-start-splunk-failed-with-crash-report/m-p/240769#M188839</link>
      <description>&lt;P&gt;Seeing anything in splunkd.log?&lt;/P&gt;

&lt;P&gt;This appears to be an issue with threads being unable to be opened from your crash report.&lt;/P&gt;

&lt;P&gt;42/45 doesn't seem inordinately high, but i would recommend opening a support ticket to see if there isn't something bigger wrong.&lt;/P&gt;

&lt;P&gt;one other thing you may want to look at is your ulimits for processes and files for the user splunk is running as.&lt;/P&gt;</description>
      <pubDate>Sat, 26 Sep 2015 20:47:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unable-to-start-splunk-failed-with-crash-report/m-p/240769#M188839</guid>
      <dc:creator>scruse</dc:creator>
      <dc:date>2015-09-26T20:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to start splunk, failed with crash report</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Unable-to-start-splunk-failed-with-crash-report/m-p/240770#M188840</link>
      <description>&lt;P&gt;index= earliest=-2d@d | stats count by host, _time | join host [search index= earliest=-2d@d | stats latest(_time) as latesttime by host | table host, latesttime] | eval lastTwoHrCount = if(_time&amp;lt;=now() AND _time&amp;gt;=now()-7200,count,0) | eval lastHrCountFrmLatestEvent = if(_time&amp;lt;=now() AND _time&amp;gt;=now()-7200,count,0) | stats sum(lastTwoHrCount) as lastTwoHrCount, max(lastHrCountFrmLatestEvent) as lastHrCountFrmLatestEvent by host | eval status = if(lastTwoHrCount==0 AND lastHrCountFrmLatestEvent&amp;lt;5000 ,"DOWN","UP") &lt;BR /&gt;
| table host,lastTwoHrCount,lastHrCountFrmLatestEvent,status &lt;BR /&gt;
| rename host as Host, lastTwoHrCount as "Last 2hrs Count", lastHrCountFrmLatestEvent as "Last Hour Count from LatestEvent", status as Status | fillnull&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 07:29:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Unable-to-start-splunk-failed-with-crash-report/m-p/240770#M188840</guid>
      <dc:creator>jitsinha</dc:creator>
      <dc:date>2020-09-29T07:29:33Z</dc:date>
    </item>
  </channel>
</rss>

