Commander
Commander
827 views

Agent driven Inventory manual deployment

Hello all,

I'd like to know if it's possible to manually deploy the UDA in agent driven mode on a windows pc.

I've tried to follow the documentation and I've installed the UDA first, then I've inserted the registry keys

into : HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hewlett-Packard\Universal Discovery\V1\Options in particular SCHEDULER_Enabled to True and the probe restapi info in SCHEDULER_ProbeBaseURL.

But when I look into the discagnt.log I see this error reported every few seconds:

05-22-19 13:43:51: Warning: The key pass is empty, the agent might not be installed properly.
05-22-19 13:48:54: Error: can't open file 'c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\scanschedule.txt' (error 2: the system cannot find the file specified.)
05-22-19 13:48:54: Warning: No valid scan schedule found in schedule file (c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\scanschedule.txt)

Where I can get ahold of the scanschedule.txt file? Is there a template which can be provided to leverage from? 

What is the error related to the key pass is empty about?

Are there any missing steps to have the full functionality in place ?

Thanks so much in advance for the help

Roberto 

 

    •  
0 Likes
16 Replies
Captain Captain
Captain

Hi Roberto,

Have you created scanschedule.txt manually or auto created. It suppose to create automatically. Try to check port from UCMDB probe to target machine on 2738 and from target machine to probe on 9443 port. Also have done the configuration changes on probe server to make the agent driven discovery to be happen?

 

Regards

Annindya

0 Likes
Commander
Commander

Hi Annindya,

I've enabled Agent driven inventory discovery job but nothing seems to run , no ci reported. So you mean that this job should be the one in charge to deliver scanschedule.txt to the targeted client?

Which are the modification you mention to be made on probe side?

Regarding the ports do you mean that I should check if the ports are opened between probe and clients?             Other jobs such as Inventory discovery by scanner works perfectly on this client ...

What about the error about the key pass?

 

thanks

Roberto

0 Likes
Captain Captain
Captain

Hi Roberto,

 

for agentdriven first need to modify the DataFlowProbe.properties file with below parameter.

"com.hp.ucmdb.discovery.probe.agents.probegw.agentdrivenflow.twowayssl.enable=true

com.hp.ucmdb.discovery.probe.agents.probegw.agentdrivenflow.custom.port=9443"

Regards

Annindya

 

0 Likes
Commander
Commander

Hi Annindya,

I've read what you describe regarding the probe configuration file modification in the section related to deployment via discovery job here:

https://docs.microfocus.com/itom/Universal_CMDB:11.0/dfm/Agent_Deploy_smart_jobs 

what I'm referring to is a MANUAL deployment such as in :

https://docs.microfocus.com/itom/Universal_CMDB:11.0/dfm/Agent_Deploy_smart_Manual

You mean that that prerequisite should be met also in this case? So why the documentation doesn't mentioned this ? 😞

thanks

Roberto

0 Likes
Lieutenant
Lieutenant

Did you manage to fix this issue?

I am testing out the agent driven agent and experiencing the same issues as yourself.

Thanks

Liam

0 Likes
Commander
Commander

Hello,

the 2 prerequisites are to modify these 2 parameters :

"com.hp.ucmdb.discovery.probe.agents.probegw.agentdrivenflow.twowayssl.enable=true

com.hp.ucmdb.discovery.probe.agents.probegw.agentdrivenflow.custom.port=9443"

in configuration probe file DataFlowProbe.properties 

then restart the probe.

This error is in fact a wrong waming/alert should even be avoided in my opinion :

 Warning: The key pass is empty, the agent might not be installed properly.

If you have correctly installed and configured the client , through the adid job all the needed files included

scheduler.txt containing the frequency that you've set at job level is downloaded and everything should work.

 

I suggest you also to follow this article , especially the debugging part :

https://docs.microfocus.com/UCMDB/11.0/cp-docs/docs/eng/doc_lib/Content/Agent_driven_inventory_troubleshooting.htm

If you still have issues feel free to post here all the relevant files and I can try to help you troubleshooting

regards

Roberto

Commodore
Commodore

Hello Roberto,
I've got thesame issue - the agent can't get scheduler.txt file with the same error. I've only started the agid job with no changes (I rely on default part of AgentDrivenInventoryConfiguration.xml, and actually i did try custom things here too), then I installed the agent manually with that probe as callback, regedit - added SCHEDULER_ProbeBaseURL = https://probe:9443/rest/agent/, SCHEDULER_Enabled = True, the probe config contains 2 entries you mentioned oob. If i restart the agent service - the error about scheduler.txt file appears.
---------------
08-18-20 14:42:59: Universal Discovery Agent 11.50.000 (build: 524) starting ...
08-18-20 14:42:59:
08-18-20 14:43:02: Using listen port set to: 2738
08-18-20 14:43:02: Error: can't open file 'c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\scanschedule.txt' (error 2: the system cannot find the file specified.)
08-18-20 14:43:02: Warning: No valid scan schedule found in schedule file (c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\scanschedule.txt)
--------------
Increasing the log levels do not help. I see one weak point - if i do:
C:\UCMDB\DataFlowProbe\bin\jre\bin>keytool.exe -list -v -keystore C:\UCMDB\DataFlowProbe\conf\security\ProbeTrustStore.jks -storepass logomania

