How to enable email debug logging manually without using Fisheye/Crucible administration

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Symptoms

There are times, the email debug logging might not work properly even if it had been enabled under the Fisheye administration. The email debug logging can be enabled at Administration >> Global Settings >> Server >> Mail Server.

Resolution

When enabling the email debug logging from the Fisheye administration did not work, you can perform the following to enable the email debug logging manually from the configuration file:-

  1. Shutdown Fisheye/Crucible instance

  2. Navigate to FishEye/INST folder path

  3. Backup the file log4j.xml and open it using any text editor

  4. Find the fisheye.mail logger tag in the xml file and modify the level value from info to debug as shown below:-

    1 2 3 <logger name="fisheye.mail"> <level value="debug"/> </logger>
  5. Close and save the file

  6. Start your Fisheye/Crucible instance

Updated on April 8, 2025

Still need help?

The Atlassian Community is here for you.