{"id":539,"date":"2019-03-27T16:19:55","date_gmt":"2019-03-27T15:19:55","guid":{"rendered":"http:\/\/hslomka.de\/techno\/?p=539"},"modified":"2021-05-21T11:28:35","modified_gmt":"2021-05-21T11:28:35","slug":"websphere-as-global-security-adms0036e-the-configuration-synchronization-failed","status":"publish","type":"post","link":"https:\/\/techno.slomka.biz\/?p=539","title":{"rendered":"\u00a0WebSphere AS Global Security &#8211; ADMS0036E: The configuration synchronization failed"},"content":{"rendered":"<p>Nach dem Aktivieren der Global Security schl\u00e4gt die Node Synchronisation aus dem Deployment Manager fehl.<\/p>\n<p>Das Problem ist mir zumindest in diesen WebSphere Versionen begegnet:<\/p>\n<ul>\n<li>IBM WebSphere Application Server Network Deployment 8.5<\/li>\n<li>WAS ND bis 8.5.5 Fixpack 15<\/li>\n<\/ul>\n<p>In den Protokollen finden sich folgende Fehlermeldungen:<\/p>\n<p class=\"kasten\">\n  [3\/25\/19 19:53:27:932 CET] 0000008a NodeSyncTask&nbsp; A &nbsp;&nbsp; <b><span style=\"color:red\">ADMS0036E: The configuration synchronization failed.<\/span><\/b><br \/>\n[3\/25\/19 19:53:30:636 CET] 00000048 FfdcProvider&nbsp; W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on \/log\/HSL_CELL85\/ffdc\/nodeagent_2875f3_19.03.25_19.53.30.628307621416607723793.txt com.ibm.ejs.util.am._Alarm.run 95<br \/>\n[3\/25\/19 19:54:04:409 CET] 00000044 DefaultTokenP I&nbsp;&nbsp; HMGR0149E: An attempt to open a connection to core group DefaultCoreGroup has been rejected. The sending process has a name of HSL_CELL85\\DMGR1\\dmgr and an IP address of 192.168.1.100. Global security in the local process is Disabled. Global security in the sending process is Enabled. The received token starts with . The exception is <null>.<br \/>\n[3\/25\/19 19:54:27:370 CET] 00000087 FfdcProvider&nbsp; W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on \/log\/HSL_CELL85\/ffdc\/nodeagent_c0ba1e0f_19.03.25_19.54.27.1057436260776741690282.txt com.ibm.ws.management.status.NodeAgentStatusCache$StatusCacheTimedThread.run 1371<br \/>\n<b><span style=\"color:red\"> [3\/25\/19 19:54:27:785 CET] 0000009f NodeSync &nbsp;&nbsp; ADMS0005E: The system is unable to generate synchronization request java.lang.reflect.UndeclaredThrowableException<\/span><\/b><br \/>\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at com.sun.proxy.$Proxy15.queryNames(Unknown Source)<br \/>\n&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at com.ibm.ws.management.AdminClientImpl.queryNames(AdminClientImpl.java:108) <\/null><\/p>\n<h3>L\u00f6sung<\/h3>\n<p>Eine erste Synchronisation vom DMGR funktioniert nicht nach dem Einschalten der Global Security. Der Node muss die Synchronisation einmalig starten:&nbsp;<\/p>\n<p class=\"kasten\">\n  <b><span style=\"color:darkblue\">cd Profile_dir\/bin\/<br \/>\n.\/stopServer.sh nodeagent<\/span><\/b><\/p>\n<p class=\"kasten\">\n  <b><span style=\"color:darkblue\">.\/syncNode.sh localhost SOAPPORT<\/span><\/b><br \/>\nADMU0116I: Tool information is being logged in file \/logs\/syncNode.log<br \/>\nADMU0128I: Starting tool with the node profile<br \/>\nADMU0401I: Begin syncNode operation for node NODE01 with Deployment Manager<br \/>\nADMU0016I: Synchronizing configuration between node and cell.<br \/>\n<b><span style=\"color:green\">ADMU0402I: The configuration for node NODE01 has been synchronized with Deployment Manager<\/span><\/b><\/p>\n<p class=\"kasten\">\n  <b><span style=\"color:darkblue\">.\/startServer.sh nodeagent<\/span><\/b><br \/>\nADMU3000I: Server nodeagent open for e-business; process id is 20059<\/p>\n<p>Danach kann die Synchronisation auch erfolgreich vom <em>WebSphere Deployment Manager<\/em> aus gestartet werden.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Nach dem Aktivieren der Global Security schl\u00e4gt die Node Synchronisation aus dem Deployment Manager fehl. Das Problem ist mir zumindest in diesen WebSphere Versionen begegnet: IBM WebSphere Application Server Network Deployment 8.5 WAS ND bis 8.5.5 Fixpack 15 In den Protokollen finden sich folgende Fehlermeldungen: [3\/25\/19 19:53:27:932 CET] 0000008a NodeSyncTask&nbsp; A &nbsp;&nbsp; ADMS0036E: The configuration synchronization failed. [3\/25\/19 19:53:30:636 CET] 00000048 FfdcProvider&nbsp; W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on \/log\/HSL_CELL85\/ffdc\/nodeagent_2875f3_19.03.25_19.53.30.628307621416607723793.txt com.ibm.ejs.util.am._Alarm.run 95 [3\/25\/19 19:54:04:409 CET] 00000044 DefaultTokenP I&nbsp;&nbsp; HMGR0149E: An attempt to open a connection to core group DefaultCoreGroup has been rejected. The sending process has a name of HSL_CELL85\\DMGR1\\dmgr and an IP address of 192.168.1.100. Global security in the local process is Disabled. Global security in the sending process is Enabled. The received token starts with . The exception is . [3\/25\/19 19:54:27:370 CET] 00000087 FfdcProvider&nbsp; W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on \/log\/HSL_CELL85\/ffdc\/nodeagent_c0ba1e0f_19.03.25_19.54.27.1057436260776741690282.txt com.ibm.ws.management.status.NodeAgentStatusCache$StatusCacheTimedThread.run 1371 [3\/25\/19 19:54:27:785 CET] 0000009f NodeSync &nbsp;&nbsp; ADMS0005E: The system is unable to generate synchronization request java.lang.reflect.UndeclaredThrowableException &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at com.sun.proxy.$Proxy15.queryNames(Unknown Source) &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; at com.ibm.ws.management.AdminClientImpl.queryNames(AdminClientImpl.java:108) L\u00f6sung Eine erste Synchronisation vom DMGR funktioniert nicht nach dem Einschalten der Global Security. Der Node muss die Synchronisation einmalig starten:&nbsp; cd Profile_dir\/bin\/ .\/stopServer.sh nodeagent .\/syncNode.sh localhost SOAPPORT ADMU0116I: Tool information is being logged in file \/logs\/syncNode.log ADMU0128I: Starting tool with the node profile ADMU0401I: Begin syncNode operation for node NODE01 with Deployment Manager ADMU0016I: Synchronizing configuration between node and cell. ADMU0402I: The configuration for node NODE01 has been synchronized with Deployment Manager .\/startServer.sh nodeagent ADMU3000I: Server nodeagent open for e-business; process id is 20059 Danach kann die Synchronisation auch erfolgreich vom WebSphere Deployment Manager aus gestartet werden.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[34,11],"tags":[55,67,75,106,107],"class_list":["post-539","post","type-post","status-publish","format-standard","hentry","category-ibm-websphere-application-server","category-middleware","tag-deployment-manager","tag-ibm-websphere-application-server","tag-node-agent","tag-was","tag-websphere"],"_links":{"self":[{"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=\/wp\/v2\/posts\/539","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=539"}],"version-history":[{"count":1,"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=\/wp\/v2\/posts\/539\/revisions"}],"predecessor-version":[{"id":884,"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=\/wp\/v2\/posts\/539\/revisions\/884"}],"wp:attachment":[{"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=539"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=539"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/techno.slomka.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=539"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}