Your message dated Sat, 07 May 2016 00:33:52 +0000 with message-id <[email protected]> and subject line Bug#822248: fixed in sks 1.1.5-5 has caused the Debian Bug report #822248, regarding ifupdown: service failed to brought up because addresses not yet configured 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.) -- 822248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822248 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: ifupdown Version: 0.8.11 Severity: important Hi. Since quite a while already (but after we've discussed that in another bug) I have one particular case again in which a daemon, that is configured to bind to particular addresses fails to start, because when it does, the address is apparently configured. Apr 22 15:25:28 kronecker sks[825]: Starting sks daemons: sksdb.. sksrecon.. done. Apr 22 15:25:28 kronecker systemd[1]: Started sks.service. ... Apr 22 15:25:28 kronecker sks[825]: 2016-04-22 15:25:28 Failed to listen on 1.2.3.4:11370: Failure("Failure while binding socket. Probably another socket bound to this address") Apr 22 15:25:28 kronecker sks[825]: 2016-04-22 15:25:28 Failed to listen on a:b:c:d::1:2:11370: Failure("Failure while binding socket. Probably another socket bound to this address") Apr 22 15:25:28 kronecker sks[825]: Fatal error: exception Failure("Could not listen on any address.") IIRC, this didn't come with an upgrade of ifupdown (but maybe I'm wrong), so perhaps there are still some timing issues or it was due to a chance in systemd? Last time we've had discussed issues like these, the resolution, AFAIR, was to use auto/allow-auto, right? This is the case, i.e. lo and eth0 (on which the addresses above are set is brought up with allow-auto). Interestingly, sks runs two daemons (or better said the same one in two modes, db and recon)... db always succeeds to start up, while recon always fails. Any ideas? Chris. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ifupdown depends on: ii adduser 3.114 ii init-system-helpers 1.29 ii iproute2 4.3.0-1+b1 ii libc6 2.22-7 ii lsb-base 9.20160110 Versions of packages ifupdown recommends: ii isc-dhcp-client [dhcp-client] 4.3.4-1 Versions of packages ifupdown suggests: ii ppp 2.4.7-1+2 pn rdnssd <none> -- debconf information: ifupdown/convert-interfaces: true
--- End Message ---
--- Begin Message ---Source: sks Source-Version: 1.1.5-5 We believe that the bug you reported is fixed in the latest version of sks, 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. Daniel Kahn Gillmor <[email protected]> (supplier of updated sks 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, 06 May 2016 20:10:29 -0400 Source: sks Binary: sks Architecture: source Version: 1.1.5-5 Distribution: unstable Urgency: medium Maintainer: Christoph Martin <[email protected]> Changed-By: Daniel Kahn Gillmor <[email protected]> Description: sks - Synchronizing OpenPGP Key Server Closes: 715360 795080 822248 Changes: sks (1.1.5-5) unstable; urgency=medium . * canonicalize header files * bump to Standards-Version 3.9.8 (no changes needed) * move logrotate from Depends: to Suggests: * pull upstream fixes, and changes that support handling Curve 25519 keys * make sysvinit script depend on $network (Closes: #822248) * Depend: on db-util so that cronjob can clean up (Closes: #795080) * added systemd service files (Closes: #715360) Checksums-Sha1: 7939b1d1974979464911e2590e93dba7b176a378 2112 sks_1.1.5-5.dsc 5605be997832b791afdea60d0ef35b65dbb9b749 23608 sks_1.1.5-5.debian.tar.xz Checksums-Sha256: ddc6b3e3743bf2854dba0dff2ac513b11acc98357790bd47cd16bfde5b60c906 2112 sks_1.1.5-5.dsc d27718531e4a81f771bd9387f7ddd0786ea009eccb08bf13a763c83f1fe08419 23608 sks_1.1.5-5.debian.tar.xz Files: 2260b89778707bf746ade3424002e5a7 2112 net optional sks_1.1.5-5.dsc 12b9d49e20a4ea2831fa301c045a44c9 23608 net optional sks_1.1.5-5.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJXLTSRXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRFREIyRTc0RjU2RkNGMkI2NzI5N0I3MzUy NEVDRkY1QUZGNjgzNzBBAAoJECTs/1r/aDcKTgIP/0kRU8NvUMfxXYouy/YIQ3dq Vf4sOYGEDm5wTZLPV33VN7WAneL9qOwn4f+PyXS17z77RAgh+Is49WAOyr8j1GJI 3pcLL95xP5SWAsEPyamYkoAEjfoGk7hNtZOlFXJiyjc3sabGczouTe7XY762dkxh aNAnPQa0v7XSAecgiu/QYx4HSQ1WL9jQJnJ6GD2x77uO7twdFeTr4nyO7lXKM0de m2eB1bpQJd8ArtUu5d6/tCiZHBN1w0WfnCG0hobfLIQCwXwfjWlb7L0MbfWYZ4k1 PhyohOFCdNOaLAkQSc/olCIY0Jsig1mV6oDsYFEbWVs/il4nYERtCKMqwFiCNhmv gQNqqq+kgSwJzvOWxCgsOnJSEW7xuBRJEJCCS4Fnnve0Rg5EBXUNNe732Oxv2B8S C/elCVjT4UQAeGh+8JCxqBmlIhgIfyi4H8vcPLQtzH0LsLQLlNKhUThffT2rL4hs EFiCuJn1w45NDRiTKUPrXhGqTqAFKf7ZxCkgMdMi5ciGL58Fxkkoe2dBFUVONZiD AB4pvMhFpWie2MYozC1W8h/HTNOQcfrkNx1lwzC3/zriRk0wdpJQYhKkN1MSc6wC O5ebXCq6R7doxEJ1uCc5MKItO37JPgmJA3QzrxwXvTr8ioP5JEfSmkDbR+4/vHS4 w8b6o+S5ydEBe+hHC7B7 =RddQ -----END PGP SIGNATURE-----
--- End Message ---
