Hi all!,

In WAS 8.5.5.18 we have a cell with two nodes. The synchronization of the dmrg eith 2 agent nodes is not working, the exception shown in the logs of the node agent seems to be related to the certification chain: 

[11/30/23 13:52:45:962 UTC] 0000016a NodeSync      E   ADMS0005E: The system is unable to generate synchronization request: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr	at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:552)	at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:427)	at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:248)	at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)	at java.lang.Thread.run(Thread.java:822)

The dmgr shows in the logs this error message:

11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0207I: Node Synchronization state for node: WEPREODMDCSRVNode01 - initiate time: 2023.11.30 at 13:52:45:962 UTCcomplete time: 2023.11.30 at 13:52:45:971 UTCresult: ErrorNo update occurred.[11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0206I: The configuration synchronization failed for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0203I: The automatic synchronization mode is enabled for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0209W: The configuration synchronization complete for cell, errors occurred.

The caducity of the server certificate was expiring yesterday and we imported the new certificate in the cell and in the nodes. We added also the certificate of the CA chain in the turst.p12 of the cell and the nodes.

We re-started all and seems to be working but still the WAS console shows that the dmgr cannot synch with the nodes. Looks like the node agent cannot find the dmgr (nodeagent has not discovered the dmgr).

¿Is there something more that we need todo? 

Thanks in advance.

Best regards.

From the logs it is hard to say what causes the issue. What I'd do is to stop all WAS servers on the failing node (including the nodeagent) and then run a `syncNode.sh` to manually sync the node and then startup the nodeagent again to see if the sync works again.

What I've seen several times in the past was that the certificate used to secure the communication between the dmgr and nodeagent expired and the new certificate could not be synced (for example bacause the nodeagent was down). Therefore a manual sync should fix that. So I'd say give it a try and lets know the result.

Have a good day, Hermann

Hi all!,

In WAS 8.5.5.18 we have a cell with two nodes. The synchronization of the dmrg eith 2 agent nodes is not working, the exception shown in the logs of the node agent seems to be related to the certification chain: 

[11/30/23 13:52:45:962 UTC] 0000016a NodeSync      E   ADMS0005E: The system is unable to generate synchronization request: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr	at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:552)	at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:427)	at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:248)	at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)	at java.lang.Thread.run(Thread.java:822)

The dmgr shows in the logs this error message:

11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0207I: Node Synchronization state for node: WEPREODMDCSRVNode01 - initiate time: 2023.11.30 at 13:52:45:962 UTCcomplete time: 2023.11.30 at 13:52:45:971 UTCresult: ErrorNo update occurred.[11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0206I: The configuration synchronization failed for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0203I: The automatic synchronization mode is enabled for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0209W: The configuration synchronization complete for cell, errors occurred.

The caducity of the server certificate was expiring yesterday and we imported the new certificate in the cell and in the nodes. We added also the certificate of the CA chain in the turst.p12 of the cell and the nodes.

We re-started all and seems to be working but still the WAS console shows that the dmgr cannot synch with the nodes. Looks like the node agent cannot find the dmgr (nodeagent has not discovered the dmgr).

¿Is there something more that we need todo? 

Thanks in advance.

Best regards.

[12/14/23 11:00:22:679 UTC] 0000008c DataSourceCon E   DSRA8040I: Failed to connect to the DataSource "jdbc/ilogDataSource".  Encountered java.sql.SQLException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server did not return a response. The connection has been closed. ClientConnectionId:2c98d6a4-bd5e-48e0-9e5f-324f19da5b1b". DSRA0010E: SQL State = 08S01, Error Code = 0at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1668)at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1323)at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:621)

• WebSphere Platform 8.5.5.18
• Java version: 1.8.0_261
• SQLDriver: sqljdbc4.jar

The custom properties of the DataSource, as shown in the picture:

From the logs it is hard to say what causes the issue. What I'd do is to stop all WAS servers on the failing node (including the nodeagent) and then run a `syncNode.sh` to manually sync the node and then startup the nodeagent again to see if the sync works again.

What I've seen several times in the past was that the certificate used to secure the communication between the dmgr and nodeagent expired and the new certificate could not be synced (for example bacause the nodeagent was down). Therefore a manual sync should fix that. So I'd say give it a try and lets know the result.

Have a good day, Hermann

Hi all!,

In WAS 8.5.5.18 we have a cell with two nodes. The synchronization of the dmrg eith 2 agent nodes is not working, the exception shown in the logs of the node agent seems to be related to the certification chain: 

[11/30/23 13:52:45:962 UTC] 0000016a NodeSync      E   ADMS0005E: The system is unable to generate synchronization request: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr	at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:552)	at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:427)	at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:248)	at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)	at java.lang.Thread.run(Thread.java:822)

The dmgr shows in the logs this error message:

