Skip to end of banner
Go to start of banner

Problem Determination Information - 4.x

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Description

If requested by our support representative, please follow these steps to turn on some debug logging that helps us determine the problem.

Steps to collect debug information

  1. Read: Confluence logging - how to configure additional temporary logging in Confluence
  2. Add an entry for DEBUG using org.swift.confluence.macrosecurity
    • Temporary logging gets you started without a server restart. It does not carry over after restart.
    • Should look like: 
  3. Run a test scenario and then look in the server log. Find the time period close to your test run time and look for entries including text: org.swift.confluence.macrosecurity
    • If none found, then search for macrosecurity (as logging output can vary)
  4. Attach one of the following
    1. Cut and paste the entries into a comment (if small) or into a file and attach (recommended)
    2. Ensure the Zip of your server log doesn't contain sensitive information
    3. Copy your server log and remove earlier entries or other information you may not want to share
  • No labels

Log a request with our support team.

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.