[389-users] The admin server: failed to get a socket for 0.0.0.0

[Jan Tomasek]

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 at 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 at 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 at 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/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: setup3KfWko.log
Type: text/x-log
Size: 10152 bytes
Desc: not available
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20140115/04349a61/attachment.bin>