389-users July 2005

389-users@lists.fedoraproject.org

47 participants
66 discussions

[Fedora-directory-users] CLI search from localhost kills server without SASL
by Kevin M. Myer 21 Jul '05

21 Jul '05

Hello, I just had a curioius occurrence. I executed a search with ldapsearch from the CLI of the same host that is running FDS. I do not have SASL configured for authentication, but I forgot to include the -x switch to ldapsearch. It prompted me for a password, I hit CTL-C and the entire slapd daemon promptly died. This is all thats logged in the error log (and then my restart of the daemon): [21/Jul/2005:22:53:47 -0400] - sasl(5): DIGEST-MD5 server step 1[21/Jul/2005:22: 53:51 -0400] - sasl(5): DIGEST-MD5 server step 2[21/Jul/2005:22:54:07 -0400] - F edora-Directory/7.1 B2005.146.1918 starting up [21/Jul/2005:22:54:07 -0400] - Detected Disorderly Shutdown last time Directory Server was running, recovering database. [21/Jul/2005:22:54:08 -0400] - slapd started. Listening on All Interfaces port 389 for LDAP requests [21/Jul/2005:22:54:08 -0400] - Listening on All Interfaces port 636 for LDAPS re quests Any thoughts on what might be going on? Kevin -- Kevin M. Myer Senior Systems Administrator Lancaster-Lebanon Intermediate Unit 13 http://www.iu13.org

1 0

RE: [Fedora-directory-users] Samba and FDS 7.1 on Fedora Core 4 Error
by Tay, Gary 21 Jul '05

21 Jul '05

