Deployment Architecture

Splunk Lightforwarder coredumping on Solaris SPARC

Path Finder

Any idea of what might be causing this error? I see it occur quite often, is this triggered splunk is restarting? it is filling up our /var/core directory.

uname -a

SunOS server 5.10 Generic_142909-17 sun4v sparc SUNW

root@server [/var/core]# mdb core_server_splunkd_10118_10115_1297852199_3760
mdb: core file data for mapping at ffffffff7d400000 not saved: Bad address
mdb: core file data for mapping at ffffffff7d414000 not saved: Bad address
Loading modules: [ libumem.so.1 libc.so.1 ld.so.1 ]
> ::status
debugging core file of splunkd (64-bit) from server
file: /opt/splunk/bin/splunkd
initial argv: splunkd -p 8089 restart
threading model: multi-threaded
status: process terminated by SIGABRT (Abort)
panic message: Assertion failed: _linkp == NULL, file /opt/splunk/p4/splunk/branches/prince/src/util/TimeoutHeap.cpp, line 21
> ::stack
libc.so.1`_lwp_kill+8(6, 0, 10122e438, ffffffffffffffff, ffffffff7d43c000, 0)
libc.so.1`abort+0x118(1, 1d8, 1003e71d4, 1f0dfc, 0, 0)
libc.so.1`_assert+0x74(100c994a8, 100c992e0, 15, 0, 1f0ab4, 100185378)
0x1003e71d4(0, ffff, 101208528, 1012ebed0, ffffffff7d449bc0, 1c00)
0x100185378(ffffffff7d449e40, ffffffff7d448240, 1c00, 101228000, 3, 0)
_fini+4(ffffffff7d449bc0, 1cc4, ffffffff7d448240, ffffffff76b03a00, ffffffff7d449bc0, 1c00)
libc.so.1`_exithandle+0x48(ffffffff7d449e40, ffffffff7d448240, 1c00, 101228000, 3, 0)
libc.so.1`exit+4(0, 100c5ba60, 168, 0, 0, 0)
_ZN5Killa4mainEv+0x40(1042d1000, 1005713fc, ffffffff76b03b58, 101228000, 3, 0)
_ZN6Thread8callMainEPv+0x80(0, 200000, 0, 0, 10055c884, 1)
libc.so.1`_lwp_start(0, 0, 0, 0, 0, 0)
Tags (2)
1 Solution

SplunkTrust
SplunkTrust

The most important line in that dump is:

panic message: Assertion failed: _linkp == NULL, file /opt/splunk/p4/splunk/branches/prince/src/util/TimeoutHeap.cpp, line 21

Failed assertions can suggest a bug of some sort. You should open a case with Splunk support.

View solution in original post

SplunkTrust
SplunkTrust

The most important line in that dump is:

panic message: Assertion failed: _linkp == NULL, file /opt/splunk/p4/splunk/branches/prince/src/util/TimeoutHeap.cpp, line 21

Failed assertions can suggest a bug of some sort. You should open a case with Splunk support.

View solution in original post

Path Finder

Thanks, I have filed a bug to Splunk support.

0 Karma
State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!