Your message dated Fri, 17 Mar 2023 16:19:25 +0000
with message-id <[email protected]>
and subject line Bug#1031326: fixed in crowdsec 1.4.6-2
has caused the Debian Bug report #1031326,
regarding crowdsec: delays during upgrade from 1.0.9-*
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.)


-- 
1031326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031326
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: crowdsec
Version: 1.4.2-1
Severity: important

Hi,

Seen during upgrade tests, starting at 1.0.9-*: there's an important
delay (~ 1 minute) during the upgrade, with no apparent activity.
According to crowdsec.log, we're waiting for the existing process to
shut down following the SIGTERM:

    time="14-02-2023 22:27:53" level=info msg="Crowdsec engine shutting down"

I'll ask upstream to comment on this. Gut feeling would be: it might be
acceptable to be a little more aggressive, tweaking the postinst script
to include some sort of timeout, and killing the existing process after
say 10 seconds (if terminating didn't return by then). Of course, if a
clean shutdown is preferable (internal data that need to be stored,
etc.), maybe it'll be better to actually dig into why the old version is
taking so long to shut down. But a fix would likely involve pushing an
update to stable, which would be more work for everyone…


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

--- End Message ---
--- Begin Message ---
Source: crowdsec
Source-Version: 1.4.6-2
Done: Cyril Brulebois <[email protected]>

We believe that the bug you reported is fixed in the latest version of
crowdsec, 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.
Cyril Brulebois <[email protected]> (supplier of updated crowdsec 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: SHA512

Format: 1.8
Date: Fri, 17 Mar 2023 14:42:04 +0100
Source: crowdsec
Architecture: source
Version: 1.4.6-2
Distribution: unstable
Urgency: medium
Maintainer: Cyril Brulebois <[email protected]>
Changed-By: Cyril Brulebois <[email protected]>
Closes: 1031324 1031326 1031328
Changes:
 crowdsec (1.4.6-2) unstable; urgency=medium
 .
   * Prefix package version with `v` when setting BUILD_VERSION, e.g.
     crowdsec/v1.4.6-2-linux-debian (Closes: #1031324).
   * Stop shipping a logrotate configuration snippet, as crowdsec rotates
     logs on its own via lumberjack.Logger, and that can be configured in
     the main configuration file (/etc/crowdsec/config.yaml):
      - Delete debian/crowdsec.logrotate
      - Add debian/crowdsec.conffiles, marking /etc/logrotate.d/crowdsec
        with the remove-on-upgrade flag.
   * When purging the package, remove internally-rotated log files, in
     addition to removing main log files and the logrotate-generated ones.
   * Really enable upstream-recommended collections, not just the items
     they require: everything would work fine without this, but those
     collections wouldn't appear in `cscli collections list`, and they
     wouldn't be upgraded if admins decided to switch to the online hub.
   * Compensate for the missing collections when upgrading from 1.4.6-1
     specifically (including binNMUs).
   * Enable the crowdsecurity/whitelists parser as well.
   * When performing a fresh install (as determined by the postinst's being
     called with just `configure`), and when /run/systemd/system exists,
     apply a workaround for upstream issue #2120 based on crowdsec.log:
      - Exit immediately if the unit is not active (e.g. the admin masked
        it before installing the package).
      - Check whether entries are received from the Central API, and exit
        if that's the case.
      - Check whether `received 0 new entries` is logged, and restart then
        exit if that's the case.
      - Repeat those checks every second, up to 20 times.
   * When performing an upgrade from pre-1.4.x versions, apply a workaround
     to avoid huge delays at the `restart` step: lower TimeoutStopSec from
     90s (default) to only 20s, using a runtime override (Closes: #1031326).
   * Add a dh_install-indep override to get rid of files left over after
     running the test suite (Closes: #1031328).
Checksums-Sha1:
 594f200d5373a5b967725d85b6cd88baf68cb202 4936 crowdsec_1.4.6-2.dsc
 4190b46cf07d3c52170bac1a868f6f0428e0632f 26480 crowdsec_1.4.6-2.debian.tar.xz
 f94fa378bbf5f45a851d0d6739afd7fb5be39464 7644 crowdsec_1.4.6-2_source.buildinfo
Checksums-Sha256:
 9867f3be59108b625d503a4de5a97d8c6b56eed732cb4c58443e21701db12725 4936 
crowdsec_1.4.6-2.dsc
 a836fe283177bc5ad64e705fe6ef3fca6d066f5a1913e6ae71f3911e41797ad4 26480 
crowdsec_1.4.6-2.debian.tar.xz
 90b91c11b1642c7635c25a4aff7dd0cf8458b4d28df773688b13b78627270692 7644 
crowdsec_1.4.6-2_source.buildinfo
Files:
 2792177eed110cf25e91e6dfb39f01eb 4936 golang optional crowdsec_1.4.6-2.dsc
 b58d467016a1a8dcadb6ab0a53da7d45 26480 golang optional 
crowdsec_1.4.6-2.debian.tar.xz
 c19e324b0ac57a3b7289d6b3e19ea296 7644 golang optional 
crowdsec_1.4.6-2_source.buildinfo

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

iQJEBAEBCgAuFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmQUjx4QHGtpYmlAZGVi
aWFuLm9yZwAKCRD/kUrwwrNVIKSkD/sHRf2ovjTuX8uc7g2LN3JA0tfjfkuOdNin
b0St6PWpB1CQhkKiM89vkXbvOlsE/kc21x4R3v7zmwbSOSsnxqYCwcCurX8tYwF7
ipi4M4PCXSY0HqZobnWlgGO9hDjayU95E2FOj9Sl2IUrYJBUG0jmf6WonqKWmtan
tf9E29SJXKtXOsvDjXSWLumlmdq5oC/ntFNxKcgNkbFT/7gna7pjp9gvn5QEogBO
y9lT5wSZ58g3UZj91Cj58TqAet2ea7phRypb6UlQ63TXXSikwFBQcZOC4Lara9PC
K9q4y75mC3LPhGiuHCFUk44x3ptibvGkAn65taUkksfp96kJOFsugnGZOfD+Gb6V
DLQl+rj6Xu6BPV2ybSAKRVq/QLFrF31puto0a0hQjh77v2OgSWDT/zkEFWfWORP2
M4PZ9b6iVUQFW6/XBjmp+AoyBpxhYC+woKk/anZkTV6Rdlg+egWc3H8RNFUSWGnZ
yFCMOBcnsipdtbwYG0Swt89RJlntORLdFBsav04Bn7lbn55v5R3+ESy6eSwYdOSc
FbdJFZ/CGCWw3FFYBHZv6RJzOWM/k4i/ZJOXZio0c9Zy98momthSYr8nO7lE+L4O
C2UNEMjICwYiSabfMW2c1QJ6P3+6tOnBTlnobTcWcNc0SZ3EdWZaXqj3hkJwFfvt
LWKTC3hrUQ==
=FRP5
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to