[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#490859: marked as done (libaprutil1 Depends libmysqlclient15off >= 5.0.27-1 is wrong)

Your message dated Tue, 15 Jul 2008 23:44:41 +0200
with message-id <200807152344.41880.sf@sfritsch.de>
and subject line Re: bug #490859: libaprutil1 Depends libmysqlclient15off >= 5.0.27-1 is wrong
has caused the Debian Bug report #490859,
regarding libaprutil1 Depends libmysqlclient15off >= 5.0.27-1 is wrong
to be marked as done.

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

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
490859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490859
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: php5-mysql
Version: 5.2.6-2
Severity: normal


I just helped out a guy on a german privat forum, so unfortunatly I
can't give you a link.
He uses stable but wanted Apache2 and PHP from testing/unstable

With Apache 2.2.8 and PHP 5.2.5 it worked fine
With PHP 5.2.6 he got defunct apache processes.

I remembered that there was this libmysqlclient_r change.
So I looked things up and found that Apache doestn't have a versioned
dependency on libapr1 and libaprutil1, so he still got the ones from
stable.
He updated them and still got these zombie process
On Apache2 there was a bug which sounded sth. like that: #480210
Since he updated libmysqlclient15off to 5.0.51a-6 it now works fine

I wasn't sure if I should report it, I think it's a rare case that one
uses stable and just a few packets from testing/unstable
I even don't know if the backports will/are affected. Maybe it even
doestn't matter because lenny will be released soon.

I'll reply to that Apache Bug and mention this bug report there.

Feel free to close it, if you think it's not worth a change on the
depends.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages php5-mysql depends on:
ii  libapache2-mod-php5 [phpapi-2 5.2.6-2    server-side, HTML-embedded scripti
ii  libc6                         2.7-12     GNU C Library: Shared libraries
ii  libmysqlclient15off           5.0.51a-9  MySQL database client library
ii  php5-common                   5.2.6-2    Common files for packages built fr

php5-mysql recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tuesday 15 July 2008, Felix Zielcke wrote:
> He got these messages in his log
>
> [Sun Jul 13 22:56:02 2008] [warn] child process 4322 still did not
> exit, sending a SIGTERM
> [Sun Jul 13 22:56:02 2008] [warn] child process 4323 still did not
> exit, sending a SIGTERM
> [Sun Jul 13 22:56:04 2008] [error] child process 3283 still did not
> exit, sending a SIGKILL
> [Sun Jul 13 22:56:04 2008] [error] child process 3285 still did not
> exit, sending a SIGKILL
> [Sun Jul 13 22:56:04 2008] [error] child process 3352 still did not
> exit, sending a SIGKILL
> ...
> [Sun Jul 13 22:56:05 2008] [notice] caught SIGTERM, shutting down

That's something different than what you saw, then.

> I told him to update libapr1 and libaprutil1 because of that
> libmysqlclient_r.so change in PHP but that didn't help
> Only as he updated after that libmysqlclient15off from etch to
> lenny version it worked

It could be a bug in the old libmysqlclient_r.so that does not affect 
libmysqlclient.so and is fixed in the newer version. In any case, if 
the current libmysqlclient15off fixes the problem, then there is 
nothing we can do. The problem is obviously not severe enough for a 
stable backport and unstable is already fixed.

Therefore I will close the bug report. If you get any relevant new 
information, feel free to reopen the bug report. But I am not sure if 
it is worth the effort.

Cheers,
Stefan

--- End Message ---
Reply to: