- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2024 02:58 AM
Hi,
I have this warning in the Service Mapping Discovery Log, during the Pre Pattern Execution:
2024-10-30 08:47:01: script: ProcessInfoLinux - message: Process not found in cmdb
The Service Mapping process continues after this, but not being able to initiate the correct pattern (I know there's a Tomcat server on it).
I think this later step is dependant on the above:
Lightweight identification for Tomcat
2024-10-30 08:47:13: setAttribute(process,null)
What type of Process Info is it not able to find?
I have been searching script includes and so forth, but not been able to find the source. What script is producing this warning?
Anyone else has this?
Best regards, /Johan
Solved! Go to Solution.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2024 11:49 AM
Please, check the "input" from the ADM probe, in the payload there should be information for the running processes and also for the open ports, I have faced some permission issues on Windows where the ports were not collected. Usually if there is an error executing the command it will be in the payload.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2024 05:19 AM
Hi, did you check the PID, is there a process classifier defined
Best regards
Surya Prakash Garg
Connect me on Linked In
https://www.linkedin.com/in/spgarg/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2024 07:08 AM
I have the same issue. It looks like I am missing the actual script from the high level. I have a CS on HI open on it right now, it just got picked up by support. I'll let you know where we land.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2024 07:26 AM
Hi,
1. Do you have the server on which the Tomcat is running discovered in the CMDB?
2. Do you have the ADM enabled and running processes tab is populated with data on the server.
3. Check if there is a process listening on that port which you use for entry point.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2024 10:54 AM
Hi,
1. Server is discovered and Tomcat is discovered (Lightweight, but this should not make a difference).
2. ADM is enabled and Running Processes tab contains refreshed data for the server.
3. The "Listening on" field is empty though (in the Running Processes tab). Expecting port 16000+16001, but no, it's empty.
