PM51254: SYNCNODE COMMAND SHOULD NOT RUN ON DEPLOYMENT MANAGER NODE

Fixes are available

APAR status

Closed as program error.

Error description

Versiosn : WebSphere Application Server Network Deployment
edition versions 6.1, 7.0 and 8.0.

Problem :
This problem can be reproduced on v6.1, v7.0 and v8.0

1. Dmgr Profile and Application Server Profile
2. Deployment Manager is the only profile in this Install
3. start DMGR and do SyncNode from WSAS_HOME/bin and it fails
with
error :

C:\IBM\WebSphere\AppServer610\bin>syncnode IBM-7DC837CC664 8893
ADMU0116I: Tool information is being logged in file

C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\logs\syncNode.log
ADMU0128I: Starting tool with the Dmgr02 profile
ADMU0401I: Begin syncNode operation for node
IBM-7DC837CC664CellManager02 with
Deployment Manager IBM-7DC837CC664: 8893
ADMU0111E: Program exiting with error:
java.io.FileNotFoundException:

C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\config\cells\IBM-7
DC837
CC664Cell02\nodes\IBM-7DC837CC664CellManager02\servers\nodeagent
\server.
xml
(The system cannot find the path specified.)
ADMU1211I: To obtain a full trace of the failure, use the -trace
option.
ADMU0211I: Error details may be seen in the file:

C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\logs\syncNode.log

2. So If you  create nodeagent directory under
DMGR_HOME/config/<cellname>/nodes/<DMGR_NODE>/servers/
Then syncNode works and wipes out entire Node configuration

5, Here are results of SyncNode
C:\IBM\WebSphere\AppServer610\bin>syncnode IBM-7DC837CC664 8893
ADMU0116I: Tool information is being logged in file

C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\logs\syncNode.log
ADMU0128I: Starting tool with the Dmgr02 profile
ADMU0401I: Begin syncNode operation for node
IBM-7DC837CC664CellManager02 with
Deployment Manager IBM-7DC837CC664: 8893
ADMU0016I: Synchronizing configuration between node and cell.
ADMU0402I: The configuration for node
IBM-7DC837CC664CellManager02 has
been
synchronized with Deployment Manager IBM-7DC837CC664:
8893

3. After this complete configuration for all the nodes are lost
under DMGR configuration.

The messages coming from the syncNode command indicate it is
using the Dmgr's profile and Dmgr node during processing.
There is no nodeagent for the Dmgr node, so that could have been
a clue that something was incorrect.



The syncNode command should have detected the use of
the Dmgr node and exited with an informative message.

This APAR is to fix SyncNode command.

Local fix

```
N/A
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Network Deployment edition           *
****************************************************************
* PROBLEM DESCRIPTION: The syncNode script is run from         *
*                      <was_home>/bin without the              *
*                      -profileName option.  The syncNode      *
*                      script exits with confusing messages.   *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
If the syncNode script is run from <was_home>/bin without the
-profileName option, it will exit with confusing message that
could lead to inappropriate actions.
The error message seen in this case is:
ADMU0111E: Program exiting with error:
java.io.FileNotFoundException:
C:\IBM\WebSphere\AppServer610\profiles\Dmgr02\config\cells\<cell
name>\nodes\<nodename>\servers\nodeagent\server.xml
(The system cannot find the path specified.)
With no profileName option, the syncNode code will use the
default profile which is usually the Dmgr's profile.
There is no nodeagent for Dmgr profile, so it is confusing and
could lead to incorrect actions.

Problem conclusion

The syncNode code has been modified to check for Dmgr's node
and if found, exit with new error message(ADMU0044E).
The fix for this APAR is currently targeted for inclusion in
fix packs 6.1.0.43,  7.0.0.23 and 8.0.0.3. Please refer to the
recommended updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM51254
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
610
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-11-01
Closed date
2012-01-03
Last modified date
2012-01-03

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
28 October 2021

Tips

PM51254: SYNCNODE COMMAND SHOULD NOT RUN ON DEPLOYMENT MANAGER NODE

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

Document Information

Share your feedback

Need support?