host in question is: FreeBSD goose.ee.washington.edu 6.3-STABLE FreeBSD 6.3-STABLE #6: Wed Mar 26 17:03:35 PDT 2008 root@goose.ee.washington.edu:/usr/obj/usr/src/sys/NIKOLA i386 This box was recently updated to a release that was exactly the same source base as two other boxes I've been using for a month. Upon upgrade amd(8) is now aborting shortly after launch (sometimes even before I can log in on the console there are references to missing amd process(es) in /var/log/messages). I would really appreciate it if someone could take a look at the truss & gdb output at <http://ssli.ee.washington.edu/people/nomad/amd-crash1/truss.out> (181MB!) and <http://ssli.ee.washington.edu/people/nomad/amd-crash1/gdb.out> along with <https://ssli.ee.washington.edu/people/nomad/amd-crash1/amd.log> and see if they can give me a clue about what the problem is. I also have a core file and a copy of the binary available though I'd prefer not to send that URL out to the world. :) It looks like it might be related to nss_ldap. I've removed and reinstalled all of the ldap ports with no success. Any help with this would be greatly appreciated. No one has home directories right now because this is the main homedir server in the lab. thanks, nomad
Lee Damon wrote:> Any help with this would be greatly appreciated. No one has home > directories right now because this is the main homedir server in the lab.I have recently updated by 7.0-PRERELEASE box to 7.0-STABLE and amd(8) has crashed at least twice since then (it was not the case with 7.0-PRE). I am using it only for removable USB devices on my laptop, therefore it is not used all the time. My backtrace shows crash in dlopen() in a similar way yours, but I am not sure whether my debug symbols are right (generated after the crash). Do you have any certain way to reproduce the problem? amd works fine most of the time (although seldom used). --Marcin