TERMINATED THE PROBE BECAUSE THE MAX TIMEOUT WAS EXCEEDED: 60 SECONDS.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2024 03:12 PM
Hello experts,
When discovering some Linux servers, I get this as FQDN:
TERMINATED THE PROBE BECAUSE THE MAX TIMEOUT WAS EXCEEDED: 60 SECONDS.
I debugged the pattern and in step 8.1. Run FQDN script file, I didn't get anything as output when I clicked on Run Operation. Is this because the FQDN or Domain name don't exist on the server? The scrip file that searches for domain name is "linux_fqdn.sh".
Thank you for providing feedbacks.
bk
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2024 08:13 AM
Hi @BK14 ,
Good Day !!
You can modifiy the using the Mid Server Properties.
- Navigate to MID Server > Servers.
- From the list of MID Servers, select a MID Server to configure.
- Select the Configuration Parameters related list and click New.
- Refer the attached screenshot.
- Restart the MID Server, Also refer the Docs URL given below.
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024
Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
Thanks
AJ
Linkedin Profile:- https://www.linkedin.com/in/ajay-kumar-66a91385/
ServiceNow Community Rising Star 2024

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-05-2024 06:26 AM
Hi Ajay,
Thank you for the useful information you gave me. I will keep them for future references.
My issue is resolved. The problem actually came from the servers themselves. They did not have the FQDN in this config file: /etc/resolv.conf
They added and discovery updated the FQDN correctly now.
Thank you again,
bk