Did you actually run the server setup script
(/opt/fedora-ds/setup/setup)? That needs to run before
the admin scripts get created. Could you give us what
ls shows in your DS root (/opt/fedora-ds)?
Get on-the-go sports scores, stock quotes, news and more. Check it out!
I also had this same problem with startconsole except that I was getting
the same problem even when connected to the X console. After installing
xorg-x11-deprecated-libs RPM it works both from the X console aswell as
via X forwarding over ssh.
Interestingly, before this fix I had tried replacing
/opt/fedora-ds/bin/base/jre/bin/java with a symbolic link to the java
binary from jre1.5...I then was able to get the initial splash screen
without any java errors, but it wouldn't show the login prompt
Steve Mahaffey wrote:
>You hit it. Thanks!
>I had jpackage-utils-1.5.38-1jpp_3rh and alsa-lib-1.0.6-8.FC3, but not
>xorg...package. Did a yum install of it, which installed
>xorg-x11-deprecated-libs-6.8.2-1.FC3.13 and now startconsole works.
Thanks for the fix guys. I've updated the bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=159384 with the
appropriate information. Please check it and make sure the info is
correct. Steve, you may want to add yourself to the CC.
>Mike Jackson wrote:
>>It worked after I installed the IBM java RPM. It did not work before
>>that. This is a headless server, with a very minimal list of installed
>>I removed the IBM java RPM now, and it still works.
>>Now I think that I know why it didn't work before. When I installed
>>IBM java RPM, it forced/suggested me to first install these packages:
>>So, I am guessing that at least those three should be dependencies to
>>the fds RPM, or some more stuff should be added into the FDS RPM to
>>satisfy the included java.
>>LDAP Directory Consulting: http://www.netauth.com
>>Fedora-directory-users mailing list
>>Fedora-directory-users redhat com
>Fedora-directory-users mailing list
>Fedora-directory-users redhat com
IMPORTANT: This email (including any attachments) may contain confidential,
private or legally privileged information and may be protected by copyright. You
may only use it if you are the person(s) it was intended to be sent to and if you
use it in an authorised way. No one is allowed to use, review, alter, transmit,
disclose, distribute, print or copy this e-mail without appropriate authority.
If this e-mail was not intended for you and was sent to you by mistake, please
telephone (07 3842 8888) or e-mail me immediately, destroy any hard copies of
this e-mail and delete it and any copies of it from your computer systems. Any
legal privilege and confidentiality attached to this e-mail is not waived or
destroyed by that mistake.
It is your responsibility to ensure that this e-mail does not contain and is not
affected by computer viruses, defects or interference by third parties or
replication problems (including incompatibility with your computer system).
Fedora/Red Hat DS puts its schema files in the same
place as the Netscape and Sun directories, under the
directory server root in
slapd-instancename/config/schema. With the rpm
install, it will be in
defaults to the relative domain name of the host. On
one of my servers, for example, they're in
/opt/fedora-ds/slapd-serv02/config/schema. The files
are loaded in numeric order. The file the system puts
user-defined (through the console) schema objects is
99user.ldif. Just adding your schema objects to this
file or another similarly named (I've got one called
98samba.ldif to support Samba accounts) will cause it
to be read in the next time the service is restarted.
The Netscape family of directory servers are usually
not a strict about enforcing schema rules as OpenLDAP,
but you should compare the file you want to import to
the standard files that are already there (don't ever
modify *those* files) to make sure you've got the
format correct. There are slight differences between
how Netscape and OpenLDAP cast schema objects that
could cause you trouble. The Red Hat Directory
documentation (in particular the Schema Guide) are
really excellent resources on this stuff. As you get
more familiar with the directory product what you find
in the doc begins to make even more sense.
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
I looked through the documentation and console/adm-srv options but
didn't found how to import or configure the use of a external schema
(evolutionperson.schema / = evolution addressbook). openldap uses the
slapd.conf with <include path>. How could this be done with DS ?
Dipl. Inform. H. Burde
EMail: hburde(a)t-online.de ; hburde(a)uni-bremen.de
Wenn Gauß heute lebte, wäre er ein Hacker. /P.Sarnak
I apologize. I should have mentioned in my original
post that we are in fact running Sun One Directory 5.1
SP2, and not 5.2, in our environment.
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
Having gotten the admin console running as described in a previous
thread, I found that I didn't have the admin server daemon running. The
admin manual page currently refers to the one for the Red Hat DS, so I
Those docs say to start the admin server daemon with
"serverRoot/start-admin". The only problem here is that the rpm package
didn't install this. Checking the package with rpm -q:
rpm -q --filesbypkg fedora-ds-7.1-2.RHEL4|grep start-admin
Is it not in the rpm package yet, or has the name been changed or is it
I'm embarking on a project at my company to sync the two together. It's
not important for me that fedora directory updates (passwords, etc) make
it back to the active directory server, so I'd hope that the setup would
be fairly straight forward.
It seems like this would be a common/useful way to use FDS and beyond
setting it up myself I'm interested in writing a HOWTO so that others
can do this easily without indepth knowledge of FDS or LDAP.
I do, however, lack this knowledge myself. Can someone provide a high
level overview of what's needed to make this happen? I can fill in
details myself as I have many years of UNIX, but reading through the
online manual for most of the day it's not obvious to me how much setup
needs to be done beyond the chapter specifically about syncing with
Is anyone aware of any resources or willing to provide some guidance on
how to make this happen?
Thanks, and I promise at least a rough HOWTO out of this effort.
I know that as of now, it is supported on Linux and Solaris, but I'm
wondering what it takes to
deploy it on Windows NT(2000, xp, 2003, ETC).
Since redhat supports cygwin AND originally NDS worked on Windows, it
should NOT be too
difficult. What would be more useful would be a native port of NDS on
Windows (minGNU comes to mind)
what with APR(http://apr.apache.org/) available.
Are there any efforts to
a) come out with a binary for windows
b) help anyone who's already working on a windows port.
c) atleast provide a source level build.
LDAP is seriously needed (and missing) on enterprise infrastructures and
support for Windows(as
Firefox showed) will take a product much further than without windows.
Nathan Kinder Wrote:
Actually, FDS uses, and ships with, the IBM JRE on Linux. Other
platforms, such as Solaris, require the Sun JRE.
After trying Suns 1.4.x and 5 JDK versions, I saw the post above.
I've installed fedora-ds via rpm on FC3 and it's in /opt/fedora-ds. I set some environment variables:
I added /opt/fedora-ds/bin/base/jre/bin/ to my path.
However I get the exact same strings of errors that Mike Jackson posted earlier when executing startconsole.
Any ideas what I've got wrong?
I'm sure this was tried successfully by the development team, but for
all the admins out there: setting up a Fedora Directory on RHEL 3/Intel
as a consumer of an existing Sun One on Solaris/Sparc supplier is
seamless. Took all of 25 minutes after downloading the rpm to get my
30,000+ entry development environment replicated to a test box. I
figured this would not require alot of effort, just didn't anticipate it
would be almost *no* effort. For anyone considering migrating their LDAP
environment to x86 Linux the release of the Red Hat/Fedora Directory
product is going to be a watershed event.
Thanks again to the development team for a job well done. Keep up the
IT Infrastucture Applications Engineering
Arrow Electronics, Inc.