Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

remove growing log files

Hi Community,

our Jira instance is running on a linux system. The log files are growing quiet large under [...]/jira/logs and I already followed this suggestions to reduze catalina.out size. https://confluence.atlassian.com/jirakb/configure-log-rotation-for-the-catalina-log-in-jira-server-224398003.html

In this directory there are plenty of other log files. The files are created every day new. It's about the following files:

  • manager.<timestamp>.log
  • localhost.<timestamp>.log
  • host-manager.<timestamp>.log
  • catalina.<timestamp>.log
  • atlassian-jira-gc-<timestamp>.log.0.current
  • access_log.<timestamp>

My newbie question is, if I can remove those files after like 1 month or so. Or do I / the application need those files? As I told I don't really know these files and never needed them. Can anybody explain and give an advice how to handle. Thanks!

1 answer

1 accepted

1 vote
Answer accepted

There is no harm in removing most of these files, they're not actively used by the system and deletion won't affect them.   Sometimes Jira will stop logging (which you don't want) if you remove the currently active version of the log (it'll start logging again on the next day or restart).  That glitch won't affect the running of the system though, it really is just not writing the logs.

I'd recommend you keep some of them for a while, just in case someone reports an issue that you need to go to the logs for help with.  After all, that's what they're for!  And sometimes the access log is useful for longer, but the rules are up to your needs

I usually set up a logrotate that does something really simple like "every day, delete logs over 8 days old (32 for access_log)"

Just don't delete logs for today, and you won't have any problems.

Thanks Nic for your answer. Will do so. 

Appreciate your help!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...

405 views 19 23
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you