topic Re: Why am I getting error "Configuration initialization for {Path} took longer than expected when dispatching a search"? in Splunk Search

Why am I getting error "Configuration initialization for {Path} took longer than expected when dispatching a search"?

himapate — Thu, 17 Dec 2015 21:36:58 GMT

The following error is displayed can't figure any solution need help.

Configuration initialization for {Path} took longer than expected when dispatching a search

Re: Why am I getting error "Configuration initialization for {Path} took longer than expected when dispatching a search"?

jkat54 — Fri, 18 Dec 2015 10:48:47 GMT

When you create a search, it creates a "search bundle" that contains all the knowledge objects associated with that search (lookups, etc.).

{PATH} should have been populated with a file system path to the bundle.

My guess is you have bad file system permissions and need to recursively chown your splunk directory and insure the proper user is running splunk.

Re: Why am I getting error "Configuration initialization for {Path} took longer than expected when dispatching a search"?

himapate — Fri, 18 Dec 2015 18:14:27 GMT

Hi ,

Thanks for your reply

As you mentioned " Proper user is running splunk" By which user should i login inorder to avoid this error message.

Re: Why am I getting error "Configuration initialization for {Path} took longer than expected when dispatching a search"?

jkat54 — Tue, 29 Nov 2016 06:02:01 GMT

The user that the SplunkD service is running as.

Many times in linux, people start splunk as root one day and as splunk the next. Well files will then be owned by root user and the splunk user can't modify those files then.

Re: Why am I getting error "Configuration initialization for {Path} took longer than expected when dispatching a se

rmanrique — Thu, 09 Jul 2020 16:26:16 GMT

But finally how do I solve this problem?