http://directory.fedoraproject.org/wiki/Howto:systemd
1) To setup the system for testing add an entry into your /etc/hosts such as
127.0.0.1 example.com
2) To install 389 add the packages to fedora 16.
3) Run the command sudo setup-ds-admin.pl There is a setup-ds.pl but that I believe sets up separate ldap servers and not config the entire system including the admin.
4) When it asks for a host, it will give something like example.com.locahost Enter example.com
5) Enter the domain.
On mine it asks for dc=com. I entered instead dc=example,dc=com
6) Answer the remaining questions and complete the installation
(If you make a mistake run sudo remove-ds-admin.pl)
7) To connect to 389 as an admin
run 389-console
Enter
User ID: dc=Directory Manager
Passsword: [whatever u entered during the setup process]
Administration
URL: http://localhost/9830
If you have problems use the java from sun instead of openjdk.
(google java sun alternatives linux)
---
Starting and Stop the service.
1) Start the 389 admin service
service dirsrv-admin start
This however starts up the admin portion of 389 and not the ldap server that stores data.
2) Start your 389 ldap service
I usually use service to start and stop my services
sudo service dirsrv@example start
With fedora 16, I'm finding that I'm using systemctl more often
This will also start and stop the dirsrv service
sudo systemctl start dirsrv@example
To start and stop all your ldap services
sudo systemctl start dirsrv.target
3) The ldap server does not start on boot.
Current unsure why service dirsrv start does not work.
-
1 comment:
I found the same startup issue. I found a Red Hat bug, not worked about the systemctl scripts being wrong.
https://bugzilla.redhat.com/show_bug.cgi?id=755754
Skipped service and systemctl, used the 389 scripts: start-dirsrv & start-ds-admin That got both the slapd server and the admin server running.
Post a Comment