on 07-23-2014 1:42 PM
Hello All,
When ever we update LM_Service component, SMD agents also get updated. But in our landscape most of the SMD agents are updating along with LM_Service but few agents are missing to update and they are in not connected state at Agent administration page. Checked at OS level they are up and running, please suggest the fix for this issue.
Regards,
Anil
Hi Anil,
Check agent logs to find out why it's not connected.
Share it here, if possible.
Divyanshu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Divyanshu,
As per error log it is socket is not available, but the agent port is open only.
Connecting to SMD server ms://FQDN:PORT/P4 failed - error counter: 137746 - com.sap.eng
ine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:
FQDN]
Regards,
Anil
Hi Divyanshu,
it was already maintained in host files. these agents are installed year back and running without any issue. As soon as we have updated our Solution manager stack to SP11 few agents are in not connected state.
Below is the agent log file,
Jul 23, 2014 7:47:02 AM [Thread[Connector,5,main]] Info [SMDConnector.resetBroker] reset the p4 broker (close:true)
Jul 23, 2014 7:47:02 AM [Thread[Connector,5,main]] Info [SMDConnector.resetBroker] p4 broker closed.
Jul 23, 2014 7:47:02 AM [Thread[Connector,5,main]] Info Local P4 port opened on port '58304'.
Jul 23, 2014 7:47:02 AM [Thread[Connector,5,main]] Info Local P4 server configured with transport layer 'None'.
Jul 23, 2014 7:47:02 AM [Thread[Connector,5,main]] Info [SMDConnector.resetBroker] p4 broker initialized.
Jul 23, 2014 7:47:02 AM [Thread[Connector,5,main]] Info [ms://FQDN:PORT/P4] Checking server availability...
Jul 23, 2014 7:47:02 AM [Thread[Connector,5,main]] Warning Connecting to SMD server ms://pFQDN:PORT/P4 failed - error counter: 137748 - com.sap.eng
ine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.io.IOException: Can't get Socket. Reason:
FQDN]
Here is the log of smd.2.connector.listener.log
Jul 23, 2014 1:10:41 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to
LAST_CONNECT_ON_ERROR
Jul 23, 2014 1:11:16 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from LAST_CONNECT_O
N_ERROR to CONNECTING
Jul 23, 2014 1:11:16 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to
LAST_CONNECT_ON_ERROR
Jul 23, 2014 1:11:51 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from LAST_CONNECT_O
N_ERROR to CONNECTING
Jul 23, 2014 1:11:51 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to
LAST_CONNECT_ON_ERROR
Jul 23, 2014 1:12:26 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from LAST_CONNECT_O
N_ERROR to CONNECTING
Jul 23, 2014 1:12:26 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from CONNECTING to
LAST_CONNECT_ON_ERROR
Jul 23, 2014 1:13:01 PM [Thread[Connector,5,main]] Info [SMDAgent.IConnectionStatusListener.statusChanged] SMD Agent connection status changed from LAST_CONNECT_O
N_ERROR to CONNECTING
Regards,
Anil
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.