Good Afternoon,
I was trying to upgrade one of my 389ds consumers and it does not seem to have
worked.Started with the following:
[server-03]# cat /etc/issueCentOS release 6.3 (Final)Kernel \r on an \m
[server-03]# rpm -qa
389*389-adminutil-1.1.15-1.el6.x86_64389-admin-console-1.1.8-1.el6.noarch389-dsgw-1.1.9-1.el6.x86_64389-console-1.1.7-1.el6.noarch389-ds-base-libs-1.2.10.2-20.el6_3.x86_64389-admin-1.1.29-1.el6.x86_64389-ds-console-1.2.6-1.el6.noarch389-admin-console-doc-1.1.8-1.el6.noarch389-ds-1.2.2-1.el6.noarch389-ds-base-1.2.10.2-20.el6_3.x86_64389-ds-console-doc-1.2.6-1.el6.noarch
Ran the following commands:
[server-03]# yum update[server-03]# yum upgrade 389-ds-base
[server-03]# rpm -qa
389*389-admin-console-doc-1.1.8-1.el6.noarch389-admin-console-1.1.8-1.el6.noarch389-dsgw-1.1.9-1.el6.x86_64389-ds-console-1.2.6-1.el6.noarch389-ds-1.2.2-1.el6.noarch389-ds-base-1.2.11.15-48.el6_6.x86_64389-adminutil-1.1.15-1.el6.x86_64389-ds-console-doc-1.2.6-1.el6.noarch389-console-1.1.7-1.el6.noarch389-admin-1.1.29-1.el6.x86_64389-ds-base-libs-1.2.11.15-48.el6_6.x86_64
[server-03]# setup-ds-admin.pl -u==============================================================================The
update option will allow you to re-register your servers with theconfiguration directory
server and update the information about yourservers that the console and admin server
uses. You will need yourconfiguration directory server admin ID and password to
continue.Continue?
[yes]:==============================================================================Please
specify the information about your configuration directoryserver. The following
information is required:- host (fully qualified), port (non-secure or secure), suffix,
protocol (ldap or ldaps) - this information should be provided in the form of an LDAP url
e.g. for non-secureldap://host.example.com:389/o=NetscapeRoot or for
secureldaps://host.example.com:636/o=NetscapeRoot- admin ID and password- admin domain- a
CA certificate file may be required if you choose to use ldaps and security has not yet
been configured - the file must be in PEM/ASCII format - specify the absolute path and
filenameConfiguration directory server URL
[ldap://server-01.my.company.net:389/o=NetscapeRoot]:Configuration directory server admin
ID [uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot]:Configuration
directory server admin password:Configuration directory server admin domain
[
my.company.net]:
==============================================================================
The interactive phase is complete. The script will now set up yourservers. Enter No or
go Back if you want to change something.Are you ready to set up your servers? [yes]:Could
not open TLS connection to server-03.my.company.net:389 - trying regular connectionCould
not open a connection to server-03.my.company.net:389Could not open a connection to the
server at server-03.my.company.net port 389 as
'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot'.Please make
sure the server is up and running before using online mode,or use offline mode.Could not
reconfigure the admin server.Exiting . . .Log file is '/tmp/setup4jz4q9.log'
[server-03]# cat /tmp/setup4jz4q9.log[15/06/09:16:18:14] - [Setup] Info The update option
will allow you to re-register your servers with theconfiguration directory server and
update the information about yourservers that the console and admin server uses. You will
need yourconfiguration directory server admin ID and password to
continue.[15/06/09:16:18:14] - [Setup] Info Continue?[15/06/09:16:18:16] - [Setup] Info
yes[15/06/09:16:18:16] - [Setup] Info Please specify the information about your
configuration directoryserver. The following information is required:- host (fully
qualified), port (non-secure or secure), suffix, protocol (ldap or ldaps) - this
information should be provided in the form of an LDAP url e.g. for
non-secureldap://host.example.com:389/o=NetscapeRoot or for
secureldaps://host.example.com:636/o=NetscapeRoot- admin ID and password- admin domain- a
CA certificate file may be required if you choose to use ldaps and security has not yet
been configured - the file must be in PEM/ASCII format - specify the absolute path and
filename[15/06/09:16:20:38] - [Setup] Info Configuration directory server
URL[15/06/09:16:20:42] - [Setup] Info
ldap://server-01.my.company.net:389/o=NetscapeRoot[15/06/09:16:20:42] - [Setup] Info
Configuration directory server admin ID[15/06/09:16:20:43] - [Setup] Info
uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot[15/06/09:16:20:43] -
[Setup] Info Configuration directory server admin password[15/06/09:16:20:50] - [Setup]
Info Configuration directory server admin domain[15/06/09:16:20:50] - [Setup]
Info my.company.net[15/06/09:16:20:50] - [Setup] Info The interactive phase is
complete. The script will now set up yourservers. Enter No or go Back if you want to
change something.[15/06/09:16:20:50] - [Setup] Info Are you ready to set up your
servers?[15/06/09:16:20:54] - [Setup] Info yesCould not open TLS connection
to server-03.my.company.net:389 - trying regular connectionCould not open a connection
to server-03.my.company.net:389[15/06/09:16:20:54] - [Setup] Info Could not open a
connection to the server at server-03.my.company.net port 389 as
'uid=admin,ou=Administrators,ou=TopologyManagement,o=NetscapeRoot'.Please make
sure the server is up and running before using online mode,or use offline
mode.[15/06/09:16:20:54] - [Setup] Fatal Could not reconfigure the admin
server.[15/06/09:16:20:54] - [Setup] Fatal Exiting . . .Log file is
'/tmp/setup4jz4q9.log'
[server-03]# ps -ef | grep slapldapuser 15748 1 2 Jun06 ? 01:53:42 ./ns-slapd
-D /etc/dirsrv/slapd-server-03 -i /var/run/dirsrv/slapd-server-03.pid -w
/var/run/dirsrv/slapd-server-03.startpidroot 19243 18984 0 16:21 pts/0 00:00:00
grep slap
[server-03]# netstat -tap | grep LIST | grep -E "httpd|ldaps|ldap"
tcp 0 0 *:9830 *:*
LISTEN 15635/httpd.workertcp 0 0
*:ldap *:*
LISTEN 15748/./ns-slapdtcp 0 0 *:ldaps
*:* LISTEN 15748/./ns-slapd
Not sure why I can not connect back to the localhost when running ./setup-ds-admin.pl -u
EVEN when trying to connect on just 389 and not use TLS
Any ideas? Not sure what I am doing wrong here.