topic Re: Qualys Technology Add on Error in All Apps and Add-ons

Qualys Technology Add on Error

manish_singh_77 — Tue, 24 Mar 2020 12:46:00 GMT

Hi @lakshman239

We have installed "Qualys TA" in our HF instance, configured the credentials and data inputs for "fim events" but when we search the events in our search head it doesn't show up.

We get this error message : [idx-123-abc.splunkcloud.com] Search process did not exit cleanly, exit_code=255, description="exited with code 255". Please look in search.log for this peer in the Job Inspector for more info.

Re: Qualys Technology Add on Error

richgalloway — Tue, 24 Mar 2020 13:12:57 GMT

What did you find in search.log?

Re: Qualys Technology Add on Error

manish_singh_77 — Wed, 25 Mar 2020 04:54:26 GMT

Nothing much

Re: Qualys Technology Add on Error

manish_singh_77 — Wed, 25 Mar 2020 05:40:09 GMT

@richgalloway @lakshman239

Do we need to install "Qualys TA Add On" on both HF and SH in the distributed environment?

We would like to see only "FIM Events" in SH.

Re: Qualys Technology Add on Error

richgalloway — Wed, 25 Mar 2020 12:52:35 GMT

The app's page on splunkbase has a link for support. I suggest you contact them.

Re: Qualys Technology Add on Error

manish_singh_77 — Thu, 26 Mar 2020 07:13:21 GMT

@richgalloway @lakshman239

I am getting this error message now in the Search Head:

[MainThread] ERROR: Error in connection: [Errno -5] No address associated with hostname . Sleeping for 300 seconds and retrying. Retry count: 3

Re: Qualys Technology Add on Error

manish_singh_77 — Thu, 26 Mar 2020 08:57:09 GMT

@richgalloway @lakshman239

Issue got resolved, credentials and api url was not correct. After entering the correct information, it worked.

Re: Qualys Technology Add on Error

manish_singh_77 — Thu, 26 Mar 2020 08:57:19 GMT

Issue got resolved, credentials and api url was not correct. After entering the correct information, it worked.

Re: Qualys Technology Add on Error

manish_singh_77 — Thu, 26 Mar 2020 08:58:03 GMT

Issue got resolved, credentials and api url was not correct. After entering the correct information, it worked.