Skip to content
Snippets Groups Projects

Resolve "Repmgr logrotation stops working"

Closed Ian Baum requested to merge 2695-repmgr-logrotation-stops-working into master
2 unresolved threads
Edited by Ian Baum

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
87 87 #{mattermost_user}
88 88 #{registry_user}
89 89 #{prometheus_user}
90 #{consul_user}
91 90 )
91 userlist << consul_user if node.recipe?('gitlab-ee::default')
  • DJ Mountney
    DJ Mountney @twk3 started a thread on the diff
  • 35 35 end
    36 36
    37 37 node['gitlab']['logrotate']['services'].each do |svc|
    38 if node['gitlab'].key?(svc)
  • Contributor

    @ibaum I'm not very familiar with logrotate myself. But it looks like our current config only rotates .log files, and if I turn on consul, and check it's log directory for example, it only has the runit logs.

    Also, we should add the log directories to the gitlab.rb template, in the cases where they aren't already. Like Repmgr

  • assigned to @ibaum

  • Author Developer

    Thanks @twk3, I looked a little closer at the problem, and it's not a problem :) For consul and repmgr at least. I do still need to update pgbouncer.

    As part of #2712 (closed) we got rid of repmgr.log and just use the runit logs for repmgr. As you pointed out, consul is already doing this, so logrotate isn't coming into play for either of these. The svlogd rotation should be working fine for both of these.

  • closed

  • Please register or sign in to reply
    Loading