[Bug 1527685] Re: Please merge freeipmi 1.4.11-1 (main) from Debian unstable (main)
Temporary build also available at https://launchpad.net/~tdaitx/+archive/ubuntu/openjdk/+sourcepub/5845178 /+listing-archive-extra ** Patch added: "debdiff between debian 1.4.11-1 and the proposed merge 1.4.11-1ubuntu1" https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1527685/+attachment/4536998/+files/debdiff_freeipmi_1.4.11-1_-_freeipmi_1.4.11-1ubuntu1.diff ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to freeipmi in Ubuntu. https://bugs.launchpad.net/bugs/1527685 Title: Please merge freeipmi 1.4.11-1 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1527685/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527685] [NEW] Please merge freeipmi 1.4.11-1 (main) from Debian unstable (main)
Public bug reported:
Please merge freeimpi 1.4.11-1 into Ubuntu. There are multiple changes,
some of which are bug fixes, and some of which are workarounds and other
changes. Most patches in debian/patches from 1.1.5-3ubuntu7 have been
upstreamed as well.
-
freeipmi's 1.4.11 NEWS file has 583 lines of new features, bug fixes,
and overall changes since the 1.1.5 release. See
http://sources.debian.net/src/freeipmi/1.4.11-1/NEWS/
-
Debian changelog entries since 1.1.5-3ubuntu7 release:
freeipmi (1.4.11-1) unstable; urgency=medium
* [186d83b] Merge tag 'upstream/1.4.11'
Upstream version 1.4.11
* [95cfc3a] Updating symbols file.
-- Bernd Zeimetz Wed, 25 Nov 2015 21:40:35 +0100
freeipmi (1.4.9-1) unstable; urgency=medium
* Fresh upstream release
- removes duplicate entry from manpage (Closes: #781633)
-- Yaroslav Halchenko Wed, 01 Jul 2015
09:52:35 -0400
freeipmi (1.4.5-3) unstable; urgency=medium
* ACK and re-include NMU 1.4.4-1.2
-- Yaroslav Halchenko Wed, 08 Oct 2014
10:15:25 -0400
freeipmi (1.4.5-2) unstable; urgency=medium
* Return to using /etc/logrotate.d/bmc-watchdog (Closes: #763136)
-- Ferenc Wágner Tue, 07 Oct 2014 10:21:42 +0200
freeipmi (1.4.5-1) unstable; urgency=medium
* [7e02411b] Merge tag 'upstream/1.4.5'
Upstream version 1.4.5
-- Bernd Zeimetz Sun, 05 Oct 2014 14:08:36 +0200
freeipmi (1.4.4-1.2) unstable; urgency=medium
* Non-maintainer upload.
* Fix debian/libipmimonitoring5a.symbols after incomplete
SONAME bump (Closes: #760920)
-- Jonathan Wiltshire Tue, 09 Sep 2014 14:33:33 +0100
freeipmi (1.4.4-1.1) unstable; urgency=medium
* Non-maintainer upload.
* Add postinsts to replace /usr/share/doc/*
with a symlink (Closes: #691439)
-- Jonathan Wiltshire Sun, 07 Sep 2014 13:09:22 +0100
freeipmi (1.4.4-1) unstable; urgency=low
[ Tollef Fog Heen ]
* New upstream release
- bump sonames
- new tool: ipmi-config
- refresh quilt patches
- upstream dropped freeipmi-bmc-watchdog logrotate.d snippet,
reintroduce as a Debian patch.
* Add freeipmi-ipmiseld package.
* Adjust dh_fixperms_override call to only be called on binary-indep.
-- Yaroslav Halchenko Fri, 15 Aug 2014
09:23:03 -0400
freeipmi (1.1.6-1) experimental; urgency=low
* [35d19e11] Merge tag 'upstream/1.1.6'
Upstream version 1.1.6
* [b343fe99] Add myself to Uploaders.
* [b7ece9fc] Refreshing patches, dropping those which were applied upstream.
-- Bernd Zeimetz Fri, 03 Aug 2012 15:31:39 +0200
freeipmi (1.1.5-4) experimental; urgency=low
[ Ferenc Wágner ]
* Refresh lintian overrides
* Fix typo (meta-package) in control file found by lintian
* New quilt patch to fix upstream typos found by lintian
* debian/control:
- remove duplicate Section fields
- add myself to Uploaders
- add ipmi-pet to freeipmi-tools description
* debian/rules:
- make mode and ownership change on freeipmi.conf effective
- go to debhelper compatibility level 9, but keep away from multiarch
- keep both upstream ChangeLogs and provide the changelog symlink
- install manpages and documentation via dh_install and make use of
--fail-missing
- trust dh_installdocs --link-doc to arrange things correctly
- clean up unused copy of bmc-watchdog default file to misspelled name
* debian/copyright:
- Link to versioned licence texts (suggestion by lintian
copyright-refers-to-symlink-license)
* Install symlinks for dash-separated utility names
* debian/source/options:
- Ignore files changed during build
[ Yaroslav Halchenko ]
* Listed the team as the Maintainer and moved myself into Uploaders
* Point to team's GIT repository on alioth instead of a private one
-- Yaroslav Halchenko Wed, 11 Jul 2012
13:34:54 -0400
** Affects: freeipmi (Ubuntu)
Importance: Undecided
Assignee: Tiago Stürmer Daitx (tdaitx)
Status: New
** Changed in: freeipmi (Ubuntu)
Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to freeipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1527685
Title:
Please merge freeipmi 1.4.11-1 (main) from Debian unstable (main)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1527685/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1527306] [NEW] Sync freeipmi 1.4.11-1 (main) from Debian unstable (main)
Public bug reported: Please sync freeipmi 1.4.11-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Don't probe the legacy SMBIOS address in /dev/mem on ARM platforms. (LP: #1499838) * Don't probe the legacy SMBIOS address in /dev/mem on ARM platforms. (LP: #1499838) * No-change rebuild for the libgcrypt20 transition. * No-change rebuild for the libgcrypt20 transition. * debian/patches/freeipmi-uefi.patch: Fix ipmi-locate on non ia64 architectures. (LP: #1359285) * debian/patches/freeipmi-uefi.patch: Fix ipmi-locate on non ia64 architectures. (LP: #1359285) * debian/patches/Retry-ssif-reads-as-needed.patch: Retry SSIF reads as needed, LP: #1324992 * Use dh-autoreconf to update libtool for ppc64el. * Fix dso linking on the convenience library. * Use dh-autoreconf to update libtool for ppc64el. * Fix dso linking on the convenience library. * No change rebuild to resolve publication issue. * No change rebuild to resolve publication issue. * No change rebuild to resolve publication issue. * No change rebuild to resolve publication issue. * Resolve outstanding MIR issues, LP: #1052056 [ Andres Rodriguez ] * debian/rules: Build with "-pie,-bindnow" * debian/patches/0002_excel_when_opening_tmp.patch: Open files with O_EXCL. [ Dave Walker (Daviey) ] * debian/patches/fix-Wunused-result.patch: Resolve -Wunused-result's warnings, by checking for non-0 return. * Resolve outstanding MIR issues, LP: #1052056 [ Andres Rodriguez ] * debian/rules: Build with "-pie,-bindnow" * debian/patches/0002_excel_when_opening_tmp.patch: Open files with O_EXCL. [ Dave Walker (Daviey) ] * debian/patches/fix-Wunused-result.patch: Resolve -Wunused-result's warnings, by checking for non-0 return. The ubuntu changes either don't apply any longer due to upstream code refactoring (as in fix-Wunused-result.patch) or have been upstreamed already (0002_excel_when_opening_tmp.patch, dso-linking.patch, Fix-ipmi-locate-probing-issue-on-arm32-systems.patch, Fix-probing-issue-on-arm64-systems.patch, freeipmi-uefi.patch, Retry-ssif-reads-as-needed.patch). As of now only d/p/deb_bmc-watchdog_noRUN is required. Debian still carries 0001-Fix-Wformat-security-warnings.patch and up_fixmanpages, but those don't seem to be used during the package build. Changelog entries since current xenial version 1.1.5-3ubuntu7: freeipmi (1.4.11-1) unstable; urgency=medium * [186d83b] Merge tag 'upstream/1.4.11' Upstream version 1.4.11 * [95cfc3a] Updating symbols file. -- Bernd Zeimetz Wed, 25 Nov 2015 21:40:35 +0100 freeipmi (1.4.9-1) unstable; urgency=medium * Fresh upstream release - removes duplicate entry from manpage (Closes: #781633) -- Yaroslav Halchenko Wed, 01 Jul 2015 09:52:35 -0400 freeipmi (1.4.5-3) unstable; urgency=medium * ACK and re-include NMU 1.4.4-1.2 -- Yaroslav Halchenko Wed, 08 Oct 2014 10:15:25 -0400 freeipmi (1.4.5-2) unstable; urgency=medium * Return to using /etc/logrotate.d/bmc-watchdog (Closes: #763136) -- Ferenc Wágner Tue, 07 Oct 2014 10:21:42 +0200 freeipmi (1.4.5-1) unstable; urgency=medium * [7e02411b] Merge tag 'upstream/1.4.5' Upstream version 1.4.5 -- Bernd Zeimetz Sun, 05 Oct 2014 14:08:36 +0200 freeipmi (1.4.4-1.2) unstable; urgency=medium * Non-maintainer upload. * Fix debian/libipmimonitoring5a.symbols after incomplete SONAME bump (Closes: #760920) -- Jonathan Wiltshire Tue, 09 Sep 2014 14:33:33 +0100 freeipmi (1.4.4-1.1) unstable; urgency=medium * Non-maintainer upload. * Add postinsts to replace /usr/share/doc/* with a symlink (Closes: #691439) -- Jonathan Wiltshire Sun, 07 Sep 2014 13:09:22 +0100 freeipmi (1.4.4-1) unstable; urgency=low [ Tollef Fog Heen ] * New upstream release - bump sonames - new tool: ipmi-config - refresh quilt patches - upstream dropped freeipmi-bmc-watchdog logrotate.d snippet, reintroduce as a Debian patch. * Add freeipmi-ipmiseld package. * Adjust dh_fixperms_override call to only be called on binary-indep. -- Yaroslav Halchenko Fri, 15 Aug 2014 09:23:03 -0400 freeipmi (1.1.6-1) experimental; urgency=low * [35d19e11] Merge tag 'upstream/1.1.6' Upstream version 1.1.6 * [b343fe99] Add myself to Uploaders. * [b7ece9fc] Refreshing patches, dropping those which were applied upstream. -- Bernd Zeimetz Fri, 03 Aug 2012 15:31:39 +0200 freeipmi (1.1.5-4) experimental; urgency=low [ Ferenc Wágner ] * Refresh lintian overrides * Fix typo (meta-package) in control file found by lintian * New quilt patch to fix upstream typos found by lintian * debian/control: - remove duplicate Section fields - add myself to Uploaders - add ipmi-pet to freeipmi-tools description * debian/rules: - make mode and ownership change on freeipmi.conf effective - go to debhelper compatibility level 9, but keep away from multiarch - ke
Re: [Bug 1502178] Re: update squid from 3.3.8 to 3.3.14
Adam, That's a good point. None of the reported LP bugs are fixed by this particular update. That said, the list of bug fixes in this update is quite high. I would be willing to SRU this for Trusty as well to keep it in sync. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1502178 Title: update squid from 3.3.8 to 3.3.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1502178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer
Brian, thank you for uploading and publishing those to -proposed. I have tested them on both Precise and Trusty and can confirm that they work as expected: squid is killed with SIGINT, closing all outstanding connections immediately and unlinking the PID file. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1073478 Title: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer
> Yeah, but is the bug present in the sysinit script? I'm assuming not,
> but it wouldn't hurt to verify.
Michael, indeed, thanks for the heads up. I did try it when
researching the SRU, but I forgot to include evidence that it worked
just fine. I have collected that just now.
# /etc/init.d/squid3 start
[ ok ] Starting squid3 (via systemctl): squid3.service.
# /etc/init.d/squid3 stop
[ ok ] Stopping squid3 (via systemctl): squid3.service.
# strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
Process 2925 attached
0.00 --- SIGTERM {si_signo=SIGTERM, si_code=SI_USER,
si_pid=3028, si_uid=0} ---
0.68 kill(2923, SIGUSR1) = 0
0.46 rt_sigreturn()= -1 EINTR (Interrupted system call)
0.81 stat("/etc/localtime", {st_mode=S_IFREG|0644,
st_size=127, ...}) = 0
9.395299 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED,
si_pid=2943, si_status=1, si_utime=0, si_stime=1} ---
0.000778 rt_sigreturn()= -1 EINTR (Interrupted system call)
21.948196 stat("/etc/localtime", {st_mode=S_IFREG|0644,
st_size=127, ...}) = 0
0.002870 kill(2931, SIGTERM) = 0
0.000606 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED,
si_pid=2931, si_status=SIGTERM, si_utime=0, si_stime=0} ---
0.000271 rt_sigreturn()= 9
0.010035 unlink("/var/run/squid3.pid") = 0
0.000397 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 10
0.000353 open("/etc/group", O_RDONLY|O_CLOEXEC) = 10
0.005137 +++ exited with 0 +++
As expected. it exits after about ~30 seconds.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1073478
Title:
[SRU] Update squid3 upstart script to kill it with SIGINT and wait
longer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer
On the contrary, thanks for bringing that up. I was good to be made aware
of such problems. Just because it worked now on Precise and Trusty didn't
mean I should skip that check, as I might as well run into an obsolete or
deleted feature (not that upstart seem to have those). =)
On Oct 14, 2015 9:56 AM, "Robie Basak" <1073...@bugs.launchpad.net> wrote:
> On Wed, Oct 14, 2015 at 12:34:33PM -0000, Tiago Stürmer Daitx wrote:
> > According to http://upstart.ubuntu.com/cookbook/#stanzas-by-category
> > both "kill timeout" (all upstart versions) and "kill signal" (since
> > upstart 1.3) should be supported by upstart 1.5 in Precise so this SRU
> > should be fine.
>
> You're right. Sorry for the noise.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1073478
>
> Title:
> [SRU] Update squid3 upstart script to kill it with SIGINT and wait
> longer
>
> Status in squid3 package in Ubuntu:
> Triaged
>
> Bug description:
> [Impact]
>
> Squid 3.1.19-1ubuntu3.12.04.3 on Precise and 3.3.8-1ubuntu6.3 on
> Trusty do not clean up its PID file, causing logrotate to spit out an
> error each night when cron runs it.
>
> The underlying issue here is that the upstart script does not wait
> long enough for squid3 to finish - one might also argue that it is
> using the wrong signal if it expects squid to finish quickly.
>
> By default, when squid3 receives a SIGTERM it will close the socket
> for incoming connections and will wait for existing connections to
> complete. The shutdown_lifetime directive configures how long it waits
> before forcefully closing those open connections and it is set by
> default to 30 seconds.
>
> Current setting, SIGKILL happens after 5 seconds (which is the upstart
> default):
> =
> # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
> Process 20865 attached - interrupt to quit
>0.00 --- SIGTERM (Terminated) @ 0 (0) ---
>0.000440 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
>0.000418 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>5.006483 +++ killed by SIGKILL +++
>
> Killing squid with SIGKILL might lead to cache index corruption and a
> very slow startup the next time it is started: http://lists.squid-
> cache.org/pipermail/squid-users/2015-July/004752.html
>
> The first way to avoid this is by increasing upstart's "kill timeout"
> to a few seconds more then the "shutdown_lifetime" directive.
>
> With "kill timeout 40" in upstart script, notice the pid file being
> unlinked (the ~30 seconds wait is due to the default value of
> shutdown_lifetime directive):
> =
> # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
> Process 20805 attached - interrupt to quit
>0.00 --- SIGTERM (Terminated) @ 0 (0) ---
>0.000284 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
>0.000402 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
> 31.611726 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>0.001792 --- SIGCHLD (Child exited) @ 0 (0) ---
>0.000247 rt_sigreturn(0x) = 63
>0.006027 unlink("/var/run/squid3.pid") = 0
>0.000539 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
>0.000387 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
> Process 20805 detached
>
> Still, this will unfortunately lead to a slow shutdown time as
> reported in http://askubuntu.com/questions/18127/squid3-starts-and-
> stops-slowly
>
> To solve this it is better to issue a SIGINT instead of SIGTERM
> (upstart default) by adding "kill signal SIGINT" to squid's upstart
> script.
>
> With "kill signal SIGINT", which does not wait on outstanding
> connections:
> =
> # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
> Process 20891 attached - interrupt to quit
>0.00 --- SIGINT (Interrupt) @ 0 (0) ---
>0.000312 rt_sigreturn(0x2) = -1 EINTR (Interrupted system call)
>0.000237 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>1.123564 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
> ...}) = 0
>0.000754 --- SIGCHLD (Child exited) @ 0 (0) ---
>0.000103 rt_sigreturn(0x) = 0
>0.002031 unlink("/var/run/squid3.pid") = 0
>0.000154 open("/proc/s
[Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer
Thank you Michael! We only need to touch Wily if we want to keep the upstart script updated there as well, but as you said Wily no longer uses upstart. Updating it would not change any behavior. So far I couldn't find any documentation explaining how to proceed on this scenario, so I'm open to suggestions. I'm also ok providing a debdiff for it if we decide to go that way. =) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1073478 Title: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer
Thanks for the feedback. Do you mean LP: #1272788 "php5-fpm upstart job is not compatible with precise upstart" or LP: #1242376 "reload php5-fpm crashes"? That was one was caused because of the "reload" directive, only introduced in upstart 1.10 while Precise only supports upstart 1.5. According to http://upstart.ubuntu.com/cookbook/#stanzas-by-category both "kill timeout" (all upstart versions) and "kill signal" (since upstart 1.3) should be supported by upstart 1.5 in Precise so this SRU should be fine. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1073478 Title: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073478] Re: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer
** Summary changed: - squid3 logrotate fails when squid is not running + [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1073478 Title: [SRU] Update squid3 upstart script to kill it with SIGINT and wait longer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073478] Re: squid3 logrotate fails when squid is not running
** Patch added: "squid3_3.1.19-1ubuntu3.12.04.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+attachment/4493998/+files/squid3_3.1.19-1ubuntu3.12.04.4.debdiff ** Tags removed: needs-upstream-report ** Tags added: patch precise trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1073478 Title: squid3 logrotate fails when squid is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073478] Re: squid3 logrotate fails when squid is not running
** Patch added: "squid3_3.3.8-1ubuntu6.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+attachment/4493997/+files/squid3_3.3.8-1ubuntu6.4.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1073478 Title: squid3 logrotate fails when squid is not running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073478] Re: squid3 logrotate fails when squid is not running
** Description changed:
[Impact]
Squid 3.1.19-1ubuntu3.12.04.3 on Precise and 3.3.8-1ubuntu6.3 on Trusty
do not clean up its PID file, causing logrotate to spit out an error
each night when cron runs it.
The underlying issue here is that the upstart script does not wait long
enough for squid3 to finish - one might also argue that it is using the
wrong signal if it expects squid to finish quickly.
By default, when squid3 receives a SIGTERM it will close the socket for
incoming connections and will wait for existing connections to complete.
The shutdown_lifetime directive configures how long it waits before
forcefully closing those open connections and it is set by default to 30
seconds.
Current setting, SIGKILL happens after 5 seconds (which is the upstart
default):
=
# strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
Process 20865 attached - interrupt to quit
- 0.00 --- SIGTERM (Terminated) @ 0 (0) ---
- 0.000440 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
- 0.000418 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
- 5.006483 +++ killed by SIGKILL +++
+ 0.00 --- SIGTERM (Terminated) @ 0 (0) ---
+ 0.000440 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
+ 0.000418 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 5.006483 +++ killed by SIGKILL +++
Killing squid with SIGKILL might lead to cache index corruption and a
very slow startup the next time it is started: http://lists.squid-
cache.org/pipermail/squid-users/2015-July/004752.html
The first way to avoid this is by increasing upstart's "kill timeout" to
a few seconds more then the "shutdown_lifetime" directive.
With "kill timeout 40" in upstart script, notice the pid file being unlinked
(the ~30 seconds wait is due to the default value of shutdown_lifetime
directive):
=
# strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
Process 20805 attached - interrupt to quit
- 0.00 --- SIGTERM (Terminated) @ 0 (0) ---
- 0.000284 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
- 0.000402 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
- 31.611726 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
- 0.001792 --- SIGCHLD (Child exited) @ 0 (0) ---
- 0.000247 rt_sigreturn(0x) = 63
- 0.006027 unlink("/var/run/squid3.pid") = 0
- 0.000539 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
- 0.000387 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
+ 0.00 --- SIGTERM (Terminated) @ 0 (0) ---
+ 0.000284 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
+ 0.000402 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 31.611726 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 0.001792 --- SIGCHLD (Child exited) @ 0 (0) ---
+ 0.000247 rt_sigreturn(0x) = 63
+ 0.006027 unlink("/var/run/squid3.pid") = 0
+ 0.000539 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
+ 0.000387 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
Process 20805 detached
Still, this will unfortunately lead to a slow shutdown time as reported
in http://askubuntu.com/questions/18127/squid3-starts-and-stops-slowly
To solve this it is better to issue a SIGINT instead of SIGTERM (upstart
default) by adding "kill signal SIGINT" to squid's upstart script.
With "kill signal SIGINT", which does not wait on outstanding connections:
=
# strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
Process 20891 attached - interrupt to quit
- 0.00 --- SIGINT (Interrupt) @ 0 (0) ---
- 0.000312 rt_sigreturn(0x2) = -1 EINTR (Interrupted system call)
- 0.000237 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
- 1.123564 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
- 0.000754 --- SIGCHLD (Child exited) @ 0 (0) ---
- 0.000103 rt_sigreturn(0x) = 0
- 0.002031 unlink("/var/run/squid3.pid") = 0
- 0.000154 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
- 0.000142 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
+ 0.00 --- SIGINT (Interrupt) @ 0 (0) ---
+ 0.000312 rt_sigreturn(0x2) = -1 EINTR (Interrupted system call)
+ 0.000237 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 1.123564 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 0.000754 --- SIGCHLD (Child exited) @ 0 (0) ---
+ 0.000103 rt_sigreturn(0x) = 0
+ 0.002031 unlink("/var/run/squid3.pid") = 0
+ 0.000154 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
+ 0.000142 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
Process 20891 detached
The whole stop process is very quick. The downside is that squid will
[Bug 1073478] Re: squid3 logrotate fails when squid is not running
** Description changed:
- Squid3 on Precise does not clean up its PID file, causing logrotate to
- spit out an error each night when cron runs it. This is on a server where
- we want squid3 installed and ready to go but not running by default.
+ [Impact]
- 0 root@rackspace:/etc/mysql#start squid3
+ Squid 3.1.19-1ubuntu3.12.04.3 on Precise and 3.3.8-1ubuntu6.3 on Trusty
+ do not clean up its PID file, causing logrotate to spit out an error
+ each night when cron runs it.
+
+ The underlying issue here is that the upstart script does not wait long
+ enough for squid3 to finish - one might also argue that it is using the
+ wrong signal if it expects squid to finish quickly.
+
+ By default, when squid3 receives a SIGTERM it will close the socket for
+ incoming connections and will wait for existing connections to complete.
+ The shutdown_lifetime directive configures how long it waits before
+ forcefully closing those open connections and it is set by default to 30
+ seconds.
+
+ Current setting, SIGKILL happens after 5 seconds (which is the upstart
default):
+ =
+ # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
+ Process 20865 attached - interrupt to quit
+ 0.00 --- SIGTERM (Terminated) @ 0 (0) ---
+ 0.000440 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
+ 0.000418 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 5.006483 +++ killed by SIGKILL +++
+
+ Killing squid with SIGKILL might lead to cache index corruption and a
+ very slow startup the next time it is started: http://lists.squid-
+ cache.org/pipermail/squid-users/2015-July/004752.html
+
+ The first way to avoid this is by increasing upstart's "kill timeout" to
+ a few seconds more then the "shutdown_lifetime" directive.
+
+ With "kill timeout 40" in upstart script, notice the pid file being unlinked
(the ~30 seconds wait is due to the default value of shutdown_lifetime
directive):
+ =
+ # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
+ Process 20805 attached - interrupt to quit
+ 0.00 --- SIGTERM (Terminated) @ 0 (0) ---
+ 0.000284 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
+ 0.000402 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 31.611726 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 0.001792 --- SIGCHLD (Child exited) @ 0 (0) ---
+ 0.000247 rt_sigreturn(0x) = 63
+ 0.006027 unlink("/var/run/squid3.pid") = 0
+ 0.000539 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
+ 0.000387 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
+ Process 20805 detached
+
+ Still, this will unfortunately lead to a slow shutdown time as reported
+ in http://askubuntu.com/questions/18127/squid3-starts-and-stops-slowly
+
+ To solve this it is better to issue a SIGINT instead of SIGTERM (upstart
+ default) by adding "kill signal SIGINT" to squid's upstart script.
+
+ With "kill signal SIGINT", which does not wait on outstanding connections:
+ =
+ # strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
+ Process 20891 attached - interrupt to quit
+ 0.00 --- SIGINT (Interrupt) @ 0 (0) ---
+ 0.000312 rt_sigreturn(0x2) = -1 EINTR (Interrupted system call)
+ 0.000237 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 1.123564 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118,
...}) = 0
+ 0.000754 --- SIGCHLD (Child exited) @ 0 (0) ---
+ 0.000103 rt_sigreturn(0x) = 0
+ 0.002031 unlink("/var/run/squid3.pid") = 0
+ 0.000154 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
+ 0.000142 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
+ Process 20891 detached
+
+ The whole stop process is very quick. The downside is that squid will
+ forcefully close all open connections immediately, but that was already
+ happening when SIGKILL was being issued before - so we are actually
+ keeping the same behavior as before and there are no bugs complaining
+ about it. And the PID file gets removed anyway.
+
+ The proposal is to add both "kill signal SIGINT" and "kill timeout 40"
+ to squid, so squid should have enough time to close all open cache index
+ files.
+
+
+ [Test Case]
+
+ # start squid3
squid3 start/running, process 10392
- 0 root@rackspace:/etc/mysql#cat /var/run/squid3.pid
+ # cat /var/run/squid3.pid
10392
- 0 root@rackspace:/etc/mysql#stop squid3
+ # stop squid3
squid3 stop/waiting
- 0 root@rackspace:/etc/mysql#cat /var/run/squid3.pid
+ # cat /var/run/squid3.pid
10392
- 0 root@rackspace:/etc/mysql#logrotate -f /etc/logrotate.d/squid3
+ # logrotate -f /etc/logrotate.d/squid3
squid: ERROR: Could not send signal 10 to process 10392: (3) No such process
error: error running shared postrotate script for '/var/log/squid3/*.log '
- 1 root@rackspace:/etc/mysql#lsb_release -d
+
+
+ [Regression Potential]
+
+ * The main regression potencial
[Bug 1502178] Re: update squid from 3.3.8 to 3.3.14
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1502178 Title: update squid from 3.3.8 to 3.3.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1502178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
This patch also fixes LP: #1501566 and LP: #1496924. ** Patch added: "squid3_3.3.8-1ubuntu16.debdiff" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+attachment/4489239/+files/squid3_3.3.8-1ubuntu16.debdiff ** Patch removed: "fixes for this bug as well as LP: #1501566 and LP: #1496924" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+attachment/4480476/+files/squid3_3.3.8-1ubuntu16.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
libecap3 was been deleted. I have created LP: #1504200 to handle the gcc5 transition. After it gets sponsored it should be ok to apply the squid debdiff. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501566] Re: squid3 FTBFS due to missing --name arg to pod2man
libecap3 was been deleted. I have created LP: #1504200 to handle the gcc5 transition. After it gets sponsored it should be ok to apply this fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1501566 Title: squid3 FTBFS due to missing --name arg to pod2man To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1501566/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1504200] Re: libecap2 FTBFS due to gcc5 transition
libecap3 has been deleted from -proposed, it is now ok to apply this fix. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1504200 Title: libecap2 FTBFS due to gcc5 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1504200/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1504200] Re: libecap2 FTBFS due to gcc5 transition
* GCC5 transition (LP: #1504200) - d/control: rename libecap2 to libecap2v5 - d/rules: call dh_clean to remove *.debhelper.log files - d/libecap2v5.symbols: update symbols ** Patch added: "libecap_0.2.0-1ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1504200/+attachment/4488758/+files/libecap_0.2.0-1ubuntu6.debdiff ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1504200 Title: libecap2 FTBFS due to gcc5 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1504200/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1504200] Re: libecap2 FTBFS due to gcc5 transition
While there is a newer libecap in -proposed (1.0), the current squid3 version is under the 3.3 series, which can only be build with libecap 0.20. In order to use the libecap in version available in proposed we would need to update squid to 3.5, so while that does not happen it would be good to fix libecap FTBFS and allow the currently packaged squid 3.3 to be build. ** Also affects: squid3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libecap in Ubuntu. https://bugs.launchpad.net/bugs/1504200 Title: libecap2 FTBFS due to gcc5 transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libecap/+bug/1504200/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1504200] [NEW] libecap2 FTBFS due to gcc5 transition
Public bug reported: Currently libecap2 FTBFS on a rebuild with a few symbol changes due to gcc5 transition. rebuild FTBFS: http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test /test-rebuild-20151001-wily.html#ubuntu-server Log from https://launchpad.net/ubuntu/+archive/test-rebuild-20151001/+build/8031290 = dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libecap2/DEBIAN/symbols doesn't match completely debian/libecap2.symbols --- debian/libecap2.symbols (libecap2_0.2.0-1ubuntu5_amd64) +++ dpkg-gensymbolshtUyNq 2015-10-02 02:33:20.177489000 + @@ -15,8 +15,10 @@ _ZN7libecap12methodDeleteE@Base 0.2.0 _ZN7libecap12protocolHttpE@Base 0.2.0 _ZN7libecap12protocolWaisE@Base 0.2.0 - _ZN7libecap13TextExceptionC1ERKSsPKci@Base 0.2.0 - _ZN7libecap13TextExceptionC2ERKSsPKci@Base 0.2.0 + _ZN7libecap13TextExceptionC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPKci@Base 0.2.0-1ubuntu5 +#MISSING: 0.2.0-1ubuntu5# _ZN7libecap13TextExceptionC1ERKSsPKci@Base 0.2.0 + _ZN7libecap13TextExceptionC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPKci@Base 0.2.0-1ubuntu5 +#MISSING: 0.2.0-1ubuntu5# _ZN7libecap13TextExceptionC2ERKSsPKci@Base 0.2.0 _ZN7libecap13TextExceptionD0Ev@Base 0.2.0 _ZN7libecap13TextExceptionD1Ev@Base 0.2.0 _ZN7libecap13TextExceptionD2Ev@Base 0.2.0 @@ -42,14 +44,19 @@ _ZN7libecap23metaAuthenticatedGroupsE@Base 0.2.0 (arch=armhf i386 powerpc)_ZN7libecap4Area14FromTempBufferEPKcj@Base 0.2.0 (arch=any-amd64)_ZN7libecap4Area14FromTempBufferEPKcm@Base 0.2.0 - _ZN7libecap4Area14FromTempStringERKSs@Base 0.2.0 + _ZN7libecap4Area14FromTempStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.2.0-1ubuntu5 +#MISSING: 0.2.0-1ubuntu5# _ZN7libecap4Area14FromTempStringERKSs@Base 0.2.0 _ZN7libecap4Name6NextIdEv@Base 0.2.0 _ZN7libecap4Name9TheLastIdE@Base 0.2.0 - _ZN7libecap4NameC1ERKSs@Base 0.2.0 - _ZN7libecap4NameC1ERKSsi@Base 0.2.0 + _ZN7libecap4NameC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.2.0-1ubuntu5 + _ZN7libecap4NameC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 0.2.0-1ubuntu5 +#MISSING: 0.2.0-1ubuntu5# _ZN7libecap4NameC1ERKSs@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# _ZN7libecap4NameC1ERKSsi@Base 0.2.0 _ZN7libecap4NameC1Ev@Base 0.2.0 - _ZN7libecap4NameC2ERKSs@Base 0.2.0 - _ZN7libecap4NameC2ERKSsi@Base 0.2.0 + _ZN7libecap4NameC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.2.0-1ubuntu5 + _ZN7libecap4NameC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEi@Base 0.2.0-1ubuntu5 +#MISSING: 0.2.0-1ubuntu5# _ZN7libecap4NameC2ERKSs@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# _ZN7libecap4NameC2ERKSsi@Base 0.2.0 _ZN7libecap4NameC2Ev@Base 0.2.0 _ZN7libecap4NameD1Ev@Base 0.2.0 _ZN7libecap4NameD2Ev@Base 0.2.0 @@ -58,9 +65,9 @@ _ZN7libecap6MyHostEv@Base 0.2.0 _ZN7libecap7Message10addTrailerEv@Base 0.2.0 _ZN7libecap7Message7trailerEv@Base 0.2.0 - (optional)_ZN7libecap7MessageD0Ev@Base 0.2.0 - (optional)_ZN7libecap7MessageD1Ev@Base 0.2.0 - (optional)_ZN7libecap7MessageD2Ev@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# (optional)_ZN7libecap7MessageD0Ev@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# (optional)_ZN7libecap7MessageD1Ev@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# (optional)_ZN7libecap7MessageD2Ev@Base 0.2.0 _ZN7libecap7adapter7Service11reconfigureERKNS_7OptionsE@Base 0.2.0 _ZN7libecap7adapter7Service4stopEv@Base 0.2.0 _ZN7libecap7adapter7Service5startEv@Base 0.2.0 @@ -81,22 +88,24 @@ _ZN7libecaplsERSoRKNS_4AreaE@Base 0.2.0 _ZNK7libecap13TextException4whatEv@Base 0.2.0 _ZNK7libecap13TextException5printERSo@Base 0.2.0 - _ZNK7libecap4Area8toStringEv@Base 0.2.0 + _ZNK7libecap4Area8toStringB5cxx11Ev@Base 0.2.0-1ubuntu5 +#MISSING: 0.2.0-1ubuntu5# _ZNK7libecap4Area8toStringEv@Base 0.2.0 _ZNK7libecap4Name12assignHostIdEi@Base 0.2.0 _ZNK7libecap4Name14assignedHostIdEv@Base 0.2.0 _ZNK7libecap7Message7trailerEv@Base 0.2.0 _ZNK7libecap8BodySize7badSizeEv@Base 0.2.0 - (optional)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base 0.2.0 - (optional)_ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 0.2.0 - (optional)_ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 0.2.0 - (optional)_ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# (optional)_ZNSs12_S_constructIPcEES0_T_S1_RKSaIcESt20forward_iterator_tag@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# (optional)_ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# (optional)_ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 0.2.0 +#MISSING: 0.2.0-1ubuntu5# (optional)_ZNSt15basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 0.2.0 _ZNSt3tr110shared_ptrIN7libecap4host4HostEED1Ev@Base 0.2.0 _ZNSt3tr110shared_ptrIN7libecap4host4HostEED2Ev@Ba
[Bug 1081952] Re: squid 3.1.19 external_acl_type fail
Apologies, the right status was Incomplete. ** Changed in: squid3 (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1081952 Title: squid 3.1.19 external_acl_type fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1081952/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073478] Re: squid3 logrotate fails when squid is not running
The underlying issue here is that the upstart script does not wait long
enough for squid3 to finish.
By default, when squid3 receives a SIGTERM it will close the socket for
incoming connections and will wait for existing connections to complet.
How long it waits before forcefully closing those connections is
configured by the shutdown_lifetime directive - 30 seconds by default.
Current setting, SIGKILL after 5 seconds:
=
# strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
Process 20865 attached - interrupt to quit
0.00 --- SIGTERM (Terminated) @ 0 (0) ---
0.000440 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
0.000418 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...})
= 0
5.006483 +++ killed by SIGKILL +++
With "kill timeout 40" in upstart script, notice the pid file being unlinked
(the ~30 seconds wait is due to the default value of shutdown_lifetime
directive):
=
# strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
Process 20805 attached - interrupt to quit
0.00 --- SIGTERM (Terminated) @ 0 (0) ---
0.000284 rt_sigreturn(0xf) = -1 EINTR (Interrupted system call)
0.000402 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...})
= 0
31.611726 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...})
= 0
0.001792 --- SIGCHLD (Child exited) @ 0 (0) ---
0.000247 rt_sigreturn(0x) = 63
0.006027 unlink("/var/run/squid3.pid") = 0
0.000539 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
0.000387 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
Process 20805 detached
Note that the current behavior is also quite bad and can corrupt cache
index files, which is a really bad thing as squid will take a long time
to start the next time when it detects a corrupted cache index file [1].
I'm willing to submit a SRU for this, but I wonder if we should replace
SIGTERM with SIGINT. Using SIGINT means that squid will drop outstanding
connections immediately and then proceed to write cache index files.
This will avoid squid slowing down shutdown times for users [2] and we
somewhat keep the current behavior (ie. the current 5-sec SIGKILL
already does that and I don't see anyone complaining).
With "kill signal SIGINT", which does not wait on outstanding connections:
=
# strace -r -e trace=signal,file -p $(cat /var/run/squid3.pid)
Process 20891 attached - interrupt to quit
0.00 --- SIGINT (Interrupt) @ 0 (0) ---
0.000312 rt_sigreturn(0x2) = -1 EINTR (Interrupted system call)
0.000237 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...})
= 0
1.123564 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=118, ...})
= 0
0.000754 --- SIGCHLD (Child exited) @ 0 (0) ---
0.000103 rt_sigreturn(0x) = 0
0.002031 unlink("/var/run/squid3.pid") = 0
0.000154 open("/proc/sys/kernel/ngroups_max", O_RDONLY) = 0
0.000142 open("/etc/group", O_RDONLY|O_CLOEXEC) = 0
Process 20891 detached
Still, let me reiterate that even with SIGINT enabled I believe we
should still increase "kill timeout" somewhat as we surely want to avoid
any cache corruption. According to [1] we don't need to wait that much,
so I guess anything between 20~40 should be fine. Again, since issuing a
SIGKILL during cache write *WILL* corrupt it, it might be sane to wait
even longer for cases when the system is under high load and/or has a
lot of cache dirs - this would/should be quite rare anyway: in most
cases squid shutdown time with SIGINT should be under 5 secs.
Of course, since there is still a chance that SIGKILL does get issued,
we will also need the fix proposed in #1 because there's a chance the
pid file was not removed.
[1] http://lists.squid-cache.org/pipermail/squid-users/2015-July/004752.html
[2] http://askubuntu.com/questions/18127/squid3-starts-and-stops-slowly
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid3 in Ubuntu.
https://bugs.launchpad.net/bugs/1073478
Title:
squid3 logrotate fails when squid is not running
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1073478/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501566] Re: squid3 FTBFS due to missing --name arg to pod2man
Daniel, thanks for sponsoring this. I apologize, the main discussion for Squid FTBFS was being done in LP: #1496223 and I forgot to add here the piece that this patch actually requires libecap2 gcc5 transition for it to work. I also missed the fact that the bot subscribed ubuntu-sponsors, which was not my intention - at least until we decide to either keep the current squid3 version or merge a newer from Debian. What is the appropriate action: should I remove the patch from here or just drop the patch flag+patch checkbox? If the latter then someone will have to unsubscribe ubuntu-sponsors. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1501566 Title: squid3 FTBFS due to missing --name arg to pod2man To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1501566/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1473691] Re: Update to latest upstream stable release (3.5)
In case we are unable to merge Squid 3.5+, I have prepared debdiffs to upgrade the current squid3-3.3.8-1ubuntu15 in proposed to 3.3.8-1ubuntu16 and from there to 3.3.14-0ubuntu1. See LP: #1496223 debdiffs for: 1. gcc5 transition of libecap2 (the current libecap3 on proposed will be unused and should be safely removed) 2. update from 3.3.8-1ubuntu15 (currently FTBFS on proposed) to 3.3.8-1ubuntu16 Then LP: #1502178 debdiff to update from 3.3.8-1ubuntu16 to 3.3.14-0ubuntu1. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1473691 Title: Update to latest upstream stable release (3.5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1502178] Re: update squid from 3.3.8 to 3.3.14
Apologies, this is not a duplicate of LP: #1473691. That one is about updating to 3.5+ and closing a bug that AFAICS was not fixed in 3.3.14. This is a continuation of LP: #1496223 to be used if and only if we don't get a merge of 3.5+. Thanks! =) ** This bug is no longer a duplicate of bug 1473691 Update to latest upstream stable release (3.5) ** Tags added: ftbfs ** Description changed: squid 3.3.8 was released on 2013-07-13, more than 2 years ago. Unless it gets merged with Debian's 3.5 it should at least be updated the new 3.3.14 release from 2015-05-01. + + Note: this is not a duplication of LP: #1473691; that one is about + updating from 3.3 to 3.5+ and closing a bug that AFAICS was not fixed in + 3.3.14. Still, this is a continuation of LP: #1496223 to be used if and + only if we don't merge 3.5+ from Debian. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1502178 Title: update squid from 3.3.8 to 3.3.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1502178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1405351] Re: First run: Failed to verify one of the swap directories
** Changed in: squid3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1405351 Title: First run: Failed to verify one of the swap directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1405351/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1423498] Re: FTP upload causes squid hang
Thank you for reporting this bug to Ubuntu. Utopic reached EOL on July 23, 2015. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases ** Changed in: squid3 (Ubuntu) Status: New => Confirmed ** Changed in: squid3 (Ubuntu Trusty) Status: New => Confirmed ** Changed in: squid3 (Ubuntu Vivid) Status: New => Confirmed ** Changed in: squid3 (Ubuntu Utopic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1423498 Title: FTP upload causes squid hang To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1423498/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1391159] Re: squid3 : missing helper /usr/lib/squid3/ext_time_quota_acl
** Changed in: squid3 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1391159 Title: squid3 : missing helper /usr/lib/squid3/ext_time_quota_acl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1391159/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1462729] Re: init config doesn't located at /etc/init.d
** Changed in: squid3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1462729 Title: init config doesn't located at /etc/init.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1462729/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1502178] Re: update squid from 3.3.8 to 3.3.14
*** This bug is a duplicate of bug 1473691 *** https://bugs.launchpad.net/bugs/1473691 Requires libecap2v5 (gcc5 transition of libecap2) and squid3-3.3.8-1ubuntu16, debdiffs available at LP: #1496223 Build test package at https://launchpad.net/~tdaitx/+archive/ubuntu/testing/+sourcepub/5473877 /+listing-archive-extra ** Patch added: "update to 3.3.14" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1502178/+attachment/4482131/+files/squid3_3.3.14-0ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1502178 Title: update squid from 3.3.8 to 3.3.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1502178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1098641] Re: visible_hostname defaults to hostname of first http_port IP, not get_hostname()
** Tags added: precise ** No longer affects: squid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1098641 Title: visible_hostname defaults to hostname of first http_port IP, not get_hostname() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1098641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1098641] Re: visible_hostname defaults to hostname of first http_port IP, not get_hostname()
** Bug watch added: Squid Bugzilla #2997 http://bugs.squid-cache.org/show_bug.cgi?id=2997 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=2997 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1098641 Title: visible_hostname defaults to hostname of first http_port IP, not get_hostname() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1098641/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1194310] Re: cachemgr.cgi crashes after login
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 1194310 and any other logs that are relevant for this particular issue. ** Tags added: precise ** Changed in: squid3 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1194310 Title: cachemgr.cgi crashes after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1194310/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1235681] Re: squid3 always run with -N option, incompatible with SMP option (workers)
** Tags added: trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1235681 Title: squid3 always run with -N option, incompatible with SMP option (workers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1235681/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1213455] Re: pinger crashed with SIGSEGV in __strftime_internal()
** Bug watch added: Squid Bugzilla #4276 http://bugs.squid-cache.org/show_bug.cgi?id=4276 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4276 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1213455 Title: pinger crashed with SIGSEGV in __strftime_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1213455/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1214806] Re: pinger crashed with SIGSEGV in __tzfile_compute()
** Bug watch added: Squid Bugzilla #4276 http://bugs.squid-cache.org/show_bug.cgi?id=4276 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4276 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1214806 Title: pinger crashed with SIGSEGV in __tzfile_compute() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214806/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1214379] Re: pinger crashed with SIGSEGV in malloc_consolidate()
** Bug watch added: Squid Bugzilla #4276 http://bugs.squid-cache.org/show_bug.cgi?id=4276 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4276 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1214379 Title: pinger crashed with SIGSEGV in malloc_consolidate() To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1214379/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1361373] Re: package squid3 3.1.19-1ubuntu3.12.04.2 failed to install/upgrade: ErrorMessage: 子程序 新的 pre-installation script 傳回了錯誤退出狀態 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect and any other logs that are relevant for this particular issue. ** Changed in: squid3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1361373 Title: package squid3 3.1.19-1ubuntu3.12.04.2 failed to install/upgrade: ErrorMessage: 子程序 新的 pre-installation script 傳回了錯誤退出狀態 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1361373/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1390132] Re: Cannot change the maximum number of filedescriptors
** Bug watch added: Red Hat Bugzilla #976815 https://bugzilla.redhat.com/show_bug.cgi?id=976815 ** Also affects: squid3 (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=976815 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1390132 Title: Cannot change the maximum number of filedescriptors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1390132/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1404876] Re: pinger assert failure: *** Error in `(pinger)': free(): invalid pointer: 0x00007f3b5e73ebf0 ***
** Bug watch added: Squid Bugzilla #4276 http://bugs.squid-cache.org/show_bug.cgi?id=4276 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4276 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1404876 Title: pinger assert failure: *** Error in `(pinger)': free(): invalid pointer: 0x7f3b5e73ebf0 *** To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1404876/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1462729] Re: init config doesn't located at /etc/init.d
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). 4. Ubuntu and package version Please make sure you are running a supported Ubuntu version and the latest update available for squid3. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1462729 Title: init config doesn't located at /etc/init.d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1462729/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1502178] [NEW] update squid from 3.3.8 to 3.3.14
Public bug reported: squid 3.3.8 was released on 2013-07-13, more than 2 years ago. Unless it gets merged with Debian's 3.5 it should at least be updated the new 3.3.14 release from 2015-05-01. ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Description changed: - squid 3.3.8 was released on 2013-07-13, more than 2 years ago. It needs - to be updated to the new 3.3.14 release from 2015-05-01. + squid 3.3.8 was released on 2013-07-13, more than 2 years ago. Unless it + gets merged with Debian's 3.5 it should at least be updated the new + 3.3.14 release from 2015-05-01. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1502178 Title: update squid from 3.3.8 to 3.3.14 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1502178/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
This issue was marked as fixed by an earlier release. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978419] Re: squid binary package includes /etc/logrotate.d/squid which fails
This seems to have been fixed in an earlier squid release. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/978419 Title: squid binary package includes /etc/logrotate.d/squid which fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/978419/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1081952] Re: squid 3.1.19 external_acl_type fail
Thank you for reporting this bug to Ubuntu. There is a new 3.1.19-1ubuntu3.12.04.3 release available, I will be setting this bug as Invalid until it is tested with the new release. ** Changed in: squid3 (Ubuntu) Status: New => Invalid ** Tags added: precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1081952 Title: squid 3.1.19 external_acl_type fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1081952/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 561750] Re: squid starts and stops immediately (after upgrade from karmic to lucid)
This issue was marked as fixed by an earlier release. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/561750 Title: squid starts and stops immediately (after upgrade from karmic to lucid) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 995523] Re: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise
This issue was reported as fixed by LP: #978356. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/995523 Title: squid3 is killed by /etc/resolvconf/update-libc.d/squid3 in Precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/995523/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 805660] Re: squid_session causing segmentation fault
This seems to have been fixed in an earlier squid release. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/805660 Title: squid_session causing segmentation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/805660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 772810] Re: Squid3 Natty: Squid3 has to be restarted so it starts using the newly established internet connection
This seems to have been fixed in an earlier squid release. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/772810 Title: Squid3 Natty: Squid3 has to be restarted so it starts using the newly established internet connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/772810/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 496886] Re: Squid crashes with "assertion failed" authenticateUserAuthenticated
This seems to have been fixed in an earlier squid release. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/496886 Title: Squid crashes with "assertion failed" authenticateUserAuthenticated To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/496886/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 988802] Re: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0"
** Bug watch added: Squid Bugzilla #3819 http://bugs.squid-cache.org/show_bug.cgi?id=3819 ** Changed in: squid Importance: Medium => Unknown ** Changed in: squid Status: Invalid => Unknown ** Changed in: squid Remote watch: Squid Bugzilla #3097 => Squid Bugzilla #3819 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/988802 Title: squid3 killed by ABRT signal. assertion failed: disk.cc377: "fd >= 0" To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/988802/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 591365] Re: Squid3.0 provides no option for re-enabling a cache peer
This seems to have been fixed in an earlier squid release. ** Changed in: squid3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/591365 Title: Squid3.0 provides no option for re-enabling a cache peer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/591365/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 745082] Re: DNS queries go to the wrong DNS server when moving between networks
This seems to have been fixed in an earlier squid release. ** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/745082 Title: DNS queries go to the wrong DNS server when moving between networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/745082/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 805931] Re: assertion failed: comm.cc:572: "fdc_table[fd].active == 1"
This seems to have been fixed in an earlier squid release. ** Changed in: squid3 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/805931 Title: assertion failed: comm.cc:572: "fdc_table[fd].active == 1" To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/805931/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 115475] Re: tproxy support (iptables & squid)
** Changed in: squid3 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/115475 Title: tproxy support (iptables & squid) To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/115475/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 392077] Re: Squid crashes with "assertion failed" mem->swapout.sio
** Changed in: squid3 (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/392077 Title: Squid crashes with "assertion failed" mem->swapout.sio To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/392077/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
I agree that merging the new one is the best approach and rbasak was already working in it, for this reason I was withholding my patches (at the time they required -D_GLIBCXX_USE_CXX11_ABI=0 since I didn't have a libecap2 compiled for gcc5). I decided to publish my patches for 3.3.8 just in case we don't get it in time and also because yadi said it was better to revert libecap at this time [1] and to avoid duplicated work since sil200 also tried to fix it. As yadi also commented in [1], Squid 3.3 and 3.4 require libecap 0.20 (libecap2), only squid 3.5 works with libecap 1.0 (libecap3). [1] https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/comments/7 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496924] Re: squid3 FTBFS due to bad libecap3 dependency and logical-not-parentheses warning
Debdiffs for squid3 fixes and libecap2 transition were provided in LP: #1496223 Let me know if I should move or copy them here. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496924 Title: squid3 FTBFS due to bad libecap3 dependency and logical-not- parentheses warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
The squid3_3.3.8-1ubuntu16.debdiff patch requires gcc5 transition of libecap2. I kept the lib soname and added a Conflicts: as per https://wiki.debian.org/TransitionBestPractices libecap2 and squid3 have been build at https://launchpad.net/~tdaitx/+archive/ubuntu/testing/+sourcepub/5445490/+listing-archive-extra https://launchpad.net/~tdaitx/+archive/ubuntu/testing/+sourcepub/5445498/+listing-archive-extra ** Patch added: "gcc5 transition for libecap2" https://bugs.launchpad.net/squid/+bug/1496223/+attachment/4480477/+files/libecap_0.2.0-1ubuntu6.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
** Patch added: "fixes for this bug as well as LP: #1501566 and LP: #1496924" https://bugs.launchpad.net/squid/+bug/1496223/+attachment/4480476/+files/squid3_3.3.8-1ubuntu16.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501566] Re: squid3 FTBFS due to missing --name arg to pod2man
** Patch added: "patch with fixes for this bug as well as LP: #1496223 and LP: #1496924" https://bugs.launchpad.net/squid/+bug/1501566/+attachment/4480475/+files/squid3_3.3.8-1ubuntu16.debdiff ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1501566 Title: squid3 FTBFS due to missing --name arg to pod2man To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1501566/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501566] Re: squid3 FTBFS due to missing --name arg to pod2man
** Description changed: squid3 fails with: - dh_install -psquid3 --sourcedir=/«PKGBUILDDIR»/debian/tmp + dh_install -psquid3 --sourcedir=/«PKGBUILDDIR»/debian/tmp cp: cannot stat '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No such file or directory dh_install: cp --reflink=auto -a /«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8 debian/squid3//usr/share/man/man8/ returned exit code 1 make: *** [binary-install/squid3] Error 2 /usr/share/cdbs/1/rules/debhelper.mk:213: recipe for target 'binary-install/squid3' failed caused by helpers/auth_basic/DB/config.test failure during configure phase, which filters out the DB basic auth. The error in config.test is caused by a missing --name argument to pod2man: IO::File=IO(0x24d5e30) around line 1: No name given for document POD document had syntax errors at /usr/bin/pod2man line 71. + This also affects helpers/external_acl/SQL_session/config.test and + helpers/log_daemon/DB/config.test + + Cause + = Since Perl 5.20.2-4 pod2man behavior changed for pipes and now the --name parameter must be included (or --errors set to 'pod', 'stderr', or 'none'). As per Debian [1] and pod2man change log page [2]: "[Pod::Man] Attempt to detect if the input came from a pipe and therefore has a completely unhelpful (and nonreproducible) source file name, and diagnose this as an error. Document that the name option (--name to pod2man) is required when processing POD source from standard input. (Debian Bug#777405)" [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777405 [2] http://www.eyrie.org/~eagle/software/podlators/news.html -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1501566 Title: squid3 FTBFS due to missing --name arg to pod2man To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1501566/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1501566] [NEW] squid3 FTBFS due to missing --name arg to pod2man
Public bug reported: squid3 fails with: dh_install -psquid3 --sourcedir=/«PKGBUILDDIR»/debian/tmp cp: cannot stat '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8': No such file or directory dh_install: cp --reflink=auto -a /«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/basic_db_auth.8 debian/squid3//usr/share/man/man8/ returned exit code 1 make: *** [binary-install/squid3] Error 2 /usr/share/cdbs/1/rules/debhelper.mk:213: recipe for target 'binary-install/squid3' failed caused by helpers/auth_basic/DB/config.test failure during configure phase, which filters out the DB basic auth. The error in config.test is caused by a missing --name argument to pod2man: IO::File=IO(0x24d5e30) around line 1: No name given for document POD document had syntax errors at /usr/bin/pod2man line 71. Since Perl 5.20.2-4 pod2man behavior changed for pipes and now the --name parameter must be included (or --errors set to 'pod', 'stderr', or 'none'). As per Debian [1] and pod2man change log page [2]: "[Pod::Man] Attempt to detect if the input came from a pipe and therefore has a completely unhelpful (and nonreproducible) source file name, and diagnose this as an error. Document that the name option (--name to pod2man) is required when processing POD source from standard input. (Debian Bug#777405)" [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777405 [2] http://www.eyrie.org/~eagle/software/podlators/news.html ** Affects: squid Importance: Unknown Status: Unknown ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs ** Bug watch added: Squid Bugzilla #4338 http://bugs.squid-cache.org/show_bug.cgi?id=4338 ** Also affects: squid via http://bugs.squid-cache.org/show_bug.cgi?id=4338 Importance: Unknown Status: Unknown ** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1501566 Title: squid3 FTBFS due to missing --name arg to pod2man To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1501566/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
** Project changed: linux => squid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/squid/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
** Bug watch added: Squid Bugzilla #4323 http://bugs.squid-cache.org/show_bug.cgi?id=4323 ** Also affects: linux via http://bugs.squid-cache.org/show_bug.cgi?id=4323 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
** Attachment removed: "debdiff to fix libecap dependency and logical-not-parentheses warning" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+attachment/4465698/+files/squid3_3.3.8-1ubuntu16-FTBFS.debdiff ** Description changed: - Note: currently squid3 fails due to libecap3-dev dependency, this is - easily fixed by going back to libecap2-dev (only squid 3.5+ will build - with libecap3-dev [1]). - - After libecap2-dev dependency fix, squid then fails due to "logical-not- - parentheses". - - g++ -DHAVE_CONFIG_H -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr - /include/mit-krb5 -isystem /usr/include/mit-krb5 -I. -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 - - isystem /usr/include/mit-krb5 -isystem /usr/include/mit-krb5 -I/usr/include/libxml2 -Wall -Wpointer - -arith -Wwrite-strings -Wcomments -Werror -pipe -D_REENTRANT -m64 -g -O2 -fPIE -fstack-protector-st - rong -Wformat -Werror=format-security -std=c++0x -c -o lru/store_repl_lru.o lru/store_repl_lru.cc - heap/store_repl_heap.cc: In function 'StoreEntry* heap_purgeNext(RemovalPurgeWalker*)': - heap/store_repl_heap.cc:224:36: error: logical not is only applied to the left hand side of compari - son [-Werror=logical-not-parentheses] - if (!heap_nodes(heap->theHeap) > 0) - ^ - - Fixing that, it then fails due to mismatching headers between linux- - libc-dev_4.2.0-10.11 and libc6-dev_2.21-0ubuntu4. + With the fix at LP: #1496924 applied, squid3 fails due to mismatching + headers between linux-libc-dev_4.2.0-10.11 and libc6-dev_2.21-0ubuntu4. In file included from /usr/include/linux/netfilter.h:7:0, - from /usr/include/linux/netfilter_ipv4.h:8, - from Intercept.cc:99: + from /usr/include/linux/netfilter_ipv4.h:8, + from Intercept.cc:99: /usr/include/linux/in.h:28:16: error: redeclaration of 'IPPROTO_IP' -IPPROTO_IP = 0, /* Dummy protocol for TCP */ - ^ + IPPROTO_IP = 0, /* Dummy protocol for TCP */ + ^ In file included from /usr/include/arpa/inet.h:22:0, - from ../../include/util.h:42, - from ../../include/Array.h:39, - from ../../src/comm/forward.h:4, - from ../../src/comm/Connection.h:40, - from Intercept.cc:34: + from ../../include/util.h:42, + from ../../include/Array.h:39, + from ../../src/comm/forward.h:4, + from ../../src/comm/Connection.h:40, + from Intercept.cc:34: /usr/include/netinet/in.h:42:5: note: previous declaration ' IPPROTO_IP' - IPPROTO_IP = 0,/* Dummy protocol for TCP. */ - ^ + IPPROTO_IP = 0,/* Dummy protocol for TCP. */ + ^ In file included from /usr/include/linux/netfilter.h:7:0, - from /usr/include/linux/netfilter_ipv4.h:8, - from Intercept.cc:99: + from /usr/include/linux/netfilter_ipv4.h:8, + from Intercept.cc:99: /usr/include/linux/in.h:30:18: error: redeclaration of 'IPPROTO_ICMP' -IPPROTO_ICMP = 1, /* Internet Control Message Protocol */ - ^ + IPPROTO_ICMP = 1, /* Internet Control Message Protocol */ + ^ In file included from /usr/include/arpa/inet.h:22:0, - from ../../include/util.h:42, - from ../../include/Array.h:39, - from ../../src/comm/forward.h:4, - from ../../src/comm/Connection.h:40, - from Intercept.cc:34: + from ../../include/util.h:42, + from ../../include/Array.h:39, + from ../../src/comm/forward.h:4, + from ../../src/comm/Connection.h:40, + from Intercept.cc:34: /usr/include/netinet/in.h:44:5: note: previous declaration ' IPPROTO_ICMP' - IPPROTO_ICMP = 1,/* Internet Control Message Protocol. */ - ^ + IPPROTO_ICMP = 1,/* Internet Control Message Protocol. */ + ^ Tried to ignore "#include linux/netfilter.h" in src/ip/Intercept.cc:99 to no avail as build fails later on due to missing "SO_ORIGINAL_DST" in Intercept.cc. Removing arpa and netinet header inclusions also lead to eventual build failures due to missing symbols. So far I have found no way to have squid linking solely to either the kernel or libc without disabling netfilter altogether. - - [1] http://wiki.squid- - cache.org/ConfigExamples/ContentAdaptation/eCAP#Build_eCAP_library -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sou
[Bug 1496924] [NEW] squid3 FTBFS due to bad libecap3 dependency and logical-not-parentheses warning
Public bug reported: Currently squid3 FTBFS due to: 1. libecap3-dev dependency, should be libecap2-dev [1] 2. error due to a "logical-not-parentheses" warning = Build error #1 checking for EXT_LIBECAP... no configure: error: Package requirements (libecap >= 0.2.0 libecap < 0.3) were not met: Requested 'libecap < 0.3' but version of eCAP is 1.0.1 You may find new versions of eCAP at http://www.e-cap.org/ = = Build error #2 ++ -DHAVE_CONFIG_H -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr /include/mit-krb5 -isystem /usr/include/mit-krb5 -I. -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 - isystem /usr/include/mit-krb5 -isystem /usr/include/mit-krb5 -I/usr/include/libxml2 -Wall -Wpointer -arith -Wwrite-strings -Wcomments -Werror -pipe -D_REENTRANT -m64 -g -O2 -fPIE -fstack-protector-st rong -Wformat -Werror=format-security -std=c++0x -c -o lru/store_repl_lru.o lru/store_repl_lru.cc heap/store_repl_heap.cc: In function 'StoreEntry* heap_purgeNext(RemovalPurgeWalker*)': heap/store_repl_heap.cc:224:36: error: logical not is only applied to the left hand side of comparison [-Werror=logical-not-parentheses] if (!heap_nodes(heap->theHeap) > 0) ^ == [1] https://launchpad.net/ubuntu/+source/squid3/3.3.8-1ubuntu15/+build/7870177 ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs patch ** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496924 Title: squid3 FTBFS due to bad libecap3 dependency and logical-not- parentheses warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496924] Re: squid3 FTBFS due to bad libecap3 dependency and logical-not-parentheses warning
** Patch added: "squid3_3.3.8-1ubuntu16.debdiff" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+attachment/4466957/+files/squid3_3.3.8-1ubuntu16.debdiff ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496924 Title: squid3 FTBFS due to bad libecap3 dependency and logical-not- parentheses warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496924] Re: squid3 FTBFS due to bad libecap3 dependency and logical-not-parentheses warning
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496924 Title: squid3 FTBFS due to bad libecap3 dependency and logical-not- parentheses warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496924] Re: squid3 FTBFS due to bad libecap3 dependency and logical-not-parentheses warning
Please note that squid will still FTBFS due to LP: #1496223 even after applying this patch. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496924 Title: squid3 FTBFS due to bad libecap3 dependency and logical-not- parentheses warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496924/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] Re: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
Note that the attached debdiff only fixes 2 of the 3 issues: - libecap2 dependency - logical-not-parentheses warning Still pending: - headers mismatch ** Patch added: "debdiff to fix libecap dependency and logical-not-parentheses warning" https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+attachment/4465698/+files/squid3_3.3.8-1ubuntu16-FTBFS.debdiff ** Tags added: ftbfs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1496223] [NEW] squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch
Public bug reported: Note: currently squid3 fails due to libecap3-dev dependency, this is easily fixed by going back to libecap2-dev (only squid 3.5+ will build with libecap3-dev [1]). After libecap2-dev dependency fix, squid then fails due to "logical-not- parentheses". g++ -DHAVE_CONFIG_H -I../.. -I../../include -I../../lib -I../../src -I../../include -isystem /usr /include/mit-krb5 -isystem /usr/include/mit-krb5 -I. -I/usr/include/libxml2 -D_FORTIFY_SOURCE=2 - isystem /usr/include/mit-krb5 -isystem /usr/include/mit-krb5 -I/usr/include/libxml2 -Wall -Wpointer -arith -Wwrite-strings -Wcomments -Werror -pipe -D_REENTRANT -m64 -g -O2 -fPIE -fstack-protector-st rong -Wformat -Werror=format-security -std=c++0x -c -o lru/store_repl_lru.o lru/store_repl_lru.cc heap/store_repl_heap.cc: In function 'StoreEntry* heap_purgeNext(RemovalPurgeWalker*)': heap/store_repl_heap.cc:224:36: error: logical not is only applied to the left hand side of compari son [-Werror=logical-not-parentheses] if (!heap_nodes(heap->theHeap) > 0) ^ Fixing that, it then fails due to mismatching headers between linux- libc-dev_4.2.0-10.11 and libc6-dev_2.21-0ubuntu4. In file included from /usr/include/linux/netfilter.h:7:0, from /usr/include/linux/netfilter_ipv4.h:8, from Intercept.cc:99: /usr/include/linux/in.h:28:16: error: redeclaration of 'IPPROTO_IP' IPPROTO_IP = 0, /* Dummy protocol for TCP */ ^ In file included from /usr/include/arpa/inet.h:22:0, from ../../include/util.h:42, from ../../include/Array.h:39, from ../../src/comm/forward.h:4, from ../../src/comm/Connection.h:40, from Intercept.cc:34: /usr/include/netinet/in.h:42:5: note: previous declaration ' IPPROTO_IP' IPPROTO_IP = 0,/* Dummy protocol for TCP. */ ^ In file included from /usr/include/linux/netfilter.h:7:0, from /usr/include/linux/netfilter_ipv4.h:8, from Intercept.cc:99: /usr/include/linux/in.h:30:18: error: redeclaration of 'IPPROTO_ICMP' IPPROTO_ICMP = 1, /* Internet Control Message Protocol */ ^ In file included from /usr/include/arpa/inet.h:22:0, from ../../include/util.h:42, from ../../include/Array.h:39, from ../../src/comm/forward.h:4, from ../../src/comm/Connection.h:40, from Intercept.cc:34: /usr/include/netinet/in.h:44:5: note: previous declaration ' IPPROTO_ICMP' IPPROTO_ICMP = 1,/* Internet Control Message Protocol. */ ^ Tried to ignore "#include linux/netfilter.h" in src/ip/Intercept.cc:99 to no avail as build fails later on due to missing "SO_ORIGINAL_DST" in Intercept.cc. Removing arpa and netinet header inclusions also lead to eventual build failures due to missing symbols. So far I have found no way to have squid linking solely to either the kernel or libc without disabling netfilter altogether. [1] http://wiki.squid- cache.org/ConfigExamples/ContentAdaptation/eCAP#Build_eCAP_library ** Affects: squid3 (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/1496223 Title: squid3 FTBFS due to linux-libc-dev and libc6-dev headers mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1496223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1483403] Re: ceph FTBFS with boost1.58
updated debdiff ** Patch added: "fix: remove unused variable (ceph #11576)" https://bugs.launchpad.net/debian/+source/ceph/+bug/1483403/+attachment/4442920/+files/ceph_0.94.2-0ubuntu3.debdiff ** Patch removed: "fix: remove unused variable (ceph #11576)" https://bugs.launchpad.net/debian/+source/ceph/+bug/1483403/+attachment/4442502/+files/attachment -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1483403 Title: ceph FTBFS with boost1.58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1483403/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1483403] Re: ceph FTBFS with boost1.58
** Bug watch added: Debian Bug tracker #795178 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795178 ** Also affects: ceph (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795178 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1483403 Title: ceph FTBFS with boost1.58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1483403/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1483403] Re: ceph FTBFS with boost1.58
Upstream bug report and fix at http://tracker.ceph.com/issues/11576 (LP won't track it). ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1483403 Title: ceph FTBFS with boost1.58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1483403/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1483403]
** Attachment added: "attachment" https://bugs.launchpad.net/bugs/1483403/+attachment/4442502/+files/attachment -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ceph in Ubuntu. https://bugs.launchpad.net/bugs/1483403 Title: ceph FTBFS with boost1.58 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1483403/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
