similar to: Issues with Dovecot/Pam/nss_ldap

Hello. I am running asterisk 1.2.14 on a Dell poweredge with a Digium FXO/FXS card connected to 6 analog lines and using Linksys spa942 phones. My users are complaining of randomly disconnected calls, and when I watch the log (debug warning,notice,error), I don't see any cause. It looks like asterisk is seeing a hangup from the analog end. I have attached my zaptel.conf and zapata.conf.

This message does not contain a bug report or any issues. It is a summary of my experiences with Postfix, Dovecot, and Ldap. 1. Do not use Dovecot 0.99, even if it's what your vendor has packaged. 1a. ... When you upgrade past 0.99, you'll get some double mail because of UIDL's. 2. Do not use PAM and Ldap and then let dovecot talk to pam. It is bad. Don't do it. 2a. Unless

Hi All, Any thoughts on why, while everything seems ok at the OS level (getent , id -a ) Samba doesn't pickup any supplementary groups when Solaris is configured with 'group: files ldap' in nsswitch.conf and using it's own native nss_ldap.so.1 but does when using PADL's nss_ldap? Everything else is equal. Do they use/accept different calls or could it be an

I'm a new dovecot user, just began using it last week. I switched from courier because my research showed that Dovecot did indexes, and allows me to store them anywhere I chose. I did this, and it fixed some severe disk IO issues that my server had. (25k horde only webmail install using imap proxy). I'm using quotas, and by default had it set to 'dirsize'. my postfix is already

hi all, some time ago i remember have had read (on the wiki) that dovecot couldn't work with pam against nss_ldap but i've build a setup using etch's dovecot rc15 and seems to work fine until now thru the server has a low usage (50 users). congratulations for such a nice imap server :)

Hello people, My difficult is get "nss_ldap" compiled and running on my server. I download the tgz file from PADL Software Pty Ltd website, decompress/untar, and then run "./configure" . ./configure runs just fine with no error message. Things go bad when I type: make This is the output after I try to do "make": root@ldap:~/nss_ldap-262# make make all-am make[1]:

Suddenly as of this morning, none of my users can authenticate to samba because nss_ldap is producing cryptic errors. Nothing has changed on either the LDAP server or the Samba server. Looks like this in /var/log/messages: Aug 11 11:19:29 edgar smbd[8394]: nss_ldap: could not soft reconnect to LDAP server - Server is unavailable Yet, the LDAP server IS available, and happily chirping away

I've been unsuccessfully trying to get nss_ldap to work. I've chased down hundreds of google searches over the last 3 days, and I can't seem to get a centos system to authenticate against ldap. Every daemon on the system is running into the same problem: nss_ldap: could not search LDAP server - Server is unavailable sshd, nscd, httpd, you name it.. slapd is clearly running, telnet

Hi all! A while ago I caught a discussion re Samba and LDAP SAM backend, with OpenLDAP and nss_ldap. It seems that the reason the smbd process keeps crashing (and thus losing connections) has something to do with the fact that the LDAP standard allows connections to be unilaterally closed by the directory server, and this was causing Samba to crash. Again - this is my hazy recollection of the

Hi list, I've seen this error now many times (at my own setup and in the archives): sam_account_ok: Checking SMB password for user Simon Dassow [2004/03/05 12:54:19, 1] auth/auth_util.c:make_server_info_sam(821) User Simon Dassow in passdb, but getpwnam() fails! But: # id 'Simon Dassow' uid=1000(Simon Dassow) gid=513(Domain Users) groups=513(Domain Users), 512(Domain Admins)

Hi, I rebooted a old Centos 5 box and now its stuck in an ever increasing timeout loop; nss_ldap: reconnecting tl LDAP server (sleeping # seconds).... This happens before network services starts. Any one know how I can break out of this? I tried booting in single user mode from the grub menu but no dice, the thing keeps nss_ldap looping. Thanks in advance, - aurf

> There is a bug with nss_ldap and bash32 ... I created a new RPM for the > nss_ldap that is currently in our testing repo. Johnny, I was wondering if that RPM includes the security fixes detailed in https://rhn.redhat.com/errata/RHSA-2008-0389.html Thanks in advance, M

Hi all, I am just after some opinions about the pros and cons of winbind compared to the 'standard' kerberos and ldap methods. I've have already got single sign on working with pam_krb5 and nss_ldap (using SASL/GSSAPI) against SBS 2003 (with MSSFU 3.0) using Debian Sarge as clients/'member servers', and integration of Samba is the next bit I'm looking at. The impressions

I have installed and configured the puppet client nodes to use LDAP to authenicate users. LDAP connection is OK and user can be authenicated via LDAP. I use nscd and with my ldap config setting specify on /etc/ldap.conf However, puppet is not happy; and in the /var/log/messages it gives tons of puppet-agent[27499]: nss_ldap: could not search LDAP server puppet-agent[27499]: nss_ldap:

Hi All: Over the weekend I install all the outstanding updates for our CentOS 4 based server. Since I had been holding off on these until I had addressed some disk space issues there were a large number (300+). I know my bad! After installing the updates I rebooted the system and it took forever to boot and once up there were problems connecting to some of our SAMBA shares. I checked the messages

Hello all, since some weeks I try to get the following configuration working Windows 2003 AD (no R2!!) with SFU 3.5 Red Hat Enterprise Linux Server release 5.4 (Tikanga) with Samba (samba-3.0.33-3.14.el5) nss_ldap (nss_ldap-253-21.el5) So I wanted to implement the following setup: http://us5.samba.org/samba/docs/man/Samba-HOWTO-Collection/idmapper.html#id2607783 The main reason using this

I see this in my logs: Nov 7 10:29:23 sn-008 puppetd[3048] nss_ldap: could not get LDAP result - Timed out and I''m not sure what Puppet is doing that relates to ldap. Grepping for LDAP in my manifests yields only references to managing File[''/etc/ldap.conf''] The server is setup for ldap to manage passwd, group, sudo, netgroups, but this should be transparent to any

Hello We have a OpenLDAP-2.2.23 + Samba 3.0.14a and the system is logging a lot (one to each minute, more or less) of errors like this: server smbd[10799]: [ID 510469 daemon.error] nss_ldap: could not get LDAP result - Can't contact LDAP server Well, I would like to ask to samba specialists if is possible that the problem is this slapd.conf option: idletimeout 30 I?m using it because

Hi Anybody can copile NSS_LDAP under Solaris 10 ?, i have a trouble compiling this tool. bash-3.00# make gcc -DHAVE_CONFIG_H -DLDAP_REFERRALS -DLDAP_DEPRECATED -D_REENTRANT -g -O2 -Wall -fPIC -c ldap-nss.c ldap-nss.c: In function `do_sasl_interact': ldap-nss.c:4113: error: `sasl_interact_t' undeclared (first use in this function) ldap-nss.c:4113: error: (Each undeclared identifier

I'm (finally) getting around to putting a backup LDAP authentication server on my network. The backup uses syncrepl to grab the database, and to my eyes both LDAP servers answer read queries identically. I'm testing the client side of this configuration on virtual CentOS 5 i386 machine. /etc/ldap.conf reads ----- %< ----- base dc=DOMAIN,dc=com timelimit 30 bind_timelimit 30