389-users February 2010

389-users@lists.fedoraproject.org

40 participants
48 discussions

nss_ldap: failed to bind to LDAP server
by 馬小布 03 Feb '10

03 Feb '10

Hi , guys: I'm currently using the 389 directory server on CentOS 5 , but today it displays something log like this : Dec 22 06:27:56 xscreenserver : nss_ldap: failed to bind to LDAP server ldap://192.168.0.134: Can't contact LDAP server Dec 22 06:27:56 :xscreenserver: nss_ldap: reconnecting to LDAP server (sleeping 64 seconds)... Dec 22 06:29:00 :xscreenserver : nss_ldap: failed to bind to LDAP server ldap://192.168.0.134: Can't contact LDAP server ..... .... The LDAP Server is located in the other server and It takes around 10 minuted for ldao to come up waiting for all the bind timeouts . I've tried googling without some useful imformation . Could someone give some suggestions to me ? Thanks in advances ~.....

3 3

With LDAP server stopped, local authentication fails...
by Sean Carolan 03 Feb '10

03 Feb '10

My LDAP server is working well, but at this point we're not ready to make the jump over to LDAP-only authentication. I would like to keep regular shadow passwords working for a while. I have run authconfig-tui on one of the CentOS clients and made sure "Use MD5 passwords", "Use Shadow Passwords", and "Local Authorization is Sufficient" are all checked. If I stop the LDAP server though, I'm unable to log onto this server with my ssh key or password. Is there a way to keep shadow passwords as a failover method for logging in if the LDAP server is down?

3 2

389-DS to work for only 636 port?
by Ajeet S Raina 03 Feb '10

03 Feb '10

I installed the fresh 389 -DS on my machine. I too ran setupssl2.sh and configured https:// for Management Console. But if i try running: # netstat -pant | grep 389 tcp 0 0 :::389 :::* LISTEN 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:55256 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.146:1777 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:44009 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.10:1192 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.146:3651 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:37322 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.210.53.152:2810 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.146:3650 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.47.22:43948 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.146:1778 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.34:2679 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:51965 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:37359 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.47.22:39271 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.21:3212 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:37377 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:37379 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:44003 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.34:2681 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.21:2926 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:37380 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:37381 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:37365 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.37.91:44006 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.152:2806 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.120:1991 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.14.47.24:389 ::ffff:10.14.53.21:3034 ESTABLISHED 10756/ns-slapd #netstat -pant | grep 636 [root@389-supplier ~]# netstat -pant | grep :636 tcp 0 0 :::636 :::* LISTEN 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.120:1771 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.120:1770 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.209.37.146:3648 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.209.37.146:3649 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.34:2677 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.21:3202 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.34:2676 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.21:3203 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.152:2787 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.152:2802 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.21:2940 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.209.37.146:1774 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.10:1205 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.21:2939 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.210.53.10:1204 ESTABLISHED 10756/ns-slapd tcp 0 0 ::ffff:10.209.47.24:636 ::ffff:10.209.37.146:1773 ESTABLISHED 10756/ns-slapd How can I make it work for only 636 port?

2 1

The installation error on the 389 LDAP
by 馬小布 01 Feb '10

01 Feb '10

Hi ,all : During I install the 389 directory server ,the result is the following : ... .. Are your ready to set up you servers? Creating directory server ... Your new DS instance "xx" was successfully created . Creating the configuration directory server... Could not authenticate as user "uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot" to server "ldap://cds.mobilepeak.com.cn:389/o=NetscapeRoot" . Error: Invaild credentials Could not register the directory server with the configuration directory server Exiting .... Log file is '/tmp/...." Why does it become that ? Could someone give some advices to me ? I installed the "centos directory server " on that server previously, but i have already remove all the file via "yum erase "centos-ds"." Maybe is it associated with that ? Thanks in advance ~

3 6

Re: [389-users] 389-users Digest, Vol 57, Issue 1
by Charles Gilbert 01 Feb '10

01 Feb '10

