Can't start Directory Server instance
I just installed DSEE 6.2 and DSCC on a SPARC based Solaris 10 server. After following the Sun installation guide and accessing the DSCC panel, I tried to start a directory server instance. After entering all of the parameters, I cannot get the server instance started due to the following error.
Could not contact the DSCC agent on ldap. Use the command cacaoadm to check that the DSCC agent is installed and running on port 11162.
After this I verified the that cacaoadm was in fact running and operating on port 11162. I then tried changing the port numbers, and received the same error (although on a different port number). Can anyone advise me on a course of action to get this directory server up and running?
Thanks
Here is the dir listing:
-rw------- 1 nobody nobody 0 Oct 28 20:37 import
-rw------- 1 nobody nobody 16384 Oct 28 20:37 NetscapeRoot_uniquemember.db3
-rw------- 1 nobody nobody 41 Oct 28 20:37 DBVERSION
-rw------- 1 nobody nobody 16384 Oct 28 22:21 NetscapeRoot_uid.db3
-rw------- 1 nobody nobody 16384 Oct 28 22:21 NetscapeRoot_sn.db3
-rw------- 1 nobody nobody 16384 Oct 28 22:21 NetscapeRoot_givenName.db3
-rw------- 1 nobody nobody 16384 Oct 31 09:55 NetscapeRoot_parentid.db3
-rw------- 1 nobody nobody 16384 Oct 31 09:55 NetscapeRoot_objectclass.db3
-rw------- 1 nobody nobody 16384 Oct 31 09:55 NetscapeRoot_numsubordinates.db3
-rw------- 1 nobody nobody 90112 Oct 31 09:55 NetscapeRoot_nsuniqueid.db3
-rw------- 1 nobody nobody 204800 Oct 31 09:55 NetscapeRoot_entrydn.db3
-rw------- 1 nobody nobody 81920 Oct 31 09:55 NetscapeRoot_cn.db3
-rw------- 1 nobody nobody 40960 Oct 31 09:55 NetscapeRoot_ancestorid.db3
-rw------- 1 nobody nobody 16384 Oct 31 09:55 NetscapeRoot_aci.db3
-rw------- 1 nobody nobody 942080 Oct 31 10:14 NetscapeRoot_id2entry.db3
Similar Messages
-
Unxpected error"FAILED TO START DIRECTORY SERVER INSTANCE
hi
i was trying to install sun DS 6.3 in my system,everything is going good but while creating directory instance i get errors saying Unxpected error
"FAILED TO START DIRECTORY SERVER INSTANCE"
C:/DSEE/VAR/DSCC6/DCC/ADS
aftre that i get some errors showing
at "com.sun.directory.dcc.cli.setup.cmd ads create.perform<cmdadscreate.java:129>
com.sun.directory.dcc.cli.setup.cmd ads create.perform<cmdadscreate.java:59>
com.sun.directory.dcc.cli.setup.cmd ads create.perform<cmdadscreate.java:35>
com.sun.directory.dcc.cli.setup.cmd ads create.perform<cmdadsinitialize.java:55>
..... and few more errors displaying.
before that i start up dsccsetup/initialize
it asks for directory manager password:nnnn
reenter directory manager password:nnnn
after that i get the above errors
at the end it says
"Software installation is corrupted or incomplete"
i appreciate if someone can help me in this issue.hi,
thanks for the reply,
actually i havent known whats the certificate database password,as i'm new to DS 6.3,its hard for me,
and i installed tomcat 5.0.28,and jva,jre 1,6 ,and i get the when i setup installation it goes fine when i ask for dsccsetup initialize it asks for the token
A PIN IS REQUIRED TO ACCESS, i tried the same in other system with tomcat 5.5 with same OS XP it goes fine with no errors,i'm not sure that it may be caused by tomcat version,but still will be happy for your suggestion,
thanking you,
sasi -
Errors while installation "Failed to start Directory server instance"
hi
i was trying to install sun DS 6.3 in my system,everything is going good but while creating directory instance i get errors saying Unxpected error
"FAILED TO START DIRECTORY SERVER INSTANCE"
C:/DSEE/VAR/DSCC6/DCC/ADS
before that i start up dsccsetup/initialize
it asks for directory manager password:nnnn
reenter directory manager password:nnnn
after that i get the above errors
at the end it says
"Software installation is corrupted or incomplete"
i appreciate if someone can help me in this issue.Enterprise Linux is designed for industry standard server hardware. It supports a limited and well known range of peripherals in order to provide commercial support and high reliability.
If you need Linux for any Laptop or Desktop PC, choose a Desktop Linux distribution, like Ubuntu, Fedora, Debian, etc.
Your best option to run Enterprise Linux on non supported hardware is to use hardware virtualization like free Oracle Virtualbox. More information see http://www.oracle.com/technetwork/community/developer-vm/index.html. IMO, there is no compelling reason to try to install Enterprise Linux using dual boot or relying on 3rd party driver software. -
Can not start Messaging server in Sun Java System Messaging Server 6 2005Q1
Hi all,
I installed Sun Java System Messaging Server 6 2005Q1 from Solaris 10 DVD on Solaris 10.
After the installation, I got directory server, admin server running but messaging server not running. I can not start Messaging server (start smtp, http, pop, imap). I found in directory which I installed messaging server but I could not see script "start-msg" and "stop-msg".
# pwd
/opt/SUNWmsgsr/sbin
# ls
MoveUser ha_ip_config imquotacheck imsdirmig mkbackupdir
UpgradeMsg5toMsg6.pl hashdir imsbackup imsexport readership
configure imexpire imsconnutil imsimport reconstruct
control-params.txt iminitquota imscripter imsrestore relinker
deliver immonitor-access imsdaaci mboxutil useconfig
Any idea what might have gone wrong?
Thanks.Thanks.
I have a problem when I configure the Messaging Server (by running the /opt/SUNWmsgsr/sbin/configure script):
Hostname mailtest for this machine is not a fully qualified domain name. Please
correct this before attempting to configure Messaging Server. Please make sure
that your DNS is working properly.
<Press ENTER to continue> {"<" goes back, "!" exits}
Can you help me fix this problem?
Thanks. -
Can't start http server ASControl service
Hi, I installed http server from companion cd for oracle 10.2.0.3 but when configuration assistants was setting http server give the message failed.
Now i can´t start http server service.
INFO: El asistente de configuración "OC4J Configuration Assistant" se ha ejecutado correctamente
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Created a new file C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.1
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.2
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.3
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.4
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.5
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: Iniciando la ejecución de los asistentes de configuración
INFO: Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe startall
Command = C:\oracle\product\10.2.0\http_1/opmn/bin/opmnctlw.exe has failed
INFO: El asistente de configuración "Starting HTTP Server" ha fallado
*** Starting OUICA ***
Oracle Home set to C:\oracle\product\10.2.0\http_1
Configuration directory is set to C:\oracle\product\10.2.0\http_1\cfgtoollogs. All xml files under the directory will be processed
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.6
GRAVE: OUI-25031: Fallo de algunos asistentes de configuración. Se recomienda volver a probar los asistentes de configuración en este momento. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
1. Compruebe en el panel Detalles de la pantalla de Asistentes de Configuración los errores resultantes de los fallos.
2. Corrija los errores que causan estos fallos.
3. Seleccione los asistentes que han fallado y haga clic en el botón 'Reintentar' para volver a probarlos.
INFO: Usuario seleccionado: Sí/Aceptar
INFO: --------------------------------------
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands" contiene todos los comandos con fallos, saltados o cancelados. Este archivo se puede utilizar para ejecutar estos asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: El archivo de comandos "C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolAllCommands" contiene todos los comandos que van a ejecutar los asistentes de configuración. Este archivo se puede utilizar para ejecutar los asistentes de configuración fuera de OUI. Tenga en cuenta que puede que tenga que actualizar este archivo de comandos con contraseñas (si se aplican) antes de ejecutar el mismo.
INFO: Since the option is to overwrite the existing C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands file, backing it up
INFO: The backed up file name is C:\oracle\product\10.2.0\http_1\cfgtoollogs\configToolFailedCommands.bak.7
GRAVE: OUI-25029: Uno o más asistentes de configuración "recomendados" no han terminado correctamente. Si no se ejecuta correctamente algún asistente "recomendado", el sistema no se configurará correctamente.
INFO: Usuario seleccionado: Sí/Aceptar
INFO:
*** Fin de Instalación Página***
La instalación de Oracle Database 10g Companion Products ha sido correcta, pero han fallado, se han cancelado o se han saltado algunos asistentes de configuración opcionales.
ADVERTENCIA: ¿Seguro que desea salir?
INFO: Usuario seleccionado: Sí/Aceptaruser13078324 wrote:
How ?in cmd run this
netstat -an
and search for a line like
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
The important is TCP, 80 and keyword LISTENING
Other may differ -
New install of SJS Ent 8 on Solaris, can't start Application Server 8.1
Hello,
Appreciate in advance your help.
Just downloaded and installed SJS 8.1 on a new Sun Solaris 10 box. I'm able to run the IDE and have started the Tomcat server, but when attempting to start the SJS 8.1 application server, I get:
The Sun Java System Application Server 8.1 could not start.
More information about the cause is in the Server log file.
Possible reasons include:
- Port conflicts. (use netstat -a to detect possible port numbers already used)
- Incorrect server configuration
- Corrupted Deployed Applications
The problems are:
- There is no server.log file in the expected directory at /opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs
- I ran netstat -a, but could glean no useful information
- I have not modified the server configuration since the new install
- I have not deployed my application (since I can't start the server).
Forgive my ignorance since I'm not a Solaris expert. I would greatly appreciate your assistance.No difference in server.log after setting level="FINEST".
Don't know if it would help, but the contents of my server.log file follow:
[#|2006-09-25T15:39:46.485-0400|INFO|sun-appserver-pe8.1_02|javax.enterprise.tools.launcher|_ThreadID=10;|
/opt/sun/jstudio_ent8/jdk1.5.0_04/bin/java
-client
-Xmx512m
-XX:NewRatio=2
-Dcom.sun.aas.defaultLogFile=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/logs/server.log
-Djava.endorsed.dirs=/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/endorsed
-Djava.security.policy=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/server.policy
-Djava.security.auth.login.config=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/login.conf
-Dsun.rmi.dgc.server.gcInterval=3600000
-Dsun.rmi.dgc.client.gcInterval=3600000
-Djavax.net.ssl.keyStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/keystore.jks
-Djavax.net.ssl.trustStore=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/config/cacerts.jks
-Djava.ext.dirs=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/ext:/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1/lib/ext
-Djdbc.drivers=com.pointbase.jdbc.jdbcUniversalDriver
-Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
-Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
-Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
-Dcom.sun.enterprise.taglisteners=jsf-impl.jar
-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
-Dcom.sun.aas.configName=server-config
-Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
-Ddomain.name=myDomain1
-Djmx.invoke.getters=true
-Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
-Dcom.sun.aas.promptForIdentity=true
-Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
-Dcom.sun.aas.instanceRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/domains/myDomain1
-Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
-Dcom.sun.aas.domainName=myDomain1
-Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
-Dproduct.name=Sun-Java-System/Application-Server
-Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
-Dcom.sun.aas.configRoot=/opt/sun/jstudio_ent8/AppServ8.1UR2/config
-Djava.library.path=/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386/client:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/lib/i386:/opt/sun/jstudio_ent8/jdk1.5.0_04/jre/../lib/i386:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib:/usr/lib/lwp::/usr/lib
-Dcom.sun.aas.instanceName=server
-Dcom.sun.aas.processLauncher=SE
-cp
/opt/sun/jstudio_ent8/jdk1.5.0_04/lib/tools.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/activation.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/mail.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/admin-cli.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-admin.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-jstl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-logging.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee-svc.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jax-qname.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/dom.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxr-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jaxrpc-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/relaxngDatatype.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/saaj-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xsdlib.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jmxremote_optional.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/jsf-impl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/rmissl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xalan.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/xercesImpl.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ja.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_zh_CN.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_ko.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_fr.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-assemblytool_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-cmp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-rt_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/commons-launcher_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/deployhelp_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/j2ee_es.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-upgrade.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/appserv-ext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/install/applications/jmsra/imqjmsra.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/jaxm-api.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/imq/lib/fscontext.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/lib/ant/lib/ant.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbclient.jar:/opt/sun/jstudio_ent8/AppServ8.1UR2/pointbase/lib/pbembedded.jar
com.sun.enterprise.server.PEMain
start|#]
I do notice that the class path references jdk1.5.0_04. When installing SJS I selected the separately installed jdk1.5.0_07. Could that be causing the problem?
You have great patience. -
Unable to start directory server
We are getting error when starting directory server :
Recovery will take a while
Unable to start directory server 5.2The logs should contain more detailed information.
Check the file 'errors' inside the 'logs' directory of your instance for hints. -
Urgent: Can not start admin server
I installed Sun One directory server 5.1 on Solaris 8 01/01 version patched with Solaris 8 patch cluster.
In installation, there is error message
Can't start Admin server [home/iplanet/servers/start-admin > /var/tmp/aaax0aOBb 2>&1] (error: No such file or directory)
idskture only shows one ERROR message:
ERROR : Patch 111085-02 (SunOS 5.8: /usr/bin/login patch) is required but not installed.
But it seems fine since I reinstalled Solaris 8 01/01 release and install 5.1sp2 and with the same error message running idsktune, the installation of 5.1 but works fine.
Do you have any idea why the installation fail before I reinstlall Solaris 8?
Thanks,
IrisHave you checked the EAS logs, <MIDDLEWARE_HOME>user_projects\epmsystem1\diagnostics\logs\services
Cheers
John
http://john-goodwin.blogspot.com/ -
Can't start report server on windows 2000
I can't start report server with error code 186, my tnsname.ora is
REP60_DUQ = Rep60_DUQ
is it error?
who can tell me how to resolve it!!!but I have add tnsnames.ora following
Rep60_REPORT_SERVER =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = REPORT_SERVER)(PORT = 1951))
then I start report server with:
/PATH_TO_REPORTSERVER/report60_server start
it still says:
REP-0186: Daemon failed to listen to port
what is problem?
any thing must be done to activate changes in
tnsnames.ora?
null -
Unable to start the server Instance
Hello!!
I am using the JDeveloper(11g) IDE first time.I am reading the help provided with the IDE.Uptill now I know how to create an application.When I run the jsp file for first 2-3 times it runs well, but after that the error comes like "Failed to start the server instance" and due to this I unable to proceed my work.
Please tell me the exact solution to this error.When I run a JSPX file,following error comes in the log file:
http://Running application Sample1 on Server Instance DefaultServer...
Uploading credentials.
---- Deployment started. ---- Feb 21, 2009 4:07:56 AM
Target platform is (Weblogic 10.3).
Running dependency analysis...
2009-02-21 04:07:57.128: Writing WAR file to F:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Sample1\Sample1-ViewController-webapp
2009-02-21 04:07:57.394: Wrote WAR file to F:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Sample1\Sample1-ViewController-webapp
2009-02-21 04:07:57.41: Writing EJB JAR file to F:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Sample1\Sample1-Model-ejb
2009-02-21 04:07:57.488: Wrote EJB JAR file to F:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Sample1\Sample1-Model-ejb
2009-02-21 04:07:58.675: Writing EAR file to F:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Sample1
2009-02-21 04:07:58.847: Wrote EAR file to F:\Oracle\Middleware\jdeveloper\system\system11.1.1.0.31.51.56\o.j2ee\drs\Sample1
#### Deployment incomplete. #### Feb 21, 2009 4:08:01 AM
oracle.jdeveloper.deploy.DeployException
at oracle.jdevimpl.deploy.adrs.wls.Jsr88AdrsRemoteDeployer.initializeHelper(Jsr88AdrsRemoteDeployer.java:52)
at oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer.deployImpl(Jsr88RemoteDeployer.java:139)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdeveloper.deploy.common.BatchDeployer.deployImpl(BatchDeployer.java:82)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.WrappedDeployer.deployImpl(WrappedDeployer.java:39)
at oracle.jdeveloper.deploy.common.AbstractDeployer.deploy(AbstractDeployer.java:94)
at oracle.jdevimpl.deploy.fwk.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:436)
at oracle.jdeveloper.deploy.DeploymentManager.deploy(DeploymentManager.java:209)
at oracle.jdevimpl.runner.adrs.AdrsStarter$4$1.run(AdrsStarter.java:1316)
Caused by: oracle.rc.asadapter.connection.ConnectionException: J2EE Deployment SPI:260010Unable to connect to 't3s://127.0.0.1:7002' as user, 'weblogic'. Error received: null
at oracle.rc.asadapter.weblogic.connection.Weblogic10Jsr88Provider.getPresentation(Weblogic10Jsr88Provider.java:100)
at oracle.rc.asadapter.connection.AppServerConnectionImpl.getPresentation(AppServerConnectionImpl.java:65)
at oracle.jdevimpl.deploy.adrs.wls.Jsr88AdrsRemoteDeployer.initializeHelper(Jsr88AdrsRemoteDeployer.java:43)
... 11 more
Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: J2EE Deployment SPI:260010Unable to connect to 't3s://127.0.0.1:7002' as user, 'weblogic'. Error received: null
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
at oracle.rc.asadapter.weblogic.connection.Weblogic10Jsr88Provider.getPresentation(Weblogic10Jsr88Provider.java:97)
... 13 more
Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException: J2EE Deployment SPI:260010Unable to connect to 't3s://127.0.0.1:7002' as user, 'weblogic'. Error received: null
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:251)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:191)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:147)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
... 15 more
Caused by: java.io.IOException
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:156)
at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:240)
... 19 more
Caused by: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://127.0.0.1:7002: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:143)
... 23 more
Caused by: java.net.ConnectException: t3s://127.0.0.1:7002: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
... 31 more
Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
java.net.ConnectException: Connection refused: connect; No available router to destination
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
... 36 more
#### Cannot run application Sample1 due to error deploying to DefaultServer.
Application Sample1 stopped and undeployed from Server Instance DefaultServer
And on status bar the following message is shown:
Failed to start application in server instance
Please assist me with exact solution.
Please help me I am doing my final year project using this tool.And I am geting furstrated due to this problem.
Please reply quick!!
Edited by: [email protected] on Feb 22, 2009 10:53 PM -
IDS 5.x: Is a separate configuration directory server instance even needed?
Because iDS 5.x supports multiple database instances, why is there a need to suggest installing the directory server with a separate configuration directory server instance (on say port 390)?
In large multi-tiered iDS 4.x directory server implementations, using a single master configuration directory server is very cumbersome, so many implementations are using a local configuration directory server instance, on port 390 with the data instance on the usual port 389.
With the iDS 5.x release, we will be implementing local directory server instances, all on port 389, on all of our tiered LDAP servers. There will be no separate configuration directory server instance, as it is not needed.
At this point, I am questioning the "best practices" suggested by the SunOne documentation to use a separate configuration directory server instance. It does not need to be on a separate port now with iDS 5.x supporting multiple databases.
And I note that the present "/usr/sbin/directoryserver setup" script will not allow for a directory instance to be installed on port 390.
AdamYes, with iDS 5.X, it's much safer to have the o=NetscapeRoot tree served by the same instance as your corp/user tree. The separation approach was created to avoid the pitfalls when importing LDIF, but the -n argument to ldif2db lets you avoid such problems.
-
Can't start manager server on other machine from admin console
hi, m fredzh
i have weblogic 10.3.2 where i created a cluster named cluster1 on production mode
the machines and servers list as follow:
cluster1 192.168.1.100
--machine1
--server1 192.168.1.100
--machine2
-server2 192.168.1.101
i create nodemanager on machine2, and set the type as ssl, the listener address 192.168.1.101,
then login on 192.168.1.101, and run wlst.sh , nmEnroll and then start startNodemanaged.sh ..
start server2 on the admin console(on 192.168.1.100), failed and the log as follow:
can anbody help me, thank you..
==============================================================================
<Critical> <WebLogicServer> <localhost.localdomain> <managerServer2> <main> <<WLS Kernel>> <> <> <1286788326928> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:125)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:173)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: fredzh on 2010-10-12 下午6:54hi,Jay
i followed the steps as follow:
1、change prod mode to dev
2、modified the config.xml entrys on the all two servers:
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<credential-encrypted>test</credential-encrypted>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
3、enrolled the node, then started the two adminservers, started server2's nodemanager..server2 can be started from the cluster admin console.
4、change the dev mode to prod mode on admin console, it failed throw error:
"in production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean"
i checked the config.xml ,the entrys i had changed were not aotomatically encrypted,may i manually encryp the clear text value? ..follow is the config.xml :
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>cluster_domain</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>cluster_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<anonymous-admin-lookup-enabled>false</anonymous-admin-lookup-enabled>
<credential-encrypted>test</credential-encrypted>
<web-app-files-case-insensitive>false</web-app-files-case-insensitive>
<compatibility-connection-filters-enabled>false</compatibility-connection-filters-enabled>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<principal-equals-case-insensitive>false</principal-equals-case-insensitive>
<principal-equals-compare-dn-and-guid>false</principal-equals-compare-dn-and-guid>
<downgrade-untrusted-principals>false</downgrade-untrusted-principals>
<enforce-strict-url-pattern>true</enforce-strict-url-pattern>
<cross-domain-security-enabled>false</cross-domain-security-enabled>
</security-configuration>
<jta>
<security-interop-mode>default</security-interop-mode>
</jta>
<server>
<name>AdminServer</name>
<ssl>
<hostname-verifier xsi:nil="true"></hostname-verifier>
<hostname-verification-ignored>true</hostname-verification-ignored>
<export-key-lifespan>500</export-key-lifespan>
<client-certificate-enforced>false</client-certificate-enforced>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<inbound-certificate-validation>BuiltinSSLValidationOnly</inbound-certificate-validation>
<outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
<allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
<use-server-certs>false</use-server-certs>
</ssl>
<listen-port>7110</listen-port>
<listen-address></listen-address>
</server>
<server>
<name>server2</name>
<machine>machine2</machine>
<listen-port>7110</listen-port>
<listen-address>192.168.1.101</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>/opt/jdk1.6.0_21</java-home>
<bea-home>/root/Oracle/Middleware</bea-home>
<root-directory>/root/Oracle/Middleware/user_projects/domains/cluster_domain</root-directory>
<username>weblogic</username>
<password-encrypted>{AES}xhSI75AxXtXdMrCXRgA2uY5pfcxUGE9X4YXTjfe1XEY=</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>machine2</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>192.168.1.101</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<admin-server-name>AdminServer</admin-server-name>
</domain>
Edited by: fredzh on 2010-10-13 下午7:57 -
We are running Sun Directory Server 5 as part of our messageing server on RHEL 4. These systems are in development as a replacement for Netscape 4.X messageing servers that are being used onboard NOAA's research vessel fleet.
Is there any way to configure mutilple instances of Directory Server on a single Linux platform (without virtualization)?
Our email systems that are operated aborad reseach vessels may, or may not, have a internet connection while underway; even if they do the bandwith is typically limited to 128KBS per vessel (no directory replication possible).
As a result we have a requirement to host one directory for the local users on the ship and a second instance that holds the addresses of all
non local users in the enterprise mail system (Basically a lookup directiry). We periodicly overwrite the second instance (lookup directory) by importing an LDIF file from our shore based systems. Both instances of the Netscape Directory Server run on a single host, using port 389 and port 390.
Can we configure Sun Directory Server is a similar manner?
Note:
We use a custom MTA system to transport the email messages between ship and shore via cell phone, sat phones Inmarsat or sattelitte based WAN connectivity, dependant upon the ship's communications equipment suite. The MTA system provides ship to shore email services as long as one communications system is available.Yes you can have multiple intances running.
You can either start each instance on different port, or
setup an interface alias (ifconfig eth0:1 IP netmask NETMASK)
and start the second instance on that IP only.
I agree with the_dude to go for DS 6.3.
On 6.3 you can specify the listening interface/ports by using the commands
dsconf set-server-prop listen-address:127.0.0.1
dsconf set-server-prop listen-address+:192.168.1.1
dsconf set-server-prop secure-listen-address:127.0.0.1
dsconf set-server-prop secure-listen-address+:192.168.1.1
dsconf set-server-prop ldap-port:389
dsconf set-server-prop ldap-secure-port:636
hope it helps,
Giannis -
start http server powered by apache.I got such message:
'[alert]<5>...:FastCGI:CreateMUtex()failed
Syntax error on line 92 of c:/oracle/ora92/sqlplus/admin/isqlplus.conf:
Failed to create FastCGI application accept mutex'
my isqlplus.conf:
# Copyright (c) 2001, 2002, Oracle Corporation. All rights reserved.
# NAME
# isqlplus.conf
# PURPOSE
# Oracle HTTP Server directives for the iSQL*Plus server
# USAGE
# This file should be included in the Oracle HTTP Server
# "oracle_apache.conf" file.
# Enable handling of all virtual paths beginning with "/iplus/"
# Note: only /iplus/ is mapped, /iplus is not being mapped
<IfModule mod_alias.c>
Alias /iplus/ "C:\oracle\ora92\sqlplus\admin\iplus/"
# Disallow users from trying to access /iplus/ directory listing
<Directory "C:\oracle\ora92\sqlplus\admin\iplus">
AllowOverride None
Options FollowSymLinks
Order deny,allow
Allow from all
</Directory>
</IfModule>
# Maps all virtual paths beginning with "/isqlplus*" to the iSQL*Plus
# FastCGI application
<IfModule mod_alias.c>
ScriptAliasMatch ^/isqlplus(.*) C:\oracle\ora92\bin\isqlplus
ScriptAliasMatch ^/isqlplusdba(.*) C:\oracle\ora92\bin\isqlplus
<Directory "C:\oracle\ora92\bin">
AllowOverride None
Options FollowSymLinks
Order deny,allow
Allow from all
</Directory>
</IfModule>
# Enable handling of all virtual paths beginning with "/isqlplus"
<Location /isqlplus>
SetHandler fastcgi-script
Order deny,allow
# Comment "Allow ..." and uncomment the four lines "AuthType ..."
# to "Require ..." if Oracle HTTP authentication access is required
# for the http://.../isqlplus URL
Allow from all
#AuthType Basic
#AuthName 'iSQL*Plus'
#AuthUserFile C:\oracle\ora92\sqlplus\admin\iplus.pw
#Require valid-user
</Location>
# Enable handling of all virtual paths beginning with "/isqlplusdba".
# Note: Oracle HTTP authentication access must be configured to
# prevent unauthorized users performing DBA operations on
# the database
# Use the HTTP server utility script "htpasswd" to add users to the
# "iplusdba.pw" file.
<Location /isqlplusdba>
SetHandler fastcgi-script
Order deny,allow
AuthType Basic
AuthName 'iSQL*Plus DBA'
AuthUserFile C:\oracle\ora92\sqlplus\admin\iplusdba.pw
Require valid-user
</Location>
# Setup the iSQL*Plus FastCGI application.
<IfModule mod_fastcgi.c>
FastCgiServer C:\oracle\ora92\bin\isqlplus -port 8228 -initial-env iSQLPlusNumberOfThreads=20 -initial-env iSQLPlusTimeOutInterval=30 -initial-env iSQLPlusLogLevel=off -initial-env iSQLPlusAllowUserEntMap=none -idle-timeout 3600
</IfModule>I appreciate your help.
I have been offline for a long time since I had a business trip two week ago.
I can not start the apache http server, so it isn't on running status within NT services manager.
In fact, there is someting wrong---fail to create FastCGI when startup. Oracle system message tells me that syntax error exists on line 92 of isqlplus.conf but I don't know how to correct it.
Henry -
Can not start Weblogic server after Reordering the provider
Dear Geeks
I have ran into big trouble. I defined a new authentication provider in the weblogic and set the Control Flag to 'Required'.
I didn't realise that the user weblogic doesn't exist in the AD and because of AD's naming convention, we can not create a user named as weblogic.
Since, the installation was done using the weblogic user and the authentication provider has been changed, is there a way to start the server back up.
It is too critical and i am running out of time.
I would appreciate if anyone out there could help.
Thanks
Regards
ACMHi,
Goto Domain_home/config directory. Take one backup of config.xml, edit config.xml make Control Flag to SUFFICIENT against authentication provider that you have added. try to restart the server.
please mark if this helps.
Regards,
Kishore
Maybe you are looking for
-
I have ATT Yahoo! DSL and a bridged siemens speedstream dsl modem connected to a Airport Extreme Base Station (802.11n). They work fine usually but sometimes, more often than not, all the computers connected wirelessly and hard wired are not able to
-
Can I order a oracle 9i cd instead of downloading?
Can I order a oracle 9i cd instead of downloading? This download is not going to work anyway as it is too large for my connection speed.
-
Funtion to write numeric amount in words for printing cheques
Need to create a report to print cheques. The numeric amount of the cheque needs to written in words also on the line below the payee's name. eg. $100 = "One hundred" I would like to know if there is a function to do this task.
-
My iphone 4s went dead, recovered and dies twice or more times a day after that
My Iphone 4s was found dead during the day. I did a hard reset and manage to open it, asked me to restore it again and succesfully worked for less than a day. This is happening for the last 5 days. Today it went dead 5 times. I bought this device in
-
Why is iPhoto importing duplicates?
I am putting SD card into Mac mini and it is coming up with 2 on every photo on SD card. Weirdly, one version of the photo appears to be slightly darker than the other. This is driving me mad and taking up so much space.