Your message dated Tue, 27 Aug 2024 09:54:42 +0000
with message-id <[email protected]>
and subject line Bug#1078911: fixed in puppetserver 8.4.0-5
has caused the Debian Bug report #1078911,
regarding missing reports cleanup job
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
1078911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078911
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: puppetserver
Version: 7.9.5-2
Severity: grave

On our "good old" puppetmaster server running 5.5, we have a cron job
that cleans up old reports, part of the Debian package:

root@pauli:/etc# cat cron.daily/puppet-master 
#!/bin/sh

if [ -e /var/lib/puppet/reports ] ; then
        find /var/lib/puppet/reports -maxdepth 2 -type f -ctime +30 -delete
fi

exit 0
root@pauli:/etc# dpkg -S cron.daily/puppet-master
puppet-master: /etc/cron.daily/puppet-master

(In fact, we have *another* similar job here:

root@pauli:/etc# cat cron.d/local-puppet-reports
@daily root [ -d /var/lib/puppet/reports ] && find /var/lib/puppet/reports 
-type f -mtime +30 -delete && find /var/lib/puppet/reports -type d -empty 
-delete

... where that is from is a mystery to me... Also notice how it checks mtime
instead of ctime, doesn't have the empty cleanup, aand the maxdepth. Anyways.)

On my home lab running the shiny new puppetserver from bookworm (well,
not so new anymore, but anyway), I *don't* have such a job. And today,
/var ran out of disk space, with /var/lib/puppet/reports taking a
whopping 45GiB of disk space. 

I stopped the bleeding by purging all the 2023 reports by hand, which
freed up 10GiB, but it really seems to me we dropped something in that
upgrade there, we should have a cron job or systemd timer that does that
cleanup automatically.

What exactly the command should be doesn't seem to matter much, all
those three are equivalent on my end:

root@marcos:/home/anarcat# find /var/lib/puppet/reports -maxdepth 2 -type f 
-ctime +30 | wc -l 
5242
root@marcos:/home/anarcat# find /var/lib/puppet/reports -maxdepth 2 -type f 
-mtime +30 | wc -l 
5242
root@marcos:/home/anarcat# find /var/lib/puppet/reports -type f -mtime +30 | wc 
-l 
5242

And it finds only one empty directory, from a node that hasn't ran in
ages and should probably be considered lost/retired at this point. Still
seems like a good idea to add that as well.

I mark this as grave because it can "cause data loss" (in my case
bounced email) due to unbounded disk usage.

A.

-- System Information:
Debian Release: 12.6
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable'), 
(1, 'unstable'), (1, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-23-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages puppetserver depends on:
ii  default-jre-headless                         2:1.17-74
ii  facter                                       4.3.0-2
ii  hiera                                        3.10.0-1
ii  jruby                                        9.3.9.0+ds-8
ii  libclj-time-clojure                          0.15.2-2
ii  libclj-yaml-clojure                          0.7.2-1
ii  libclojure-java                              1.11.1-2
ii  libcomidi-clojure                            0.3.2-2
ii  libcommons-exec-java                         1.3-2
ii  libcommons-io-java                           2.11.0-2
ii  libcommons-lang-java                         2.6-10
ii  libdropwizard-metrics-java                   3.2.6-1
ii  libdujour-version-check-clojure              0.2.3-1
ii  libjruby-utils-clojure                       4.0.3-4
ii  libkitchensink-clojure                       3.2.1-1
ii  libliberator-clojure                         0.15.3-1
ii  libprismatic-schema-clojure                  1.2.0-4
ii  libpuppetlabs-http-client-clojure            2.1.1-1
ii  libpuppetlabs-i18n-clojure                   0.9.2-2
ii  libpuppetlabs-ring-middleware-clojure        1.3.1-3
ii  libraynes-fs-clojure                         1.5.2-1
ii  libsemver-clojure                            0.3.0-2
ii  libshell-utils-clojure                       1.0.2-3
ii  libslingshot-clojure                         0.12.2-3
ii  libssl-utils-clojure                         3.5.0-2
ii  libtrapperkeeper-authorization-clojure       1.0.0-4
ii  libtrapperkeeper-clojure                     3.2.0-4
ii  libtrapperkeeper-comidi-metrics-clojure      0.1.2-2
ii  libtrapperkeeper-filesystem-watcher-clojure  1.2.2-3
ii  libtrapperkeeper-metrics-clojure             1.5.0-5
ii  libtrapperkeeper-scheduler-clojure           1.1.3-7
ii  libtrapperkeeper-status-clojure              1.1.1-4
ii  libtrapperkeeper-webserver-jetty9-clojure    4.4.1-5
ii  libyaml-snake-java                           1.33-2
ii  puppet-agent                                 7.23.0-1
ii  ruby                                         1:3.1
ii  ruby-deep-merge                              1.1.1-2
ii  ruby-fast-gettext                            2.0.3-2
ii  ruby-gettext                                 3.3.3-2
ii  ruby-hocon                                   1.3.1-2
ii  ruby-locale                                  2.1.3-1
ii  ruby-puppet-resource-api                     1.8.16-2
ii  ruby-puppetserver-ca-cli                     2.4.0-4
ii  ruby-semantic-puppet                         1.0.4-1
ii  ruby-text                                    1.3.1-1

Versions of packages puppetserver recommends:
ii  puppet-module-puppetlabs-augeas-core   1.1.2-1
ii  puppet-module-puppetlabs-cron-core     1.1.0+dfsg1-1
pn  puppet-module-puppetlabs-host-core     <none>
pn  puppet-module-puppetlabs-mount-core    <none>
pn  puppet-module-puppetlabs-selinux-core  <none>
ii  puppet-module-puppetlabs-sshkeys-core  2.3.0-1

puppetserver suggests no packages.

-- Configuration Files:
/etc/puppet/puppetserver/conf.d/auth.conf [Errno 13] Permission non accordée: 
'/etc/puppet/puppetserver/conf.d/auth.conf'
/etc/puppet/puppetserver/conf.d/ca.conf [Errno 13] Permission non accordée: 
'/etc/puppet/puppetserver/conf.d/ca.conf'
/etc/puppet/puppetserver/conf.d/global.conf [Errno 13] Permission non accordée: 
'/etc/puppet/puppetserver/conf.d/global.conf'
/etc/puppet/puppetserver/conf.d/metrics.conf [Errno 13] Permission non 
accordée: '/etc/puppet/puppetserver/conf.d/metrics.conf'
/etc/puppet/puppetserver/conf.d/puppetserver.conf [Errno 13] Permission non 
accordée: '/etc/puppet/puppetserver/conf.d/puppetserver.conf'
/etc/puppet/puppetserver/conf.d/web-routes.conf [Errno 13] Permission non 
accordée: '/etc/puppet/puppetserver/conf.d/web-routes.conf'
/etc/puppet/puppetserver/conf.d/webserver.conf [Errno 13] Permission non 
accordée: '/etc/puppet/puppetserver/conf.d/webserver.conf'
/etc/puppet/puppetserver/logback.xml [Errno 13] Permission non accordée: 
'/etc/puppet/puppetserver/logback.xml'
/etc/puppet/puppetserver/request-logging.xml [Errno 13] Permission non 
accordée: '/etc/puppet/puppetserver/request-logging.xml'
/etc/puppet/puppetserver/services.d/bootstrap.cfg [Errno 13] Permission non 
accordée: '/etc/puppet/puppetserver/services.d/bootstrap.cfg'
/etc/puppet/puppetserver/services.d/ca.cfg [Errno 13] Permission non accordée: 
'/etc/puppet/puppetserver/services.d/ca.cfg'

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: puppetserver
Source-Version: 8.4.0-5
Done: Thomas Goirand <[email protected]>

We believe that the bug you reported is fixed in the latest version of
puppetserver, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand <[email protected]> (supplier of updated puppetserver package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Tue, 27 Aug 2024 11:21:52 +0200
Source: puppetserver
Architecture: source
Version: 8.4.0-5
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 
<[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Closes: 1078911
Changes:
 puppetserver (8.4.0-5) unstable; urgency=medium
 .
   * Add debian/puppetserver.cron.daily to clean-up reports (Closes: #1078911).
Checksums-Sha1:
 ca01e61248d78fa88d157b68e3454843d6c7ec69 3917 puppetserver_8.4.0-5.dsc
 d8e59d59b6ee6f80d175b647106ddce52e0ac3de 26124 
puppetserver_8.4.0-5.debian.tar.xz
 df3ba0d80e2866b6af78c242488c8b924be409cf 16832 
puppetserver_8.4.0-5_amd64.buildinfo
Checksums-Sha256:
 4d89b1a2118759dc3685414e8faf101a3b654c777bc5b33f3b6aad05e2849d88 3917 
puppetserver_8.4.0-5.dsc
 b3e88ab6ec7a5b91cefd8cc7e7e9ff7b4287a4856a8e6176bca992b468950863 26124 
puppetserver_8.4.0-5.debian.tar.xz
 e13a482273adb0cd6aafaeb0f7755d6928851c58af069570db9f2e1d6fa753cf 16832 
puppetserver_8.4.0-5_amd64.buildinfo
Files:
 0e1fda03f8ec516c6839f8b916ed3a2d 3917 admin optional puppetserver_8.4.0-5.dsc
 653ae5dd58bc933d5f4f646a25033732 26124 admin optional 
puppetserver_8.4.0-5.debian.tar.xz
 30acb754b4c3998f2e12eb4b2e08ef24 16832 admin optional 
puppetserver_8.4.0-5_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmbNnVQACgkQ1BatFaxr
Q/44Sw//bZeilympogH6BO65MVtxZx5v1L8Yi6XRgQXgo1nxbrdDTHiTdIGwUzke
L3nWjCptsDbdWu7RnjnE4B1qlGfgZ/cMdbc3MdkOhpCJ2gCyD8s+gRAdvyIhcwww
VbFSniQmnef8kteeGxLRzVAUM9ciDFV45bpZr+b4NrPlyN7Hk0n5sqIx3r0E+jr4
R1xyxGWgHpArwaKfN3nL7/ApZHVNfuh4jOU+vjf1B8RpEWlwqExNj8YxS11Y3pw/
mbGKQB0K/eJLsHajP8giUBxgbQRsoWvN+hQSIIgEhBSyCG4+4zDwfPEUiYb4Jp7t
sRf2BgtG9G0c3W3HyX3IwhJqcjxAIUoDk93Ir8fqtmmXP25xTDJQpSm/cUUbYAnz
sbfNnwGtIhaajvdHuD21c5glXRqGmesticTE2q3mJ9DpFSdh8MWa5SU2y6TucvZi
A4yPTNrG7ChPn+jXIKUAbGmazeFwyoxOddy3vY9lUlcooWh5sG91O2wgU4dxaZVA
QlA1Ei8FwpPnYrtjFiiqTrwnfl6bJ2hfxmVDyy4mVp+5La91/gi0qyMGZyYddM0L
fWbJasudRBoUmv52W+cCPOCIuueriNcrAwMFDB0xCeVnJHGwpd0/ZjihkN4NHpKf
Vj3kZjQrno1XGQsLvuUrgoKr2kY1jHFicvLOeDQK/U3W04QFLg4=
=Vgaw
-----END PGP SIGNATURE-----

Attachment: pgp_nLHLn7oAi.pgp
Description: PGP signature


--- End Message ---

Reply via email to