Leon wrote: === if i use "ldapsearch -x -Z '(uid=Administrator)' i get the right entry, i suppose the same entry found with the other command: ____________________ [root@fedorac4 ~]# ldapsearch -x -Z '(uid=Administrator)' ldap_start_tls: Protocol error (2) additional info: unsupported extended operation === I suspect that Leon has TWO versions of LDAP products on his Samba+LDAP server. I guess "ldapsearch" command he shown is from /usr/bin/ldapsearch which is most likely OpenLDAP version. If this is true and Leon is sure that he would prefer FDS bin and lib path to take precedence, he could do these: As root user 1) Add a line to end of /etc/bashrc something like: export PATH=/opt/fedora-ds/shared/bin:$PATH:/opt/IDEALX/sbin 2) Add few lines to beginning of /etc/ld.so.conf, something like: /opt/fedora-ds/lib /opt/fedora-ds/share/lib /opt/fedora-ds/clients/lib include ld.so.conf.d/*.conf /usr/X11R6/lib 3) Run "ldconfig" # ldconfig 4) Check # ldd `which ldapsearch` # ldd `which ldapsearch` libldap50.so => /opt/fedora-ds/clients/lib/libldap50.so (0x00c56000) libssldap50.so => /opt/fedora-ds/clients/lib/libssldap50.so (0x00b48000) libprldap50.so => /opt/fedora-ds/clients/lib/libprldap50.so (0x00b1b000) libssl3.so => /opt/fedora-ds/clients/lib/libssl3.so (0x00354000) libnss3.so => /opt/fedora-ds/clients/lib/libnss3.so (0x00f2c000) libsoftokn3.so => /opt/fedora-ds/clients/lib/libsoftokn3.so (0x00111000) libdl.so.2 => ../lib/libdl.so.2 (0x00625000) libresolv.so.2 => ../lib/libresolv.so.2 (0x0089d000) libpthread.so.0 => ../lib/tls/libpthread.so.0 (0x00733000) libplc4.so => /opt/fedora-ds/clients/lib/libplc4.so (0x0020c000) libplds4.so => /opt/fedora-ds/clients/lib/libplds4.so (0x00177000) libnspr4.so => /opt/fedora-ds/clients/lib/libnspr4.so (0x00998000) libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00cec000) libm.so.6 => ../lib/tls/libm.so.6 (0x0062b000) libgcc_s.so.1 => ../lib/libgcc_s.so.1 (0x00db8000) libc.so.6 => ../lib/tls/libc.so.6 (0x004fa000) /lib/ld-linux.so.2 (0x004e1000) 5) If smbldap tools from IDEALX is used, check that in any bin/lib path in any config files the need to point them to FDS paths. My 2-cent. Rgds Gary -----Original Message----- From: fedora-directory-users-bounces(a)redhat.com [mailto:fedora-directory-users-bounces@redhat.com] On Behalf Of Leonardo Pugliesi Sent: Thursday, July 21, 2005 9:44 PM To: General discussion list for the Fedora Directory server project. Subject: Re: [Fedora-directory-users] Samba and FDS 7.1 on Fedora Core 4 Error Adam Stokes ha scritto: >On Thu, 2005-07-21 at 10:36 +0200, Leonardo Pugliesi wrote: > > >>Adam Stokes ha scritto: >> >> >> >>>>>Leon, >>>>> >>>>>I think since you have an administrator account set already, do >>>>> >>>>>smbpasswd Adminsitrator >>>>> >>>>>the '-a' switch tells samba to add that user without it will just >>>>>change the password and add the appropriate entries to directory >>>>>server >>>>> >>>>>-- >>>>>Fedora-directory-users mailing list >>>>>Fedora-directory-users(a)redhat.com >>>>>https://www.redhat.com/mailman/listinfo/fedora-directory-users >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>if i use "smbpasswd Administrator" i get: >>>>_______________________________ >>>>[root@fedorac4 ~]# smbpasswd Administrator >>>>New SMB password: >>>>Retype new SMB password: >>>>Failed to find entry for user administrator. >>>>Failed to modify password entry for user administrator >>>>[root@fedorac4 ~]# _______________________________ >>>>so it seems that i can't add Administrator because the entry alredy >>>>exists, but i can't modify it because it doesn't exists..... >>>>am i missing something :-) >>>> >>>>thanx >>>> >>>>-- >>>>Fedora-directory-users mailing list >>>>Fedora-directory-users(a)redhat.com >>>>https://www.redhat.com/mailman/listinfo/fedora-directory-users >>>> >>>> >>>> >>>> >>>What does your smb.conf look like? Also is there anything in the >>>samba logs? >>> >>>-- >>>Fedora-directory-users mailing list Fedora-directory-users(a)redhat.com >>>https://www.redhat.com/mailman/listinfo/fedora-directory-users >>> >>> >>> >>> >>> >>This is smb.conf (global section): >> >>[global] >> workgroup = FEDORAC4 >> username map = /etc/samba/smbusers >> enable privileges = yes >> server string = Samba Server %v >> security = user >> encrypt passwords = Yes >> min passwd length = 3 >> obey pam restrictions = No >> ldap passwd sync = Yes >> #unix password sync = Yes >> passwd program = /opt/IDEALX/sbin/smbldap-passwd -u %u >> #passwd chat = "Changing password for*\nNew password*" %n\n "*Retype new password*" %n\n" >> ldap passwd sync = Yes >> log level = 0 >> syslog = 0 >> log file = /var/log/samba/log.%m >> max log size = 100000 >> time server = Yes >> socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 >> mangling method = hash2 >> Dos charset = 850 >> Unix charset = ISO8859-1 >> logon script = logon.bat >> logon drive = H: >> logon home = >> logon path = >> domain logons = Yes >> os level = 65 >> preferred master = Yes >> domain master = Yes >> wins support = Yes >> passdb backend = ldapsam:ldap://fedorac4.localdomain >> #passdb backend = ldap:ldap://fedorac4.localdomain >> # passdb backend = ldapsam:"ldap://127.0.0.1/ ldap://slave.idealx.com" >> ldap filter = (&(objectclass=sambaSamAccount)(uid=%u)) >> ldap admin dn = cn=Directory Manager >> ldap suffix = dc=localdomain >> ldap group suffix = ou=Groups >> ldap user suffix = ou=People >> ldap machine suffix = ou=Computers >> ldap idmap suffix = ou=Users >> #ldap ssl = start tls >> add user script = /opt/IDEALX/sbin/smbldap-useradd -m "%u" >> ldap delete dn = Yes >> #delete user script = /opt/IDEALX/sbin/smbldap-userdel "%u" >> add machine script = /opt/IDEALX/sbin/smbldap-useradd -w "%u" >> add group script = /opt/IDEALX/sbin/smbldap-groupadd -p "%g" >> #delete group script = /opt/IDEALX/sbin/smbldap-groupdel "%g" >> add user to group script = /opt/IDEALX/sbin/smbldap-groupmod -m "%u" "%g" >> delete user from group script = /opt/IDEALX/sbin/smbldap-groupmod -x "%u" "%g" >> set primary group script = /opt/IDEALX/sbin/smbldap-usermod -g >>"%g" "%u" >> >> >>samba logs is empty >>Leon >> >> >> >> >>-- >>Fedora-directory-users mailing list Fedora-directory-users(a)redhat.com >>https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> > >Not sure at this point, looks like you are using idealx scripts for >some of the administration maybe they created the admin account? > >-- >Fedora-directory-users mailing list Fedora-directory-users(a)redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > the entry "Administrator.... " has been created with the ldif2ldap method, as shown in the how-to. the problem, in my opinion, is that if i use "smbldap-usershow Administrator" i get the right entry: _____________________________ [root@fedorac4 ~]# /opt/IDEALX/sbin/smbldap-usershow Administrator dn: uid=Administrator,ou=People,dc=localdomain uid: Administrator cn: Samba Admin givenName: Samba sn: Admin mail: Administrator@localdomain objectClass: person,organizationalPerson,inetOrgPerson,posixAccount,top loginShell: /bin/bash uidNumber: 0 gidNumber: 0 homeDirectory: /root gecos: Samba Admin userPassword: {SSHA}2b/re4djmAJmmNCWnJmKcJLGlCRqdGdU _____________________________ if i use "ldapsearch -x -Z '(uid=Administrator)' i get the right entry, i suppose the same entry found with the other command: ____________________ [root@fedorac4 ~]# ldapsearch -x -Z '(uid=Administrator)' ldap_start_tls: Protocol error (2) additional info: unsupported extended operation # extended LDIF # # LDAPv3 # base <> with scope sub # filter: (uid=Administrator) # requesting: ALL # # Administrator, People, localdomain dn: uid=Administrator,ou=People,dc=localdomain uid: Administrator cn: Samba Admin givenName: Samba sn: Admin mail: Administrator@localdomain objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson objectClass: posixAccount objectClass: top loginShell: /bin/bash uidNumber: 0 gidNumber: 0 homeDirectory: /root gecos: Samba Admin # search result search: 3 result: 0 Success # numResponses: 2 # numEntries: 1 [root@fedorac4 ~]# _________________________________________- i suppose the two command give me the same entry because sghould be querying the same database...... if i use pdbedit -u Administrator i get _________________ [root@fedorac4 ~]# pdbedit -u Administrator Username not found! [root@fedorac4 ~]# _________________ so if only samba related commands seem not to work properly perhaps the problem is in samba configuration, but in the guides downloaded from the website i didn't found how to configure the part of the file for what concern the scripts of entries managemant such as adding users, machine, etc...... what should i do now? bye leon -- Fedora-directory-users mailing list Fedora-directory-users(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users

