Server(Admin) start is failing in WLST bt able to start using startWeblg.sh

Hi,
I'm a newbie to weblogic, i have installed wls 11g in sloaris SunOS ,Sun-Fire-T200)
Unable to start weblogic sever(Admin) through WLST, however when i'm using ./startWeblogic.sh, the server starting without any issues.
Issue occuring since the port change(Admin Server) done thru WLST.
Below is the error
wls:/offline/nmdomain/Server/AdminServer>startServer()Starting weblogic server ...
Server started successfully.
'WLST-WLS-1329227901091'
wls:/offline/nmdomain/Server/AdminServer>WLST-WLS-1329227901091: <Feb 14, 2012 8:58:26 AM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 17.0-b16 from Sun Microsystems Inc.>
WLST-WLS-1329227901091: <Feb 14, 2012 8:58:29 AM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
WLST-WLS-1329227901091:
WLST-WLS-1329227901091: There are 1 nested errors:
WLST-WLS-1329227901091:
WLST-WLS-1329227901091: weblogic.management.upgrade.ConfigFileHelper$ConfigFileException: [Management:141242]Invalid config version found at /appdata/wkst/cspt3/sunil/domains/nmdomain/config/config.xml version = 10
WLST-WLS-1329227901091: at weblogic.management.upgrade.ConfigFileHelper.isUpgradeNeeded(ConfigFileHelper.java:215)
WLST-WLS-1329227901091: at weblogic.management.upgrade.ConfigFileHelper.isUpgradeNeeded(ConfigFileHelper.java:60)
WLST-WLS-1329227901091: at weblogic.upgrade.domain.DomainUpgradeServerService.start(DomainUpgradeServerService.java:40)
WLST-WLS-1329227901091: at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
WLST-WLS-1329227901091: at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
WLST-WLS-1329227901091: at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:802)
WLST-WLS-1329227901091: at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:489)
WLST-WLS-1329227901091: at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
WLST-WLS-1329227901091: at weblogic.Server.main(Server.java:67)
WLST-WLS-1329227901091:
WLST-WLS-1329227901091: >
WLST-WLS-1329227901091: <Feb 14, 2012 8:58:29 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
WLST-WLS-1329227901091: <Feb 14, 2012 8:58:29 AM EST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
WLST-WLS-1329227901091: <Feb 14, 2012 8:58:29 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
WLST-WLS-1329227901091: Stopped draining WLST-WLS-1329227901091
WLST-WLS-1329227901091: Stopped draining WLST-WLS-1329227901091

Hi,
Firstly thanks for the suggestion.
Able to start the server thru WLST by passing parameters to startServer('..','..')
wls:/offline> startServer('AdminServer','nmdomain','t3://localhost:9999','weblogic','welcome1','/home/sunil/domains/nmdomain')
however at the end of the log i got few exceptions and the wls:/offline> is not appearing any more..
Below is the log and then error, pls help in trouble shooting the issue
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
.WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 192.168.120.21:9999 for protocols iiop, t3, ldap, snmp, http.>
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on 127.0.0.1:9999 for protocols iiop, t3, ldap, snmp, http.>
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 3.182.40.53:9999 for protocols iiop, iiop, t3, t3, ldap, ldap, snmp, snmp, http, http.>
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 3.182.40.17:9999 for protocols iiop, iiop, t3, t3, ldap, ldap, snmp, snmp, http, http.>
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <WebLogicServer> <BEA-000329> <Started WebLogic Admin Server "AdminServer" for domain "nmdomain" running in Production Mode>
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
WLST-WLS-1329384454332: <Feb 16, 2012 4:28:56 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
WLST-WLS-1329384454332: Exception in thread "[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
.Could not connect to the server to verify that it has started. The error returned is: javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://localhost:9999: Destination unreachable; nested exception is:
        java.net.SocketTimeoutException: Read timed out; No available router to destination]
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 1261, in startServer
File "<iostream>", line 1848, in raiseWLSTException
WLSTException: Error occured while performing startServer : Could not start the server, the process might have timed out or there is an Error starting the server. Please refer to the log files for more details.
wls:/offline> wls:/offline> wls:/offline> wls:/offline> wls:/offline> wls:/offline> wls:/offline> wls:/offline> wls:/offline> wls:/offline> WLST-WLS-1329384454332: IOException when running WLSTProcess
java.io.IOException: Stream closed
at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:145)
at java.io.BufferedInputStream.read1(BufferedInputStream.java:255)
at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.management.scripting.utils.WLSTProcess.run(WLSTProcess.java:78)
at java.lang.Thread.run(Thread.java:619)
WLST-WLS-1329384454332: Stopped draining WLST-WLS-1329384454332
Edited by: 907822 on Feb 16, 2012 2:03 AM

Similar Messages

  • Appl Server Admin Console: Login Failed

    Hi,
    I am forget my username and password when i installed J2EE appl server. I would like to reset them to new values in order to get in into the admin console. How can reset my login info? Can anyone help?
    Thank you
    Latha

    You could try this:
    http://java.sun.com/j2ee/1.4/docs/relnotes/troubleshooting.html#1026910
    Or reinstall the appserver.

  • IChat server admin Service Running, status not available

    X-Serve running 10.6.8
    I noticed the other day thaat when I look at the iChat service in Server Admin, I observed the following:
    iChat service is: Running
    Start Time: Not Available
    Domain: Not Available
    Client Connections: Not Available
    The log screen says No Log Files exist
    I have seen similar screens when there was a slight lag in server admin gathering information to display on screen.  This stays this way indefinately.  The service is working as far as I can tell, IE people can log in, add each other, and chat.  A log file is in fact being used and updated (/var/jabberd/message_archive/)
    I noticed this because I was trying to autobuddy.sh, I script I use often to update when I add new users to the organization so they show up in everyones group list.  I attempted to stop the service from the command line using:
    #:serveradmin stop jabber
    #:jabber: state = RUNNING
    and was never able to stop iChat.  The system behaves the same after a reboot.  I am not sure what to do, or what the actual problem is.  The only thing besides a reboot that I tried was a permission repair from within the OS.
    In the log below I removed some user specific information because they are user names for users on my network.  This server and service is internal only.
    the console logs I have this:
    Nov 30 10:29:55 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:30:15: --- last message repeated 2 times ---
    Nov 30 10:30:19 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:31:05 aphrodite jabberd/router[353]: message_log received a message with empty body
    Nov 30 10:49:17 aphrodite com.mycompany.autobuddy[83710]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:12:34 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 11:12:34 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 11:19:17 aphrodite com.mycompany.autobuddy[87010]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:49:17 aphrodite com.mycompany.autobuddy[90323]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: checking user "jimrumrillcotaoilcom" access for service "chat"
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 11:54:37 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 12:03:14 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: mbr_check_service_membership returned 2
    Nov 30 12:03:14 aphrodite jabberd/c2s[354]: od_auth_check_service_membership: no access restrictions found
    Nov 30 12:03:32 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:04:26: --- last message repeated 2 times ---
    Nov 30 12:05:25 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:06:26: --- last message repeated 1 time ---
    Nov 30 12:06:26 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:06:57: --- last message repeated 1 time ---
    Nov 30 12:07:27 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:08:28: --- last message repeated 1 time ---
    Nov 30 12:08:28 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:09:26: --- last message repeated 1 time ---
    Nov 30 12:09:29 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:09:59: --- last message repeated 1 time ---
    Nov 30 12:10:30 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:11:30: --- last message repeated 1 time ---
    Nov 30 12:11:30 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:12:00: --- last message repeated 1 time ---
    Nov 30 12:12:31 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:13:32: --- last message repeated 1 time ---
    Nov 30 12:13:32 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:14:26: --- last message repeated 1 time ---
    Nov 30 12:14:33 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:15:34: --- last message repeated 1 time ---
    Nov 30 12:15:34 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:16:35: --- last message repeated 1 time ---
    Nov 30 12:16:35 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:17:05: --- last message repeated 1 time ---
    Nov 30 12:17:36 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:18:37: --- last message repeated 1 time ---
    Nov 30 12:18:37 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:19:17: --- last message repeated 1 time ---
    Nov 30 12:19:17 aphrodite com.mycompany.autobuddy[94140]: /usr/local/Scripts/auto_buddy.sh: line 2: /usr/sbin/jabber_autobuddy: No such file or directory
    Nov 30 12:19:38 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:19:53: --- last message repeated 1 time ---
    Nov 30 12:20:39 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:20:45: --- last message repeated 1 time ---
    Nov 30 12:21:40 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:22:10: --- last message repeated 1 time ---
    Nov 30 12:22:41 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:22:47: --- last message repeated 1 time ---
    Nov 30 12:23:42 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:24:26: --- last message repeated 1 time ---
    Nov 30 12:24:43 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:25:10: --- last message repeated 1 time ---
    Nov 30 12:25:44 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:26:45: --- last message repeated 1 time ---
    Nov 30 12:26:45 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:27:16: --- last message repeated 1 time ---
    Nov 30 12:28:24 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Nov 30 12:29:00: --- last message repeated 3 times ---
    Nov 30 12:29:00 aphrodite servermgrd[84]: servermgr_jabber[W]: detailed service status not available until network configuration completed
    Any help on what might be going on or a push in a direction would be greatly appreciated.
    Thanks!

    Well I searched the forums here and I found some similar issues, however the fix's I was directed too did not resolve the problem. 
    I did notice this today after reading a post regarding the use of the .local domain name, and fixing that fixes this issue:
    When i selected my server on the left hand side of server admin, click on settings at the top (the gear) then on Network, I see:
    Ethernet 1 (eth0) IPv4 192.1.1.4 Aphrodite.local
    I am not sure where the .local is coming from.  This is an internal server and has been configured with a FQDN for 2 years now, aphrodite.cotaoil.net.  On the server, the only other place I see the .local, is in system preferences, sharing, at the top it has my fqdn, but when I click on edit, it has a local host field that says Aphrodite, with a .local greyed out after, or ghosted.
    When I use the command changeip -checkhostname I recieve:
    changeip -checkhostname
    Primary address     = 192.1.1.4
    Current HostName    = aphrodite.cotaoil.net
    The DNS hostname is not available, please repair DNS and re-run this tool.
    dirserv:success = "success"
    the hostname not available message is new (well I know at some point in the not too distant past I did not have this message) so I am not sure if an update broke this or not but basically I am not sure where to go from here.
    The DNS settings are set the same as they were when I originally set up the server.  Reviewing DNS logs, I do not see anything abnormal.
    additionally when I run scutil i get:
    aphrodite:~ root# scutil --get LocalHostName
    Aphrodite
    aphrodite:~ root# scutil --get ComputerName
    Aphrodite.cotaoil.net
    I am a little stumped as to where to go from here.  I believe based on some other posts Ive read that this may have something to do with why I cannot see any iChat status and am recieving the dreaded "detailed service status not available until network configuration completed"
    Thanks for any and all thoughts.  Currently reviewing Hoffs tutorials, but I used combined Hoff tutorials and apple server guides when originally set up the server.  Please let me know what I did wrong (besides my internal IP range)

  • Start VM failed: Domain CCCCCCCC already exists with ID NNN

    Hi,
    I try to start an Oracle VM (currently stopped), the job related to the start action fails and the VM is not started.
    The job log is:
    Message:  OVMAPI_6000E Internal Error: OVMAPI_5001E Job: 1427440127270/Start Vm: ora-aa-u004/Start Vm: ora-aa-u004, failed. Job Failure Event: 1427440128820/Server Async Command Failed/OVMEVT_00C014D_001 Async command failed on server: ovms-aa-us001.mgmt.mydom.com. Object: ora-aa-u004, PID: 32049, Server error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000b3397000b8916714/VirtualMachines/0004fb0000060000b17c866636533d63/vm.cfg'] failed (1): stderr: Error: Domain '0004fb0000060000b17c866636533d63' already exists with ID '199' stdout: Using config file "/OVS/Repositories/0004fb0000030000b3397000b8916714/VirtualMachines/0004fb0000060000b17c866636533d63/vm.cfg". , on server: ovms-aa-us001.mgmt.mydom.com, associated with object: 0004fb0000060000b17c866636533d63 [Fri Mar 27 08:08:48 CET 2015] [Fri Mar 27 08:08:59 CET 2015]
    Previously I tried to migrate it to another Server of the same pool, the migration Job was successful, the VM resulted running, but actually it was cycling rebooting itself every minutes, after a few steps of the booting process. So I killed it (stopped it) and migrate it back (while in a stopping state) to the original server. When I start it on the original Server, I get the error above.
    Please note that "xm list" on the Server doesn't show that this VM 0004fb0000060000b17c866636533d63 is running, nor that any VM with ID 199 is running.
    Any suggestion? Thanks
    Oscar

    I don't think that advsiing to change the UUID inside the vm.cfg file is too beneficial. It might solve the immediate problem, but it won't make the "ghost" dom go away, which will need a OVMS boot to get rid off.
    Further more it seems like Oracle has fixed this issue and will likely roll the patch out in an upcoming update to xen. Users who have OVM under CSI can request a patch mentioning this BUG: 20687187
    I just received that patch and I will try that out tonight.
    Cheers,
    budy

  • Mac OS X Leopard Server (PPC) "forgets" settings if Server Admin is left on

    I'm not sure that I'm posting this question in the right place.
    I have a QuickSilver 2001 Power Macintosh G4 (867MHz, 2x120GB PATA hard drives, 1.5GB RAM) running a fully up-to-date copy of Mac OS X Server 10.5.2. The hardware appears to be in good shape. The disks are new and I'm very certain the RAM is good. Apple Hardware Diagnostics finds no problem with the computer itself.
    Normally, this system is very reliable. It works as a primary domain controller for Windows PCs. However, if by some chance I forget to close the Server Admin application, and the machine sits for a while without use, Server Admin will claim that "no services are configured" when I return. I also saw this problem on the 10.5 and 10.5.1 releases.
    The services really do appear to stop working when this happens. I have Open Directory, DNS, DHCP and SMB configured. All four will stop responding.
    Rebooting the computer usually gets the services going again, and Server Admin will then function properly. However, I always have to reconfigure SMB to be a primary domain controller.
    Any ideas? Since this is just a test system, I did try wiping the disks and doing a reinstallation. The problem persisted.
    I think this may be PowerPC specific, as I have an Intel Mac mini set up much the same way (Mac OS X 10.5.2 server, 4GB RAM, 320GB hard disk) and it does not appear to suffer from this issue.

    Yes, I just discovered this problem on my own machine.
    I just wanted to check some settings and discovered that the behaviour of the GUI of Server Admin was somewhat "erratic": First this "no services are configured" message. Some of the configured servers were marked with the usual green "up and running" bullet, others dark grey - those were normally configured and running and clicking the appropriate line seemed to force Server Admin to check the actual state and then turned also green. But sometimes configuration pages were "greyed out", or while switching through the tabs Server Admin claimed that where were "unsaved changes" which should be saved (or discarded).
    And then SMB: this was light grey, as usual when a service is not running and clicking on it I browsed through the configuration tabs - everything seemed ok (all my settings were correctly shown, configured as PDC with right domain name etc.) - and I started the service. Then suddenly the configuration settings changed to the default settings - no more PDC, but a "standalone server" with workgroup name "WORKGROUP"...
    Looks for me, as if Server Admin lost it's "source" file for the configuration (the file in /var/db/smb.conf says, that it is automatically generated -- does somebody were the source file is stored?)...

  • Start-up failed after software update

    Hi,
    I have N73. I decided to update the software today. I downloaded the new Nokia Software Updater, connected the phone by USB and process has started. Everything went fine, phone has been updated successfully. But when I tried to switch it on the message appeared on the screen - Phone start-up failed. Contact the retailer. I used v1.3.95 en Software Updater. I do not remember what software version did I have, it began from 3..... and the new software was 4........ Last time I updated the software everything was fine. I think this is the problem with the new software.
    Could you advice please?
    Thank you

    22-Sep-200704:38 AM
    griellwe wrote:
    Thanks. I returned phone to Nokia repair centre and it should be repaired in 28 days.
    My goodness, 28 days is forever. Do they loan you a replacement phone or something?
    I don't get a replacement phone here. I'm already unhappy if it takes 2 days to repair.

  • Mailman, Server Admin, and mailmanctl launchd item

    I upgraded my Mailman to 2.1.12 today, and I had some of the usual problems, some not so usual. I'm used to seeing that mailing lists are stopped in Server Admin, but I would like to be able to see mailman logs in Server admin, and I would prefer not to have to create my own launchd item to execute the mailmanctl command. Logs are an old problem, but the mailmanctl launchd problem is new. Are there fixes for these two problems? I configured with
    ./configure --prefix=/usr/share/mailman --with-var-prefix=/var/mailman --without-permcheck
    Thanks.

    I tried it, thanks. Mailman didn't like the config, though. It warned me about using group id "_postfix" and wouldn't distribute until I had reconfigured using --with-mail-gid=_mailman instead of --with-mail-gid=_postfix. Plus I still don't get any connectivity out of Server Admin. I had already edited the launchd file for use with my earlier replacement, so I guess I'll go back to that. It works, I just wanted fewer Server Admin orphans. I have to toss things anytime there's a system update, anyway. Thanks again.

  • Server Admin - File Sharing - Show "invisibles"

    Leopard Server, v10.5.7 - Server Admin, File Sharing: Would like to be able to see system directories (such as /var, /bin, /private) in the Volumes::Browse window. I find it odd that "mach_kernel.ctfsys" =is= visible but other system files and folders are not. Is there any way to increase the verbosity of the Volumes::Browse window?
    Thank you in advance.
    B. Bodger
    Oklahoma City, OK

    Thank you for your reply.
    We were toying with the idea of giving a few admins remote access to /etc/ and/or /dev/ without them having to access via ssh. Not a very big deal.
    B. Bodger

  • Not able to start a VM

    Hello,
    one of my VM was working fine, then i copied the entire VM from one OVM server to another. Now I am not able to start that VM.
    # xm create vm.cfg
    Using config file "./vm.cfg".
    Started domain OEL5u2 (id=25)
    It does give me the vm ID but it is not listed under "xm list"
    # xm list
    Name ID Mem VCPUs State Time(s)
    Domain-0 0 952 8 r----- 14808.1
    again i have to do xm create ..and the story repeats...
    I looked into logs and i see following:
    [2010-02-04 22:47:52 23777] INFO (XendDomain:1180) Domain OEL5u2 (25) unpaused.
    [2010-02-04 22:47:57 23777] WARNING (XendDomainInfo:1898) Domain has crashed: name=OEL5u2 id=25.
    [2010-02-04 22:47:57 23777] ERROR (XendDomainInfo:2032) VM OEL5u2 restarting too fast (Elapsed time: 4.960329 seconds). Refusing to restart to avoid loops.
    [2010-02-04 22:47:57 23777] DEBUG (XendDomainInfo:2748) XendDomainInfo.destroy: domid=25
    [2010-02-04 22:47:58 23777] DEBUG (XendDomainInfo:2221) Destroying device model
    [2010-02-04 22:47:58 23777] INFO (image:553) OEL5u2 device model terminated
    what's up with " restarting too fast" and how to avoid that ??
    -thnx

    here is the problem....
    My VM is still fine...I moved it back to the old host and it started working again..
    moved it back to the new host and it crashed again..
    it turned out to be that this new host had 72 GB of memory...hence the VM was crashing.
    I made the OVM server to see only 64 GB of memory and then I was able to start the VM on new host as well..
    then did some googling and came across this Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=448115
    Now I need to check whether i am upto the latest patch vesion for Oracle VM
    # cat /etc//redhat-release
    Oracle VM server release 2.2.0
    # uname -a
    Linux test_ovm 2.6.18-128.2.1.4.9.el5xen #1 SMP Fri Oct 9 14:57:31 EDT 2009 i686 i686 i386 GNU/Linux
    checking for any patches released after Oracle VM 2.2.0
    thnx
    Edited by: Dheeraj.Kabra on Feb 5, 2010 5:11 AM

  • Server admin fails to start tomcat only

    Hi,
    we just upgraded our server from 10.3 to 10.4. after the upgrade - the server admin tools fail to start tomcat only. sooooo when i start tomcat only service - the app says its running. but i can't connect to port 80 to show me the default page or any of my webapps.
    whats werid is that:
    it tries to startup JBoss
    instead of Tomcat.
    When I run the settings command I see:
    # serveradmin settings appserver
    appserver:jbossConsoleURL = "https://tels-berkeley.local:40000"
    appserver:configurationType = "run_TOMCAT_not_JBOSS"
    appserver:netbootIsBroken = "YES"
    appserver:allConfigurations:arrayindex:0 = "default"
    appserver:allConfigurations:arrayindex:1 = "deploy-cluster"
    appserver:allConfigurations:arrayindex:2 = "deploy-standalone"
    appserver:allConfigurations:arrayindex:3 = "develop"
    appserver:configurationName = "deploy-standalone"
    appserver:netbootClientURL = ""
    This looks like it is should use tomcat but it doesn't. After running
    serveradmin start appserver
    I ran:
    ps auxww | grep java
    Which gave me:
    appserve 1087 96.0 4.5 359912 58384 ?? R 11:24AM
    0:12.58 /usr/bin/java -server -Xmx100M
    -Djboss.server.temp.dir=/var/tmp/jbosstmpdata1083
    -classpath /Library/JBoss/3.2/bin/run.jar org.jboss.Main -c
    deploy-standalone
    however, if i stop the services and start tomcat manaully with ./startup.sh it works fine.
    the logs say nothing. does anyone have a clue whats going on? where i can investigate.
    thnks
    Anthony

    I've been doing a little investigating, and I think I'm seeing the cause of the problem, but I don't know how to fix it.
    When I do a "tail /var/log/servermgrd/servermgrderrorlog" on the server, I don't get normal error log lines. Instead, I get the text that you see when you type "serveradmin", namely:
    ============================================
    Usage: serveradmin [-dhvx] [list | start | stop | status | fullstatus | settings | command] [<service_key> [ = <value> ]]
    -h, --help display this message
    -v, --version display version info
    -d, --debug print command
    -x, --xml print output as XML plist
    Examples:
    serveradmin list
    --Lists all services
    serveradmin start afp
    --Starts afp server
    serveradmin stop ftp
    --Stops ftp server
    serveradmin status web
    --Returns current status of the web server
    serveradmin fullstatus web
    --Returns more complete status of the web server
    serveradmin settings afp
    --Returns all afp configuration parameters
    serveradmin settings afp:guestAccess
    --Returns afp guestAccess attribute
    serveradmin settings afp:guestAccess = yes
    --Sets afp guestAccess to true
    serveradmin settings
    --Takes settings commands like above from stdin
    serveradmin command afp:command = getConnectedUsers
    --Used to perform service specific commands
    serveradmin command
    --Takes stdin to define generic command that requires other parameters
    ============================================
    This shows up repeatedly in the error log, as if it were trying to use serveradmin to perform tasks, but is instead just getting the standard help message back...
    Anyone have clue as to why this would be the case?

  • Not able to start SOA managed server first time with node manager by WLST

    Hi all,
    I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
    Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
    But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
    Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
    In server log file I am getting the following error : -
    Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
    I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
    If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
    Can anyone please tell me what can be the issue?
    Thanks in Advance!!!
    Edited by: 008 on Dec 6, 2012 7:53 PM

    Hi,
    I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
    If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
    The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
    I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
    username=type-the-username-here
    password=type-the-password-here
    Cheers,
    Vlad

  • Creating Open Directory Replica fails with Server Admin Error Value 1127

    Hallo,
    I have seen a lot of similar threads here and they were helpful up to a certain point, but in the end, they did not solve my problem.
    Currently, it comes down to this. The Server Admin Error message ist really meaningless and I could not find a single for the error value on the whole wide web. As such, I switched to the command line versions of the tools involved to geht more meaningful results. It worked. Specifically, creating a replica of an openldap master means using slapconfig.
    When executing
    slapconfig -createreplica master.ourdomain.com diradmin
    as root on the prospective replica machine, I get the following error message:
    ssh command failed with status 127
    That command is not allowed with the root account via public key authentication.
    That makes perfect sense to me, but how is it meant to work then?
    Executing slapconfig as admin tells me that this tool is to be executed as root. On the other hand, root login via ssh is not allowed in Mac OS X by default, which seems fine to me. I even changed /etc/sshd_config on the Open Directory Master machine to "PermitRootLogin yes". However, neither reloading ssh using launchctl nor restarting the whole server made this setting operational. Trying to login from command line as root still tells me:
    root login is not permitted to this machine via public key authentication.
    While this is the current state where I need help urgently, I changed some other things before. I tell about to exclude these issues as possible reason of failure. I got this message for quite a while:
    Replica Setup failed : This machine does not have a valid computer name
    I was sure, this machine meant the target machine, the open directory master, because the domain had changed there once before I had taken over responsibility as an admin in this environment. And in fact, changeip disguised an issue there. The command proposed by changeip to fix the situation did not seem appropriate because this machine is multihomed with a public and a private IP adress. Proper name resolution is available for both interfaces including reverse lookup. I dont like this setup, but it was the only way to get mail service running smoothly. Running changeip on the machine itself using these arguments
    changeip /LDAPv3/127.0.0.1 internalIP internalIP old.ours.com current.ours.com
    reported success in updating password server, open directory, both interfaces, hostconfig (which in fact did not change) and samba. It reported an issue with kadmin which is related to Kerberos (we dont use Kerberos yet).
    Changing the hostname of the server using changeip did not solve the issue. I then found the hint to check with scutil. This showed that the Hostname was not set on the prospective replica machine. (A question aside: in how many place is the hostname stored? The traditional /etc/hostname has gone, but seems to be replaces with several other configuration files and databases. I cant see this as an advantage). Setting the hostname using scutil worked fine. However, it did not solve the problem either. At least, slapconfig now started to complain about not being able to log in as root instead of failing from the start.
    I also checked all log files on bboth machines that might have to do with openldap, as there are /var/log/slapd.log, /var/log/system.log and /Library/Log/slapconfig.log. I also checked the log of th layer on top of openldap which is /Library/Log/DirectoryService.server.log. None of them revealed anything noticeable beside a lot of of entries that I have googled in the last few hours and which all dont seem to be associated with the problem in question.
    I will take a break now, but I have to fix this until tomorrow and I hope to get the ultimate hint from you, dear reader.
    Thanks and bye, Christian Völker

    ssh command failed with status 127
    That command is not allowed with the root account via public key authentication.
    Initial OD replication takes place via 'ssh'. If you have 'sshd' configured on the OD Master to authenticate with public keys then the OD replica will not be able to communicate with the OD Master via 'ssh'. You must configure the OD Master to use 'ssh' with password authentication and root login enabled.
    Demote the replica back to standalone. Stop any services that you may have running on the primary network interface. Then stop any services that you may have running on the secondary network interface. In the 'Network' System Prefpane remove the IP number from the secondary interface then deactivate the secondary network interface.
    Assign the private IP address and hostname that you wish to use for the replica to the primary network interface. Assign the 'public' IP number to the secondary interface. Check the DNS to see that the IP address and hostname for the primary network interface resolve both forward and reverse for the hostname of the replica that you have chosen. If it does not, fix your DNS before proceeding.
    In the 'Sharing' System Prefpane, change the name of the machine to the hostname (server.domain.tld) of the replica that you have chosen. Then use 'changeip -checkhostname' to see if the IP/hostname matches. Fix it if it doesn't.
    Then configure the /etc/sshd_config file on the OD master like this:
    \# Authentication:
    PermitRootLogin yes
    PasswordAuthentication yes
    PubkeyAuthentication no
    and the /etc/ssh_config file on the OD replica like this:
    PasswordAuthentication yes
    PubkeyAuthentication no
    Then from the OD replica as the 'root' user issue:
    slapconfig -createreplica <ODMasterIPorFQDN> <diradmin user>
    Make sure that the 'diradmin' user's password contains only alpha-numeric characters -no 'option-characters' or symbols, change it first if it does. Once the process completes, reactivate the secondary interface for the 'public' IP and check the configuration of services that will be using that IP, then start your other services. Secure the 'ssh' service on both machines to disable password authentication and 'root' logins.

  • Server appears to start but fails when accessed

    I have installed (and re-installed) the application server (version 8.2) and it appears to be successful - I have just taken all the defaults along the way.
    When I try http://localhost:8080/ it fails every time. The log is below.
    the PATH variable is set to: C:\Sun\AppServer1\bin;C:\Program Files\Java\jdk1.5.0_05\bin
    Can anyone give me some suggestions as to what I have done wrong, please?
    Log:
    [#|2006-05-22T11:30:08.234+0100|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2006-05-22T11:30:08.234+0100|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Program Files/Java/jdk1.5.0_05\bin\java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/AppServer1/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/AppServer1/lib/endorsed
    -Djava.security.policy=C:/Sun/AppServer1/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/AppServer1/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/AppServer1/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/AppServer1/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_05/jre/lib/ext;C:/Sun/AppServer1/domains/domain1/lib/ext;C:/Sun/AppServer1/derby/lib
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -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=domain1
    -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=C:/Sun/AppServer1/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -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=C:/Sun/AppServer1/config
    -Djava.library.path=C:\Program Files\Java\jdk1.5.0_05\jre\bin\client;C:\Sun\AppServer1\lib;C:\Sun\AppServer1\lib;C:\Program Files\Java\jdk1.5.0_05\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Sun\AppServer1\lib;C:\Sun\AppServer1\bin;C:\Sun\AppServer1\lib;C:\Sun\AppServer1\bin;C:\Sun\AppServer1\bin;C:\Sun\AppServer1\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH;C:\Program Files\Novell\ZENworks\;C:\DOCUME~1\sasmith\LOCALS~1\Temp\XrefTemp;C:\Program Files\Java\jdk1.5.0_05\bin;C:\Sun\AppServer\bin;,�ut;Z:.;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Program Files/Java/jdk1.5.0_05/lib/tools.jar;C:/Sun/AppServer1/lib/appserv-rt.jar;C:/Sun/AppServer1/lib\activation.jar;C:/Sun/AppServer1/lib\admin-cli.jar;C:/Sun/AppServer1/lib\appserv-admin.jar;C:/Sun/AppServer1/lib\appserv-cmp.jar;C:/Sun/AppServer1/lib\appserv-ext.jar;C:/Sun/AppServer1/lib\appserv-jstl.jar;C:/Sun/AppServer1/lib\appserv-upgrade.jar;C:/Sun/AppServer1/lib\commons-launcher.jar;C:/Sun/AppServer1/lib\commons-logging.jar;C:/Sun/AppServer1/lib\dom.jar;C:/Sun/AppServer1/lib\j2ee-svc.jar;C:/Sun/AppServer1/lib\j2ee.jar;C:/Sun/AppServer1/lib\jax-qname.jar;C:/Sun/AppServer1/lib\jaxr-api.jar;C:/Sun/AppServer1/lib\jaxr-impl.jar;C:/Sun/AppServer1/lib\jaxrpc-api.jar;C:/Sun/AppServer1/lib\jaxrpc-impl.jar;C:/Sun/AppServer1/lib\jmxremote.jar;C:/Sun/AppServer1/lib\jmxremote_optional.jar;C:/Sun/AppServer1/lib\jsf-api.jar;C:/Sun/AppServer1/lib\jsf-impl.jar;C:/Sun/AppServer1/lib\mail.jar;C:/Sun/AppServer1/lib\relaxngDatatype.jar;C:/Sun/AppServer1/lib\rmissl.jar;C:/Sun/AppServer1/lib\saaj-api.jar;C:/Sun/AppServer1/lib\saaj-impl.jar;C:/Sun/AppServer1/lib\xalan.jar;C:/Sun/AppServer1/lib\xercesImpl.jar;C:/Sun/AppServer1/lib\xsdlib.jar;C:/Sun/AppServer1/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/AppServer1/imq/lib/jaxm-api.jar;C:/Sun/AppServer1/imq/lib/fscontext.jar;C:/Sun/AppServer1/lib/ant/lib/ant.jar
    com.sun.enterprise.server.PEMain
    start
    display
    native|#]
    [#|2006-05-22T11:30:14.142+0100|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\AppServer1\imq\bin].|#]
    [#|2006-05-22T11:30:14.142+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
    [#|2006-05-22T11:30:14.913+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
    [#|2006-05-22T11:30:14.913+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2006-05-22T11:30:15.404+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2006-05-22T11:30:16.075+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
    [#|2006-05-22T11:30:16.085+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
    [#|2006-05-22T11:30:16.916+0100|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3700"|#]
    [#|2006-05-22T11:30:16.926+0100|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3820"|#]
    [#|2006-05-22T11:30:16.936+0100|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: all interfaces/3920"|#]
    [#|2006-05-22T11:30:17.968+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
    [#|2006-05-22T11:30:22.124+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
    [#|2006-05-22T11:30:23.195+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 75254459587952640|#]
    [#|2006-05-22T11:30:23.616+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2006-05-22T11:30:23.946+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 75254459892498432|#]
    [#|2006-05-22T11:30:24.507+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
    [#|2006-05-22T11:30:24.507+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
    [#|2006-05-22T11:30:24.537+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
    [#|2006-05-22T11:30:24.627+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
    [#|2006-05-22T11:30:24.737+0100|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2006-05-22T11:30:24.827+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
    [#|2006-05-22T11:30:24.837+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
    [#|2006-05-22T11:30:24.847+0100|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2006-05-22T11:30:24.858+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
    [#|2006-05-22T11:30:24.978+0100|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
    [#|2006-05-22T11:30:26.810+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2006-05-22T11:30:26.810+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
    [#|2006-05-22T11:30:26.971+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
    [#|2006-05-22T11:30:27.111+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
    [#|2006-05-22T11:30:27.111+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
    [#|2006-05-22T11:30:27.111+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
    [#|2006-05-22T11:30:27.211+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2006-05-22T11:30:27.211+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
    [#|2006-05-22T11:30:27.211+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
    [#|2006-05-22T11:30:48.421+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]1 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://NY043496.NYCC.internal:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]|#]
    [#|2006-05-22T11:30:48.421+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://NY043496.NYCC.internal:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:104)
         at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    Caused by: java.io.IOException: Cannot bind to URL [rmi://NY043496.NYCC.internal:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]
         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
         at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:177)
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:95)
         ... 3 more
    Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
         at javax.naming.InitialContext.bind(InitialContext.java:359)
         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
         ... 5 more
    Caused by: java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
         at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
         ... 9 more
    Caused by: java.net.ConnectException: Connection timed out: no further information
         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
         at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
         at com.sun.enterprise.server.ss.ASClientSocketImpl.connect(ASClientSocketImpl.java:181)
         at java.net.Socket.connect(Socket.java:507)
         at java.net.Socket.connect(Socket.java:457)
         at java.net.Socket.<init>(Socket.java:365)
         at java.net.Socket.<init>(Socket.java:178)
         at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
         at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
         ... 14 more
    |#]
    [#|2006-05-22T11:30:48.421+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
    [#|2006-05-22T11:30:48.421+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
    [#|2006-05-22T11:30:48.431+0100|WARNING|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:122)
         at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    |#]
    [#|2006-05-22T11:30:48.431+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
    [#|2006-05-22T11:30:48.441+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8080|#]
    [#|2006-05-22T11:30:48.441+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 8181|#]
    [#|2006-05-22T11:30:48.451+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 4848|#]
    [#|2006-05-22T11:30:48.632+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
    [#|2006-05-22T11:30:48.632+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2006/05/22 11:30:48]|#]
    [#|2006-05-22T11:30:48.632+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 :  Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
    [#|2006-05-22T11:30:48.642+0100|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
    [#|2006-05-22T11:30:48.642+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
    [#|2006-05-22T11:30:48.642+0100|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
    [#|2006-05-22T11:30:48.922+0100|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
    [#|2006-05-22T11:30:49.112+0100|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
    [#|2006-05-22T11:30:49.112+0100|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]

    I have also tried this with version 9 but it looks like the server isn't starting successfully. Any thoughts anyone?
    log follows:
    [#|2006-05-22T15:07:45.279+0100|INFO|sun-appserver-pe9.0|javax.enterprise.tools.launcher|_ThreadID=10;_ThreadName=main;|
    C:/Program Files/Java/jdk1.5.0_05\bin\java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/AppServe/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/AppServe/lib/endorsed
    -Djava.security.policy=C:/Sun/AppServe/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/AppServe/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/AppServe/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/AppServe/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=C:/Program Files/Java/jdk1.5.0_05/jre/lib/ext;C:/Sun/AppServe/domains/domain1/lib/ext;C:/Sun/AppServe/javadb/lib
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -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
    -Dcom.sun.aas.classloader.optionalOverrideableChain=appserv-ws.jar,commons-logging.jar,commons-launcher.jar
    -Dcom.sun.aas.classloader.appserverChainJars=admin-cli.jar,admin-cli-ee.jar,dbschema.jar,j2ee-svc.jar
    -Dcom.sun.aas.classloader.serverClassPath.ee=%HADB_HOME%/lib/hadbjdbc4.jar,C:/Sun/AppServe/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbm.jar,%HADB_HOME%/lib/hadbmgt.jar,C:/Sun/AppServe/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
    -Dcom.sun.aas.configName=server-config
    -Ddomain.name=domain1
    -Djmx.invoke.getters=true
    -Dcom.sun.aas.promptForIdentity=true
    -Dcom.sun.aas.classloader.optionalOverrideableChain.ee=
    -Dcom.sun.aas.instanceRoot=C:/Sun/AppServe/domains/domain1
    -Dcom.sun.aas.domainName=domain1
    -Dcom.sun.aas.classloader.sharedChainJars=javaee.jar,C:/Program Files/Java/jdk1.5.0_05/lib/tools.jar,install/applications/jmsra/imqjmsra.jar,commons-launcher.jar,C:/Sun/AppServe/imq/lib/jaxm-api.jar,C:/Sun/AppServe/imq/lib/fscontext.jar,C:/Sun/AppServe/imq/lib/imqbroker.jar,C:/Sun/AppServe/imq/lib/imqjmx.jar,C:/Sun/AppServe/imq/lib/imqxm.jar,C:/Sun/AppServe/lib/ant/lib/ant.jar,appserv-ws.jar,mail.jar,jsf-api.jar,jsf-impl.jar,appserv-jstl.jar,appserv-env.jar,jmxremote_optional.jar,C:/Sun/AppServe/lib/SUNWjdmk/5.1/lib/jdmkrt.jar,commons-logging.jar,activation.jar,appserv-rt.jar,appserv-admin.jar,appserv-cmp.jar
    -Dcom.sun.aas.classloader.sharedChainJars.ee=appserv-se.jar,appserv-ee.jar,%HADB_HOME%/lib/dbstate.jar,%HADB_HOME%/lib/hadbjdbc4.jar,jgroups-all.jar,C:/Sun/AppServe/lib/SUNWmfwk/lib/mfwk_instrum_tk.jar
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.xml.bind,javax.help,javax.portlet
    -Dcom.sun.aas.classloader.serverClassPath=C:/Sun/AppServe/lib/install/applications/jmsra/imqjmsra.jar,C:/Sun/AppServe/imq/lib/jaxm-api.jar,C:/Sun/AppServe/imq/lib/fscontext.jar,C:/Sun/AppServe/imq/lib/imqbroker.jar,C:/Sun/AppServe/imq/lib/imqjmx.jar,C:/Sun/AppServe/lib/ant/lib/ant.jar,C:/Sun/AppServe/lib/SUNWjdmk/5.1/lib/jdmkrt.jar
    -Dcom.sun.aas.classloader.appserverChainJars.ee=
    -Dcom.sun.aas.configRoot=C:/Sun/AppServe/config
    -Djava.library.path=C:\Sun\AppServe\lib;C:\Sun\AppServe\lib;C:\Program Files\Java\jdk1.5.0_05\bin;.;C:\WINDOWS\System32;C:\WINDOWS;C:\Sun\AppServe\lib;C:\Sun\AppServe\bin;C:\Sun\AppServe\bin;C:\Sun\AppServe\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH;C:\Program Files\Novell\ZENworks\;C:\DOCUME~1\sasmith\LOCALS~1\Temp\XrefTemp;C:\Program Files\Java\jdk1.5.0_05\bin;C:\Sun\AppServer1\bin;C:\Program Files\Java\jdk1.5.0_05\bin;Z:.;
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -Dcom.sun.aas.installRoot=C:/Sun/AppServe
    -Dcom.sun.aas.ClassPathPrefix=
    -Dcom.sun.aas.ClassPathSuffix=
    -Dcom.sun.aas.ServerClassPath=
    -cp
    ;C:/Sun/AppServe/lib/appserv-launch.jar
    com.sun.enterprise.server.PELaunch
    start|#]
    [#|2006-05-22T15:07:45.900+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Starting Sun Java System Application Server Platform Edition 9.0 (build b48) ...|#]
    [#|2006-05-22T15:07:47.031+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5098: AS Socket Service Initialization has been completed.|#]
    [#|2006-05-22T15:07:47.081+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;Java HotSpot(TM) Client VM;1.5.0_05;Sun Microsystems Inc.;|CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_05] from [Sun Microsystems Inc.]|#]
    [#|2006-05-22T15:07:47.141+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;|SEC1002: Security Manager is OFF.|#]
    [#|2006-05-22T15:07:48.273+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM0001:MBeanServer initialized successfully|#]
    [#|2006-05-22T15:07:50.396+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.security|_ThreadID=10;_ThreadName=main;com.sun.enterprise.security.provider.PolicyWrapper;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2006-05-22T15:07:50.496+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core.selfmanagement|_ThreadID=10;_ThreadName=main;|sgmt.service_initialized|#]
    [#|2006-05-22T15:07:54.272+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.tools.admin|_ThreadID=10;_ThreadName=main;|ADM1079: Initialization of AMX MBeans successful|#]
    [#|2006-05-22T15:08:15.833+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@6e3e28;com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://NY043496.NYCC.internal:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information];_RequestID=cd2f4e0d-e1aa-42e0-a47b-11b172de47b7;|Service com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@6e3e28 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://NY043496.NYCC.internal:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]|#]
    [#|2006-05-22T15:08:15.833+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=cd2f4e0d-e1aa-42e0-a47b-11b172de47b7;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://NY043496.NYCC.internal:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:127)
         at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:326)
         at com.sun.enterprise.server.ondemand.OnDemandServer.onStartup(OnDemandServer.java:112)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:326)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
         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:585)
         at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
    Caused by: java.io.IOException: Cannot bind to URL [rmi://NY043496.NYCC.internal:8686/management/rmi-jmx-connector]: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]
         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
         at com.sun.enterprise.admin.jmx.remote.server.rmi.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:196)
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:118)
         ... 9 more
    Caused by: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information]
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
         at javax.naming.InitialContext.bind(InitialContext.java:359)
         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
         ... 11 more
    Caused by: java.rmi.ConnectException: Connection refused to host: NY043496.NYCC.internal; nested exception is:
         java.net.ConnectException: Connection timed out: no further information
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:574)
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:185)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
         at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
         ... 15 more
    Caused by: java.net.ConnectException: Connection timed out: no further information
         at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
         at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:525)
         at com.sun.enterprise.server.ss.provider.ASClientSocketImpl.connect(ASClientSocketImpl.java:206)
         at java.net.Socket.connect(Socket.java:507)
         at java.net.Socket.connect(Socket.java:457)
         at java.net.Socket.<init>(Socket.java:365)
         at java.net.Socket.<init>(Socket.java:178)
         at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
         at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
         at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:569)
         ... 20 more
    |#]
    [#|2006-05-22T15:08:15.843+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=cd2f4e0d-e1aa-42e0-a47b-11b172de47b7;|Server Startup failed. Exiting...|#]
    [#|2006-05-22T15:08:15.843+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|Server shutdown in progress...|#]
    [#|2006-05-22T15:08:15.843+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5051: Shutting down all J2EE applications ...|#]
    [#|2006-05-22T15:08:15.843+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5060 :  Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
    [#|2006-05-22T15:08:15.843+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE 5061 : Resource adapters Stop() Complete|#]
    [#|2006-05-22T15:08:15.843+0100|INFO|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;|CORE5052: Application shutdown complete.|#]
    [#|2006-05-22T15:08:15.863+0100|WARNING|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=cd2f4e0d-e1aa-42e0-a47b-11b172de47b7;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:145)
         at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:440)
         at com.sun.enterprise.server.ondemand.OnDemandServer.onShutdown(OnDemandServer.java:123)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:343)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:260)
         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:585)
         at com.sun.enterprise.server.PELaunch.main(PELaunch.java:272)
    |#]
    [#|2006-05-22T15:08:16.133+0100|SEVERE|sun-appserver-pe9.0|javax.enterprise.system.core|_ThreadID=10;_ThreadName=main;_RequestID=cd2f4e0d-e1aa-42e0-a47b-11b172de47b7;|Server stopped due to Server startup failure.|#]

  • Not able to start the weblogic admin server

    Hi,
    I am getting the error while starting the weblogic admin server of OAM console.
    Below is the stack trace of the error
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834234> <BEA-000000> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834387> <BEA-000000> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    ####<Sep 18, 2013 4:47:14 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459834847> <BEA-000000> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
    ####<Sep 18, 2013 4:47:15 AM IST> <Info> <Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459835526> <BEA-000000> <Version: WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    ####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the username attribute value of {AES}MCSBg4hMfpsECc7LXYV6gR52kLO5DHUWyo9I1UZXMaE= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
    ####<Sep 18, 2013 4:47:16 AM IST> <Critical> <Security> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459836980> <BEA-000000> <Could not decrypt the password attribute value of {AES}1hgzo9/RGaCoWQyFXIJEbYMqmz5gg9LQzjQ/J6DxbQM= from the file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/security/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception weblogic.security.internal.encryption.EncryptionServiceException.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849081> <BEA-000000> <Server state changed to STARTING>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WorkManager> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849088> <BEA-000000> <Initializing self-tuning thread pool>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849138> <BEA-000000> <WebLogic Server "AdminServer" version:
    WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050  Copyright (c) 1995, 2011, Oracle and/or its affiliates. All rights reserved.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849208> <BEA-170019> <The server log file /ebiz/Middleware/user_projects/domains/OAM_domain/servers/AdminServer/logs/AdminServer.log is opened. All server side log events will be written to this file.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Log Management> <oad.4iapps.com> <> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1379459849213> <BEA-170023> <The Server Logging is initialized with Java Logging API implementation.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Diagnostics> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849260> <BEA-320001> <The ServerDebug service initialized successfully.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849305> <BEA-002622> <The protocol "t3s" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "http" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849306> <BEA-002622> <The protocol "https" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiop" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849307> <BEA-002622> <The protocol "iiops" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldap" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849308> <BEA-002622> <The protocol "ldaps" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849310> <BEA-002622> <The protocol "cluster" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849311> <BEA-002622> <The protocol "clusters" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849313> <BEA-002622> <The protocol "snmp" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002622> <The protocol "admin" is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <Server> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849314> <BEA-002624> <The administration protocol is "t3s" and is now configured.>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <RJVM> <oad.4iapps.com> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1379459849325> <BEA-000570> <Network Configuration for Channel "AdminServer"
    Listen Address :7003
    Public Address N/A
    Http Enabled true
    Tunneling Enabled false
    Outbound Enabled false
    Admin Traffic Enabled true>
    ####<Sep 18, 2013 4:47:29 AM IST> <Critical> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849347> <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:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      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:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    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:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      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:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    Caused By: weblogic.security.internal.encryption.EncryptionServiceException
      at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:139)
      at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:187)
      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:1092)
      at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:737)
      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:1096)
      at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1109)
      at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:600)
      at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:296)
      at weblogic.server.channels.ChannelService.start(ChannelService.java:254)
      at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
    >
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000365> <Server state changed to FAILED>
    ####<Sep 18, 2013 4:47:29 AM IST> <Error> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849410> <BEA-000383> <A critical service failed. The server will shut itself down>
    ####<Sep 18, 2013 4:47:29 AM IST> <Notice> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849411> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<Sep 18, 2013 4:47:29 AM IST> <Info> <WebLogicServer> <oad.4iapps.com> <AdminServer> <main> <<WLS Kernel>> <> <> <1379459849412> <BEA-000236> <Stopping execute threads.>
    Kindly help me to solve this issue.
    Is anyone had faced this issue.....

    Hi,
    I had tried by putting the username and password in boot.properties but we are getting the same issue.
    we tried by editing the config.xml file of the domain.
    i.e. by
    Before:      <credential-encrypted>{AES}b3I7UhWtRyj4DuKMIDVtW4Ln2nzH+HiYRhhQw1H2qpU0qJMOaDlK8iFZ+LvlJu+iZs6pptFJgWz8ryyudL1Zyvf00Rg11z9Iib7hoDC8covMFuig8wx7iOGK88zeKH7U</credential-encrypted>
    After: <credential-encrypted>MyCredentialInPlainText</credential-encrypted>
    and restarted the admin server but shows the same error.
    kindly suggest us...

  • Not able to start Managed server using nohup command and failed to authenticate weblogic user

    Hi,
    I stopped weblogic Admin server, managed server and opmnctl. and restarted Admin server successfully but I'm able to start managed start without nohup command. if I use nohup command then it's not able to get authenticate and faild to start managed server. I created boot.property file with weblogic user name and password still not working. is there anyother way to suppy login credentials for managed server?
    how can I supply login credentials in below command?
    nohup ./startManagedWebLogic.sh bi_server1 t3://machine:7001 > bis1_startup.log &
    Appreciate you for your help
    Thanks
    Jay.

    /app/obiee_11g/Oracle_BI1/jdk/bin/java -server -Xms256m -Xmx1024m -XX:MaxPermSize=512m -XX:-UseSSE42Intrinsics -Dweblogic.Name=bi_server1 -Djava.security.policy=/app/obiee_11g/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.ProductionModeEnabled=true -Dweblogic.security.SSL.trustedCAKeyStore=/app/obiee_11g/wlserver_10.3/server/lib/cacerts -da -Dplatform.home=/app/obiee_11g/wlserver_10.3 -Dwls.home=/app/obiee_11g/wlserver_10.3/server -Dweblogic.home=/app/obiee_11g/wlserver_10.3/server -Dcommon.components.home=/app/obiee_11g/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/app/obiee_11g/user_projects/domains/bifoundation_domain -Djrockit.optfile=/app/obiee_11g/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/servers/bi_server1 -Doracle.domain.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/carml -Digf.arisidstack.home=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/app/obiee_11g/oracle_common/modules/oracle.ossoiap_11.1.1,/app/obiee_11g/oracle_common/modules/oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dbi.oracle.home=/app/obiee_11g/Oracle_BI1 -DEPM_ORACLE_HOME=/app/obiee_11g/Oracle_BI1 -Dweblogic.MaxMessageSize=50000000 -DEPM_ORACLE_HOME=/app/obiee_11g/Oracle_BI1 -DHYPERION_HOME=/app/obiee_11g/Oracle_BI1 -DEPM_ORACLE_INSTANCE=novalue -Dhyperion.home=/app/obiee_11g/Oracle_BI1 -DEPM_REG_PROPERTIES_PATH=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/fmwconfig -Depm.useApplicationContextId=false -Doracle.biee.search.bisearchproperties=/app/obiee_11g/Oracle_BI1/bifoundation/jee/BISearchConfig.properties -Dweblogic.management.clearTextCredentialAccessEnabled=true -Doracle.notification.filewatching.interval=2000 -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.SSL.enableJSSE=true -Dfile.encoding=utf-8 -Doracle.ecsf.security.service=oracle.biee.search.security.BISearchSecurityService -Doracle.ecsf.configuration.class=oracle.biee.search.services.BISearchServiceConfiguration -Dxdo.server.config.dir=/app/obiee_11g/user_projects/domains/bifoundation_domain/config/bipublisher -DXDO_FONT_DIR=/app/obiee_11g/Oracle_BI1/common/fonts -Drtd.instanceName=RTD_bi_server1 -Dem.oracle.home=/app/obiee_11g/oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=01scqabi01.natusmed.natus.com:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/app/obiee_11g/patch_wls1035/profiles/default/sysext_manifest_classpath weblogic.Server
    <Nov 17, 2013 12:24:00 AM PST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
    <Nov 17, 2013 12:24:00 AM PST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
    <Nov 17, 2013 12:24:01 AM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.10-b01 from Sun Microsystems Inc.>
    <Nov 17, 2013 12:24:07 AM PST> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:Error: Failed to get value from Standard Input
    Enter password to boot WebLogic server:
    <Nov 17, 2013 12:24:07 AM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
    <Nov 17, 2013 12:24:09 AM PST> <Error> <Configuration Management> <BEA-150021> <The admin server failed to authenticate the identity of the user starting the managed server. The reason for the error is .>
    <Nov 17, 2013 12:24:09 AM PST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://01scqabi01.natusmed.natus.com:7001.>
    <Nov 17, 2013 12:24:09 AM PST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
    <Nov 17, 2013 12:24:09 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Nov 17, 2013 12:24:09 AM PST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Nov 17, 2013 12:24:09 AM PST> <Notice> <Log Management> <BEA-170019> <The server log file /app/obiee_11g/user_projects/domains/bifoundation_domain/servers/bi_server1/logs/bi_server1.log is opened. All server side log events will be written to this file.>
    <Nov 17, 2013 12:24:19 AM PST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Nov 17, 2013 12:24:20 AM PST> <Critical> <Security> <BEA-090403> <Authentication for user denied>
    <Nov 17, 2013 12:24:20 AM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
    weblogic.security.SecurityInitializationException: Authentication for user denied
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:965)
    at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:873)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    Truncated. see log file for complete stacktrace
    Caused By: javax.security.auth.login.FailedLoginException: [Security:090304]Authentication Failed: User javax.security.auth.login.LoginException: [Security:090301]Password Not Supplied
    at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.login(LDAPAtnLoginModuleImpl.java:261)
    at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(LoginModuleWrapper.java:110)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.bea.common.security.internal.service.LoginModuleWrapper.login(LoginModuleWrapper.java:106)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    Truncated. see log file for complete stacktrace
    >
    <Nov 17, 2013 12:24:20 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <Nov 17, 2013 12:24:20 AM PST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <Nov 17, 2013 12:24:20 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

Maybe you are looking for