KB Article #182041

After updating to Jan21 or later, the NM fails to start after rolling back to the backup taken by update_apigateway.sh fails

Problem

When you update a Nov2020 or older gateway to January2021 or later, then attempt to rollback using the backup created by update_apigw.sh, you see an error like the following when trying to start the Node Manager:


XML parse failed for "" / "": line 0: unable to open primary document entity 'system/conf/config.xml' service failed to start

Resolution

This is happening due to a problem with the nodemanager.xml file, which is getting changed by part of the process before the backup step is performed.


From January 2021 release DTD configuration was changed to XML configuration as DTD support was disabled by default in the API Gateway system due to security concerns. As a result, the update process required the nodemanager.xml configuration to be updated to check whether the Node Manager process is running before applying the update, which happens before the backup is taken. To properly restore the backup after rollback, the nodemanager.xml file has to be manually restored to use the older DTD configuration as in the table below: