Splunk DB Connect 2: Why am I getting a socket error trying to make a connection to a DB2 database?

[Federica_92]

Hi everyone,

I have updated from Splunk DB connect 1 (that was running fine) to DB connect 2 I got a few errors trying to pull data from the database.
DB2 is SUPER slow. It takes one hundred tries to even make a connection to the database.

I checked the splunkd.log errors and I got this:

  02-15-2016 16:22:33.742 +0000 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\mi_lookup.py""   File "C:\Program Files\Splunk\Python-2.7\Lib\logging\handlers.py", line 77, in emit
  02-15-2016 16:22:33.742 +0000 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\mi_lookup.py"" Traceback (most recent call last):

   02-15-2016 16:22:33.742 +0000 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\mi_lookup.py"" Logged from file health.py, line 186

   02-15-2016 16:22:33.742 +0000 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\mi_lookup.py"" WindowsError: [Error 32] The process cannot access the file because it is being used by another process

    02-15-2016 16:22:33.742 +0000 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\mi_lookup.py""     os.rename(self.baseFilename, dfn)

    02-15-2016 16:22:33.742 +0000 ERROR ExecProcessor - message from "python "C:\Program Files\Splunk\etc\apps\splunk_app_db_connect\bin\mi_lookup.py""     self.doRollover()

  02-15-2016 16:21:43.139 +0000 WARN  HttpListener - Socket error from 127.0.0.1 while accessing /servicesNS/nobody/splunk_app_db_connect/db_connect/connections/-/status: Winsock error 10053

Any clue? Thanks.

[davebrooking]

There is a similar question https://answers.splunk.com/answers/308062/splunk-db-connect-2-windowserror-error-32-the-proc.html#an.... I don't know about the winsock warning, but I suspect the ERRORs are to do with Splunk being able to rollover the py_health.log file ready for the next generation of the file.

Dave