1 0

[Fedora-directory-users] Adding Admin Startup and Console Start to init.d
by jimjano＠ptd.net 21 Jul '05

21 Jul '05

Hello all, I am running RHEL4 and installed Fedora Directory Server. Running great! How would I go about adding the admin and console startup to init.d so I don't have to start them manually? Thanks! Jim

3 3

RE: [Fedora-directory-users] Centos 4.1 - FDS Problems
by Tay, Gary 21 Jul '05

21 Jul '05

I also think the FDS should be re-installed, using default settings. If Centos 4.1 is based on SELINUX based kernel, some adjustments may be needed (this is at leaset my case). # cat /etc/sysconfig/selinux SELINUX=disabled SELINUXTYPE=targeted One FireWall rule for port 389 (ldap), another for admin port. Assuming admin port is 38900 # vi /etc/sysconfig/iptables Add two lines to the INPUT section: -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 389 -j ACCEPT -A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 38900 -j ACCEPT Gary -----Original Message----- From: fedora-directory-users-bounces(a)redhat.com on behalf of Rob Crittenden Sent: Thu 7/21/2005 10:29 PM To: General discussion list for the Fedora Directory server project. Cc: Subject: Re: [Fedora-directory-users] Centos 4.1 - FDS Problems He is also trying to start FDS on port 389 as a non-root user. That simply won't work. It may be better to wipe this installation and start over from scratch (rather than having unknown and perhaps wide open permissions). If you don't want to have to be root when starting this choose all ports > 1024 on the next install. To bind to port 389 you must be root when the server starts (but the server doesn't have to run as root). As for admin server, it isn't suddenly exiting when you connect to it. It simply isn't starting up. We've traced this in the past to an interaction with the IBM JDK and SMP kernels. Try a uni-processor kernel as a test to see if this helps things. rob Rich Megginson wrote: > Those permissions problems are troubling. I know the console is having > problems writing to something. Check your $HOME/.mcc directory. The > console needs to be able to create and write to files in that directory. > > As for the admin server, I'm not sure. But lets see if we can remove > those console errors first. > > Vik P wrote: > >> Apologies for continually pestering you but I am really tearing my >> hair out trying to get this to work. I ran startconsole in debug mode >> and got the following dump: >> >> [user@node fedora-ds]$ ./startconsole -D >> /opt/fedora-ds/bin/base/jre/bin/java -ms8m -mx64m -cp >> .:./mcc70_en.jar:./nmclf70.jar:./mcc70.jar:./ldapjdk.jar:./base.jar:./jss3.jar:./nmclf70_en.jar >> -Djava.library.path=/opt/fedora-ds/lib/jss >> -Djava.util.prefs.systemRoot=/opt/fedora-ds/java/.java >> -Djava.util.prefs.userRoot=/opt/fedora-ds/java >> com.netscape.management.client.console.Console -D -A >> http://node.internal-datacom.com:40795 >> Fedora-Management-Console/7.0 B2005.132.2143 >> 21-Jul-2005 11:41:34 java.util.prefs.FileSystemPreferences$2 run >> WARNING: java.io.IOException: Permission denied >> CommManager> New CommRecord >> (http://node.internal-datacom.com:40795/admin-serv/authenticate) >> http://node.internal-datacom.com:40795/[0:0] open> Ready >> http://node.internal-datacom.com:40795/[0:0] accept> >> http://node.internal-datacom.com:40795/admin-serv/authenticate >> http://node.internal-datacom.com:40795/[0:0] send> GET \ >> http://node.internal-datacom.com:40795/[0:0] send> >> /admin-serv/authenticate \ >> http://node.internal-datacom.com:40795/[0:0] send> HTTP/1.0 >> http://node.internal-datacom.com:40795/[0:0] send> Host: >> node.internal-datacom.com:40795 >> http://node.internal-datacom.com:40795/[0:0] send> Connection: Keep-Alive >> http://node.internal-datacom.com:40795/[0:0] send> User-Agent: >> Fedora-Management-Console/7.0 >> http://node.internal-datacom.com:40795/[0:0] send> Accept-Language: en >> http://node.internal-datacom.com:40795/[0:0] send> Authorization: >> Basic \ >> http://node.internal-datacom.com:40795/[0:0] send> YWRtaW46cGFzc3dvcmQ= \ >> http://node.internal-datacom.com:40795/[0:0] send> >> http://node.internal-datacom.com:40795/[0:0] send> >> http://node.internal-datacom.com:40795/[0:0] error> >> java.net.SocketException: Connection reset >> CommManager> Retry CommRecord >> (http://node.internal-datacom.com:40795/admin-serv/authenticate) >> http://node.internal-datacom.com:40795/[0:0] error> >> java.net.ConnectException: Connection refused >> http://node.internal-datacom.com:40795/[0:0] accept> >> http://node.internal-datacom.com:40795/admin-serv/authenticate >> http://node.internal-datacom.com:40795/[0:0] error> >> java.net.SocketException: Connection reset >> CommManager> Retry CommRecord >> (http://node.internal-datacom.com:40795/admin-serv/authenticate) >> http://node.internal-datacom.com:40795/[0:0] error> >> java.net.ConnectException: Connection refused >> http://node.internal-datacom.com:40795/[0:0] close> Closed >> java.lang.SecurityException: Could not lock User prefs. Lock file >> access denied. at >> java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:937) >> >> at >> java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) >> >> at >> java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732) >> >> at >> java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) >> >> at >> java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:469) >> >> at >> java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) >> >> at >> java.util.prefs.FileSystemPreferences$4.run(FileSystemPreferences.java:437) >> >> at java.util.TimerThread.mainLoop(Timer.java:447) >> at java.util.TimerThread.run(Timer.java:397) >> java.lang.SecurityException: Could not lock User prefs. Lock file >> access denied. at >> java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:937) >> >> at >> java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) >> >> at >> java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732) >> >> at >> java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) >> >> at >> java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:469) >> >> at >> java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) >> >> at >> java.util.prefs.FileSystemPreferences$6.run(FileSystemPreferences.java:447) >> >> >> As you can see, the fun starts when the connection is reset, and this >> happens the same time start-admin randomly stops running. So I think >> the problem is with that element of the FDS. If it can run fine, then >> suddenly stop, without any error codes in any of the logs, etc, then >> it can only mean that there's a setting somewhere for the timeout, >> making adminserver just stop. Trouble is finding it... >> >> >> ---------------------------------------------------------------------------------------------------------- >> >> >>> From: Rich Megginson <rmeggins(a)redhat.com> >>> Reply-To: "General discussion list for the Fedora Directory server >>> project." <fedora-directory-users(a)redhat.com> >>> To: "General discussion list for the Fedora Directory server >>> project." <fedora-directory-users(a)redhat.com> >>> Subject: Re: [Fedora-directory-users] Centos 4.1 - FDS Problems >>> Date: Wed, 20 Jul 2005 09:32:22 -0600 >>> >>> Try startconsole -D for debug mode. Some preferences are written to >>> a file in $HOME/.mcc - I can't remember the name. >>> >>> Vik P wrote: >>> >>>> I've chowned the lock and server folder to the ldap user, and even >>>> tried as nobody and I still got the same warning. After changing >>>> several other permissions ./start-admin still doesn't remain running >>>> but when I run startconsole, while continually running start-admin >>>> (as su) I eventually got the following error dump: >>>> >>>> [user@node fedora-ds]$ ./startconsole >>>> 20-Jul-2005 12:40:39 java.util.prefs.FileSystemPreferences$2 run >>>> WARNING: java.io.IOException: Permission denied >>>> java.lang.SecurityException: Could not lock User prefs. Lock file >>>> access denied. at >>>> java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:937) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:469) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences$4.run(FileSystemPreferences.java:437) >>>> >>>> >>>> at java.util.TimerThread.mainLoop(Timer.java:447) >>>> at java.util.TimerThread.run(Timer.java:397) >>>> java.lang.SecurityException: Could not lock User prefs. Lock file >>>> access denied. at >>>> java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:937) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:469) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) >>>> >>>> >>>> at >>>> java.util.prefs.FileSystemPreferences$6.run(FileSystemPreferences.java:447) >>>> >>>> >>>> >>>> Trying to run start-admin as non-root doesn't do anything at all, >>>> checking the log files reveals that they weren't even written to >>>> meaning the admin server didn't even attempt to start. I've checked >>>> all the permissions and I can't see any problems. >>>> >>>> Any help would be appreciated. >>>> >>>> >>>> ------------------------------------------------------------------------------------------------------ >>>> >>>> >>>> >>>>> From: Rich Megginson <rmeggins(a)redhat.com> >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------------------------------ >>>> >>>> >>>> >>>>> Reply-To: "General discussion list for the Fedora Directory server >>>>> project." <fedora-directory-users(a)redhat.com> >>>>> To: "General discussion list for the Fedora Directory server >>>>> project." <fedora-directory-users(a)redhat.com> >>>>> Subject: Re: [Fedora-directory-users] Centos 4.1 - FDS Problems >>>>> Date: Tue, 19 Jul 2005 07:49:53 -0600 >>>>> >>>>> Vik Lionheart wrote: >>>>> >>>>>> Yes I have x11 installed, it is required for nomachine to run >>>>>> correctly, which has been installed correctly. >>>>>> >>>>>> I tried running start-slapd as a non-root and, after fixing >>>>>> several permission errors I got the following message: >>>>>> >>>>>> [user@node slapd-node]$ ./start-slapd >>>>>> Server failed to start !!! Please check errors log for problems >>>>>> >>>>>> Viewing the error log revealed the following: >>>>>> >>>>>> [19/Jul/2005:11:56:12 +0100] - Warning - couldn't set the >>>>>> ownership for /opt/fedora-ds/slapd-node/locks/server/4346 >>>>> >>>>> >>>>> >>>>> >>>>> Make sure you chown locks and locks/server to the uid of the slapd >>>>> process (e.g. ldap). Make sure those directories are writable by >>>>> the uid of the slapd process. >>>>> >>>>>> [19/Jul/2005:11:56:12 +0100] - Fedora-Directory/7.1 B2005.146.2010 >>>>>> starting up >>>>>> [19/Jul/2005:11:56:12 +0100] createprlistensocket - PR_Bind() on >>>>>> All Interfaces port 389 failed: Netscape Portable Runtime error >>>>>> -5966 (Access Denied.) >>>>>> >>>>>> This may be the reason why admin server kept randomly stopping. >>>>>> I've made sure that no other services are trying to run on port >>>>>> 389 but I still have this error. >>>>>> >>>>>> >>>>>> >>>> >>>> _________________________________________________________________ >>>> Use MSN Messenger to send music and pics to your friends >>>> http://messenger.msn.co.uk >>>> >>>> -- >>>> Fedora-directory-users mailing list >>>> Fedora-directory-users(a)redhat.com >>>> https://www.redhat.com/mailman/listinfo/fedora-directory-users >>> >>> >>> >>> << smime.p7s >> >>> -- >>> Fedora-directory-users mailing list >>> Fedora-directory-users(a)redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> >> >> _________________________________________________________________ >> Winks & nudges are here - download MSN Messenger 7.0 today! >> http://messenger.msn.co.uk >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users(a)redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users

