Troubleshooting common problems

Upgrading an agent on Solaris requires running pkgrm command

Use the pkgrm BFAgent command to remove the existing Solaris Build Forge agent before running the pkgadd command.

URL for 7.0 notification templates might not work in later versions

The notification template URL opens the Build Forge job report when you click the URL link in the notification email.

In versions 7.0.1 and 7.1, the URL in the notification templates changed; consequently, the URL might not work when you upgrade from 7.0 to a later version.

If you experience a link error, complete these steps to manually edit the notification templates:
  1. Select Project > Templates.
  2. Click the notification template name to display its properties on the Details tab.
  3. In the Body field, locate the URL for the template. The URL should be similar to the one in the following example:
    http://${CONSOLEHOST}:${CONSOLEPORT}/fullcontrol/index.php?mod=projectruns&action=
    edit&bfid=${PID}&bfid=${BID}&bfid=${UID}
  4. Replace the following URL elements with the appropriate 7.0.1 and later URL elements:
    URL elements 7.0.1 (and later) URL elements
    projectruns jobs
    & &
    action=edit action=build.view
    &bfid=${PID} | &bfid=${BID} | &bfid=${UID} &bf_id=${BID}

Product unresponsive

If Rational Build Forge becomes unresponsive, check the logs in <bfinstall>/Apache/tomcat/logs/ (UNIX or Linux) or <bfinstall>\Apache\tomcat\logs\ (Windows) for a message similar to the following one:


Services: 20075: CRRBF1381I: Established connection to Build Forge Services.
DBD::DB2::st execute failed: [IBM][CLI Driver] SQL30081N  A communication error has been detected.  
   Communication protocol being used: "TCP/IP".  
   Communication API being used: "SOCKETS".  
   Location where the error was detected: "XXX.XXX.XXX.XXX".  
   Communication function detecting the error: "recv".  
   Protocol specific error code(s): "131", "*", "0".  SQLSTATE=08001
   August 17, 2010  7:18:14 AM EDT 
Database: 20075: CRRBFEEEEE: DBD::DB2::st execute failed: 
   [IBM][CLI Driver] SQL30081N  A communication error has been detected.  
   Communication protocol being used: "TCP/IP".  
   Communication API being used: "SOCKETS".  
   Location where the error was detected: "XXX.XXX.XXX.XXX".  
   Communication function detecting the error: "recv".  
   Protocol specific error code(s): "131", "*", "0".  SQLSTATE=08001

Database: 20075: CRRBF0551I: StackTrace from Process id [20075] called from [
   BuildForge::DB::db2(./PerlApp/BuildForge/DB/db2.pm:65)
   BuildForge::Utilities::SysParams(./PerlApp/BuildForge/Utilities/SysParams.pm:57)
   main(.buildforge.pl:305)
   main(.buildforge.pl:213)
]
Database: 20075: CRRBF0556I: Trying to call [execute] on a non-existant database handle
DBD::DB2::st fetchrow_hashref failed: no statement executing at /PerlApp/BuildForge/DB/db2.pm 
  line 78, <$sock> line 1054.
20075: CRRBF0555E: Problem performing Database Operation [fetchrow_hashref] : DBD::DB2::st 
  fetchrow_hashref failed: no statement executing at /PerlApp/BuildForge/DB/db2.pm 
  line 78, <$sock> line 1054.

Database: 20075: CRRBFEEEEE: DBD::DB2::st fetchrow_hashref failed: no statement executing 
  at /PerlApp/BuildForge/DB/db2.pm line 78, <$sock> line 1054.

Database: 20075: CRRBF0551I: StackTrace from Process id [20075] called from [
   BuildForge::Utilities::SysParams(./PerlApp/BuildForge/Utilities/SysParams.pm:59)
   main(.buildforge.pl:305)
   main(.buildforge.pl:213)
]
[IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003 at /PerlApp/BuildForge/DB/Handle.pm 
   line 385, <$sock> line 1054.
Database: 20075: CRRBF0555E: Problem performing Database Operation [prepare] : 
   query [SELECT * FROM bf_jobcount WHERE bf_engine_id=?] 
DBD::DB2::db prepare failed: [IBM][CLI Driver] CLI0106E  Connection is closed. 
   SQLSTATE=08003 at /PerlApp/BuildForge/DB/Handle.pm line 385, <$sock> line 1054.

Database: 20075: CRRBFEEEEE: DBD::DB2::db prepare failed: [IBM][CLI Driver] CLI0106E  
   Connection is closed. SQLSTATE=08003 at /PerlApp/BuildForge/DB/Handle.pm 
   line 385, <$sock> line 1054.

where XXX.XXX.XXX.XXX is the server hosting your database.

This message indicates that there is not a connection between Rational Build Forge and the database.

To re-establish the connection:

  1. Shut down Rational Build Forge, as discussed in Starting and stopping the Perl engine.
  2. Make sure the database is running.
  3. Start Rational Build Forge, as discussed in Starting and stopping the Perl engine.

Feedback