Am Samstag, den 27.02.2016, 23:59 +0100 schrieb Aurelien Jarno: > On 2016-02-26 22:03, Fabian Niepelt wrote: > > > > > > > > IMHO making sure that programs are restarted after applying the > > > security > > > update should be enough, but I am not fully sure about my > > > analysis, so a > > > confirmation would be nice to have. > > The machines in question have been rebooted a few times after > > upgrading. > Ok then my scenario might be wrong. > > > > > I will try to get a full backtrace next week. Sadly, I won't have > > access to the systems over the weekend. > Ok, no problem. > > > > > > > > > It wonder if it could be that the process is started with the > > > old libc and is later dlopening the new nss libraries. > > Going to investigate if there are old libs lying around somewhere > > in the system on monday. > I am able to trigger similar (but slightly different) segmentation > fault > by doing name resolving with the new libc (ie 2.13-38+deb7u10) but > with > the old /lib/x86_64-linux-gnu/libnss_dns.so.2 (ie from 2.13- > 38+deb7u9). > Do you have any nss modules which do not come from the libc6 package > installed (either from another package or manually installed)? >
Yep, this was it. Searching for the lib yielded an old version of it that is not managed by package management... Thank you for giving me the hint. > Thanks for your help in debugging. Thank you all for your time and sorry for the noise! Greetings