11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0207I: Node Synchronization state for node: WEPREODMDCSRVNode01 - initiate time: 2023.11.30 at 13:52:45:962 UTCcomplete time: 2023.11.30 at 13:52:45:971 UTCresult: ErrorNo update occurred.[11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0206I: The configuration synchronization failed for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0203I: The automatic synchronization mode is enabled for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0209W: The configuration synchronization complete for cell, errors occurred.

The caducity of the server certificate was expiring yesterday and we imported the new certificate in the cell and in the nodes. We added also the certificate of the CA chain in the turst.p12 of the cell and the nodes.

We re-started all and seems to be working but still the WAS console shows that the dmgr cannot synch with the nodes. Looks like the node agent cannot find the dmgr (nodeagent has not discovered the dmgr).

¿Is there something more that we need todo? 

Thanks in advance.

Best regards.

Hello,

is this the only error message you get when you try to connect? No further messages in the logs? The error says "SQL Server did not return a response" so are you sure the request hits teh SQL Server? Or is there probably a Firewall in between preventing the connection? What is the status of the sockets? If you start a tcpdump while trying to connect - which packets are flowing? You are trying to connect via SSL - does the DB server connect SSL? Any messages at the DB server side? 

Hope that helps to investigate further but unforunately that's all I can say from the message. 

Have a good day, Hermann

P.S: I guess you are aware but your WebSphere Application Server code WAS 8.5.5.18 is quite outdated and old (over three! years). Not saying that it is related to the connection issue but definitely a (security) risk!

[12/14/23 11:00:22:679 UTC] 0000008c DataSourceCon E   DSRA8040I: Failed to connect to the DataSource "jdbc/ilogDataSource".  Encountered java.sql.SQLException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "SQL Server did not return a response. The connection has been closed. ClientConnectionId:2c98d6a4-bd5e-48e0-9e5f-324f19da5b1b". DSRA0010E: SQL State = 08S01, Error Code = 0at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1667)at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1668)at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1323)at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:991)at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:827)at com.microsoft.sqlserver.jdbc.SQLServerDataSource.getConnectionInternal(SQLServerDataSource.java:621)

• WebSphere Platform 8.5.5.18
• Java version: 1.8.0_261
• SQLDriver: sqljdbc4.jar

The custom properties of the DataSource, as shown in the picture:

From the logs it is hard to say what causes the issue. What I'd do is to stop all WAS servers on the failing node (including the nodeagent) and then run a `syncNode.sh` to manually sync the node and then startup the nodeagent again to see if the sync works again.

What I've seen several times in the past was that the certificate used to secure the communication between the dmgr and nodeagent expired and the new certificate could not be synced (for example bacause the nodeagent was down). Therefore a manual sync should fix that. So I'd say give it a try and lets know the result.

Have a good day, Hermann

Hi all!,

In WAS 8.5.5.18 we have a cell with two nodes. The synchronization of the dmrg eith 2 agent nodes is not working, the exception shown in the logs of the node agent seems to be related to the certification chain: 

[11/30/23 13:52:45:962 UTC] 0000016a NodeSync      E   ADMS0005E: The system is unable to generate synchronization request: com.ibm.websphere.management.exception.AdminException: Admin client connection to deployment manager is unavailable; nodeagent has not discovered the dmgr	at com.ibm.ws.management.sync.NodeSync.getAdminClient(NodeSync.java:552)	at com.ibm.ws.management.sync.NodeSync.getCellRepositoryEpoch(NodeSync.java:427)	at com.ibm.ws.management.sync.NodeSyncTask.doSync(NodeSyncTask.java:248)	at com.ibm.ws.management.sync.NodeSyncTask.run(NodeSyncTask.java:157)	at java.lang.Thread.run(Thread.java:822)

The dmgr shows in the logs this error message:

11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0207I: Node Synchronization state for node: WEPREODMDCSRVNode01 - initiate time: 2023.11.30 at 13:52:45:962 UTCcomplete time: 2023.11.30 at 13:52:45:971 UTCresult: ErrorNo update occurred.[11/30/23 13:53:15:971 UTC] 000002c5 MultiSyncMana A   ADMS0206I: The configuration synchronization failed for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0203I: The automatic synchronization mode is enabled for node: WEPREODMDCSRVNode01.[11/30/23 13:53:16:034 UTC] 000002c5 MultiSyncMana A   ADMS0209W: The configuration synchronization complete for cell, errors occurred.

The caducity of the server certificate was expiring yesterday and we imported the new certificate in the cell and in the nodes. We added also the certificate of the CA chain in the turst.p12 of the cell and the nodes.

We re-started all and seems to be working but still the WAS console shows that the dmgr cannot synch with the nodes. Looks like the node agent cannot find the dmgr (nodeagent has not discovered the dmgr).

¿Is there something more that we need todo? 

Thanks in advance.

Best regards.