conntrack log file taking up 40Gb after 1 month

Bug #1497287 reported by Sam Stoelinga
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Kyrylo Galanov
6.1.x
Confirmed
High
MOS Maintenance
7.0.x
Confirmed
High
MOS Maintenance

Bug Description

Conntrack log file which became about 40Gb took up the whole root filesystem after running an 6.1 env for a month. Had to delete the conntrack log file and after that kill the process which opened the log file with `lsof | grep "/var" | grep deleted`

I don't have any specifics to reproduce other than run a 8 node environment with 3 controllers in HA using OVS + vlan.

Version: 6.1 nightly build
  build_number: "273"
  build_id: "2015-06-12_05-40-59"

Edit: After inspecting conntrackd.conf I found that following parameter is present LogFile off so there shouldn't be any logfile but there was a logfile. Can anybody check whether /var/log/conntrackd.log is present?

description: updated
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
Changed in fuel:
milestone: none → 8.0
importance: Undecided → High
status: New → Confirmed
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Kyrylo Galanov (kgalanov)
Revision history for this message
Matthew Mosesohn (raytrac3r) wrote :

We should just add "/var/log/conntrack*.log" to our list of files to rotate.

tags: added: logging low-hanging-fruit
Revision history for this message
Sam Stoelinga (sammiestoel) wrote :

It seems to me there shouldn't have been a log in the first place after looking at conntrackd.conf but I could be wrong. I didn't understand why the log file was created and became this big, as after restarting the service the log file wasn't recreated. The option LogFile off was present

Revision history for this message
Kyrylo Galanov (kgalanov) wrote :

Hi Sam,

Do you still face this issue?
What is the 'tail' of /var/log/conntrackd.log file?

Best regards,
Kyrylo

Revision history for this message
Sam Stoelinga (sammiestoel) wrote :

I did not face this issue after restarting conntrackd and the contrackd.log file is no longer present after the restart.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.