> I noticed there is potentially libc6 problem.
>
> At Mon, 18 Aug 2003 12:54:21 +0900,
> GOTO Masanori wrote:
> > > w3m http://localhost/cgi-bin/test.py
> >
> > First syslog run
> > openlog run
> > finished
> > > sudo tail -2 /var/log/messages
> > Aug 18 01:44:10 celesta python: Should be ok
> > Aug 18 01:44:10 celesta test_libc6[8968]: Should be also ok
> >
> > It worked. Could you reduce your apache setting, or check your
> > environment special setting. Also try to use strace -f, or ltrace.
>
> Under my environment, the test is still ok. But, Gottfried, Nikita,
> could you try to use this libc6 version?:
>
> http://people.debian.org/~gotom/glibc/2.3.2-1.test.20030708/
>
I'm sorry to say: the problem also appears with your test version of libc6.
Find attached the output of strace -f for the processes involved.
> If it works for you, we can doubt libc6 locking bug. However I wonder
> why only your enviroment breaks something. Any special settings for
> syslog, or pam?
Well, not really.
I have add the line
local1.* -/var/log/hr_server.log
to /etc/syslog.conf
pam isn't modified at all.
>
> Regards,
> -- gotom
>
Cheers,
Gottfried
Attachment:
libc6-error.strace
Description: Binary data