I'm just installed Splunk 6.1 on a Mac with OS X 10.9.2, using splunk-6.1.0-206881-macosx-10.7-intel.dmg package and tried adding some data. Below is the crash report.
When I try to restart splunkd, it just crashes again after a little while with similar messages in the crash report. I also get these assertion failures and complaints about not being able to find the manifest file in the crash report:
2014-05-11 21:01:10.299 +1000 splunkd started (build 206881) Assertion failed: (n <= rawSize()), function removeStartOfRaw, file /Users/eserv/wrangler/build-src/6.1.0/src/framework/PipelineData.h, line 382. 2014-05-11 22:09:08.649 +1000 splunkd started (build 206881) Cannot open manifest file inside "/Applications/Splunk/var/lib/splunk/_internaldb/db/db_1398999122_1398999122_0/rawdata": No such file or directory Cannot open manifest file inside "/Applications/Splunk/var/lib/splunk/_introspection/db/db_1399806670_1399806670_0/rawdata": No such file or directory Assertion failed: (n <= rawSize()), function removeStartOfRaw, file /Users/eserv/wrangler/build-src/6.1.0/src/framework/PipelineData.h, line 382.
Thanks in advance,
[build 206881] 2014-05-11 21:33:09
Received fatal signal 6 (Abort trap: 6).
Unknown signal origin (sicode=0).
Crashing thread: parsing
RIP: [0x00007FFF8E3B3866] _pthreadkill + 10 (/usr/lib/system/libsystemkernel.dylib)
Backtrace (NOTE: symbols may be wrong -- dladdr() is unreliable on OS/X):
[0x00007FFF8DFB5B1A] abort + 125 (/usr/lib/system/libsystemc.dylib)
[0x00007FFF8DF7F98E] _assertrtn + 272 (/usr/lib/system/libsystemc.dylib)
[0x00000001058CE177] ZN12PipelineData16removeStartOfRawEm + 183 (/Applications/Splunk/bin/splunkd)
[0x00000001058CEF0C] _ZN27StructuredDataHeaderRemoverD0Ev + 2684 (/Applications/Splunk/bin/splunkd)
[0x0000000105E9C2F7] _ZNSt8RbtreeI3StrSt4pairIKS012CronIntervalESt10Select1stIS4ESt4lessIS0ESaIS4EE4findERS2_ + 9223 (/Applications/Splunk/bin/splunkd)
[0x00000001058CE9C2] ZN27StructuredDataHeaderRemoverD0Ev + 1330 (/Applications/Splunk/bin/splunkd)
[0x00000001058CD928] _ZN6FifoFdC2ER8PathnameR15CowPipelineDataP9EventLoopP18FifoInputProcessorR13PropertiesMap + 8392 (/Applications/Splunk/bin/splunkd)
[0x0000000105C76327] _ZN22PersistentCacheVersionD0Ev + 11223 (/Applications/Splunk/bin/splunkd)
[0x0000000105F8F692] _ZN35TcpOutboundTerminateExternallyActorD0Ev + 6034 (/Applications/Splunk/bin/splunkd)
[0x00007FFF8C7BB899] _pthreadbody + 138 (/usr/lib/system/libsystempthread.dylib)
[0x00007FFF8C7BB72A] _pthreadstructinit + 0 (/usr/lib/system/libsystempthread.dylib)
[0x00007FFF8C7BFFC9] threadstart + 13 (/usr/lib/system/libsystempthread.dylib
Hmm, I would try installing with the .tgz tar ball instead. I am not having trouble and that is what I used for my Mac. I'd also check permissions.
You should only start/stop Splunk as the same user who owns all the Splunk files. If you once started Splunk using root, then some of the file ownership may have changed. This is one way that permissions problems happen. You may want to use
chown -R to fix that.
I'd also check that your download wasn't corrupt. But if all of these suggestions fail, I'd submit a bug: at that point, I would guess that Splunk published a bad download package for the Mac.
OK. So I checked the md5sum against the .dmg package and they match. The chown -R wasn't necessary as the files are all owned by the right user.
So, I uninstalled and installed the .tgz tarball. I still get the same behaviour. After indexing the input files (about 1.5Gb worth - not sure if that is a problem given the 500Mb limit/day but it shouldn't crash the daemon), splunk crashed and when restarted, it crashes again within a few seconds. Errors are similar to my initial post.
Any help would be really appreciated!
Thanks for the suggestions. I started Splunk with the same user as the one that ran the installation. The strange thing is that Splunk was running fine while adding a few million events from the input files and then at some point splunkd crashed and from then would crash almost immediately after restarting. I tried reinstalling Splunk and the same sequence of events occurred.
I'll check the md5sum of the installer, running chown -R and if that doesn't shed any light, will try the .tgz tarball install.