Symptom:
AS Java bootstrap fails to synchronize the system’s files and stops with one of the following exit codes: 501, 502, 510, 545.
Scenario Type: Error analysis
SAP NetWeaver Component: Application Server Java (AS Java)
Analysis:
The bootstrap can fail to synchronize the engine's files due to problems with the configuration of the module.○ 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 501: Properties file found, but cannot be read. Check the file permissions. |
The file bootstrap.properties exists in the file system. The bootstrap module uses this file to read the user preferences. If the file cannot be read, some data important for the synchronization may be skipped. Since this may cause undesired effects to the file system content, this is considered fatal.
Check the permissions of the /usr/sap/<SID>/JC<XX>/j2ee/cluster/bootstrap/bootstrap.properties file for the <sid>admuser under which the AS Java runs.
| Exit code 502: Incorrect property value. For more information about the valid values, see SAP Note 915825. |
The file bootstrap.properties can contain only one property (element.resynch) described in SAP Note 710663. Use the note to understand more about the correct values and the purpose of this property.
| Exit code 510: Inconsistent bit length configuration. The JVM reports different bit length than the bit length of the Java Startup and Control Framework. Check the installation consistency. For more information, see SAP Note 915825. |
The bit length of the JVM is different from the bit length of the binaries of the Java Startup and Control Framework. This may be caused by the wrong CD content or wrong bit-length detection during installation.
Create a CSS message under the component BC-INS and attach the bootstrap logs and the version of the jlaunch executable. You can determine the version with the command:
● for Windows: <drive>:\usr\sap\<SID>\JC<XX>\exe\jlaunch.exe -version
● for UNIX based: /usr/sap/<SID>/JC<XX>/exe/jlaunch –version
| Exit code 545: Current VM type is not supported according to the specified compatibility list. For more information, check the bootstrap logs and see SAP Note 915825. |
Not every VM can ensure the same degree of performance and stability for the AS Java. A special compatibility list exists in the Product Availability Matrix (PAM) to ensure that the VM is able to perform as expected. If the VM is not in this list, the bootstrap stops with this exit code.
Some JVM options could also cause this exit code and especially the server switch (see SAP Note 709140 for recommended JVM settings).
Install a VM that is in the list of supported VMs, or change the VM type.
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.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.Start the system or the bootstrap module only with <sid>adm user, otherwise the files have incorrect permissions.
Solution
- 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:
○ 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.
- 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.
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 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.
Bootstrap Stops Due to Database Problems
Scenario Type: Error analysis
SAPNetWeaver Component: Application Server Java (AS Java)
Analysis
The bootstrap module fails to synchronize the files due to problems with the connection to the database or database inconsistency.
Solution:
If you get one of the exit codes listed above, take the following steps:
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. Perform a database consistency check following the procedure below. If any of the steps is not completed successfully, stop the check and report the result in a CSS message.
a. Start the Config Tool to check if it connects to the database.
b. Check if you can connect to the database using an external tool. This external tool can be DBManager for MaxDB or Enterprise Manager for MSSQL Server.
c. Run the integrity check tool provided with the database (for example, DBManager for MaxDB).
3. Proceed depending on the particular exit code.
| Exit code 503: Error while initializing the database connection. Check if the database is running. For more information, check the bootstrap logs and see SAP Note 915825. |
The connection to the database cannot be initialized. Try the following steps in the order they are described:
...
1. If the database is not started, start the database.
2. Check if database drivers are correctly set in the instance profiles.
In the profile /usr/sap/<SID>/SYS/profile/<SID>_J<XX>_<HOSTNAME>, check for the j2ee/dbdriver entry and make sure that it is correct for the database you are using. Check if the files in the entry really exist and have the correct permissions for access from <SID>adm user.
3. Make sure the user name and the password for accessing the database are correct.
4. Perform a database consistency check.
| Exit code 504: Custom parameters mappings not found in the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825. |
| Exit code 505: Problem accessing the database. Check if the database is running and the database connection details. For more information, check the bootstrap logs and see SAP Note 915825. |
These exit codes indicate problems with access to the custom parameters mappings. The parameter mappings are used when Software Deployment Archives (SDA) are deployed that contain parameterized settings. Parameterized settings contain system parameters provided by the Configuration Manager that are transparently substituted during runtime. The custom parameters are defined by the user of the system. Some parameters may be vital for the work of other system components and if they cannot be substituted, their incorrect value may cause inconsistencies in the system.
If you deployed a SDA that uses a custom parameter, which it is not found in the database, this causes the bootstrap to exit.
Proceed depending on when the problem occurred. If the problem appeared after:
● installation: Create a CSS message under component BC-INS.
● upgrade: Create a CSS message under component BC-INS or BC-UPG-TLS-TLJ depending on the tool used (SAPInst or JINUP)
● deploy: Create a CSS message under component BC-JAS-DPL
In the CSS message for this problem include:
● the bootstrap logs
● description of the installations/deployments/upgrades you performed lately
● the logs of the server(s) from /usr/sap/<SID>/JC<XX>/j2ee/cluster/server<n>/log.
● a report about any of the steps that failed during the database consistency check.
| Exit codes 506 and 507: Cannot access the synchronization root. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825. |
The content that needs to be synchronized is located under specific location (root) in the database. The bootstrap module cannot find this root so the synchronization fails to start. These exit codes indicate problems with the:
● Database consistency - the state can be caused by errors during installation, upgrade or deploy.
Check the database consistency and include the report for the steps that failed.
Create a CSS message depending on whether the problem occurred after installation, upgrade, or deploy under the components listed above.
● Wrong or missing profile entry j2ee/instance_id, which determines the specific instance root.
Find the profile in /usr/sap/<SID>/SYS/profile/<SID>_J<XX>_<HOSTNAME>. Check if the entry is missing and if so, create a CSS message under BC-INScomponent.
| Exit codes 508 and 509: Cannot access the version information in the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825. |
The bootstrap uses special versioning to optimize the synchronization process. Without this optimization, everything from the database has to be downloaded to the file system. This information is always present in the database. If it is not there, the bootstrap stops with an exit code.
The problem can be caused by erroneous installation, upgrade or deploy. The reason for the error may be:
● Missing or improperly linked template
● Missing instance ID entry from the profile
Create a CSS message depending on whether the problem occurred after installation, upgrade, or deploy under the components listed above. In the CSS message for this problem include:
● the bootstrap logs
● description of the installations/deployments/upgrades you performed lately
● the logs of the server(s) from /usr/sap/<SID>/JC<XX>/j2ee/cluster/server<n>/log.
● a report about any of the steps that failed during the database consistency check.
| Exit codes 511, 512 and 513: Problem accessing the instance metadata. Check the database settings. For more information, check the bootstrap logs and see SAP Note 915825. |
The instance metadata contains information about the JVM location, JVM settings (heap and perm sizes, GC options, and so on), the infrastructure (SCS host and ports). If the instance data cannot be read, the instance does not run as desired so the bootstrap exits.
Create a CSS message for this problem and attach the bootstrap logs.
| Exit codes 515 and 516: Cannot find information about the native files. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825. |
The database contains metadata about the native files that are synchronized in /usr/sap/<SID>/JC<XX>/j2ee/os_libs. If this metadata cannot be obtained, the bootstrap has to exit, otherwise the AS Java does not function properly.
Check the database consistency and create a CSSmessage with the consistency report and the bootstrap logs.
| Exit codes 517, 518, 519, 520 and 521: Error while reading index information from the database. Possible reason: incorrect or inconsistent database content. For more information, check the bootstrap logs and see SAP Note 915825. |
Bootstrap uses indexes to optimize the synchronization process. If these indexes cannot be read from the database, all the binaries have to be downloaded, which takes a lot of time. The indexes are always present in the database. If the bootstrap exits because of access problem while reading the indexes, this may be an indication of database inconsistency.
Check the database consistency and create a CSSmessage with the consistency report and the bootstrap logs.
| Exit codes 524, 525 and 526: Problem accessing the cluster file system global version. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825. |
The Cluster File System (CFS) is used for deploying single file system archive in multiple file systems in the whole cluster. The CFS serves as a repository for the deployed files, while the bootstrap is responsible for the synchronization of the CFS components in the FS of the cluster elements. The global version is used for optimization purposes. If it is missing this may be an indication of:
● Database corruption.
Check the database consistency.
● Version mismatch between the bootstrap and deploy controller versions.
Check the versions of the components as described above.
Create a CSS message that includes the database consistency report, the versions of the components and the bootstrap logs.
| Exit codes 527 and 528: Problem accessing the versions repository of the cluster file system. Possible reason: incorrect or inconsistent database content. Check the Deploy Controller version. For more information, check the bootstrap logs and see SAP Note 915825. |
The version’s repository of the CFS is used to optimize the synchronization time. If it is missing this may be an indication of:
● Version mismatch between the bootstrap and deploy controller versions.
Check the versions of the components using:
○ SystemInfo application if the engine is running
○ Version script located in the folder /usr/sap/<SID>/JC<XX>/j2ee/cluster/bootstrap/scripts if the engine cannot start
Create a CSS message, including the version information displayed by the tool you are using. The minimum information required is the bootstrap and the deploy controller components versions. You also have to include the name of the tool (“SystemInfo application” or “version script”) used to obtain the versions.
● Database corruption
Check the database consistency. Create a CSSmessage that includes the database consistency report, the versions of the components and the bootstrap logs.
| Exit codes 529 and 530: Problem accessing the metadata of the cluster file system. Check the database state and the Deploy Controller component version. For more information, check the bootstrap logs and see SAP Note 915825. |
The CFS is used for deploying single file system archive in multiple file systems in the whole cluster. The CFS serves as a repository for the deployed files, while the bootstrap is responsible for the synchronization of the CFS components in the file system of the cluster elements.
If any data required for the synchronization of the CFSarchives is missing or not accessible, the bootstrap exits. This may be an indication of:
● Version mismatch between the bootstrap and deploy controller versions: Check the versions of the components as described above.
● DB corruption: Check the database consistency.
Create a CSS message that includes the database consistency report, the versions of the components and the bootstrap logs.
| Exit codes 532 and 542: Index not found in the database. Check the database consistency and the version of the OfflineDeploy component. For more information, check the bootstrap logs and see SAP Note 915825. |
The bootstrap uses database indexes along with the file system indexes to optimize the synchronization process. If a database index cannot be found, one or more components are unknown to the bootstrap and cannot be downloaded to the file system. This can result in the AS Java not working as expected.
The error may indicate inconsistent database. Check the database consistency and create a CSS message with the consistency report and the bootstrap logs attached.
| Exit code 546: Problem reading kernel properties from the DB. For more information, check the bootstrap logs and see SAP Note 915825. |
| Exit codes 548, 549: Problem reading the managers' properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825. |
| Exit codes 550, 551: Problem reading the services' properties. Check the database consistency. For more information, check the bootstrap logs and see SAP Note 915825. |
The bootstrap reads the kernel properties; the properties of the managers that compose the kernel of the AS Java; and the services’ properties from the database. All these properties are used to configure the kernel so they are vital for the work of the managers. If they cannot be obtained, the bootstrap exits.
These errors may indicate an inconsistent database. Check the database consistency and create a CSS message with the consistency report and the bootstrap logs attached.
No comments:
Post a Comment