1 0

Re: [Fedora-directory-users] Centos 4.1 - FDS Problems
by Vik P 21 Jul '05

21 Jul '05

I've chowned the lock and server folder to the ldap user, and even tried as nobody and I still got the same warning. After changing several other permissions ./start-admin still doesn't remain running but when I run startconsole, while continually running start-admin (as su) I eventually got the following error dump: [user@node fedora-ds]$ ./startconsole 20-Jul-2005 12:40:39 java.util.prefs.FileSystemPreferences$2 run WARNING: java.io.IOException: Permission denied java.lang.SecurityException: Could not lock User prefs. Lock file access denied. at java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:937) at java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) at java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732) at java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) at java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:469) at java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) at java.util.prefs.FileSystemPreferences$4.run(FileSystemPreferences.java:437) at java.util.TimerThread.mainLoop(Timer.java:447) at java.util.TimerThread.run(Timer.java:397) java.lang.SecurityException: Could not lock User prefs. Lock file access denied. at java.util.prefs.FileSystemPreferences.checkLockFile0ErrorCode(FileSystemPreferences.java:937) at java.util.prefs.FileSystemPreferences.lockFile(FileSystemPreferences.java:926) at java.util.prefs.FileSystemPreferences.sync(FileSystemPreferences.java:732) at java.util.prefs.FileSystemPreferences.flush(FileSystemPreferences.java:825) at java.util.prefs.FileSystemPreferences.syncWorld(FileSystemPreferences.java:469) at java.util.prefs.FileSystemPreferences.access$1200(FileSystemPreferences.java:51) at java.util.prefs.FileSystemPreferences$6.run(FileSystemPreferences.java:447) Trying to run start-admin as non-root doesn't do anything at all, checking the log files reveals that they weren't even written to meaning the admin server didn't even attempt to start. I've checked all the permissions and I can't see any problems. Any help would be appreciated. ------------------------------------------------------------------------------------------------------ >From: Rich Megginson <rmeggins(a)redhat.com> ------------------------------------------------------------------------------------------------------ >Reply-To: "General discussion list for the Fedora Directory server >project." <fedora-directory-users(a)redhat.com> >To: "General discussion list for the Fedora Directory server project." ><fedora-directory-users(a)redhat.com> >Subject: Re: [Fedora-directory-users] Centos 4.1 - FDS Problems >Date: Tue, 19 Jul 2005 07:49:53 -0600 > >Vik Lionheart wrote: > >>Yes I have x11 installed, it is required for nomachine to run correctly, >>which has been installed correctly. >> >>I tried running start-slapd as a non-root and, after fixing several >>permission errors I got the following message: >> >>[user@node slapd-node]$ ./start-slapd >>Server failed to start !!! Please check errors log for problems >> >>Viewing the error log revealed the following: >> >>[19/Jul/2005:11:56:12 +0100] - Warning - couldn't set the ownership for >>/opt/fedora-ds/slapd-node/locks/server/4346 > >Make sure you chown locks and locks/server to the uid of the slapd process >(e.g. ldap). Make sure those directories are writable by the uid of the >slapd process. > >>[19/Jul/2005:11:56:12 +0100] - Fedora-Directory/7.1 B2005.146.2010 >>starting up >>[19/Jul/2005:11:56:12 +0100] createprlistensocket - PR_Bind() on All >>Interfaces port 389 failed: Netscape Portable Runtime error -5966 (Access >>Denied.) >> >>This may be the reason why admin server kept randomly stopping. I've made >>sure that no other services are trying to run on port 389 but I still have >>this error. >> >> >> _________________________________________________________________ Use MSN Messenger to send music and pics to your friends http://messenger.msn.co.uk

