Discovery Schedule status

[AishwaryaS1]

Discovery has been scheduled.

I received the errors like below snap attached.

Also received warnings as well:

Why should I received this type of logs.

[AishwaryaS1 · Accepted solution]

hi @Selva Arun 

From the discovery_credentials table, I've tested the credentials using ip address but the "Authentication Failed" popup appears. So using this way I've tested the credentials but I think the credentials were invalid. am I right? 

And due to this all this errors are appeared.

One more thing is there any way to resolved this credentials issue and errors while discovery schedule?

[Selva Arun]

If testing the credentials fails, it means either the account is locked out or the password is invalid. Please check with your Server Team/AD Team to unlock the account or reset the password.

Thank you,

Selva

If you believe the solution provided has adequately addressed your query, could you please **mark it as 'Helpful'** and **'Accept it as a Solution'**? This will help other community members who might have the same question find the answer more easily.

Thank you for your consideration.

[ChiranjeeviR]

Hi @AishwaryaS1 ,

please follow the below step for the cause and resolution.

Cause:

This is due to missing credential privileges being used by Discovery.  For Docker Virtualization discovery we require the credential to be root or the credential should be a member of the docker

group.  This is detailed in our product documentation here under the section User Privileges. 

Resolution:

Either use a root credential or add the user credential to the docker group by logging into the Linux server targeted by Discovery and running the command "sudo usermod -a -G user_name docker".

This will add Linux user with name "user_name" to the group "docker".

Thanks and Regards,

Chiranjeevi🇮🇳
Please mark as Correct Answer/Helpful, if applicable.

[AishwaryaS1]

Hi @ ChiranjeeviR 

Can below error will be resolved by using the above solution.

[code]Failed Exploring CI Pattern, Pattern name: <b>Docker Pattern</b>, Process ID: <b>2375</b>, To Check Pattern Log Press <a href="$sw_horizontal_discovery_log.do?discoLogId=468fae13971fc654825d39871153af1b&amp;saDiscoLogSysId=028fae13971fc654825d39871153af1b&amp;ipAddress=10.10.3.120&amp;pid=2375&amp;preExecution=eyJ1c2VGdWxsTWFuaWZlc3RJRCI6ImZhbHNlIiwidXNlRnVsbE1hbmlmZXN0SURUcnVuY2F0ZSI6ImZhbHNlIn0=&amp;host_sys_id=c2c520f987228150c0550edc0ebb3556&amp;host_name=sjc01eninfapp10&amp;patternId=dd15665a7fe022004e83e2065f2a0c57&amp;patternName=Docker Pattern&amp;patternType=1&amp;isCloud=false&amp;isHistoricalLog=true"><u><b>Here</b></u></a>[/code]