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} ---
stat("/home/build/build-home/kimono/lib/tls/x86_64",
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?
