Bootstrap Stops Due to File System Problems (SAP Library

Bootstrap Stops Due to File System Problems

Symptom

AS Java bootstrap fails to synchronize the system’s files and stops with one of the following exit codes: 514, 522, 523, 531, 541, 533, 534, 535, 536, 537, 538, 539, 540, 543, 544, 547, 552.

Scenario Type: Error analysis

SAP NetWeaver Component: Application Server Java (AS Java)

Analysis

The bootstrap module collects metadata about the instance and the files it has to synchronize and then downloads the required files to the file system. File permissions must be set so that the <sid>adm user can have full (read/write) access. If there are problems while reading or writing files, the bootstrap exits.

Note

Start the system or the bootstrap module only with <sid>adm user, otherwise the files have incorrect permissions.

Solution

1. Find a detailed description of the problem in the bootstrap log files, which are located in the /usr/sap/<SID>/JC<XX>/work/ folder. The log files are:

○ dev_bootstrap* - logs from the Java Startup and Control Framework that shows the parameters with which the bootstrap was started.

○ log_bootstrap* - logs from the execution of the bootstrap that show the execution flow from the last session and the possible errors.

○ jvm_bootstrap* - logs from the JVM output for the bootstrap process that show possible JVM problems during the bootstrap execution.

2. Proceed depending on the particular exit code.

Exit code 514: Problem accessing the file system entry j2ee/os_libs. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap tries to get the full path name to the /usr/sap/<SID>/JC<XX>/j2ee/os_libs folder. The construction of the path name may fail due to unresolved links on UNIX based machines, for instance. This causes the bootstrap module to exit.

Check if the j2ee/os_libs folder is accessible and its file permissions are set for <sid>adm user. If not, set the permissions for full access by the <sid>adm user.

Exit codes 522 and 523: Cannot access the file system index file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

When the bootstrap is in FORCE synchronization mode, it does not rely on the file system indexes and tries to create them. If this is not possible due to an Input/Output problem, it exits.

Check the permissions for the file /usr/sap/<SID>/JC<XX>/j2ee/cluster/version.bin and the files under /usr/sap/<SID>/JC<XX>/j2ee/cluster/bin. Set the permissions for full access by the <sid>adm user.

Exit codes 531 and 541: Index not found in the file system. Check the file system consistency. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap uses file system indexes along with the database indexes to optimize the synchronization process. If a file system index cannot be found, one or more components are not synchronized since the bootstrap is not aware of their state in the file system. This can result in the AS Java working improperly.

This error may indicate a problem with the files in the file system. Run the file system integrity utility to scan for errors. If there are no errors, create a CSS message with the bootstrap logs attached.

Exit codes 533, 534, 535 and 536: Error while synchronizing the files in j2ee/cluster/bootstrap. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap tries to perform a self-update. If the operation does not succeed, it exits.

The problem may be caused by missing or incorrectly set permissions for <sid>adm user.

Check the file system permissions for /usr/sap/<SID>/JC<XX>/j2ee/cluster/bootstrap.

Set the permissions for full access by the <sid>adm user.

Exit code 537: Error while synchronizing the files in j2ee/oslibs. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap tries to update the native files in /usr/sap/<SID>/JC<XX>/os_libs. If the operation does not succeed, the bootstrap exits.

The problem may be caused by missing or incorrectly set permissions for <sid>adm user.

Check the file system permissions for /usr/sap/<SID>/JC<XX>/os_libs. Set the permissions for full access by the <sid>adm user.

Exit code 538: Error while updating the j2ee/cluster/instance.properties file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The /usr/sap/<SID>/JC<XX> /j2ee/cluster/instance.properties file is updated on every start by the bootstrap. The Java Startup and Control Framework uses this file to obtain information about the number of nodes it has to launch and their parameters. If the file update fails, the AS Java cannot work properly so the bootstrap exits.

The problem is caused by missing or incorrectly set permissions for the file /usr/sap/<SID>/JC<XX>/j2ee/cluster/instance.properties. Check the permissions and ensure that the file can be used by the <sid>adm user.

Exit code 539: Error while synchronizing the server files in j2ee/cluster/server<n>/dtd. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap synchronizes Document Type Definition (DTD) files needed for the proper work of the server nodes. If these files cannot be synchronized, it exits.

The problem is caused by missing or incorrectly set permissions for the files in /usr/sap/<SID>/JC<XX>/j2ee/cluster/server<n>/dtd. To determine the location of the problematic files you can have a look at the bootstrap files. Make sure that the files have all (read/write) permissions for <sid>admuser.

Exit code 540: Error while synchronizing the server files in j2ee/cluster/server<n>. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap synchronizes the files that are required for the server nodes to work properly. If these files cannot be synchronized, it exits.

The problem is caused by missing or incorrectly set permissions for the files in /usr/sap/<SID>/JC<XX>/j2ee/cluster/server<n>folders. To determine the exact location, examine the bootstrap logs. Check and ensure that the files have all permissions for use by the <sid>adm user.

Exit code 543: Error while synchronizing the server Java binaries. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap synchronizes the files that are required for the AS Java to work properly in /usr/sap/<SID>/JC<XX>/j2ee/cluster/bin. If these files cannot be synchronized, the bootstrap exits.

The problem is caused by missing or incorrectly set permissions for the files in /usr/sap/<SID>/JC<XX>/j2ee/cluster/bin folders. To determine the exact location of the file that cannot be synchronized, examine the bootstrap logs. Check and ensure that the files have all permissions for use by the <sid>adm user.

Exit code 544: Error while writing the j2ee/cluster/version.bin file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The file version.bin is used for storing the indexes of the synchronized components. The indexes are used to speed up synchronization. If the file cannot be updated, synchronization is slow.

Exit code 547: Problem writing cluster/kernelProperties.bin file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap creates and stores the file kernelProperties.bin in the cluster folder to allow the kernel of the AS Java to read the file and provide the internal information to the managers. If this file cannot be stored on the file system, the bootstrap exits.

The problem is caused by missing or incorrectly set permissions for the file /usr/sap/<SID>/JC<XX>/j2ee/cluster/kernelProperties.bin. Check the permissions and ensure that the file can be used by the <sid>adm user.

Exit code 552: Problem writing cluster/servicesProperties.bin or cluster/kernelProperties.bin file. Check the file system permissions. For more information, check the bootstrap logs and see SAP Note 915825.

The bootstrap creates and stores the files servicesProperties.bin and kernelProperties.bin in the cluster folder to allow the kernel of the AS Java to read the files and provide the internal information to the managers and services. If one of these files cannot be stored on the files system, the bootstrap exits.

The problem is caused by missing or incorrectly set permissions for the files /usr/sap/<SID>/JC<XX>/j2ee/cluster/servicesProperties.bin and /usr/sap/<SID>/JC<XX>/j2ee/cluster/kernelProperties.bin.

Check the permissions and ensure that the files can be used by the <sid>adm user.