when you rebooted chances are whatever was holding on to the port didn't come back after the reboot.
For future reference netstat -tnp can be very helpful in these cases
-- Sent from my HP Pre3
On Jan 19, 2014 11:49, Jan Tomasek <jan@xxxxxxxxxx> wrote:
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/
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
