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/
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users