1. How To add a user to a netgroup You simply need to add an nisnetgrouptriple as the attribute. The synta then for the user is as follows (machinename,username,domain). You do no need a machine name or the domain. My entries as always (,username,) Do not add any extra fluff such as (-,username,-) or it will not work as part of authentication with Red Hat and Solaris netgroups. Hope that helps! Chuck On Mon, Feb 1, 2010 at 7:00 AM, <389-users-request(a)lists.fedoraproject.org>wrote: > Send 389-users mailing list submissions to > 389-users(a)lists.fedoraproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://admin.fedoraproject.org/mailman/listinfo/389-users > or, via email, send a message with subject or body 'help' to > 389-users-request(a)lists.fedoraproject.org > > You can reach the person managing the list at > 389-users-owner(a)lists.fedoraproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of 389-users digest..." > > > Today's Topics: > > 1. How to add user to NetGroup? (Ajeet S Raina) > 2. The installation error on the 389 LDAP (Majian) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 1 Feb 2010 09:25:27 +0530 > From: Ajeet S Raina <ajeetraina(a)gmail.com> > Subject: [389-users] How to add user to NetGroup? > To: "General discussion list for the 389 Directory server project." > <fedora-directory-users(a)redhat.com> > Message-ID: > <6239e2931001311955n74c69e4euac5b07a42e8160d5(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Guys, > > Anyone who can suggest me the command to add a new user to NetGroup? > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.fedoraproject.org/pipermail/389-users/attachments/20100201/750… > > ------------------------------ > > Message: 2 > Date: Mon, 1 Feb 2010 18:52:18 +0800 > From: Majian <jiannma(a)gmail.com> > Subject: [389-users] The installation error on the 389 LDAP > To: 389-users(a)lists.fedoraproject.org > Message-ID: > <eb686fc71002010252l7074078cg6e9a1a8452c7c42f(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi ,all : > > During I install the 389 directory server ,the result is the following : > > > ... > > .. > > Are your ready to set up you servers? > Creating directory server ... > Your new DS instance "xx" was successfully created . > > Creating the configuration directory server... > Could not authenticate as user > "uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot" > to server "ldap://cds.mobilepeak.com.cn:389/o=NetscapeRoot" . Error: > Invaild > credentials > > > Could not register the directory server with the configuration directory > server > Exiting .... > > Log file is '/tmp/...." > > > Why does it become that ? Could someone give some advices to me ? > > I installed the "centos directory server " on that server previously, > but i have already remove all the file via "yum erase "centos-ds"." > > > Maybe is it associated with that ? > > > Thanks in advance ~ > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.fedoraproject.org/pipermail/389-users/attachments/20100201/512… > > ------------------------------ > > -- > 389 users mailing list > 389-users(a)lists.fedoraproject.org > https://admin.fedoraproject.org/mailman/listinfo/389-users > > End of 389-users Digest, Vol 57, Issue 1 > **************************************** >

1 0

Fedora DS dies with segfault
by Tom 01 Feb '10

01 Feb '10

Hi all, we've been running Fedora DS 1.04 for quite some time without issue but just recently, the server process died inexplicably with the following in syslog: localhost kernel: ns-slapd[2945]: segfault at 0000000000000000 rip 0000002a9574d4aa rsp 0000007fbffff250 error 4 Nothing is logged in the FedoraDS error logs. Does anyone have any ideas? Thanks, Tom

2 1

Fedora Management Console simply hangs when trying to create user
by Sean Carolan 01 Feb '10

01 Feb '10

I'm attempting to add a user to a new directory that I set up for testing purposes. I have started fedora-idm-console and logged on successfully as cn=directory manager, but when I hit the "Create" button to add a new user, the cursor simply sits there spinning, and spinning.... Anyone have a suggestion how to fix this?

4 13

How to add user to NetGroup?
by Ajeet S Raina 31 Jan '10

31 Jan '10

Guys, Anyone who can suggest me the command to add a new user to NetGroup?

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users February 2010