Package: apt
Version: 1.1.5
Severity: normal
Since some time, the rred phase during aptitude/apt-get update is very
slow and produces very high system cpu-load.
Today I managed to get an strace of the relevant process (the one
matched by "pgrep -f rred", I don't know the exact name right now).
Resending after unarchiving.
-- Forwarded Message --
Subject: Re: Bug#798727: Bug #798727: Breaks sa-learn
Date: Saturday 12 December 2015, 14:00:09
From: Niko Tyni <nt...@debian.org>
To: Stefan Fritsch <s...@sfritsch.de>, 798...@bugs.debian.org
CC: 799...@bug
This breaks sa-learn from the spamassassin package, which makes bayes
learning difficult to impossible. Please backport the fix to jessie
UTF-16:Unrecognised BOM 7300 at
/usr/share/perl5/Mail/SpamAssassin/Message/Node.pm line 406. at
/usr/bin/sa-learn line 497.
On Monday 30 November 2015 10:09:09, Harald Dunkel wrote:
> Package: apache2
> Version: 2.4.10-10+deb8u3
>
> I get a reproducible segmentation fault if I do a git clone
> over http (using simple http, not "smart http", not https).
> See attached debug output (thread 4).
>
> git is version 2.4.6.
On Tuesday 01 September 2015 13:35:11, Vitaliy Okulov wrote:
>* What led up to the situation?
> Install apache2-mpm-itk and exim4. Configure apache vhost to some
> user and group.
>
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
> Add vhost, set
tags 805966 help
thanks
On Tuesday 24 November 2015 12:38:36, Michal Mauser wrote:
> we have a problem with (not only) phpbb forum freezing for like 2
> minutes when doing file_get_contents (on itself) via https
> (verified certificate). We found that this problem occurs when we
> use
rent perl. Closes: #803472
+ * Fix tests on deferred mpm switch. Add special casing for mpm_itk,
+which is not an mpm anymore, despite the name. Closes: #789914
+Closes: #791902
+ * Fix secondary-init-script to not source the main init script with 'set -e'.
+Closes: #803177
+
+ -- Stefan Frits
Hi,
On Saturday 21 November 2015 04:25:38, Vieno Foo wrote:
>* What led up to the situation?
> less /etc/apache2/conf-available/security.conf
>
>* What was the outcome of this action?
> finding Apache2.2 syntax at the first example of a entry
>
>* What outcome did you expect
reassign 779077 libapache2-mod-fcgid
found 779077 1:2.3.9-1
affects 779077 apache2
thanks
On Tuesday 03 November 2015 13:02:00, Chris Boot wrote:
> We've just hit the same crash again, but on a different server for a
> different client of ours. This time it was an upgrade from Wheezy
> to Jessie,
reassign 805737 apache2
found 805737 2.4.17-2
affects 805737 libembperl-perl
retitle 805737 apache2 crash when started with -X
thanks
On Saturday 21 November 2015 22:42:00, Niko Tyni wrote:
> The test apache2 process is crashing with this backtrace:
> Core was generated by `/usr/sbin/apache2
Adding crypt blowfish would improve interopability (e.g. for NIS). So
far there has been md5 crypt as common algorithm that is supported by
most platforms, but that is now considered insecure and it has been
removed from some platforms.
So, there is for example no password algorithm that is
This still affects
linux-image-4.2.0-1-amd644.2.5-1
but it is fixed with
linux-image-4.3.0-rc7-amd64 4.3~rc7-1~exp1
Package: src:linux
Version: 4.2.3-2
Severity: important
Hi,
I cannot use KVM with 4.2, qemu loops with 100% CPU during seabios
initialization. Booting with the latest linux-image-4.1.0-2-amd64 fixes
the issue.
The simplest reproducer is
qemu-system-x86_64 --enable-kvm
but it happens with all
Another false positive:
E: apache2 source: source-is-missing
docs/manual/style/scripts/prettify.js
This file is actually the source. The minified version is in
docs/manual/style/scripts/prettify.min.js . See
http://sources.debian.net/src/apache2/2.4.16-3/docs/manual/style/scripts/
On Tuesday 29 September 2015 07:06:46, Jörg Frings-Fürst wrote:
> Hello Stefan,
>
> I have forward your bug and the first answer was:
> > Mon Sep 28 15:54:38 2015, comment #1:
> >
> >
> > What does the "extracted smbios file" look like? How was it
> > generated? The DMI table is beyond the
Package: devscripts
Version: 2.15.8
Severity: wishlist
Tags: patch
Hi,
I sometimes use annotate-output with a constant prefix (not containing a
time format string) to mark the output of several programs that run at
the same time. In this case, it is not necessary to call 'date' for each
line.
for now, because it is at least
not complete or maybe causes regressions (see #791902). Re-opens
#789914
-- Stefan Fritsch s...@debian.org Fri, 28 Aug 2015 18:24:17 +0200
This reverts the apache2.postinst part of the 2.4.10-10+deb8u2 diff.
Sorry for the hassle.
Cheers,
Stefan
Hi Carlos,
On Friday 28 August 2015 15:02:11, Ondřej Surý wrote:
On Fri, Aug 28, 2015, at 00:43, Carlos C Soto wrote:
Same problem here but I'm running Debian 8.1
Package: libapache2-mod-php5
Version: 5.6.12+dfsg-0+deb8
Architecture: amd64
Configuring libapache2-mod-php5
[ Stefan Fritsch ]
* Fix upgrade logic: When upgrading from wheezy with apache2.2-common
but without apache2 installed to jessie, part of the conffile handling
logic would not run, causing outdated conffile content to be kept.
This is part of the solution for bug #794933
Package: dmidecode
Version: 2.12-3
Severity: normal
Dear Maintainer,
running dmidecode on the extracted smbios file from a thinkpad T450s causes a
crash. The way we extracted the smbios works with other laptops. While the
file may be corrupt, dmidecode should not crash in any case. Backtrace is
On Fri, 21 Aug 2015, Adam D. Barratt wrote:
On Sun, 2015-08-16 at 13:43 +0200, Stefan Fritsch wrote:
Please review ssl-cert_1.0.32+deb7u1 for inclusion in oldstable. The
main change is switching from sha1 to sha256 for new certificates
because browsers start marking sha1 as insecure.
I'm
The apache2-module-depends-on-real-apache2-package appears to either be
bogus or be pointing to a bug in dh_apache2.
yes, we have changed dh_apache2 recently and without much preparation
because that was needed for a subversion security update.
I think the lintian check will have to be
On Tue, 18 Aug 2015, Takatsugu Nokubi wrote:
Sorry fo late reply.
I tried it with rebuilded deb because I use i386 arch.
So it seems to work fine.
Thanks for the testing
Stefan
as insecure.
ssl-cert (1.0.32+deb7u1) wheezy; urgency=medium
* Switch to SHA2 for newly generated certificates. Closes: #733255, #773815
* Set umask to make sure that the generated key is not world-readable
for a short timespan while make-ssl-cert runs. Closes: #780828
-- Stefan Fritsch s
AFAICS, this happens when one upgrades from wheezy from a state where
only apache2.2-common is installed but not apache2. There is a bug in
apache2's preinst in jessie that makes it not recognize this case and
not execute the conffile handling.
While I think I have a fix, I am not not
On Saturday 08 August 2015 00:25:37, Felicitus wrote:
Please try the version from https://people.debian.org/~sf/794383/
and check if it either fixes the problem or at least gives some
more information in the error log. You may either replace all
packages with dpkg or only the
On Saturday 08 August 2015 11:38:14, Andreas Beckmann wrote:
during a test with piuparts I noticed your package failed the
piuparts upgrade test because dpkg detected a conffile as being
modified and then prompted the user for an action. As there is no
user input, this fails. But this is not
On Saturday 08 August 2015 09:34:52, Andreas Beckmann wrote:
With apache2.2-common being gone this should be rather easy.
IIRC these conffiles were taken over by the apache2 package, so
all that should be needed are unversioned
Breaks+Replaces: apache2.2-common
in the apache2
Hi,
On Sunday 02 August 2015 14:14:11, Felicitus wrote:
[Sun Aug 02 13:19:52 2015] [error] Failed to configure CA
certificate chain!
Please try the version from https://people.debian.org/~sf/794383/
and check if it either fixes the problem or at least gives some
more information in the error
On Monday 20 July 2015 13:33:04, Jean-Michel Vourgère wrote:
We want to backport that to jessie, don't we? I mean a minimal fix.
Yes, we do.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
reassign 789914 apache2
found 789914 2.4.10-3
thanks
This also affects jessie + stretch.
On Thursday 25 June 2015 10:27:59, Andreas Beckmann wrote:
Enabling conf serve-cgi-bin.
Enabling site 000-default.
info: mpm_prefork: No action required
This is wrong. There seems to be a ! that
severity 790943 normal
thanks
On Friday 03 July 2015 10:56:54, Daniel Pocock wrote:
I've marked this bug serious because it could lead to security
problems if people mix root certs and other certs in the same
directory
The certificates generated by make-ssl-cert all have X509v3 Basic
This module has been broken for 2 years. A replacement exists in the
form of mod_auth[nz]_dbd in the apache2 package. We will request its
removal very soon now.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: ftp.debian.org
Severity: normal
cruft-report has:
* source package apache2 version 2.4.12-2 no longer builds
binary package(s): apache2-mpm-event apache2-mpm-itk apache2-mpm-prefork
apache2-mpm-worker apache2-suexec apache2.2-bin apache2.2-common
libapache2-mod-macro
Hi,
On Tuesday 05 May 2015 14:01:56, Michael Ablassmeier wrote:
we recently migrated over an OTRS instance from another system to
debian jessie and it appears we may have the same issue, sporadic
segfauls, but we do not use the event_mpm but the default worker:
[Tue May 05 13:02:19.929973
Hi Chris,
On Tuesday 24 February 2015 09:36:58, Chris Boot wrote:
We have been experiencing segmentation faults in apache2 when using
the event MPM in jessie. These manifest themselves with log entries
I have uploaded a fix to unstable. It would be great if you could grab
2.4.10-11 from there
On Friday 20 March 2015 02:36:36, Daniel Kahn Gillmor wrote:
make-ssl-cert appears to create the secret key material and then
chmod it to restrict permissions. This leaves a race condition
where a non-privileged user on the system can read the file before
the permissions change takes effect,
You need to provide more information.
How do you use squirrelmail/roundcube? With mod_php or with fcgi or
with some other config? Reverse proxy?
Does your ssl config may cause renegotiation to occur? For example, do
you have any ssl related directives in per-directory or per-location
On Monday 09 February 2015 16:34:02, Jean-Michel Nirgal Vourgère
wrote:
What is your opinion on that problem?
That's a valid feature request. But for after jessie.
Do you see a more generic way to restrict tor incoming connections
so that it doesn't match require local filter?
I don't have
On Wednesday 11 February 2015 20:19:41, Victor Porton wrote:
It produces errors like the following on unexistent .htaccess files.
There should be no such message.
[Wed Feb 11 20:05:51 2015] [crit] [client 220.181.108.140]
(13)Permission denied:
On Monday 16 February 2015 16:00:36, Michael Biebl wrote:
There is also natural drift between the system clock and the RTC.
Who is supposed to account for that? On a system with an uptime
of several months, the drift may be large enough to cause the
time to go backwards at a reboot.
On Mon, 16 Feb 2015, Martin Pitt wrote:
Stefan Fritsch [2015-02-13 10:32 +0100]:
Can't you agree that the best way forward for jessie is to change this in
systemd?
For jessie I'd be okay with this. I'd rather have the actual unit in
util-linux and then unmask it in systemd, but that'd
On Fri, 13 Feb 2015, Martin Pitt wrote:
Control: reassign -1 util-linux 2.25.2-5
Control: severity -1 normal
I still disagree with critical:
I also disagree this should be done in the first place. But I don't
want to put myself into eternal wars and who shouds the loudest
wins, so I'll
You really should CC the the submitter when responing.
On Tuesday 10 February 2015 09:56:28, Martin Pitt wrote:
Control: severity -1 normal
Stefan Fritsch [2015-01-31 10:19 +0100]:
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
This is severity
On Friday 13 February 2015 00:09:00, Stefan Fritsch wrote:
IMHO the only proper time to write the hardware clock is when we
know the system time is correct, i. e. after an NTP sync or when
the user sets it manually.
Even if it is decided that this is right, this would require fixing
Package: systemd
Version: 215-11
Severity: normal
According to the systemd-fsck man page, it should not start multiple
fscks on the same rotating disk in parallel but that does not seem to
work on LVM. The fstab has the passno field to configure the fsck order
manuall but systemd-fsck ignores its
severity 755722 grave
thanks
The attached service file (from [1]) seems to work if put into
/etc/systemd/system/hwclock.service and enabled with
systemctl enable hwclock
Please include it in the package.
Note that I will escalate this to the TC if you downgrade the severity
of this bug again
Package: kopete
Version: 4:4.14.1-2
Severity: normal
I just noticed that kopete installs a mozilla browser plugin. There
seems to be little information on what this plugin does. In particular,
the kopete package description does not give any hint about this.
Since this greatly increases the
On Wednesday 04 February 2015 01:41:14, Michael Biebl wrote:
Am 31.01.2015 um 10:19 schrieb Stefan Fritsch:
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
thanks
Systemd must make sure that the system clock does not go
backwards,
which
Hi Niels,
On Tuesday 27 January 2015 21:44:34, Niels Thykier wrote:
I have taken the liberty of closing this bug now. Should you have
any remarks to the patch / wording, please do not hesitate to let
me know (or file a new bug).
Thank you very much for your help. That was on my todo list but
severity 755722 serious
retitle 755722 systemd must sync systemclock to RTC on shutdown
thanks
Systemd must make sure that the system clock does not go backwards,
which causes all kinds of problems, with file systems and with other
software. To achieve that, systemd has to sync the system time
Hi,
I had this problem, too, with
systemd 215-5+b1
systemd-shim 8-4
But I haven't seen any lost systemd-logind processes since upgrading
to
systemd215-8
systemd-shim 9-1
I am still not running systemd as pid 1 on that system.
Therefore I suggest closing the bug until
This is probably this upstream bug report which concerns some
brokenness with the Define directive:
https://issues.apache.org/bugzilla/show_bug.cgi?id=57328
The config on serverfault shows that you used Define:
IfModule mod_alias.c
IfModule mod_cgi.c
Define
Just a note for people finding this via google:
Openbsd's virtio-block driver works reasonably well while its virtio-scsi
driver is not yet stable. The solution to this problem is therefore to
change qemu's commandline to use virtio-block instead of virtio-scsi. This
argument should work:
Hi,
On Mon, 12 Jan 2015, Francois Marier wrote:
After upgrading from 2.2.22-13+deb7u3 to 2.2.22-13+deb7u4, Apache refused to
start on my server with this error message in /var/log/apache2/error.log:
[error] Server should be SSL-aware but has no certificate configured [Hint:
On Mon, 12 Jan 2015, Harald Dunkel wrote:
Actually I don't see any reason why apache2 should unconditionally
listen on 80/tcp for a https-only setup, so I wonder if ports.conf
could be moved to conf.d to support a2disconf?
As ports.conf does not contain anything else, editing it should not
reassign 758068 libapache2-mod-security2
thanks
On Sunday 07 September 2014 09:11:54, Stefan Fritsch wrote:
there is now a bug report at
https://github.com/SpiderLabs/ModSecurity/issues/768
Can you please try if the patch for mod_security attached to this
mail fixes the issue?
Re
reassign 774341 gitweb
affects 774341 apache2
thanks
On Thursday 01 January 2015 09:05:26, Jörg Frings-Fürst wrote:
Trigger für libc-bin (2.19-13) werden verarbeitet ...
dpkg: Zyklus bei der Triggerverarbeitung gefunden:
Kette der Pakete, deren Trigger verantwortlich sind oder sein
könnten:
if passphrase was wrong.
+ * Also bump debhelper build-depends to get dh_installdeb with support for
+symlink_to_dir. Closes: #770421
+
+ -- Stefan Fritsch s...@debian.org Mon, 22 Dec 2014 20:24:36 +0100
+
apache2 (2.4.10-8) unstable; urgency=medium
* Bump dpkg Pre-Depends to version that supports
package: apache2
version: 2.2.22-13+deb7u3
tags: wheezy
-- Forwarded Message --
Subject: UID bug in mod SSL
Date: Saturday 11 October 2014, 19:14:13
From: René Malmgren rene.malmg...@gmail.com
To: debian-apa...@lists.debian.org
Hi guys, thanks for a great work.
I am sure that
paragraph about session ticket key life-time and forward secrecy to
+README.Debian. Closes: #762619
+
+ -- Stefan Fritsch s...@debian.org Tue, 23 Dec 2014 23:44:24 +0100
+
apache2 (2.2.22-13+deb7u3) wheezy-security; urgency=high
* CVE-2014-0226: Fix a race condition in scoreboard handling
On Monday 22 December 2014 11:55:09, Rodrigo Campos wrote:
Sorry to bother again, but any news on this front ?
I have asked the release team to confirm the update.
Meanwhile, I have put the packages for amd64 here:
https://people.debian.org/~sf/2.2.22-13+deb7u4/
$ sha256sum *deb *c *gz
reassign 773405 apache2
found 773405 2.4.10-8
thanks
On Thursday 18 December 2014 13:34:45, Michael Biebl wrote:
@apache maintainers: Are you ok if we re-assign this to the apache
package and handle it there? You can keep the
pkg-systemd-maintainers in CC if there are further questions.
makes
tags 771199 wheezy
thanks
On Friday 12 December 2014 11:29:49, Rodrigo Campos wrote:
On Thu, Dec 04, 2014 at 10:01:51PM +, Rodrigo Campos wrote:
Ping ? :)
Re-ping ?
This is a fix that we can and should include in wheezy. However I
don't know when the next stable point release is
Hi Guillem,
On Monday 17 November 2014 01:43:46, Guillem Jover wrote:
I've fixed this now locally by bumping the version for both symlink
commands to just 1.17.14, which avoids translation work, and
targetting 1.17.22.
Thanks. It seems a build-depends is also required, see #770421. Maybe
you
On Friday 21 November 2014 13:46:24, Raphael Hertzog wrote:
Technically, it's debhelper (dh_installdeb) that needs to be updated
in Build-Depends. You need debhelper = 9.20131213 (first version
that knew about that command).
And you want to file a bug report against debhelper so that it
On Wednesday 19 November 2014 16:49:44, Andreas Beckmann wrote:
On 2014-11-18 14:23, Stefan Fritsch wrote:
I think it would be best to ask the dpkg maintainers if they can
make dpkg recognize that the obsolete conffiles have been
removed. If that
that is a hard part
but I got some weird
Hi Andreas,
On Monday 10 November 2014 00:11:20, Andreas Beckmann wrote:
On 2014-11-09 19:01, Stefan Fritsch wrote:
On Sunday 09 November 2014 14:21:34, Andreas Beckmann wrote:
I'm not sure whether (or how) dpkg-maintscript-helper mv_conffile
can be used reliably to rename a conffile
Package: dpkg
Version: 1.17.21
Severity: normal
The dpkg-maintscript-helper man page claims that symlink_to_dir needs
Pre-Depends: dpkg (= 1.17.5). But the relative symlink feature in
symlink_to_dir was introduced in 1.17.14. This should be noted in the
man page.
A package that follows the man
On Sunday 09 November 2014 14:21:34, Andreas Beckmann wrote:
I'm not sure whether (or how) dpkg-maintscript-helper mv_conffile
can be used reliably to rename a conffile and switch ownership to
another package at the same time.
I don't see how there is any way to handle rename and takeofer of
Thanks for the report. The doc symlinks will be fixed in the next
upload.
But the errors about conf files seem to be false positives. The
upgraded apache2.2-common package does not contain any of those files
anymore. Therefore it is correct that they are missing.
On Sunday 02 November 2014
Hi,
Your problem is not related to Bug#533231. Please open a new report.
On Friday 31 October 2014 09:54:51, Torben Dannhauer wrote:
Every night during/after/before logrotate, Apache crashes somehow
and does not come up fully functional again. This happens als well
if I trigger manually a
On Sunday 19 October 2014 12:02:55, Francois Marier wrote:
On 2014-10-18 at 21:27:24, Stefan Fritsch wrote:
I don't think enabling SSLHonorCipherOrder by default is good. It
makes it nearly impossible for the clients to select what they
think is appropriate. Also, clients will be upgraded
On Sunday 05 October 2014 12:04:12, Daniel Pocock wrote:
The bug report is not for the behavior (I agree it makes sense to
deny the login), it is a problem with the error message.
The error message says user daniel not found - but for this
particular case, the error should be something like
severity 763582 normal
thanks
On Wednesday 01 October 2014 00:33:11, Leslie Rhorer wrote:
Doing some research, I think I found the solution to the second
issue. I installed libapache2-mod-python, and now Apache treats the
same way as the other CGI scripts, but it still will not run any
On Tuesday 23 September 2014 15:21:35, Vincent Lefevre wrote:
OK, but then, is there any reason not to announce it in the NEWS
file? This is a significant configuration change!
This is a change like the ones which happen every day in Debian
during an update. It's not newsworthy I
On Tuesday 23 September 2014 20:30:04, Rodrigo Campos wrote:
I tried to do some tests to see if maybe a reload was enough
(doesn't cause downtime :)) to re-generate the randomly generated
session ticket key at startup. But let me be very clear about
this: I'm not a security expert (far from
On Tuesday 23 September 2014 22:02:36, Rodrigo Campos wrote:
But well, that email says with that setup it did. As it did with
mine. And reading the thread I didn't see nobody saying that in all
mpms and configurations it will. They do say, though, that if a
graceful restart frees up and
On Monday 15 September 2014 15:57:05, Alex Bligh wrote:
This bug has been closed as fixed in 2.4.10-1. However, Utopic
2.4.10-1ubuntu1 which is based on 2.4.10-1 certainly does not
include mod_ident in the build. Is this a Debian/Ubuntu difference
or was this closed too soon?
It was fixed
On Tuesday 09 September 2014 01:09:03, Daniel Dickinson wrote:
Apache fails to start due to unimplemented function in the default
configuration when run on kfreebsd (at least amd64 but probably
all).
The solution is to add
AcceptMutex fcntl
in a file in /etc/apache2
Do you know if
On Friday 29 August 2014 17:34:03, Matt Taggart wrote:
For the things that do store data, I think 7 days should be enough
to ensure that they have a chance to process the logs before they
get rotated.
Thanks for the detailed analysis. Somehow 7 days seems awfully short
to me when one has to
Hi,
On Friday 15 August 2014 21:33:07, Stefan Fritsch wrote:
It seems mod_security does its own things with apr allocators, which
causes MaxMemFree not to have any effect for mod_security's
allocations. I have asked them why they do that. Let's see what
they respond.
there is now a bug
On Thursday 29 August 2013 17:37:45, Jean-Michel Vourgère wrote:
This is almost all in the subject.
I think invoke-rc.d would make sure local policy is properly
enforced.
The culprit is in source file debian/apache2.logrotate
Why is this a problem? If apache2 is running (and the pid file
serverity 736809 important
thanks
On Wednesday 30 July 2014 23:22:25, Adrian Bunk wrote:
I do not claim to fully understand the Debian apache packaging,
and after a quick test it seems you are right that you already
have that covered.
I am downgrading this for now until it has been proven to
On Sunday 24 August 2014 19:19:49, Breno Leitao wrote:
Currently apr-util fails to build on new arches, mainly in ppc64el
as shown in:
https://buildd.debian.org/status/fetch.php?pkg=apr-utilarch=ppc64e
lver=1.5.3-2stamp=1408904038
This patch fixes the problem in accordance with
On Monday 25 August 2014 21:23:36, Stefan Fritsch wrote:
Do you have any idea what needs to be changed to
make it work?
It seems apr-util insists on the library being called
libmysqlclient_r, regardless of what mysql-config tells it :(
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ
Package: libtool
Version: 2.4.2-1.7
Severity: normal
Hi,
the libtool documentation [1] says: When no tag is specified, libtool
will default to CC; this tag always exists. But this is not what
libtool does. The --tag parameter seems to be necessary, resulting
in the unable to infer tagged
severity 752872 important
found 752872 1.4.6-3
thanks
On Friday 27 June 2014 11:37:18, Joost van Baal-Ilić wrote:
While libapr1 defaults to fcntl() locking it also supports flock(),
which does not have the problems outlined above. A patch is
attached which makes libapr1 use flock() even if
On Thursday 14 August 2014 17:02:04, Nelson Elhage wrote:
On Thu, Aug 14, 2014 at 12:22 AM, Stefan Fritsch s...@sfritsch.de
wrote:
Can you please try if increasing MaxMemFree to a larger value
fixes your problem, too? 2048 (KB) is the default.
Unfortunately setting that higher (we tried
Hi,
On Wed, 13 Aug 2014, Nelson Elhage wrote:
Please disable the experimental --enable-mmap-allocator option in the
Debian libapr build.
Can you please try if increasing MaxMemFree to a larger value fixes your
problem, too? 2048 (KB) is the default.
I don't want to disable
On Mon, 23 Jun 2014, INTEN - Damian S. Kołodziejczyk wrote:
Strace shows only info about too many open files - so i increase it.
Nothing more points.
Have you looked at APACHE_ULIMIT_MAX_FILES in /etc/apache2/envvars? Maybe
you just need to set a higher value there?
On Monday 16 June 2014 14:20:27, INTEN - Damian S. Kołodziejczyk
wrote:
error log shows only AH00016: Configuration Failed
If you have separate error logs for ssl virtualhosts, please also
check those for additional error messages.
i increased max openfiles (sysctl fs.file-max=512000)
Thanks for the detailed information.
On Wed, 18 Jun 2014, Yann Schlame wrote:
Checking the logs on two affected webservers, this log entry first appeared
on February 16th 2014 in /var/log/apache2/error.log during the daily log
rotation. I'm not sure whether that coincides with prior
On Monday 09 June 2014 20:23:07, Ryan Tandy wrote:
On 07/06/14 08:21 PM, Soren Stoutner wrote:
This is a fairly old bug that appears to have been resolved. Any
reason we shouldn't close it?
It's still possible for the same problem to be introduced again; in
fact Ubuntu did so for few
On Thursday 12 June 2014 11:12:12, Theppitak Karoonboonyanan wrote:
This doesn't occur to me. It still works fine as usual.
So, lowering the severity.
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Have you tried with the i386 version of chromium? It could be that it
only affects
On Thursday 12 June 2014 22:33:44, Sven Joachim wrote:
Am 12.06.2014 um 19:31 schrieb Stefan Fritsch:
On Thursday 12 June 2014 11:12:12, Theppitak Karoonboonyanan
wrote:
This doesn't occur to me. It still works fine as usual.
So, lowering the severity.
Architecture: amd64 (x86_64
Package: chromium
Version: 35.0.1916.153-1
Severity: grave
Justification: renders package unusable
Upgrading chromium chromium-inspector to 35.0.1916.153-1 makes it
break completely for me. Every page (including the settings and the
startup page) yields the above error message and some
tags 750739 moreinfo
thanks
This report does not have enough information. Is there anything
related in the error log? What do you mean with the sysctl?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Hi Steinar,
I have finally removed the obsolete conflict of the mpms with mpm_itk
in 2.4.9-2. But in order for libapache2-mpm-itk to install cleanly, it
seems you also have to add
apache2_switch_mpm prefork
to your postinst before you call enmod.
Cheers,
Stefan
--
To UNSUBSCRIBE, email
only be logged partially. This is related to CVE-2014-0098, but Apache
2.2.22 is not vulnerable to this issue.
* mod_proxy: Fix crashes under high load with threaded mpms.
https://issues.apache.org/bugzilla/show_bug.cgi?id=50335
-- Stefan Fritsch s...@debian.org Sun, 25 May 2014 17:35
201 - 300 of 1443 matches
Mail list logo