Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Crowd (tomcat) access logs loosing contents as they rotate daily




We are noticing that our crowd (tomcat) access logs are getting converted into 1 KB files everyday as they rotate. Only the current day log retains all the data.

once it rotates (i.e. gets the date appended to it), it looses all its contents except first 4-5 lines


Below is the snippet of AccessLogValve from the server.xml, 

<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs" prefix="crowd_access_log." suffix=".log" pattern="%a %t %I &quot; %m %U%q %H &quot; %s %b %D &quot; %a &quot; %D %F" resolveHosts="false" />


Any suggestions will be really appreciated.


Thank you,
Arun Sharma

2 answers

Hi Arun,

If all configs are same between prod and non prod, then one of reason you don't see the issue in non prod is may be there is no enough load in non prod to write into access Logs. Just a thought may be you already aware of it. 


Have you checked crontab for any custom log rotation scripts that may be setup and causing this issue.

What is the version of crowd running?

Hi Reneesh,

Its 2.11.1

The issue is there from more than a year. 

Server.xml content matches with that of other instances,. And it is working fine for them

So you have crowd running as cluster with this issue on one server in the cluster? Check the user crowd is running as and check the crontab for any logs rotation script setup.

Hi Reneesh,

It is a single server, not in cluster. From other instances I meant that non prod environments.

The issue is only in production environment, that is why we are not playing around with it to see what is going wrong, all the configs look exactly the same to non-prods and the non-prods work fine.


Appreciate your help on this.

Thank you,
Arun Sharma

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events