4:30 a.m.
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/
11:57 a.m.
SELinux enabled?
On Wed, Jan 15, 2014 at 4:30 AM, Jan Tomasek <jan(a)tomasek.cz> wrote:
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/
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
1:10 p.m.
On 01/15/2014 06:57 PM, Jonathan Vaughn wrote:
SELinux enabled?
No. I would like to avoid that. The server should run inside OpenVZ
container where is not possible to enable it.
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
1:39 p.m.
Ah, I should have been more clear - I was asking if it was, because
sometimes that sort of error can be caused be SELinux blocking the bind
operation. If it's not enabled, it obviously isn't the culprit though.
Though since you mention OpenVZ... maybe there's something weird with the
OpenVZ kernel? Isn't that one of those virtualization methods that has
funky kernels that are built just for that kind of virtualization ? Those
can sometimes interfere with unexpected things... we have a dedicated
server somewhere that is dedicated but still running in some kind of
container, and we can't add swap storage, even using a file, due to the
kernel ...
On Wed, Jan 15, 2014 at 1:10 PM, Jan Tomasek <jan(a)tomasek.cz> wrote:
On 01/15/2014 06:57 PM, Jonathan Vaughn wrote:
> SELinux enabled?
No. I would like to avoid that. The server should run inside OpenVZ
container where is not possible to enable it.
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
2:54 a.m.
On 01/15/2014 08:39 PM, Jonathan Vaughn wrote:
Ah, I should have been more clear - I was asking if it was, because
sometimes that sort of error can be caused be SELinux blocking the bind
operation. If it's not enabled, it obviously isn't the culprit though.
Though since you mention OpenVZ... maybe there's something weird with
the OpenVZ kernel?
OpenVZ doesn't support SElinux, but when:
[root@ldap21shadow ~]# sestatus
SELinux status: disabled
than it should not be issue. I'm running other instances of 389 under
OpenVZ so that is not problem.
[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
[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
Server failed to start !!! Please check errors log for problems
Why Syntax error on "Listen 0.0.0.0:9830"?
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
3 a.m.
Hi,
check if you have another process listening on that port.
Regards.
On 01/16/14 09:54 AM, Jan Tomasek wrote:
On 01/15/2014 08:39 PM, Jonathan Vaughn wrote:
> Ah, I should have been more clear - I was asking if it was, because
> sometimes that sort of error can be caused be SELinux blocking the bind
> operation. If it's not enabled, it obviously isn't the culprit though.
>
> Though since you mention OpenVZ... maybe there's something weird with
> the OpenVZ kernel?
OpenVZ doesn't support SElinux, but when:
[root@ldap21shadow ~]# sestatus
SELinux status: disabled
than it should not be issue. I'm running other instances of 389 under
OpenVZ so that is not problem.
[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
[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
Server failed to start !!! Please check errors log for problems
Why Syntax error on "Listen 0.0.0.0:9830"?
--
Predrag Zečević, Technical Support Analyst, 2e Systems GmbH
Telephone: +49 6196 9505 815, Facsimile: +49 6196 9505 894
Mobile: +49 174 3109 288, Skype: predrag.zecevic
E-mail: predrag.zecevic(a)2e-systems.com
Headquarter: 2e Systems GmbH, Königsteiner Str. 87,
65812 Bad Soden am Taunus, Germany
Company registration: Amtsgericht Königstein (Germany), HRB 7303
Managing director: Phil Douglas
http://www.2e-systems.com/ - Making your business fly!
[***]===---
Q: What do little WASPs want to be when they grow up? A: The very best
person they can possibly be.
10:49 a.m.
On 01/15/2014 11:30 AM, Jan Tomasek wrote:
> [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
after upgrading to linux-image-2.6.32-5-openvz-amd64 the problem is gone.
So just for record. Versions:
# yum list installed |grep 389
389-admin.x86_64 1.1.23-1.el5 installed
389-admin-console.noarch 1.1.8-1.el5 installed
389-admin-console-doc.noarch 1.1.8-1.el5 installed
389-adminutil.x86_64 1.1.14-1.el5 installed
389-console.noarch 1.1.7-3.el5 installed
389-ds.noarch 1.2.1-1.el5 installed
389-ds-base.x86_64 1.2.9.9-1.el5 installed
389-ds-base-libs.x86_64 1.2.9.9-1.el5 installed
389-ds-console.noarch 1.2.6-1.el5 installed
389-ds-console-doc.noarch 1.2.6-1.el5 installed
389-dsgw.x86_64 1.1.7-2.el5 installed
are correctly running on OpenVZ kernel 2.6.26 from Debian Squeeze and:
# 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
are not. Weird. :)
--
-----------------------
Jan Tomasek aka Semik
http://www.tomasek.cz/
3742
days inactive
3746
days old
389-users@lists.fedoraproject.org
7 comments
4 participants
participants (4)
-
Jan Tomasek -
Jonathan Vaughn -
Paul Robert Marino -
Predrag Zečević - Technical Support Analyst