Hi all,
Thank you for the FDS software!
This morning I installed the Fedora Directory Server (FDS) on Ubuntu Dapper Drake (6.06 LTS). This procedure seems to work for me in order to get FDS running on the Dapper platform:
The procedure is almost equal to the existing howto for Ubuntu Breezy Badger and Debian GNU/Linux Sarge which is available at http://directory.fedora.redhat.com/wiki/Howto:DebianUbuntu I'll just describe the parts that deviate.
I installed the FDS on a clean minimal installation of Ubuntu Dapper Drake server-version (x86), which is available at http://www.ubuntu.com/download
As Dapper uses libc6 version 2.3.6 I took the Fedora Core 4-rpm (version 1.0.2) as a base for conversion to '.deb'. You can download the rpm at http://directory.fedora.redhat.com/wiki/Download
The necessary termcap-compat package does not seem to be available for 'Dapper', so I just used the 'Breezy' version of that package. termcap-compat depends on the 'libc5' and 'ldso' packages which aren't available for 'Dapper' eighter. You can get the Breezy-version of these packages at http://packages.ubuntu.com/
BTW, I used the Sun jdk 1.5.0_02.
After the installation of the fedora-ds .deb-package I used the setuputil and an existing 'install.inf' file (see example hereunder) to do a silent install of the FDS.
You can invoke the silent install like so: sudo /opt/fedora-ds/setup/setup -s -f /opt/install.inf
Example install.inf:
[General] FullMachineName= xenfds.intra.example.com SuiteSpotUserID= fds SuiteSpotGroup= fds ServerRoot= /opt/fedora-ds AdminDomain= intra.example.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= yourpasswordhere ConfigDirectoryLdapURL= ldap://xenfds.intra.example.com:389/o=NetscapeRoot UserDirectoryAdminID= admin UserDirectoryAdminPwd= yourpasswordhere UserDirectoryLdapURL= ldap://xenfds.intra.example.com:389/dc=intra,dc=example,dc=com
[slapd] SlapdConfigForMC= Yes SecurityOn= No UseExistingMC= No UseExistingUG= No ServerPort= 389 ServerIdentifier= xenfds Suffix= dc=intra, dc=example, dc=com RootDN= cn=Directory Manager AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= hannibal
[admin] SysUser= root Port= 7777 ServerIpAddress= ServerAdminID= admin ServerAdminPwd= yourpasswordhere ApacheDir= /usr/sbin ApacheRoot= /usr/lib/apache2
HTH, Olivier Brugman
Olivier Brugman wrote:
Hi all,
Thank you for the FDS software!
This morning I installed the Fedora Directory Server (FDS) on Ubuntu Dapper Drake (6.06 LTS). This procedure seems to work for me in order to get FDS running on the Dapper platform:
The procedure is almost equal to the existing howto for Ubuntu Breezy Badger and Debian GNU/Linux Sarge which is available at http://directory.fedora.redhat.com/wiki/Howto:DebianUbuntu I'll just describe the parts that deviate.
I installed the FDS on a clean minimal installation of Ubuntu Dapper Drake server-version (x86), which is available at http://www.ubuntu.com/download
As Dapper uses libc6 version 2.3.6 I took the Fedora Core 4-rpm (version 1.0.2) as a base for conversion to '.deb'. You can download the rpm at http://directory.fedora.redhat.com/wiki/Download
The necessary termcap-compat package does not seem to be available for 'Dapper', so I just used the 'Breezy' version of that package. termcap-compat depends on the 'libc5' and 'ldso' packages which aren't available for 'Dapper' eighter. You can get the Breezy-version of these packages at http://packages.ubuntu.com/
BTW, I used the Sun jdk 1.5.0_02.
After the installation of the fedora-ds .deb-package I used the setuputil and an existing 'install.inf' file (see example hereunder) to do a silent install of the FDS.
You can invoke the silent install like so: sudo /opt/fedora-ds/setup/setup -s -f /opt/install.inf
Example install.inf:
[General] FullMachineName= xenfds.intra.example.com SuiteSpotUserID= fds SuiteSpotGroup= fds ServerRoot= /opt/fedora-ds AdminDomain= intra.example.com ConfigDirectoryAdminID= admin ConfigDirectoryAdminPwd= yourpasswordhere ConfigDirectoryLdapURL= ldap://xenfds.intra.example.com:389/o=NetscapeRoot UserDirectoryAdminID= admin UserDirectoryAdminPwd= yourpasswordhere UserDirectoryLdapURL= ldap://xenfds.intra.example.com:389/dc=intra,dc=example,dc=com
[slapd] SlapdConfigForMC= Yes SecurityOn= No UseExistingMC= No UseExistingUG= No ServerPort= 389 ServerIdentifier= xenfds Suffix= dc=intra, dc=example, dc=com RootDN= cn=Directory Manager AddSampleEntries= No InstallLdifFile= suggest AddOrgEntries= Yes DisableSchemaChecking= No RootDNPwd= hannibal
[admin] SysUser= root Port= 7777 ServerIpAddress= ServerAdminID= admin ServerAdminPwd= yourpasswordhere ApacheDir= /usr/sbin ApacheRoot= /usr/lib/apache2
HTH, Olivier Brugman
Wow! Thanks for the awesome success report. I'm going to add this to the wiki but I have a question: Is there a reason you used a silent install to set things? Did running it interactively not work? I just want to get the page right.
cheers
rob
Rob Crittenden schreef:
but I have a question: Is there a reason you used a silent install to set things? Did running it interactively not work? I just want to get the page right.
Just haven't tried running it interactively on Ubuntu Dapper (yet). I already had the install.inf available. Furthermore I want to wanted to test the silent installation procedure as that's very convenient for server software distribution.
Regards, Olivier
Rob Crittenden schreef:
but I have a question: Is there a reason you used a silent install to set things? Did running it interactively not work? I just want to get the page right.
Running it interactively (on Debian and Ubuntu) and then choosing the '2 - Typical' install mode) one comes to the point the installer tries to locate the Apache modules, then it returns:
Unable to locate Apache modules in /modules . Press any key to continue.
In fact, the Apache modules are here on the system:
root@helix:/opt/fedora-ds/setup# ls -lsa /usr/lib/apache2/ total 28 4 drwxr-xr-x 3 root root 4096 2006-06-15 11:05 . 8 drwxr-xr-x 38 root root 8192 2006-06-15 12:02 .. 4 drwxr-xr-x 2 root root 4096 2006-06-15 11:05 modules
However if one adds 'ApacheRoot= /usr/lib/apache2' to the [admin] section of an install.inf and one runs a silent install afterwards, there seems to be no problem.
Regards, Olivier
PS Tnx. for the modifications on the Wiki. You might want to remove the double lines regarding the termcap-compat, libc5 and ldso packages on the WiKi and instead add that on Ubuntu Dapper you have to install these packages yourself (sudo dpkg -i namepackage.deb).
Olivier Brugman wrote:
Rob Crittenden schreef:
but I have a question: Is there a reason you used a silent install to set things? Did running it interactively not work? I just want to get the page right.
Running it interactively (on Debian and Ubuntu) and then choosing the '2
- Typical' install mode) one comes to the point the installer tries to
locate the Apache modules, then it returns:
Unable to locate Apache modules in /modules . Press any key to continue.
In fact, the Apache modules are here on the system:
root@helix:/opt/fedora-ds/setup# ls -lsa /usr/lib/apache2/ total 28 4 drwxr-xr-x 3 root root 4096 2006-06-15 11:05 . 8 drwxr-xr-x 38 root root 8192 2006-06-15 12:02 .. 4 drwxr-xr-x 2 root root 4096 2006-06-15 11:05 modules
However if one adds 'ApacheRoot= /usr/lib/apache2' to the [admin] section of an install.inf and one runs a silent install afterwards, there seems to be no problem.
Ok, I see. The way the installer works is it runs the copy of Apache you provide with the -V option which gives a lot of the compiled-in options. It uses HTTPD_ROOT to determine the location of the modules directory. I guess this isn't the same on Ubuntu.
Can you file a bug on this against the Fedora Directory Server at https://bugzilla.redhat.com/ and paste in the output of HTTPD -V?
Or send me the output and I'll get it filed.
Regards, Olivier
PS Tnx. for the modifications on the Wiki. You might want to remove the double lines regarding the termcap-compat, libc5 and ldso packages on the WiKi and instead add that on Ubuntu Dapper you have to install these packages yourself (sudo dpkg -i namepackage.deb).
Sure. I had meant to remove the duplication but forgot. It's gone now.
cheers
rob
-- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
Rob Crittenden schreef:
Olivier Brugman wrote:
Rob Crittenden schreef:
but I have a question: Is there a reason you used a silent install to set things? Did running it interactively not work? I just want to get the page right.
Running it interactively (on Debian and Ubuntu) and then choosing the '2 - Typical' install mode) one comes to the point the installer tries to locate the Apache modules, then it returns:
Unable to locate Apache modules in /modules . Press any key to continue.
In fact, the Apache modules are here on the system:
root@helix:/opt/fedora-ds/setup# ls -lsa /usr/lib/apache2/ total 28 4 drwxr-xr-x 3 root root 4096 2006-06-15 11:05 . 8 drwxr-xr-x 38 root root 8192 2006-06-15 12:02 .. 4 drwxr-xr-x 2 root root 4096 2006-06-15 11:05 modules
However if one adds 'ApacheRoot= /usr/lib/apache2' to the [admin] section of an install.inf and one runs a silent install afterwards, there seems to be no problem.
Ok, I see. The way the installer works is it runs the copy of Apache you provide with the -V option which gives a lot of the compiled-in options. It uses HTTPD_ROOT to determine the location of the modules directory. I guess this isn't the same on Ubuntu.
Can you file a bug on this against the Fedora Directory Server at https://bugzilla.redhat.com/ and paste in the output of HTTPD -V?
Or send me the output and I'll get it filed.
Ok, the output on Dapper is:
root@helix:/opt/fedora-ds# httpd -V Server version: Apache/2.0.55 Server built: May 29 2006 01:44:04 Server's Module Magic Number: 20020903:11 Architecture: 32-bit Server compiled with.... -D APACHE_MPM_DIR="server/mpm/worker" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D HTTPD_ROOT="" -D SUEXEC_BIN="/usr/lib/apache2/suexec2" -D DEFAULT_PIDLOG="/var/run/apache2.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types" -D SERVER_CONFIG_FILE="/etc/apache2/apache2.conf"
Regards, Olivier
I filed bug to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=195669 track this.
regards
rob
Olivier Brugman wrote:
Rob Crittenden schreef:
Olivier Brugman wrote:
Rob Crittenden schreef:
but I have a question: Is there a reason you used a silent install to set things? Did running it interactively not work? I just want to get the page right.
Running it interactively (on Debian and Ubuntu) and then choosing the '2 - Typical' install mode) one comes to the point the installer tries to locate the Apache modules, then it returns:
Unable to locate Apache modules in /modules . Press any key to continue.
In fact, the Apache modules are here on the system:
root@helix:/opt/fedora-ds/setup# ls -lsa /usr/lib/apache2/ total 28 4 drwxr-xr-x 3 root root 4096 2006-06-15 11:05 . 8 drwxr-xr-x 38 root root 8192 2006-06-15 12:02 .. 4 drwxr-xr-x 2 root root 4096 2006-06-15 11:05 modules
However if one adds 'ApacheRoot= /usr/lib/apache2' to the [admin] section of an install.inf and one runs a silent install afterwards, there seems to be no problem.
Ok, I see. The way the installer works is it runs the copy of Apache you provide with the -V option which gives a lot of the compiled-in options. It uses HTTPD_ROOT to determine the location of the modules directory. I guess this isn't the same on Ubuntu.
Can you file a bug on this against the Fedora Directory Server at https://bugzilla.redhat.com/ and paste in the output of HTTPD -V?
Or send me the output and I'll get it filed.
Ok, the output on Dapper is:
root@helix:/opt/fedora-ds# httpd -V Server version: Apache/2.0.55 Server built: May 29 2006 01:44:04 Server's Module Magic Number: 20020903:11 Architecture: 32-bit Server compiled with.... -D APACHE_MPM_DIR="server/mpm/worker" -D APR_HAS_SENDFILE -D APR_HAS_MMAP -D APR_HAVE_IPV6 (IPv4-mapped addresses enabled) -D APR_USE_SYSVSEM_SERIALIZE -D APR_USE_PTHREAD_SERIALIZE -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D APR_HAS_OTHER_CHILD -D AP_HAVE_RELIABLE_PIPED_LOGS -D HTTPD_ROOT="" -D SUEXEC_BIN="/usr/lib/apache2/suexec2" -D DEFAULT_PIDLOG="/var/run/apache2.pid" -D DEFAULT_SCOREBOARD="logs/apache_runtime_status" -D DEFAULT_ERRORLOG="logs/error_log" -D AP_TYPES_CONFIG_FILE="/etc/apache2/mime.types" -D SERVER_CONFIG_FILE="/etc/apache2/apache2.conf"
Regards, Olivier
-- Fedora-directory-users mailing list Fedora-directory-users@redhat.com https://www.redhat.com/mailman/listinfo/fedora-directory-users
389-users@lists.fedoraproject.org
-
Olivier Brugman -
Rob Crittenden