Is there an easy way to fix this? Since it is a
test server I _could_ wipe it and start over, but I
don’t want this to be a problem when we move to production.
Â*
Thanks!
Â*
Josh
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
01-19-2011, 05:58 PM
"Ellsworth, Josh"
slapd only listening on IPv6
I don't see any errors - looks like the admin server is starting up?Â* If you do a service dirsrv-admin start or restart (while the directory server is running) do you get an error?Â* Does ps -ef|grep httpd show 3 processes?
Â*
Â*
I’m sorry that I was not more clear. Nsslapd seems to only be listening on ipv6 so the admin server never starts. After rebooting the server I ran service dirsrv start. Â*Running service dirsrv-admin start resulted in Starting dirsrv-admin: appearing on the screen with no ‘OK’ for at least an hour, after which I cancelled the command with ^z. Subsequent investigations led me to believe that the cause was nsslapd only listening on ipv6.
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 1:52 PM
To: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening on IPv6
Â*
On 01/19/2011 10:23 AM, Ellsworth, Josh wrote:
OK, I think I have all of these answered.
Â*
Can you post the error log from /var/log/dirsrv/admin-serv/error?
Â*
[Tue Jan 18 16:28:40 2011] [info] done Init: Initializing NSS library
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(220): HashTableEnumerate: Key=admin-serv Val=cn=admin-serv-ldaptest,cn=389 Administration Server,cn=Server Group,cn=ldaptest.illuminatics.local,ou=illuminati cs.local,o=NetscapeRoot
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(1444): populate_tasks_from_server(): getting tasks for server [admin-serv] siedn [cn=admin-serv-ldaptest,cn=389 Administration Server,cn=Server Group,cn=ldaptest.illuminatics.local,ou=illuminati cs.local,o=NetscapeRoot]
[Tue Jan 18 16:28:40 2011] [notice] Access Host filter is: *.illuminatics.local
[Tue Jan 18 16:28:40 2011] [notice] Access Address filter is: *
[Tue Jan 18 16:28:40 2011] [error] NSS_Shutdown failed: -8038
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module authz_host_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module auth_basic_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module authn_file_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module log_config_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module env_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module mime_magic_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module expires_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module deflate_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module headers_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module unique_id_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module setenvif_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module mime_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module vhost_alias_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module negotiation_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module dir_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module actions_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module alias_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module rewrite_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module cache_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module disk_cache_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module cgi_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module restartd_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module nss_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module admserv_module
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(2501): [1792] create_server_config [0xbogus %p for (null)
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(2489): [1792] create_config [0xbogus %p for (null)
[Tue Jan 18 16:28:40 2011] [info] done Init: Initializing NSS library
[Tue Jan 18 16:28:41 2011] [notice] Apache/2.2 configured -- resuming normal operations
[Tue Jan 18 16:37:59 2011] [warn] child process 1797 still did not exit, sending a SIGTERM
[Tue Jan 18 16:38:00 2011] [notice] caught SIGTERM, shutting do
Â*
What platform?Â*
[root@ldaptest ~]# uname -a
Linux ldaptest 2.6.18-194.17.4.el5xen #1 SMP Mon Oct 25 16:36:31 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Â*
What versions of 389-ds-base and 389-admin?
[root@ldaptest ~]# yum list | grep 389
389-admin.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â* 1.1.13-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-admin.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â* 1.1.14-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-admin-console.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 1.1.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-admin-console-doc.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 1.1.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-adminutil.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â* 1.1.8-4.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-adminutil.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â* 1.1.13-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-console.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â* 1.1.4-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â*Â*Â*Â*Â* 1.2.1-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds-base.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â* 1.2.7.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds-console.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â* 1.2.3-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds-console-doc.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 1.2.3-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-dsgw.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â*Â*Â*Â* 1.1.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-dsgw.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â*Â*Â*Â* 1.1.6-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
Â*
Running ‘grep nsslapd-listenhost /etc/dirsrv/slapd-INSTANCENAME/dse.ldif’ (with no quotes of course) does not return anything.
I don't see any errors - looks like the admin server is starting up?Â* If you do a service dirsrv-admin start or restart (while the directory server is running) do you get an error?Â* Does ps -ef|grep httpd show 3 processes?
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 10:32 AM
To: General discussion list for the 389 Directory server project.
Cc: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening on IPv6
Â*
On 01/19/2011 07:11 AM, Ellsworth, Josh wrote:
I am working on a test 389DS instance and yesterday it started giving me trouble. The admin server would not start up correctly.
Can you post the error log from /var/log/dirsrv/admin-serv/error?
What platform?Â* What versions of 389-ds-base and 389-admin?
I think that the problem is because slapd is not listening on IPv4.
grep nsslapd-listenhost /etc/dirsrv/slapd-INSTANCENAME/dse.ldif
I don't see any errors - looks like the
admin server is starting up?Â* If you do a service dirsrv-admin
start or restart (while the directory server is running) do
you get an error?Â* Does ps -ef|grep httpd show 3 processes?
Â*
Â*
I’m sorry that I was not more clear.
Nsslapd seems to only be listening on ipv6 so the admin server
never starts. After rebooting the server I ran service dirsrv
start. Â*Running service dirsrv-admin start resulted in
Starting dirsrv-admin: appearing on the screen with no ‘OK’
for at least an hour, after which I cancelled the command with
^z. Subsequent investigations led me to believe that the cause
was nsslapd only listening on ipv6.
Ok.Â* I think you are running into
https://bugzilla.redhat.com/show_bug.cgi?id=588480
Â*
From: Rich Megginson
[mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 1:52 PM
To: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening on
IPv6
Â*
On 01/19/2011 10:23 AM, Ellsworth, Josh
wrote:
OK, I think I have all of these answered.
Â*
Can you post the error log from
/var/log/dirsrv/admin-serv/error?
Running ‘grep nsslapd-listenhost
/etc/dirsrv/slapd-INSTANCENAME/dse.ldif’ (with no quotes of
course) does not return anything.
I don't see any errors - looks like the
admin server is starting up?Â* If you do a service dirsrv-admin
start or restart (while the directory server is running) do
you get an error?Â* Does ps -ef|grep httpd show 3 processes?
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 10:32 AM
To: General discussion list for the 389 Directory
server project.
Cc: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening on
IPv6
Â*
On 01/19/2011 07:11 AM, Ellsworth, Josh
wrote:
I am working on
a test 389DS instance and yesterday it started giving me
trouble. The admin server would not start up correctly.
Can you post the error log from
/var/log/dirsrv/admin-serv/error?
What platform?Â* What versions of 389-ds-base and 389-admin?
I think that
the problem is because slapd is not listening on IPv4.
Is there an
easy way to fix this? Since it is a test server I _could_
wipe it and start over, but I don’t want this to be a
problem when we move to production.
Â*
Thanks!
Â*
Josh
Â*
Â*
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
Â*
Â*
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
01-19-2011, 07:06 PM
Rich Megginson
slapd only listening on IPv6
On 01/19/2011 12:30 PM, Rich Megginson wrote:
On 01/19/2011 11:58 AM, Ellsworth, Josh wrote:
I don't see any errors - looks like the
admin server is starting up?Â* If you do a service
dirsrv-admin start or restart (while the directory server is
running) do you get an error?Â* Does ps -ef|grep httpd show 3
processes?
Â*
Â*
I’m sorry that I was not more clear.
Nsslapd seems to only be listening on ipv6 so the admin
server never starts. After rebooting the server I ran
service dirsrv start. Â*Running service dirsrv-admin start
resulted in Starting dirsrv-admin: appearing on the screen
with no ‘OK’ for at least an hour, after which I cancelled
the command with ^z. Subsequent investigations led me to
believe that the cause was nsslapd only listening on ipv6.
Ok.Â* I think you are running into https://bugzilla.redhat.com/show_bug.cgi?id=588480
Could you provide your /etc/hosts and/or getent hosts and/or DNS
information for your hostname?
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 1:52 PM
To: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening
on IPv6
Â*
On 01/19/2011 10:23 AM, Ellsworth, Josh
wrote:
OK, I think I have all of these answered.
Â*
Can you post the error log from
/var/log/dirsrv/admin-serv/error?
Running ‘grep nsslapd-listenhost
/etc/dirsrv/slapd-INSTANCENAME/dse.ldif’ (with no quotes of
course) does not return anything.
I don't see any errors - looks like the
admin server is starting up?Â* If you do a service
dirsrv-admin start or restart (while the directory server is
running) do you get an error?Â* Does ps -ef|grep httpd show 3
processes?
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 10:32 AM
To: General discussion list for the 389
Directory server project.
Cc: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening
on IPv6
Â*
On 01/19/2011 07:11 AM, Ellsworth, Josh
wrote:
I
am working on a test 389DS instance and yesterday it
started giving me trouble. The admin server would not
start up correctly.
Can you post the error log from
/var/log/dirsrv/admin-serv/error?
What platform?Â* What versions of 389-ds-base and 389-admin?
I
think that the problem is because slapd is not listening
on IPv4.
Is
there an easy way to fix this? Since it is a test server I
_could_ wipe it and start over, but I don’t want
this to be a problem when we move to production.
Â*
Thanks!
Â*
Josh
Â*
Â*
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
Â*
Â*
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
01-19-2011, 08:03 PM
"Ellsworth, Josh"
slapd only listening on IPv6
Disabling ipv6 did the trick for me. Thanks for your help, Rich.
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 3:06 PM
To: General discussion list for the 389 Directory server project.
Cc: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening on IPv6
Â*
On 01/19/2011 12:30 PM, Rich Megginson wrote:
On 01/19/2011 11:58 AM, Ellsworth, Josh wrote:
I don't see any errors - looks like the admin server is starting up?Â* If you do a service dirsrv-admin start or restart (while the directory server is running) do you get an error?Â* Does ps -ef|grep httpd show 3 processes?
Â*
Â*
I’m sorry that I was not more clear. Nsslapd seems to only be listening on ipv6 so the admin server never starts. After rebooting the server I ran service dirsrv start. Â*Running service dirsrv-admin start resulted in Starting dirsrv-admin: appearing on the screen with no ‘OK’ for at least an hour, after which I cancelled the command with ^z. Subsequent investigations led me to believe that the cause was nsslapd only listening on ipv6.
Ok.Â* I think you are running into https://bugzilla.redhat.com/show_bug.cgi?id=588480
Could you provide your /etc/hosts and/or getent hosts and/or DNS information for your hostname?
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 1:52 PM
To: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening on IPv6
Â*
On 01/19/2011 10:23 AM, Ellsworth, Josh wrote:
OK, I think I have all of these answered.
Â*
Can you post the error log from /var/log/dirsrv/admin-serv/error?
Â*
[Tue Jan 18 16:28:40 2011] [info] done Init: Initializing NSS library
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(220): HashTableEnumerate: Key=admin-serv Val=cn=admin-serv-ldaptest,cn=389 Administration Server,cn=Server Group,cn=ldaptest.illuminatics.local,ou=illuminati cs.local,o=NetscapeRoot
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(1444): populate_tasks_from_server(): getting tasks for server [admin-serv] siedn [cn=admin-serv-ldaptest,cn=389 Administration Server,cn=Server Group,cn=ldaptest.illuminatics.local,ou=illuminati cs.local,o=NetscapeRoot]
[Tue Jan 18 16:28:40 2011] [notice] Access Host filter is: *.illuminatics.local
[Tue Jan 18 16:28:40 2011] [notice] Access Address filter is: *
[Tue Jan 18 16:28:40 2011] [error] NSS_Shutdown failed: -8038
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module authz_host_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module auth_basic_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module authn_file_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module log_config_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module env_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module mime_magic_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module expires_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module deflate_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module headers_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module unique_id_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module setenvif_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module mime_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module vhost_alias_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module negotiation_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module dir_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module actions_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module alias_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module rewrite_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module cache_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module disk_cache_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module cgi_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module restartd_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module nss_module
[Tue Jan 18 16:28:40 2011] [debug] mod_so.c(246): loaded module admserv_module
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(2501): [1792] create_server_config [0xbogus %p for (null)
[Tue Jan 18 16:28:40 2011] [debug] mod_admserv/mod_admserv.c(2489): [1792] create_config [0xbogus %p for (null)
[Tue Jan 18 16:28:40 2011] [info] done Init: Initializing NSS library
[Tue Jan 18 16:28:41 2011] [notice] Apache/2.2 configured -- resuming normal operations
[Tue Jan 18 16:37:59 2011] [warn] child process 1797 still did not exit, sending a SIGTERM
[Tue Jan 18 16:38:00 2011] [notice] caught SIGTERM, shutting do
Â*
What platform?Â*
[root@ldaptest ~]# uname -a
Linux ldaptest 2.6.18-194.17.4.el5xen #1 SMP Mon Oct 25 16:36:31 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
Â*
What versions of 389-ds-base and 389-admin?
[root@ldaptest ~]# yum list | grep 389
389-admin.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â* 1.1.13-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-admin.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â*Â* 1.1.14-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-admin-console.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 1.1.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-admin-console-doc.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 1.1.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-adminutil.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â* 1.1.8-4.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-adminutil.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â* 1.1.13-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-console.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â*Â*Â*Â* 1.1.4-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â*Â*Â*Â*Â* 1.2.1-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds-base.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â* 1.2.7.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds-console.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* Â*Â*Â* 1.2.3-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-ds-console-doc.noarchÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* 1.2.3-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-dsgw.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â*Â*Â*Â* 1.1.5-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
389-dsgw.x86_64Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â*Â*Â*Â*Â* 1.1.6-1.el5Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* installed
Â*
Running ‘grep nsslapd-listenhost /etc/dirsrv/slapd-INSTANCENAME/dse.ldif’ (with no quotes of course) does not return anything.
I don't see any errors - looks like the admin server is starting up?Â* If you do a service dirsrv-admin start or restart (while the directory server is running) do you get an error?Â* Does ps -ef|grep httpd show 3 processes?
Â*
From: Rich Megginson [mailto:rmeggins@redhat.com]
Sent: Wednesday, January 19, 2011 10:32 AM
To: General discussion list for the 389 Directory server project.
Cc: Ellsworth, Josh
Subject: Re: [389-users] slapd only listening on IPv6
Â*
On 01/19/2011 07:11 AM, Ellsworth, Josh wrote:
I am working on a test 389DS instance and yesterday it started giving me trouble. The admin server would not start up correctly.
Can you post the error log from /var/log/dirsrv/admin-serv/error?
What platform?Â* What versions of 389-ds-base and 389-admin?
I think that the problem is because slapd is not listening on IPv4.
grep nsslapd-listenhost /etc/dirsrv/slapd-INSTANCENAME/dse.ldif
On 01/19/2011 06:11 AM, Ellsworth, Josh wrote:
> I am working on a test 389DS instance and yesterday it started giving me
> trouble. The admin server would not start up correctly. I think that the
> problem is because slapd is not listening on IPv4.
>
> [root@ldaptest ~]# netstat -aunt
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address Foreign Address State
...
> tcp 0 0 :::389 :::* LISTEN
That's normal and workable on a standard Linux host. Is this a
Debian/Ubuntu system? They've changed the default behavior, there.
We're looking at a similar problem on the Courier MTA list. Richard, I
think the easy fix to this is to override the system default with
setsockopt:
int v6only = 0;
if (setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY,
(char *)&on, sizeof(v6only)) == -1)
perror("setsockopt IPV6_V6ONLY");
Josh, if this is Debian, you should be able to edit
/etc/sysctl.d/bindv6only.conf and disable the change that Debian made.
--
389 users mailing list
389-users@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users
slapd only listening on IPv6
