I've recently had some problems with asterisk coinciding with an upgrade to nss_ldap-253. Symptoms were: - Asterisk would not start as user asterisk '#asterisk -U asterisk', unless you also added the -f flag to prevent it forking. - Asterisk would start using '#asterisk' or '#asterisk -U asterisk -G asterisk', but then I experienced all sorts of network problems. IAX channels would complain about no route to host and SIP channels would raise a cryptic chan_sip.c error that usually meant a firewall problem. Basically asterisk was unusable for me. Moving back to nss_ldap-249 fixed all these problems. This is on an intel core 2 duo (emerge --info follows), but I was also seeing the same problem on an AMD athlon-xp.
jackfrost ~ # emerge --info Portage 2.1.1-r1 (default-linux/amd64/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.18-gentoo-r1 x86_64) ================================================================= System uname: 2.6.18-gentoo-r1 x86_64 Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz Gentoo Base System version 1.12.5 Last Sync: Mon, 06 Nov 2006 17:20:01 +0000 ccache version 2.3 [enabled] app-admin/eselect-compiler: [Not Present] dev-java/java-config: 1.3.7, 2.0.30 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.6.3, 1.7.9-r1, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r4 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=nocona -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /var/bind" CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-march=nocona -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks metadata-transfer parallel-fetch sandbox sfperms strict" GENTOO_MIRRORS="http://www.mirrorservice.org/sites/www.ibiblio.org/gentoo/ http://gentoo.blueyonder.co.uk/" LC_ALL="en_GB.UTF-8" LINGUAS="en_GB" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local/invisibles /usr/portage/local/layman/kolab2 /usr/portage/local/layman/voip /usr/portage/local/layman/xeffects" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 X a52 aac acpi alsa apache2 arts asterisk audiofile berkdb bitmap-fonts bluetooth bzip2 calendar cdparanoia cdr clamav cli cracklib crypt ctype cups dav dbus dlloader doc dri dts dv dvb dvd dvdr dvdread elibc_glibc encode exif fam ffmpeg flac fortran gdbm gpm hal horde i8x0 iconv idled imagemagick imap input_devices_evdev input_devices_keyboard input_devices_mouse ipv6 jabber java jpeg kde kdeenablefinal kernel_linux kolab ldap ldapsam libg++ linguas_en_GB logrotate matroska mime mmap mp4 musepack musicbrainz mysql mysqli mythtv ncurses nls nptl nptlonly nsplugin offensive ogg opengl oss pam pcre perl php png posix ppds pppd python readline rtc samba sasl session shorten sox spam speex spl sqlite ssl svg tcpd theora tiff transcode truetype-fonts type1-fonts udev unicode usb userland_GNU v4l v4l2 vcd video_cards_i810 vorbis wmf x264 xine xml xorg xprint xvid xvmc yahoo zlib" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_RSYNC_EXTRA_OPTS
could you please test nss_ldap OUTSIDE of asterisk, to see if this is an asterisk problem or an nss_ldap problem? In specific, make certain that you update your /etc/ldap.conf, and check your ssl settings, esp 'ssl on' as we have see weirdness with these.
Sorry, I'm not actually running nss_ldap at the moment - I've just rebuilt my server after a hardware upgrade and haven't gotten around to it yet. The asterisk network problems are unrelated to nss_ldap however - they were caused by asterisk' background DNS update manager and having hostnames in the config files. /etc/ldap.conf was up-to-date - I followed your posts on planet.gentoo.org. Apart from being unable to start asterisk using '#asterisk -U asterisk', nss_ldap-253 seemed to work as well as previous versions, which also complained *a lot* in my logs about being unable to contact the ldap server, but would work nonetheless.
when you go back to asterik with nss_ldap, please test as I requested and reopen.
