<?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 application is crashing in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460409#M3875</link>
    <description>&lt;P&gt;Hi Robert&lt;/P&gt;

&lt;P&gt;have you found the problem? &lt;BR /&gt;
Are the pathes in the crash.log always the same?&lt;BR /&gt;
Can you disable all inputs and receiving ports and restart the machine?&lt;/P&gt;</description>
    <pubDate>Sat, 04 Apr 2020 00:50:50 GMT</pubDate>
    <dc:creator>PavelP</dc:creator>
    <dc:date>2020-04-04T00:50:50Z</dc:date>
    <item>
      <title>Splunk application is crashing</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460406#M3872</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;P&gt;since two days my splunk application is crashing 5 minutes after starting the application.&lt;/P&gt;

&lt;P&gt;In the Splunkd.log I get the following error description:&lt;BR /&gt;
03-27-2020 13:00:16.418 +0100 ERROR StreamGroup - failed to drain remainder total_sz=59 bytes_freed=25106 avg_bytes_per_iv=425 sth=0x7fcb703feca0: [1585310416, /opt/splunk/var/lib/splunk/audit/db/hot_v1_27, 0x7fcb7570c650] reason=st_sync failed rc=-6 warm_rc=[-4,28]&lt;BR /&gt;
03-27-2020 13:00:16.434 +0100 ERROR StreamGroup - failed to add corrupt marker to dir=/opt/splunk/var/lib/splunk/audit/db/hot_v1_27 errno=No space left on device&lt;BR /&gt;
03-27-2020 13:00:16.454 +0100 ERROR BTreeCP - addUpdate: IOException caught: BTree::Exception: Record::writeLE failure in Node::_leafAddUpdate node offset: 24 order: 255 keys:&lt;BR /&gt;
03-27-2020 13:00:16.466 +0100 ERROR BTreeCP - failed: failed to mkdir /opt/splunk/var/lib/splunk/fishbucket/splunk_private_db/corrupt: No space left on device&lt;BR /&gt;
03-27-2020 13:00:16.466 +0100 ERROR IndexWriter - failed to add corrupt marker to path='/opt/splunk/var/lib/splunk/audit/db/hot_v1_27' (No space left on device)&lt;/P&gt;

&lt;P&gt;I checked the space on the disk and the disk areas are only 28 % in use. So there should be enough space on the disk. &lt;/P&gt;

&lt;P&gt;Does anyone have an ideas what is the issue of this problem.&lt;/P&gt;

&lt;P&gt;Thank you &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 04:46:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460406#M3872</guid>
      <dc:creator>robert_hausmann</dc:creator>
      <dc:date>2020-09-30T04:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk application is crashing</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460407#M3873</link>
      <description>&lt;P&gt;Can you post output of&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;df -h
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;df -i
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Do not redact or change anything if possible&lt;/P&gt;</description>
      <pubDate>Fri, 27 Mar 2020 22:59:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460407#M3873</guid>
      <dc:creator>PavelP</dc:creator>
      <dc:date>2020-03-27T22:59:38Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk application is crashing</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460408#M3874</link>
      <description>&lt;P&gt;output of df  -h&lt;BR /&gt;
Filesystem                   Size  Used Avail Use% Mounted on&lt;BR /&gt;
devtmpfs                      16G  8.0K   16G   1% /dev&lt;BR /&gt;
tmpfs                         16G     0   16G   0% /dev/shm&lt;BR /&gt;
tmpfs                         16G  644K   16G   1% /run&lt;BR /&gt;
tmpfs                         16G     0   16G   0% /sys/fs/cgroup&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /tmp&lt;BR /&gt;
/dev/xvda1                   976M   31M  895M   4% /boot&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /global/local&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /var/opt&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /var/tmp&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /opt&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /.snapshots&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /var/log&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /var/spool&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /home&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /lfs&lt;BR /&gt;
/dev/xvda2                    93G   26G   67G  28% /var/cache&lt;/P&gt;

&lt;P&gt;output df -i&lt;/P&gt;

&lt;P&gt;Filesystem                     Inodes     IUsed     IFree IUse% Mounted on&lt;BR /&gt;
devtmpfs                      4026057    369   4025688    1% /dev&lt;BR /&gt;
tmpfs                            4027707      2   4027705    1% /dev/shm&lt;BR /&gt;
tmpfs                           4027707     497   4027210    1% /run&lt;BR /&gt;
tmpfs                           4027707      16   4027691    1% /sys/fs/cgroup&lt;BR /&gt;
/dev/xvda2                          0           0         0     - /&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /tmp&lt;BR /&gt;
/dev/xvda1                      65536      324     65212    1% /boot&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /global/local&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /var/opt&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /var/tmp&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /opt&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /.snapshots&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /var/log&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /var/spool&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /home&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /lfs&lt;BR /&gt;
/dev/xvda2                          0     0         0     - /var/cache&lt;/P&gt;</description>
      <pubDate>Mon, 30 Mar 2020 08:05:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460408#M3874</guid>
      <dc:creator>robert_hausmann</dc:creator>
      <dc:date>2020-03-30T08:05:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk application is crashing</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460409#M3875</link>
      <description>&lt;P&gt;Hi Robert&lt;/P&gt;

&lt;P&gt;have you found the problem? &lt;BR /&gt;
Are the pathes in the crash.log always the same?&lt;BR /&gt;
Can you disable all inputs and receiving ports and restart the machine?&lt;/P&gt;</description>
      <pubDate>Sat, 04 Apr 2020 00:50:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-application-is-crashing/m-p/460409#M3875</guid>
      <dc:creator>PavelP</dc:creator>
      <dc:date>2020-04-04T00:50:50Z</dc:date>
    </item>
  </channel>
</rss>

