Error code 167 in DSCC
Hello,
I'm using the DSCC to administer two DS6 Server.
One of the Servers I can administer without getting any error messages.
However the second Server gives me some trouble.
1.
If I try to administer the Certificates I'll get the following error:
"The version of the instance /local/dsmmuc01 is more recent than dsadm ." Error code 167.
2.
The other problem is that I can not stop/start the server using the dscc. I'll get a window where I'm prompted to supply username and password of an administrator account. The error code is also 167.
What is the meaning of error code 167 ?
Any Idea what I can do to fix the problem ?
Regards,
Beate
[724 byte] By [
72716a] at [2007-11-27 2:01:38]
# 1
Hi Beate.It seems that your server has not been created with the current installed version of DS. Can we have the outputs ofdsadm --versionanddsadm info /local/dsmmuc01 ?Thanks,Carole.
# 2
Hi Carole,
these are the version numbers:
bash-3.00# ./opt/SUNWdsee/ds6/bin/dsadm --version
[dsadm]
dsadm: 6.0B2006.237.0035
[slapd 64-bit]
Sun Microsystems, Inc.
Sun-Java(tm)-System-Directory/6.0 B2006.237.0036 64-bit
ns-slapd: 6.0B2006.237.0036
Slapd Library: 6.0B2006.237.0036
Front-End Library: 6.0B2006.237.0036
bash-3.00# ./local/SUNWdsee/ds6/bin/dsadm --version
[dsadm]
dsadm: 6.0B2007.025.1703
[slapd 64-bit]
Sun Microsystems, Inc.
Sun-Java(tm)-System-Directory/6.0 B2007.025.1704 64-bit
ns-slapd: 6.0B2007.025.1704
Slapd Library: 6.0B2007.025.1704
Front-End Library: 6.0B2007.025.1704
Thank you for looking into this !
I had the BETA Version of DS6 first installed on the system.
When the official release became avalible I deinstalled the BETA Version and installed the official release.
Regards,
Beate
# 3
Hello,
please find below the data you requested.
bash-3.00# /opt/SUNWdsee/ds6/bin/dsadm info /local/dsmmuc01
Instance Path:/local/dsmmuc01
Owner:hvbldapr(hvbldapr)
Non-secure port: 10389
Secure port:10636
Bit format:64-bit
State:Running
Server PID:19035
DSCC url:ldap://172.108.248.18:3998
Sun Cluster resource group: -
SMF application name:-
Instance version:D-A00
bash-3.00# /local/SUNWdsee/ds6/bin/dsadm info /local/dsmmuc01/
Instance Path: /local/dsmmuc01
Owner:hvbldapr(hvbldapr)
Non-secure port:10389
Secure port:10636
Bit format:64-bit
State:Running
Server PID:19035
DSCC url: ldap://172.108.248.18:3998
SMF application name: -
Instance version:D-A00
bash-3.00#
Thank you for helping,
Regards,
Beate
# 4
Looking at your data, it seems that you have 2 versions of DS installed on your machine: one in /opt (which is the beta one) and one in /local (the RR one). Your instance has been created with the RR binaries. So you cannot use the beta binaries to manage it.
Error code 167 suggests that DSCC is using the beta binaries. Can you check which DSCC is running ?
# 5
Hello !
The dscc is running on the second machine (sunone02) together with the instance dsmmuc02.
output sunone02:
bash-3.00# ps -ef | grep dscc
noaccess63210Apr 23 ? 37:07 ./ns-slapd -D /var/opt/SUNWdsee/dscc6/dcc/ads -i /var/opt/SUNWdsee/dscc6/dcc/ad
bash-3.00# netstat -an | grep 6789
*.6789*.*00 491520 LISTEN
bash-3.00# /local/SUNWdsee/dscc6/bin/dsccsetup status
***
DSCC Application is registered in Sun Java (TM) Web Console
***
DSCC Agent is registered in Cacao
***
DSCC Registry has been created
Path of DSCC registry is /var/opt/SUNWdsee/dscc6/dcc/ads
Port of DSCC registry is 3998
***
bash-3.00# find . -name *dscc*
./var/opt/SUNWdsee/dscc6
./var/webconsole/webapps/dccapp/images/dscc.gif
./local/SUNWdsee/dsee6/man/man1m/dsccmon.1m
./local/SUNWdsee/dsee6/man/man1m/dsccreg.1m
./local/SUNWdsee/dsee6/man/man1m/dsccsetup.1m
./local/SUNWdsee/dscc6
./local/SUNWdsee/dscc6/bin/dsccmon
./local/SUNWdsee/dscc6/bin/dsccreg
./local/SUNWdsee/dscc6/bin/dsccsetup
./local/SUNWdsee/dscc6/dccapp/images/dscc.gif
I'm able to administer the Instance dsmmuc02 on sunone02. But I have problems with the instance dsmmuc01 on sunone01.
I administer both instances using the dscc on sunone02.
I don't have a dscc running on sunone01. The dscc is only installed on sunone02.
How can I teach the dscc to use the correct binaries, when administering an instance on sunone01 ?
Thank you for helping !
Regards,
Beate
# 6
DSCC on sunone02 is using cacao to manage instances on sunone01. Cacao is a container which runs a module called DSCC agent.
So in your case, it seems that your DSCC is talking to the beta version of the DSCC agent on sunone01. On sunone01, you have to check if cacao is running the RR DSCC agent or the beta one:
- run <path_RR>/SUNWdsee/dscc6/bin/dsccsetup status and check if the RR DSCC agent is registered
- run <path_beta>/SUNWdsee/dscc6/bin/dsccsetup status and check if the beta DSCC agent is registered
Unregister the beta DSCC agent:
<path_beta>/SUNWdsee/dscc6/bin/dsccsetup cacao-unreg
and register the RR one :
<path_RR>/SUNWdsee/dscc6/bin/dsccsetup cacao-reg
In any case, having 2 versions of the native packages installed on a same machine is not supported and is likely not to work.
One more question: which OS are you running?
# 7
Hello !
Thank you ! Problem is solved.
I unregistered the beta cacao and registered the RR cacao version.
/opt/SUNWdsee/dscc6/bin/dsccsetup cacao-unreg (beta)
/local/SUNWdsee/dscc6/bin/dsccsetup cacao-unreg (RR)
/local/SUNWdsee/dscc6/bin/dsccsetup cacao-reg (RR)
We are using Solaris 10.
I also had to enable the correct common-agent-container with svcs:
svcadm disable /application/management/common-agent-container-2:default
svcadm enable svc:/application/management/common-agent-container-3:default
then I could stop/start the cacaoadm:
bash-3.00# /usr/sbin/cacaoadm stop
bash-3.00# /usr/sbin/cacaoadm start
I'm now able to administer both Directory Server Masters using the DSCC.
I did not intent to run more than one version of cacao. Before I installed the DS6 I uninstalled the beta version. But obviously did I forget to uninstall cacao.
Thanks again,
Beate
