Connection timeout out for ADM probe- AIX server\Oracle db discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-24-2025 08:02 AM
I am working on having all our Oracle DB instances in cmdb and we made good progress but there is this one server\db when discovery is run server is discovered successfully but the Oracle DB on UNIX pattern does not launch. Its because it cant find the running processes on the server. there is connection timeout error when "AIX - Application Dependency Mapping" probe runs.
Had the Linux team verify the permission are same as other working servers, and they can run the same commands on the server using servicenow discovery user. NO Firewall restrictions. what could be the reason for this.
Tried increasing the ssh command timeout to 300000 but getting the same error.
Error; job finished with status ERROR: SSH channel 9 activity timeout in state ESTABLISHING. (timeout = 120000) com.snc.ssh.SSHTimer@1503f0d9 while in state ESTABLISHING; Channel unexpectedly closed while opening channelNo supported privileged command found, current user may be improperly configured on this host to run privileged commands, running as current user;
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-25-2025 08:05 AM - edited ‎01-25-2025 08:05 AM
Hi @Abdul Parveez ,
Below are my thoughts :
1) First thing to confirm, as the issue is seen only one server. The issue is not from Servicenow end for sure.
2 ) In order to troubleshoot the issue, I would look for a similar working aix server within the same IP range or data center. Spot out the differences between working server and non working server and the check for below things.
check if there is any firewall connection drop using traceroute command
check if the server is not loaded with high cpu usage or memory
check sudoer configuration and execute commands with your linux team on the cmd console.
Regards,
srinija
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2025 12:45 AM
1) Yes, issue only one one server\DB
2) Already did
2.a) Inside same Firewall and no blocking - Verified with security
2.b) Verified with AIX team and no issues on server w.r.t CPU\Memory
2.c) Mentioned it in initial post, had AIX team already compared permissions with working server and everything is same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2025 09:17 PM
This issue requires more hands on troubleshooting and logs history. i am not sure beyond this area .Good Luck!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-27-2025 09:43 PM
1) To start, make sure that the problem is limited to a single server. Without a certain, the problem is not with Servicenow.
2) I would search for a comparable operational Aix server in the same data center or IP range in order to troubleshoot the problem. Determine the distinctions between a functional and non-working server and look for the following.
Use the traceroute command to see whether there is a firewall connection loss.
Verify that the server is not overloaded with memory or CPU consumption.
Check the sudoer setup and use the cmd terminal to run commands with your Linux team.