I was in the same case than you respecting the requirements of Splunkit v3.2 with: - Firefox 17.0.10 on client-side - xvfb 1.1.1-48.107 on client-side - Python 2.6.8 on client-side and 2.6.6 on server-side - Splunk 6.1.0 206881 on server-side I was able to correct this freeze at "Setting up agent(s)" step by using another version of Splunk on server-side. With Splunk-6.0.13-278006, everything works fine ! Client log : [2017-03-01 11:44:28,473] ClientMain: Starting Pyro client with standalone=False, detach=False, and keep_alive=False [2017-03-01 11:44:28,473] ClientMain: Initializing PyroClient object [2017-03-01 11:44:28,473] ClientMain: Attempting to connect to server [2017-03-01 11:44:28,492] ClientMain: Fetching server properties [2017-03-01 11:44:28,545] ClientMain: Starting new agent thread [2017-03-01 11:44:28,545] AgentControl: Initializing agent thread 0 [2017-03-01 11:44:28,546] AgentControl: Connected to server, received id d2c0t [2017-03-01 11:44:28,546] AgentControl: Starting agent helper thread for agent thread 0 [2017-03-01 11:44:28,546] AgentControl: Received waiting status from agent helper thread 0 [2017-03-01 11:46:24,470] AgentControl: Setting up agent thread 0 [2017-03-01 11:46:24,571] AgentControl: Received setting up status from agent helper thread 0 Server log: [2017-03-01 11:43:53,067] ServerMain: Preparing server and test driver object [2017-03-01 11:43:53,067] TestDriver: Preparing Pyro test driver object [2017-03-01 11:43:53,067] TestDriver: Preparing results logger with CSV output enabled [2017-03-01 11:43:53,067] TestDriver: CSV fields: ['timestamp', 'unix_timestamp', 'test_name', 'test_class', 'host', 'thread', 'id', 'agent_run', 'client_run', 'elapsed', 'run_duration', 'username', 'event_count', 'result_count', 'time_to_first_event', 'time_to_search'] [2017-03-01 11:43:53,068] ServerMain: Starting pyro server thread [2017-03-01 11:43:53,074] ServerMain: Starting watchdog thread [2017-03-01 11:43:53,074] ServerMain: Starting in automatic mode [2017-03-01 11:43:53,074] ServerMain: Waiting for 1 agent(s) to connect [2017-03-01 11:44:28,546] TestDriver: User admin connected with id d2c0t from host splunktest.lan [2017-03-01 11:44:28,546] ServerMain: 1 agent(s) connected! [2017-03-01 11:44:28,546] SearchTestSetup: Reading scheduled_searches.txt for scheduled search strings, frequencies, and start/end times [2017-03-01 11:44:28,569] SearchTestSetup: Performing setup for the SplunkIt Search Test [2017-03-01 11:44:28,582] SearchTestSetup: Starting splunk, if not started already [2017-03-01 11:44:28,681] SearchTestSetup: Removing file monitors from previous runs, if applicable [2017-03-01 11:44:28,942] SearchTestSetup: Saving time range to bin/searchRecord.log, to be used later [2017-03-01 11:44:28,959] SearchTestSetup: Adding splunkit_searchtest index, OR, clean the splunkit_searchtest index if it already exists [2017-03-01 11:44:50,143] SearchTestSetup: Removing old saved seaches, including scheduled saved searches, from the server [2017-03-01 11:44:56,303] SearchTestSetup: Detected old scheduled searches from an incomplete search test run. Cleaning up old scheduled searches before proceeding [2017-03-01 11:45:24,305] SearchTestSetup: Creating new saved searches [2017-03-01 11:45:59,795] SearchTestSetup: Adding necessary conf file entries to prepare the Splunk instance for the Search test [2017-03-01 11:45:59,799] SearchTestSetup: Adding dashboards to server [2017-03-01 11:45:59,800] SearchTestSetup: Copying splunkit_results.xml dashboard to server [2017-03-01 11:45:59,812] SearchTestSetup: Copying splunkit_indexing_details.xml dashboard to server [2017-03-01 11:45:59,818] SearchTestSetup: Restarting splunk [2017-03-01 11:46:24,057] SearchTestSetup: Splunk restarted successfully [2017-03-01 11:46:24,058] SearchTestSetup: Adding file monitors for streaming data and final results (when available) [2017-03-01 11:46:24,422] TestDriver: Issuing setup command to all connected agents [2017-03-01 11:46:24,423] ServerMain: Setting up agent(s) ... View more