CA Service Management

Hi All,

We have upgraded from 12.6 Service Desk to 12.9 and one of our application hosted on DMZ has an issue.

When tried to login gets the error "AHD04042 login failed for userid('userid'); login timed out"

I can see these errors in the logs, however i have uncommented NX_SLUMP_SECONDARY_SOCKET=2100 in our DMZ application and Backgroud server . Please suggest on how to get this resolved..

04/17 05:40:20.98 DMZServer slump_nxd 7524 ERROR ping_port.c 394 Unable to get address information for (Application Server) listener port (2100), getAddrInfo() error: The requested name is valid, but no data of the requested type was found.

04/17 05:40:21.01 DMZServer slump_nxd 7524 ERROR ping_port.c 394 Unable to get address information for (Application Server) listener port (2100), getAddrInfo() error: The requested name is valid, but no data of the requested type was found.

04/17 05:40:21.03 DMZServer slump_nxd 7524 ERROR ping_port.c 394 Unable to get address information for (Application Server) listener port (2100), getAddrInfo() error: The requested name is valid, but no data of the requested type was found.

04/17 05:40:21.05 DMZServer slump_nxd 7524 ERROR ping_port.c 394 Unable to get address information for (Application Server) listener port (2100), getAddrInfo() error: The requested name is valid, but no data of the requested type was found.

04/17 05:40:21.06 DMZServer slump_nxd 7524 ERROR ping_port.c 394 Unable to get address information for (Application Server) listener port (2100), getAddrInfo() error: The requested name is valid, but no data of the requested type was found.

04/17 05:40:21.08 DMZServer slump_nxd 7524 ERROR ping_port.c 394 Unable to get address information for (Application Server) listener port (2100), getAddrInfo() error: The requested name is valid, but no data of the requested type was found.

04/17 05:40:27.92 DMZServer pdm_rfbroker_nxd 7032 SIGNIFICANT rfbroker.c 401 Waited 19998 seconds for background online notification.

Thanks & Regards,

AK

Hi,

It sounds like a network problem, ie. the 2100 port may be blocked.

If the firewall is not closing the connection (just dropping packets), then TCPView will show SYN_SENT while it waits for the connection to be established. You can see the same in netstat, but you have to be quicker on the refresh.

netstat -an|findstr 2100

The output would look like

TCP x.x.x.x:yyyy x.x.x.x:2100 SYN_SENT

If you find SYN_SENT, you may double check the firewall policies.

Regards,

Mark

Thanks Mark for your suggestion, looked at the ports but that is not the issue i think. I created a local user and able to login, the problem is only with LDAP authenticated users, working on this with CA to get this resolved

How the authentication configured?

SDM -> LDAP

or

SDM->EEM->LDAP?

for the first one, use the pdm_ldap_test utility to ensure the ldap function is good.

Thanks for your reply, it is SDM - LDAP , i get the  below error in both QA and prodcution. But QA does not have this issue not sure why this is happening in production..

ldap_connect() ERROR(81 / 17 / 81 / Server Down).  Please verify that LDAP server hostname and port are correct and server is Online.

I still think it's a network problem, may need your network team to investigate further, ensure you can access the ldap server from SDM server, and the ldap port is opened.

And double check the ldap options under Administration tab -> Options Manager -> LDAP

Enabled the ports but no luck pdm_ldap_test is working but still the same error..any help please..

HI avinash.kande

Were you able to resolve this issue... we are facing similar kind of issue. I'm getting below msgs on the

Also, is it necessary to un-comment these variables on the background,Stdby, Application and Application DMZ Server?

NX_SLUMP_SECONDARY_SOCKET=2100

NX_SLUMP_FIXED_SOCKETS=1

Recently we have faced this problem in our environment.
Our EEM has connection to several LDAP servers and one of them has been canceled, but the connection in the EEM was still active.
The solution was to remove from the EEM the connection to the AD that had been canceled.
 
The big trick was to edit the configuration file "server.xml", because the EEM itself was being harmed by the problem, presenting extreme slowness and connection drops, making it impossible to access the item "Configure >> User Store >> User Reference >> Reference From an external LDAP Directory ".

The "server.xml" file is set to "~\CA\SC\EmbeddedEntitlementsManager\config\server", simply edit it by removing the LDAP connection that is inaccessible from <userstores> <genericldapstore name = "name_xyz"> .
Save the file and restart the "CA iTechnology iGateway 4.7" (iGateway) service.

The conclusion is that any problem with any LDAP server, or connection to any LDAP server causes problems in the operation of the entire EEM.

CA SDM - CA Service Desk - AHD Codes - Error