Troubleshooting in the CBS 

Here you will find some hints to help you in solving problems that may occur when working with CBS.

CBS Does Not Process Any Requests

Symptom

Although pending requests exist in CBS they are not processed

Solution

...

       1.      First check whether the CBS service is running.

       2.      If it is, and the CBS still does not process any requests, check the database settings.

Especially data volume size and data log size are of interest. If data volume size and data log size are exceeded, CBS will not work correctly, as access to the database will fail (especially when new data is inserted into the database).

Another reason might be that request processing is disabled for the corresponding buildspace.

       3.      Therefore please check the current state of the affected buildspace via Web UI.

Creation of Files Failed in CBS

Symptom

If log files contain messages like “file not found exception …” this is an indicator for such a problem.

This may happen on Windows platforms. If the path length of the created file exceeds the 256-character limit the file will not be created. As a consequence requests may fail.

Solution

...

       1.      Check the root folder of the CBS working directory.

       2.      If it is clear that the 256-character limit is the problem, try to shorten the length of the CBS working directory root.

JDK Paths are not correctly specified

Symptom

Build and activation fails in processing. To distinguish this from “normal” build errors (i.e. syntax errors reported by compiler) have a closer look at the build request log. If in the log such a message appears, it is clear that the required JDK was not specified correctly:

BUILD DCs

 

The following problem(s) occurred during request processing:

java.io.IOException: java.io.IOException: /usr/lib/java/bin/java/bin/java: not found

...

...

Request processing FAILED.

Solution

...

Specify the JDK path correctly.