Common errors in TeamForge

Common problems and solutions in TeamForge.

• Why do I get a proxy timeout when I try to view certain SCM pages?
  If you are getting a proxy timeout error when you try to view a SCM page, you may need to configure the Apache 2.2 Proxy Timeout to 300 or less in the httpd.conf file.
• Why do I get a URL "not found" or "moved permanently" error after applying a patch/upgrade?
  If you are experiencing a URL "NOT FOUND" or "MOVED PERMANENTLY" error after applying a patch or upgrade Apache ProxyPreserveHost token to on in the httpd.conf file.
• Why can't SourceForge send my outbound mail?
  If you are unable to send email directly due to firewall restrictions, or if mail is being rejected by the application server's IP address, configure SourceForge to send outgoing messages through a gateway mail server.
• Not all my team members appear in the "assigned to" field. Why is that?
  In order to appear in the Assigned To field, the user must belong to a role giving them edit/view permissions on the tracker.
• Why does my Hudson job fail with the following error: ERROR: svn: authentication cancelled org.tmatesoft.svn.core.SVNCancelException: svn: authentication cancelled?
  This may be due to bad cached credentials in the user.subversion/auth directory. To correct this, remove this directory and perform a manual checkout as the hudson user.
• How can a user who deleted a document get it back?
  It is possible to recover the latest version of a document if someone has accidentally deleted it from SourceForge. However, note that you can recover the raw document but not undelete it from the app. The user will have to add the document back into SourceForge, and the history of the document will not be recovered. If you need a true undelete so that the history is available, please contact Technical Support and ask for us to schedule our Professional Services group for you.
• Why are the dynamic images that SourceForge creates broken?
  If you have a fresh install of SourceForge and you're noticing that the dynamic images are not correct, you may be missing a library that is needed to create the images. Check this using the steps below.
• Why can't I commit to the repository?
  A security check was introduced in SourceForge 4.3 SP1 that will cause commits to fail if the system time differs too much between the Integration and Application server. This will also cause the Integration server to fail to connect to the Application server on the server status page. This behavior is controlled by the following setting in sourceforge.properties on the Integration server:
• Why does startup fail or produce errors?
  If SourceForge fails to start up, or is starting but is throwing errors on every page, then typically something went wrong during the JBOSS bootstrap process. Fortunately, JBOSS logs this process to: /usr/local/sourceforge/jboss/jboss-<version>/server/default/log/boot.log.