FS#10429 - nscd segfault

Attached to Project: Arch Linux
Opened by Vladimir Korsun (amigo) - Friday, 16 May 2008, 14:07 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 18 December 2008, 21:25 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Andreas Radke (AndyRTR)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

nscd segfault



Additional info:

* package version(s)
glibc 2.7-9

* config and/or log files etc.
with default config file /etc/nscd.conf

archlinux% sudo grep nscd /var/log/messages.log
May 15 12:06:03 archlinux nscd[8375]: segfault at 6bc76a88 eip 8000fba2 esp af007c8c error 4

nscd -d &> attached file



Steps to reproduce:

Just run nscd and wait (ps aux | grep nscd)
   nscd.log (76 KiB)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Thursday, 18 December 2008, 21:25 GMT
Reason for closing:  Fixed
Comment by Jan de Groot (JGC) - Friday, 16 May 2008, 17:01 GMT
Removing the host cache from /etc/nscd.conf should work out. There's a bug in hosts caching in nscd. I think it should be fixed with glibc 2.8. Debian has a backport patch for this in etch-proposed-updates, but I won't apply that since I'm waiting for glibc 2.8 to build the next package.
Comment by Andreas Radke (AndyRTR) - Wednesday, 11 June 2008, 22:36 GMT
please test new glibc 2.8-2 in testing. is this solved?
Comment by Chad Catlett (dwi) - Thursday, 12 June 2008, 03:15 GMT
I'm at 4 hours and running, so that's a new record for me. :)
I only use it at work, so tomorrow I should have more heavy usage of it, and I'll know for sure.. at least in my setup.

Thanks for creating the new build of glibc.
Comment by Chad Catlett (dwi) - Saturday, 14 June 2008, 01:23 GMT
Okay got a crash again :(
sadly i can't get the message because i forgot to run it from a console :/
I'll try again.
Comment by Andreas Radke (AndyRTR) - Tuesday, 09 December 2008, 06:17 GMT
please try latest testing glibc 2.9
Comment by Chad Catlett (dwi) - Friday, 12 December 2008, 04:11 GMT
So far I've went 24 hours without a crash. Unfortunately most of my users are on holiday break, so the box isn't abusing the name services library heavily right now. I'll keep you posted.

Thanks for the update.
Comment by Chad Catlett (dwi) - Thursday, 18 December 2008, 20:55 GMT
Sorry for the delay.

I was able to run for nearly 6 days without any problems. Ultimately the machine itself went down due to a power supply issue.

So I consider it fixed. :)

Was this resolved in stock 2.9 glibc, or did you have to apply some patches?

Loading...