3 4

[Fedora-directory-users] FDS + open source Certificate Management Server
by Chivas G. Sicam 21 Jul '05

21 Jul '05

Hello, I'm looking for an open source certificate management server that I can integrate with FDS. Any ideas? Thanks. -- chivas

1 0

[Fedora-directory-users] Fedora Directory Server on other linux distributions?
by Kevin Kovach 20 Jul '05

20 Jul '05

Hello. I'd like to run Fedora Directory Server on a Slackware installation. I've made an attempt at installing using the ds-build utility but have not had any luck. I also tried using the latest RHEL4 binary rpm and ran into issues that looked to be related to Sleepy Cat. I was wondering if somebody can advise on the best way to go about putting the directory server on a different distribution of linux? Some site where I can find some docs or instructions? Thanks. - Kevin

4 3

[Fedora-directory-users] schema extension via ldif at install time
by Brian K. Jones 19 Jul '05

19 Jul '05

Hi all, I want to perform a custom installation of FDS, and when it asks for the ldif file to be imported, I want to point it at a file that contains ldif to extend the schema, and add the entries dumped from my old openldap directory. Without extending the schema, the import will fail because every entry violates the default schema. However, turning schema checking off leaves some small chance that there is something in my directory that shouldn't be there or isn't as it should be. I have another installation of FDS on a test machine, and I used the GUI to add my extra objects and attributes, and I tried copying the resulting ldif to the server I'm now trying to install (minus operational stuff), but the install ignored the cn=schema part of my LDIF file (the part holding the schema extensions), and subsequently, all of the entries failed. Has anyone done this? Any clues? Is there somewhere I can place a 99user.ldif file *before* running setup that will cause the slapd instance to use it the first time it starts up? Thanks, brian.

