Hello,
I'm trying to install new LDAP server and facing strange errors:
[14/01/15:04:47:03] - [Setup] Info Updating the configuration for the httpd engine . . .
[14/01/15:04:47:03] - [Setup] Warning Error: command 'getsebool httpd_can_connect_ldap' failed - output [getsebool: SELinux is disabled] error [][14/01/15:04:47:03] - [Setup] Info Starting admin server . . .
[14/01/15:04:47:13] - [Setup] Info output: Starting dirsrv-admin:
[14/01/15:04:47:13] - [Setup] Info output: [Wed Jan 15 04:47:03 2014] [crit] (22)Invalid argument: alloc_listener: failed to get a socket for 0.0.0.0
[14/01/15:04:47:13] - [Setup] Info output: Syntax error on line 87 of /etc/dirsrv/admin-serv/console.conf:
[14/01/15:04:47:13] - [Setup] Info output: Listen setup failed
[14/01/15:04:47:13] - [Setup] Info output: Server failed to start !!! Please check errors log for problems
[14/01/15:04:47:13] - [Setup] Info output: ESC[60G[ESC[0;31mFAILEDESC[0;39m]
[14/01/15:04:47:13] - [Setup] Info The admin server was successfully started.
[14/01/15:04:47:13] - [Setup] Info Admin server was successfully created, configured, and started.
[14/01/15:04:47:13] - [Setup] Success Exiting . . .
I have found bug 377: https://fedorahosted.org/389/ticket/377 which
seems to be fixed in 1.1.36 but sadly it's not available yet in
repositories:
[root@ldap21shadow ~]# yum list installed |grep 389
389-admin.x86_64 1.1.35-1.el6 @epel
389-admin-console.noarch 1.1.8-1.el6 @epel
389-admin-console-doc.noarch 1.1.8-1.el6 @epel
389-adminutil.x86_64 1.1.19-1.el6 @epel
389-console.noarch 1.1.7-1.el6 @epel
389-ds.noarch 1.2.2-1.el6 @epel
389-ds-base.x86_64 1.2.11.15-31.el6_5 @updates
389-ds-base-libs.x86_64 1.2.11.15-31.el6_5 @updates
389-ds-console.noarch 1.2.6-1.el6 @epel
389-ds-console-doc.noarch 1.2.6-1.el6 @epel
389-dsgw.x86_64 1.1.11-1.el6 @epel
I've tried workaround described there by rmeggins. Output is very
similar, only warning about getsebool is gone:
Creating directory server . . .
/usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
/usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
Your new DS instance 'ldap21shadow' was successfully created.
Creating the configuration directory server . . .
Beginning Admin Server creation . . .
Creating Admin Server files and directories . . .
Updating adm.conf . . .
Updating admpw . . .
Registering admin server with the configuration directory server . . .
Updating adm.conf with information from configuration directory server . . .
Updating the configuration for the httpd engine . . .
/usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
/usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
Starting admin server . . .
output: Starting dirsrv-admin:
output: [Wed Jan 15 05:11:22 2014] [crit] (22)Invalid argument: alloc_listener: failed to get a socket for 0.0.0.0
output: Syntax error on line 87 of /etc/dirsrv/admin-serv/console.conf:
output: Listen setup failed
output: Server failed to start !!! Please check errors log for problems
output: [FAILED]
The admin server was successfully started.
Admin server was successfully created, configured, and started.
Exiting . . .
Log file is '/tmp/setup3KfWko.log'
The console.conf is equal to to configuration on my other servers:
[root@ldap21shadow ~]# head -87 /etc/dirsrv/admin-serv/console.conf | tail -5
# e.g. "Listen 12.34.56.78:80"
#
# To allow connections to IPv6 addresses add "Listen [::]:80"
#
Listen 0.0.0.0:9830
I've tried
Listen 9830
Listen [::]:9830
Listen 127.0.0.1: 9830
Still the same errors:
[root@ldap21shadow ~]# /etc/init.d/dirsrv-admin start
Starting dirsrv-admin:
[Wed Jan 15 05:29:55 2014] [crit] (22)Invalid argument: alloc_listener: failed to get a socket for 0.0.0.0
Syntax error on line 87 of /etc/dirsrv/admin-serv/console.conf:
Listen setup failed
Any suggestions?
Thanks!
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
[14/01/15:05:10:46] - [Setup] Info This program will set up the 389 Directory and Administration Servers.
It is recommended that you have "root" privilege to set up the software.
Tips for using this program:
- Press "Enter" to choose the default and go to the next screen
- Type "Control-B" then "Enter" to go back to the previous screen
- Type "Control-C" to cancel the setup program
[14/01/15:05:10:46] - [Setup] Info Would you like to continue with set up?
[14/01/15:05:10:47] - [Setup] Info yes
[14/01/15:05:10:47] - [Setup] Info Your system has been scanned for potential problems, missing patches,
etc. The following output is a report of the items found that need to
be addressed before running this software in a production
environment.
389 Directory Server system tuning analysis version 23-FEBRUARY-2012.
NOTICE : System is x86_64-unknown-linux2.6.26-2-openvz-amd64 (8 processors).
NOTICE : /sbin/sysctl -n net.ipv4.tcp_keepalive_time failed
WARNING: There are only 1024 file descriptors (hard limit) available, which
limit the number of simultaneous connections.
WARNING: There are only 1024 file descriptors (soft limit) available, which
limit the number of simultaneous connections.
WARNING : The warning messages above should be reviewed before proceeding.
[14/01/15:05:10:47] - [Setup] Info Would you like to continue?
[14/01/15:05:10:50] - [Setup] Info yes
[14/01/15:05:10:50] - [Setup] Info Choose a setup type:
1. Express
Allows you to quickly set up the servers using the most
common options and pre-defined defaults. Useful for quick
evaluation of the products.
2. Typical
Allows you to specify common defaults and options.
3. Custom
Allows you to specify more advanced options. This is
recommended for experienced server administrators only.
To accept the default shown in brackets, press the Enter key.
[14/01/15:05:10:50] - [Setup] Info Choose a setup type
[14/01/15:05:10:51] - [Setup] Info 2
[14/01/15:05:10:51] - [Setup] Info Enter the fully qualified domain name of the computer
on which you're setting up server software. Using the form
<hostname>.<domainname>
Example: eros.example.com.
To accept the default shown in brackets, press the Enter key.
Warning: This step may take a few minutes if your DNS servers
can not be reached or if DNS is not configured correctly. If
you would rather not wait, hit Ctrl-C and run this program again
with the following command line option to specify the hostname:
General.FullMachineName=your.hostname.domain.name
[14/01/15:05:10:51] - [Setup] Info Computer name
[14/01/15:05:10:52] - [Setup] Info ldap21shadow.cesnet.cz
[14/01/15:05:10:52] - [Setup] Info The servers must run as a specific user in a specific group.
It is strongly recommended that this user should have no privileges
on the computer (i.e. a non-root user). The setup procedure
will give this user/group some permissions in specific paths/files
to perform server-specific operations.
If you have not yet created a user and group for the servers,
create this user and group using your native operating
system utilities.
[14/01/15:05:10:52] - [Setup] Info System User
[14/01/15:05:10:54] - [Setup] Info ldap
[14/01/15:05:10:54] - [Setup] Info System Group
[14/01/15:05:10:55] - [Setup] Info ldap
[14/01/15:05:10:55] - [Setup] Info Server information is stored in the configuration directory server.
This information is used by the console and administration server to
configure and manage your servers. If you have already set up a
configuration directory server, you should register any servers you
set up or create with the configuration server. To do so, the
following information about the configuration server is required: the
fully qualified host name of the form
<hostname>.<domainname>(e.g. hostname.example.com), the port number
(default 389), the suffix, the DN and password of a user having
permission to write the configuration information, usually the
configuration directory administrator, and if you are using security
(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port
number (default 636) instead of the regular LDAP port number, and
provide the CA certificate (in PEM/ASCII format).
If you do not yet have a configuration directory server, enter 'No' to
be prompted to set up one.
[14/01/15:05:10:55] - [Setup] Info Do you want to register this software with an existing
configuration directory server?
[14/01/15:05:10:56] - [Setup] Info no
[14/01/15:05:10:56] - [Setup] Info Please enter the administrator ID for the configuration directory
server. This is the ID typically used to log in to the console. You
will also be prompted for the password.
[14/01/15:05:10:56] - [Setup] Info Configuration directory server
administrator ID
[14/01/15:05:10:59] - [Setup] Info admin
[14/01/15:05:10:59] - [Setup] Info Password
[14/01/15:05:11:04] - [Setup] Info Password (confirm)
[14/01/15:05:11:06] - [Setup] Info The information stored in the configuration directory server can be
separated into different Administration Domains. If you are managing
multiple software releases at the same time, or managing information
about multiple domains, you may use the Administration Domain to keep
them separate.
If you are not using administrative domains, press Enter to select the
default. Otherwise, enter some descriptive, unique name for the
administration domain, such as the name of the organization
responsible for managing the domain.
[14/01/15:05:11:06] - [Setup] Info Administration Domain
[14/01/15:05:11:07] - [Setup] Info cesnet.cz
[14/01/15:05:11:07] - [Setup] Info The standard directory server network port number is 389. However, if
you are not logged as the superuser, or port 389 is in use, the
default value will be a random unused port number greater than 1024.
If you want to use port 389, make sure that you are logged in as the
superuser, that port 389 is not in use.
[14/01/15:05:11:07] - [Setup] Info Directory server network port
[14/01/15:05:11:08] - [Setup] Info 389
[14/01/15:05:11:08] - [Setup] Info Each instance of a directory server requires a unique identifier.
This identifier is used to name the various
instance specific files and directories in the file system,
as well as for other uses as a server instance identifier.
[14/01/15:05:11:08] - [Setup] Info Directory server identifier
[14/01/15:05:11:08] - [Setup] Info ldap21shadow
[14/01/15:05:11:08] - [Setup] Info The suffix is the root of your directory tree. The suffix must be a valid DN.
It is recommended that you use the dc=domaincomponent suffix convention.
For example, if your domain is example.com,
you should use dc=example,dc=com for your suffix.
Setup will create this initial suffix for you,
but you may have more than one suffix.
Use the directory server utilities to create additional suffixes.
[14/01/15:05:11:08] - [Setup] Info Suffix
[14/01/15:05:11:09] - [Setup] Info dc=cesnet, dc=cz
[14/01/15:05:11:09] - [Setup] Info Certain directory server operations require an administrative user.
This user is referred to as the Directory Manager and typically has a
bind Distinguished Name (DN) of cn=Directory Manager.
You will also be prompted for the password for this user. The password must
be at least 8 characters long, and contain no spaces.
Press Control-B or type the word "back", then Enter to back up and start over.
[14/01/15:05:11:09] - [Setup] Info Directory Manager DN
[14/01/15:05:11:10] - [Setup] Info cn=Directory Manager
[14/01/15:05:11:10] - [Setup] Info Password
[14/01/15:05:11:14] - [Setup] Info Password (confirm)
[14/01/15:05:11:16] - [Setup] Info The Administration Server is separate from any of your web or application
servers since it listens to a different port and access to it is
restricted.
Pick a port number between 1024 and 65535 to run your Administration
Server on. You should NOT use a port number which you plan to
run a web or application server on, rather, select a number which you
will remember and which will not be used for anything else.
[14/01/15:05:11:16] - [Setup] Info Administration port
[14/01/15:05:11:17] - [Setup] Info 9830
[14/01/15:05:11:17] - [Setup] Info The interactive phase is complete. The script will now set up your
servers. Enter No or go Back if you want to change something.
[14/01/15:05:11:17] - [Setup] Info Are you ready to set up your servers?
[14/01/15:05:11:18] - [Setup] Info yes
[14/01/15:05:11:18] - [Setup] Info Creating directory server . . .
[14/01/15:05:11:21] - [Setup] Info Your new DS instance 'ldap21shadow' was successfully created.
[14/01/15:05:11:21] - [Setup] Info Creating the configuration directory server . . .
[14/01/15:05:11:22] - [Setup] Info Beginning Admin Server creation . . .
[14/01/15:05:11:22] - [Setup] Info Creating Admin Server files and directories . . .
[14/01/15:05:11:22] - [Setup] Info Updating adm.conf . . .
[14/01/15:05:11:22] - [Setup] Info Updating admpw . . .
[14/01/15:05:11:22] - [Setup] Info Registering admin server with the configuration directory server . . .
[14/01/15:05:11:22] - [Setup] Info Updating adm.conf with information from configuration directory server . . .
[14/01/15:05:11:22] - [Setup] Info Updating the configuration for the httpd engine . . .
[14/01/15:05:11:22] - [Setup] Info Starting admin server . . .
[14/01/15:05:11:32] - [Setup] Info output: Starting dirsrv-admin:
[14/01/15:05:11:32] - [Setup] Info output: [Wed Jan 15 05:11:22 2014] [crit] (22)Invalid argument: alloc_listener: failed to get a socket for 0.0.0.0
[14/01/15:05:11:32] - [Setup] Info output: Syntax error on line 87 of /etc/dirsrv/admin-serv/console.conf:
[14/01/15:05:11:32] - [Setup] Info output: Listen setup failed
[14/01/15:05:11:32] - [Setup] Info output: Server failed to start !!! Please check errors log for problems
[14/01/15:05:11:32] - [Setup] Info output: [60G[[0;31mFAILED[0;39m]
[14/01/15:05:11:32] - [Setup] Info The admin server was successfully started.
[14/01/15:05:11:32] - [Setup] Info Admin server was successfully created, configured, and started.
[14/01/15:05:11:32] - [Setup] Success Exiting . . .
Log file is '/tmp/setup3KfWko.log'
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