...it says smartagent alies is valid till 2018. Even if i download it from the microfocus url. Do you have the same thing? Is it still in use as documented or not? Maybe i messed some step in configuration?

the agent certificates are ok - i used this agent with remote triggering.
I also tried on 2018.8 and 2019.05 versions - same picture.
Thank you,
Dima.


0 Likes
Commodore
Commodore

It looks like this thing was required:
com.hp.ucmdb.discovery.probe.agents.probemgr.agentdrivenflow.enabled to true.
from https://docs.microfocus.com/itom/Universal_CMDB:11.0/dfm/Agent_Deploy_smart_Manual

and certificate re-generation:
https://docs.microfocus.com/UCMDB/2018.08/ucmdb-docs/docs/eng/doc_lib/Content/hardening/Agent_driven_inventory_discovery_create_cert.htm

only with these two things it happened to work on 2019.05
0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Hi Dima, Roberto,

I am facing the same issues as desribed above:

- Error: can't open file "...\scanschedule.txt"

- Warning: No valid scan file found in schedule file [...]

- Warning: The keypass is empty, the agent might not be installed properly

 

Also, I followed all your suggestions (probe config, certificate re-generation, etc.), but still the errors / warnings are present.

Did you need to enable the Agent Driven Inventory Discovery job in UCMDB UI to make this work?
Did you install the UDA manually (as I did) or finally used the Install/Update UDA job?

Is there any configuration on the UCMDB Server side necessary?

Thanks and BR

Niklas

0 Likes
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Edit: Please find below the relevant messages from agent log file, after raising to debug level for scanscheduler (as described here: https://docs.microfocus.com/UCMDB/11.0/cp-docs/docs/eng/doc_lib/Content/Agent_driven_inventory_troubleshooting.htm).

Probe names, URLs etc. anonymized:

01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Scan scheduler configuration: Enabled: true, ProbeBaseURL: https://probefqdn:9443/rest/agent/, UseHTTP: false; ProbeBaseUrl2: , ProbeBaseUrl3: . Check Interval 300 seconds.
01-05-21 11:26:02: Error: can't open file 'c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\scanschedule.txt' (error 2: the system cannot find the file specified.)
01-05-21 11:26:02: Warning: No valid scan schedule found in schedule file (c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\scanschedule.txt)
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) No schedule is eligible to run currently.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Some resource(s) is missing, trying to download it.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Start to ping probe...
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Building URL: https://probefqdn:9443/rest/agent/ping.
01-05-21 11:26:02: Warning: The key pass is empty, the agent might not be installed properly.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) HTTPS channel would be used for probe pinging, 2 Way: true.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) HTTP proxy setting is ignored.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Ping request return code: 35.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Ping request finished in 0 seconds, response code 500.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Start to download latest resource.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Is scanner available: 0 (c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\scanner.exe).
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Is scan schedule available: 0.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Is PrePost script available: 0, c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\prescan.cmd.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Is PrePost script available: 0, c:\windows\syswow64\config\systemprofile\appdata\roaming\Micro Focus\Universal Discovery\Data\postscan.cmd.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Request meta of resource downloading: {"osdesc" : "Windows NT 6.2 (build 9200)","hostname" : "PROBENAME","agenttoken" : "","postscriptversion" : "","deviceplatform" : "win-x64","agentversion" : "11.60.000.584","uduniqueid" : "xxxxxxxxxxxxxxxxxxxxxxxx","prescriptversion" : "","scancfgversion" : [],"scannerversion" : "","scanscheduleversion" : ""}, 4 resource(s) changed.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Building URL: https://probefqdn:9443/rest/agent/getresources.
01-05-21 11:26:02: Warning: The key pass is empty, the agent might not be installed properly.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) HTTPS channel would be used for scan file uploading, 2 Way: true.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) HTTP proxy setting is ignored.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) DownloadLatestResource request return code: 35.
01-05-21 11:26:02: [ThreadID-11556]Runtime trace: (scanscheduler) Download latest resource finished in 0 seconds, response code 500, refresh UUID: 0.

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

Edit II: When also genereting the probe side log (to be setup in probeGwLog4j.properties , as described in troubleshoot section), I can see the java error:

java.security.cert.CertificateException: No subject alternative names present

This seems to be related to the hostnames / domain presented in the certificate. 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.