I was also getting errors like these, and the problem turned out to be that Splunk/Splunk_TA_vcenter doesn't fully respect use of the /etc/hosts file. You'll have to hard code the IP address in the collection configuration page, or presumably set up actual DNS. The errors I was getting: 2021-08-19 08:56:13,564 ERROR [ta_vmware_collection_worker://gamma:9861] Problem with hydra worker ta_vmware_collection_worker://gamma:9861: ('Could not login to target=%s with username=%s after num_retries=%s', 'vcenter6.local', 'administrator@vsphere.local', 3)
Traceback (most recent call last):
File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_worker.py", line 623, in run
self.assignJobToHandler(cur_job)
File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_worker.py", line 457, in assignJobToHandler
session = self.getSessionForTarget(job_tuple.target, config["username"], config["realm"])
File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_worker.py", line 425, in getSessionForTarget
session_stanza = self.updateSessionStanza(session_stanza, target, username, realm)
File "/opt/splunk/etc/apps/SA-Hydra/bin/hydra/hydra_worker.py", line 354, in updateSessionStanza
session = self.loginToTarget(target, username, password, realm)
File "/opt/splunk/etc/apps/Splunk_TA_vmware/bin/ta_vmware_collection_worker.py", line 55, in loginToTarget
raise Exception("Could not login to target=%s with username=%s after num_retries=%s", target, user, retry_count)
Exception: ('Could not login to target=%s with username=%s after num_retries=%s', 'vcenter6.local', 'administrator@vsphere.local', 3)
... View more