8 15

[Fedora-directory-users] pam_groupdn and dynamic groups in FDS 7.1.
by Alastair Neil 19 Jul '05

19 Jul '05

Hi have been trying to use the pam_groupdn to restrict access to certain machines, this works fine with a single static group in FDS. I would like to restrict access to members from two groups e.g Admin and CS. I have not found any documentation to show me how to restrict access to members from more than one group using this method. So I thought a Dynamic group would be the ticket, however this doen not seem to work. The clients do not see any members of the group inspite of the fact that when I test the group in the wizard I see the expected list of users. Does anyone have any idea what could be wrong? Is there a better way to solve this problem? I have a hard time believing it is not a common scenario. rgds Alastair

1 0

Re: [Fedora-directory-users] Centos 4.1 - FDS Problems
by Vik P 19 Jul '05

19 Jul '05

Yes I have x11 installed, it is required for nomachine to run correctly, which has been installed correctly. I tried running start-slapd as a non-root and, after fixing several permission errors I got the following message: [user@node slapd-node]$ ./start-slapd Server failed to start !!! Please check errors log for problems Viewing the error log revealed the following: [19/Jul/2005:11:56:12 +0100] - Warning - couldn't set the ownership for /opt/fedora-ds/slapd-node/locks/server/4346 [19/Jul/2005:11:56:12 +0100] - Fedora-Directory/7.1 B2005.146.2010 starting up [19/Jul/2005:11:56:12 +0100] createprlistensocket - PR_Bind() on All Interfaces port 389 failed: Netscape Portable Runtime error -5966 (Access Denied.) This may be the reason why admin server kept randomly stopping. I've made sure that no other services are trying to run on port 389 but I still have this error. ----------------------------------------------------------------------------------------------------------- >From: "Adam M. Dobrin" <adam(a)emplifyhr.com> >Reply-To: "General discussion list for the Fedora Directory server >project." <fedora-directory-users(a)redhat.com> >To: "General discussion list for the Fedora Directory server project." ><fedora-directory-users(a)redhat.com> >Subject: Re: [Fedora-directory-users] Centos 4.1 - FDS Problems >Date: Mon, 18 Jul 2005 21:27:08 -0400 > >it looks like you are having some issues here, with yourself. > >the admin server doesn't run on port 389, the LDAP server does. It looks >like you aren't starting the LDAP server. > >your admin server is listening on port 40795. > >do you have X11 installed? > >Squall Lionheart wrote: > >>I'm currently using the Sun JDK, and it appears to have been configured >>correctly. I've trawled through the logs and there is nothing that even >>remotely looks like an error message. The admin server logs show that the >>adminserver started up sucessfully. Maybe I'm missing something?? >> >> >> >>----------------------------------------------------------------------------------------------------- >> >> >>>From: "Squall Lionheart" <neuromancer101(a)hotmail.co.uk> >>>Reply-To: "General discussion list for the Fedora Directory server >>>project." <fedora-directory-users(a)redhat.com> >>>To: fedora-directory-users(a)redhat.com >>>Subject: [Fedora-directory-users] Centos 4.1 - FDS Problems >>>Date: Mon, 18 Jul 2005 11:50:48 +0100 >>> >>>I can't seem to get fds to work. I have CentOS 4.1 installed and working >>>fine. FDS appears to have installed fine as well. When I run the admin >>>server as a non-root user no messages appear, and when I try and telnet >>>to port 389 it says connection is refused, meaning the admin server isn't >>>running at all. When I try startconsole I get the following as a non-root >>>user: >>> >>>Console: Can't connect to X11 window server using ':0.0' as the value of >>>the DISPLAY variable. >>> >>>When I run start-admin as root I get the following message: >>> >>>warning: daemon is running as super-user >>>[LS ls1] http://node.internal-datacom.com, port 40795 ready to accept >>>requests >>> >>>But this doesn't stay. It appears that the admin server doesn't remain >>>running, maybe 5-10 seconds. Is there any way to fix this timeout problem >>>so that admin server remains running? >> >> >>_________________________________________________________________ >>Be the first to hear what's new at MSN - sign up to our free newsletters! >>http://www.msn.co.uk/newsletters >> >>-- >>Fedora-directory-users mailing list >>Fedora-directory-users(a)redhat.com >>https://www.redhat.com/mailman/listinfo/fedora-directory-users >> > >-- >Fedora-directory-users mailing list >Fedora-directory-users(a)redhat.com >https://www.redhat.com/mailman/listinfo/fedora-directory-users _________________________________________________________________ Want to block unwanted pop-ups? Download the free MSN Toolbar now! http://toolbar.msn.co.uk/

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users July 2005