Splunk Dev

Splunk is trying to read /home/build during startup?


I have noticed that Splunk sometimes hangs on startup in one customer's enviroment, and when it does, it seems to be trying to access a directory in /home that doesn't make much sense. Here is the behavior and where it is hanging:

$ ps ax|grep splunk
32023 pts/0    S      0:00 /opt/splunk/bin/splunk start
32032 pts/0    S      0:00 python -u /opt/splunk/lib/python2.7/site-packages/splunk/clilib/cli.py _py_internal check-xml-files
32055 pts/0    S+     0:00 grep --color=auto splunk
$ strace -p 32032
Process 32032 attached
--- SIGCONT {si_signo=SIGCONT, si_code=SI_USER, si_pid=30777, si_uid=74782} ---

This seems to happen on many versions, but sometimes the directory name is different (It seems like a codename for the version).

Why is Splunk trying to access /home/build on a production installation?

0 Karma
Get Updates on the Splunk Community!

Optimize Cloud Monitoring

  TECH TALKS Optimize Cloud Monitoring Tuesday, August 13, 2024  |  11:00AM–12:00PM PST   Register to ...

What's New in Splunk Cloud Platform 9.2.2403?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.2.2403! Analysts can ...

Stay Connected: Your Guide to July and August Tech Talks, Office Hours, and Webinars!

Dive into our sizzling summer lineup for July and August Community Office Hours and Tech Talks. Scroll down to ...