Manage Azure from VMM console ?
Hi
Is it not possibe to manage all my Azure virtual servers from VMM 2012 R2 ?
David
This is not possible as VMM doesn't have a direct connection to Azure.
However, you can use App Controller - which is also included in System Center to provide a self-service portal that spans clouds, such as VMM clouds that are private, and Azure subscriptions that are public..
App Controller will only focus on the IaaS side of Azure in this case, which is exactly what you are looking for.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )
Similar Messages
-
Starting Managed Server from Administration Console
Hi
I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
java.lang.ClassNotFoundException
Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
java.lang.ClassNotFoundException
I start the services in below order
Weblogic Server
node Manager
and
soa_server
Thanks
Hariyou must set to true the StartScriptEnabled property in nodemanager.properties
-
Unable to start Managed server from admin console using nodemanager
I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.
Hi there,
Can you check the following configuration in Weblogic admin console ?
1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
Thanks
Lakshman -
Unable to start Managed servers from admin console
Hello!
We have a problem to start Managed Servers throw Node manager.
We get an error:
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
INFO: Server error log also redirected to server log
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
<Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Additional information:
weblogic 10.3.3
PT8.51.11
Linux x86_64 RH5
When we starting Manged servers manualy, it's works fine.
Thank you.Hello!
The problem is found.
We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
<Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
INFO: Server failed during startup so will not be restarted
<Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'PIA1'
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
at weblogic.nodemanager.server.Handler.run(Handler.java:70)
at java.lang.Thread.run(Thread.java:662)
There are no errors in managed servers logs.
PIA1.out:
<Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
Attempting to start WebLogic Server PIA1
No activity will be logged to this window.
Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
PID for WebLogic Server PIA1 is: 27018
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
<Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
What can be the reason?
Thank you. -
Error start managed server from admin console in SSL mode
I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
<Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
<Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
<Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
<Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
<Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
<Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
<Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
<Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
<Feb 22, 2005 11:03:10 AM CST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
I am running everything on IBM UNIX server.
I appriciate your help.
Thanks & regards,
Laxman.Hi
From the admin console ... Are you able to check the status of Node Manager ?
If yes ... please check the SSL configuration of managed servers ...
Check the domain administration port also.
Jin -
Problems starting managed server from admin console WL70 portal
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
-
Having problems removing a managed server from WL console
Background:
Running the 11 g R1 (11.1.1.5) server on Linux.
Installed OIM, OAM, OVD, OID, WL. (other components may be added later)
Have not yet integrated OIM and OAM.
The Problem:
We were running into a problem on our oim server, that warranted removal and reinstallation.
we were attempting to remove the oim_server1 instance from the weblogic admin console.
went to deployments, and deleted the entry there for oim_server1
Then went to environment | servers
The oim_server1 now shows as "FAILED_NOT_RESTARTABLE"
and we can not remove this instance frome the admin instance.
If we attempt to remove it, It gives the errors
The server oim_server1 is a running server and may not be deleted.
All of the servers selected are in a state which is incompatible with this operation.
Restarted the WL Admin server, then went back into the console. This did not change the status of the managed server.
Tried going to
/data01/app/oracle/product/Middleware/user_projects/domains/IDMDomain/servers/oim_server1/tmp
and removing the *.lok file...
No luck.
How do we get around this, so we can remove the incorrectly configured oim_server1 ?
Edited by: 992276 on Mar 6, 2013 11:30 AMi was in the EXACT same situation but on weblogic 10.3.3.
* two servers in FAILED_NOT_RESTARTABLE
* try to delete them from admin console and i get the "is a running server and my not be deleted..../incompatible with this operation" messages
i tried lots of things and but i could not get rid of those servers.
### What ended up working. ###
i just started the servers. there is no way they should have started. i had already even deleted the server directories. but they started. and then i shut them down. and at that point i was able to delete them.
hope this helps you or somebody. it seemed like such an unlikely solution. but it worked for me.
Edited by: user8825653 on Mar 15, 2013 8:25 AM -
Configure Managed Server from Admin Console - Java arguments
Hi There;
I am configuring a managed server from the admin console and the one item that me up is when I add the following into the Arguments sections:
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol'|'oracle.fabric.common.classloaderurl.handler'|'oracle.fabric.common.uddiurl.handler'|'oracle.bpm.io.fs.protocol.
Note The command line script used double quotes (") but the console gave an error - Arguments may not contain '"' This sounded reasonable so I switched the double quotes to single quotes.
Switching to single quotes allowed me to bypass the error.
The managed server fails when I start it from the console:
Error message:
oracle.fabric.common.classloaderurl.handler ' is not recognized as an internal or external command, operable program or batch file.- it is like it ignores the values after the single quotes and fials.
How can I configure this parameter?
note: I am running weblogic 10.3.6 on widows 2008. it is a SOA Managed Server I am trying to setup to run from the Admin Console.
JTry leaving out the quotes
-Djava.protocol.handler.pkgs=oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol
See also the documentation: URL (Java Platform SE 7 ) "interpreted as a list of packages separated by a vertical slash character |" -
Starting managed servers from admin console vs. command line
Will the arguments I enter in the "Arguments" section of the "Server start" admin console page also be used if I start the managed server from the command line using startManagedWeblogic.sh?
And conversely, will changes I make to the scripts take effect when I start the server from the admin console?No,
the arguments that you set thru Console GUI are effective when Node manager start your server.
Ammar Sajdi -
SCVMM 2012 SP1 (RTM) Deployment from VMM Console fails.
Error During a library refresh, or deployment from template - It all fails:
Error (12710)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server (MyServer).
Unknown error (0x80338105)
Recommended Action
1) Ensure that the Windows Remote Management (WS-Management) service is running on the server (myserver).
2) If the System Center Virtual Machine Manager service on your VMM management server is configured to run by using the machine account, ensure that there is not a group policy that does not allow adding machine accounts to a computer's Administrators group.
If there is, you can use one of the following workarounds:
- Disable the group policy in Active Directory Domain Services (AD DS)
- Modify the group policy to allow the VMM machine account in the Administrators group
- Move the machine account to its own organizational unit (OU) and block the group policy from being applied
- Reinstall the VMM management server and choose the option to run the System Center Virtual Machine Manager service by using a domain account, and re-add all of your virtual machines.
So, as soon as SCVMM 2012 Sp1 was released we decided that it was best to upgrade so we could utilise the new features of Server 2012 as a host.
The upgrade worked a treat. VM's deployed, Server 2012 worked. Anyway, a few days after deployment we start to see errors relating to WinRM and permissions (See end of the post). After a quick trace around we found some failed services, usually on a host
but sometimes it seemed to happen on the Library/Management server as well.
So, our setup is as follows:
Management/Library server = VMware VM, Server 2012 standard, 6 GB memory, 4 vCPU's
Hosts = HP DL360p G7, HP DL360 Gen8 (we have a few of these), Server 2012. We also have a DL380 G7 on Server 2008 R2 Enterprise that fails as well, so it seems the error isn't O/S specific (I'm picking a VMM issue).
So I have tried many resolutions and now none of them work.
We have no restrictions on group policy for the local admin, this can be set manually, and works for that matter.
WinRM is working and the listening port is 5985 (I can see it working and listening via a "netstat -an")
Also, I have ensured many many times that all of the required services are up and running (SCVMMAgent, VirtualDisk managerment, WinRM) and initially these where at fault and a simple restart of each service (or even a full start from dead) fixed
it - Now it all fails. Even a library refresh fails. And all while each of the services required are up and running.So, I have now tried a reinstall of the management server & made some changes
1- Changed the service account during the install.
2 - Added the service account user to the local admins group of each host in question.
3 - Tried "winrm /qc" .which lets me know its already up and running and configured. Although I must admit, I'm not 100% sure how to use WinRM. From what I can read, this is like an express setup and ensures you are up, running and listening.
4 - Verified that WinRM is working of the right port (Listening ports dump below)
5 - Verified that I can connect to each port required for the SCVMM Management server.
BUT, it seems the error is still there and deployments still fail,
although the library refreshes correctly now.
Error (12710)
VMM does not have appropriate permissions to access the Windows Remote Management resources on the server ( Myserver).
Unknown error (0x80338105)
NETSTAT Listening ports dump.
PS C:\Users\nzadmin> netstat -an
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1801 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2103 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2105 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2107 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8000 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8100 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8101 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8102 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8103 0.0.0.0:0 LISTENING
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49170 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49201 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49211 0.0.0.0:0 LISTENING
TCP 127.0.0.1:57388 0.0.0.0:0 LISTENING
TCP 172.23.16.69:139 0.0.0.0:0 LISTENING -
Unable to start managed servers from Admin Console "FAILED_NOT_RESTARTABLE"
I recently installed WebLogic 10.3.5, JRockit, and ECM 11.1.1.5. I'm to the point where I am trying to get Nodemanager configured so I can stop/start managed servers through the admin console. I have the following listed in Environment > Servers:
AdminConsole - running
IBR_server1 - FAILED_NOT_RESTARTABLE
managedServer1 - FAILED_NOT_RESTARTABLE
UCM_server1 - FAILED_NOT_RESTARTABLE
I followed the tutorial at http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta to get to the point where the AdminServer starts when the server reboots, so I think Nodemanager is working there. If I view Machines > Monitoring, it says Nodemanager "Reachable." However, when I go to restart IBR_server1, managedServer1, or UCM_server1, I get the FAILED_NOT_RESTARTABLE status. I am using the weblogic server's IP for the machine name/host because our DNS is still screwed up. Would that have any affect on this?
I'm completely unsure what to do now. The Nodemanager log shows:
INFO - <Loading domains file: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
WARNING - <Domains file not found: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
INFO - <Loading identity key store: FileName=E:/oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
WARNING - <Node manager configuration properties file 'E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties' not found. Using default settings.>
So I'm confused why it's saying the properties file and domains file are not found... I've checked and they exist at
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.properties
and
E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.domains
The domains file contains
base_domain=e\:\\oracle\\middleware\\user_projects\\domains\\base_domain
Which is correct.
Any idea what I'm missing here? I can provide more detail if needed. Thank you.
EDIT: I should add that I can start the UCM and IBR managed servers using the start up scripts on the server, but that's not what I'm after. I want everything controlled through the AdminConsole and want to be sure that when the server reboots, all the managed servers come back up correctly.
Edited by: user5824683 on Oct 5, 2011 5:04 PM
Edited by: user5824683 on Oct 5, 2011 5:09 PMI did a bit of digging, and it seems I have an issue with -Xnohup... I've verified this arugment exists in all of my managed servers properties files, yet it still bombs when I try to restart from the webLogic console. I should note that if I start fresh from the server, I can start all my manager servers using WLST nmStart().
starting weblogic with Java version:
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1430-windows-x86_64, compiled mode)
Starting WLS with line:
E:\java\JROCKI~1.1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=IBR_server1 -Djava.security.policy=E:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\oracle\middleware\user_projects\domains\base_domain\servers\IBR_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xnohup -Xverify:none -da -Dplatform.home=E:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=E:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\servers\IBR_server1 -Doracle.domain.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\servers\IBR_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Ducm.oracle.home=E:\oracle\MIDDLE~1\ORACLE~2 -Dem.oracle.home=E:\oracle\middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://138.126.180.177:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=e:\oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
Exception in thread "Main Thread" java.lang.NoClassDefFoundError: –Xnohup
Caused by: java.lang.ClassNotFoundException: –Xnohup
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
Could not find the main class: –Xnohup. Program will exit.
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4252>
<Oct 6, 2011 12:38:13 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters> -
Starting managed server from admin console
Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
I did the same way as you said here but still getting following error.....Could you
address me where I did a mistake
Starting WebLogic Server ....
Connecting to http://localhost:7001...
<Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
Server "MyServer1" for domain "mydomain">
<Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
Start server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
***************************************************************************Start
server side stack trace:
java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
'>
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: connecting
to http://localhost:7001/wl_management_internal2/Bootstrap - with nested exception:
[java.net.ConnectException: Tried all: '1' addresses, but could not connect over
HTTP to server: 'localhost', port: '7001']
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP
to server: 'localhost', port: '7001'
at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
at weblogic.net.http.HttpClient.New(HttpClient.java:149)
at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:279)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
at weblogic.management.Admin.initialize(Admin.java:320)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
--------------- nested within: ------------------
weblogic.management.configuration.ConfigurationException: connecting to http://localhost:7001/wl_management_internal2/Bootstrap
- with nested exception:
[java.net.ConnectException: Tried all: '1' addresses, but could not connect over
HTTP to server: 'localhost', port: '7001']
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
at weblogic.management.Admin.initialize(Admin.java:320)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
Reason: Fatal initialization exception
<Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555> <WindowsProcessControl:
online successfully invoked on server 'MyServer1', pid: 1892>
Change the "Listen Address" attribute of the admin server to be its machine
name or IP address. I think you currently have it set to "localhost".
Hopefully this should fix atleast one of the exceptions below.
-- Anand
"Janavi" <[email protected]> wrote in message
news:[email protected]...
>
> Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
>
> I did the same way as you said here but still getting following
error.....Could you
> address me where I did a mistake
>
>
> __________________________________________
> Starting WebLogic Server ....
> Connecting to http://localhost:7001...
>
> <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
Managed
> Server "MyServer1" for domain "mydomain">
> <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize
the server:
> 'Fatal initialization exception
> Throwable: java.lang.ClassCastException:
weblogic.security.acl.DefaultUserInfoImpl
>
>
> Start server side stack trace:
> java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
> at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
> at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
> at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
> at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
> at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
>
> at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
> at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
> at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
> java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
>
>
***************************************************************************S
tart
> server side stack trace:
> java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
> at
weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
> at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
> at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
> at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
> at
weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
a:164)
>
> at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
> at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
> at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
> at
weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
> <<no stack trace available>>
> '>
>
> The WebLogic Server did not start up properly.
> Exception raised:
weblogic.management.configuration.ConfigurationException: connecting
> to http://localhost:7001/wl_management_internal2/Bootstrap - with nested
exception:
>
> [java.net.ConnectException: Tried all: '1' addresses, but could not
connect over
> HTTP to server: 'localhost', port: '7001']
> java.net.ConnectException: Tried all: '1' addresses, but could not connect
over HTTP
> to server: 'localhost', port: '7001'
> at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
> at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
> at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
> at weblogic.net.http.HttpClient.New(HttpClient.java:149)
> at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
> at
weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:27
9)
>
> at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
> at weblogic.management.Admin.initialize(Admin.java:320)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
> at weblogic.Server.main(Server.java:35)
> --------------- nested within: ------------------
> weblogic.management.configuration.ConfigurationException: connecting to
http://localhost:7001/wl_management_internal2/Bootstrap
> - with nested exception:
> [java.net.ConnectException: Tried all: '1' addresses, but could not
connect over
> HTTP to server: 'localhost', port: '7001']
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
> at weblogic.management.Admin.initialize(Admin.java:320)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
>
> t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
> End server side stack trace
>
> <<no stack trace available>>
> Reason: Fatal initialization exception
>
> <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555>
<WindowsProcessControl:
> online successfully invoked on server 'MyServer1', pid: 1892>
> _______________________________________
>
-
How to start managed server from console?
Hi,
After several unsuccesful attempts to start a managed server from admin console,
which starts fine by script and stops by console, can somebody please mail me
what to enter in the "remote start" tab!
The documentation is very uncertain if the path have to be absolute or not. It
seems to be a problem with the classpath.
thanks in advance
KaiThe ServerStart element should look like below (WLS6.1sp1+). Using absolute
path is definitely OK. Please provide us more info if you still have this
problem such as files under WL_HOME\NodeManagerLogs\<mgr'ed servername>
especially config and <mgr'ed server name>_error.log
<ServerStart Arguments="-mx64m -ms64m" BeaHome="d:\bea"
ClassPath="d:\bea\load1;d:\bea\load1\lib\weblogic_sp.jar;d:\bea\load1\lib\we
blogic.jar"
Name="Server-1005280911753"
OutputFile="d:\bea\load1\config\NodeManagerClientLogs\managed1\startserver_1
005280991998.log"
RootDirectory="d:\bea\load1"
SecurityPolicyFile="d:/bea/load1/lib/weblogic.policy"/>
"Kai" <[email protected]> wrote in message news:3bea490f$[email protected]..
>
Hi,
After several unsuccesful attempts to start a managed server from adminconsole,
which starts fine by script and stops by console, can somebody please mailme
what to enter in the "remote start" tab!
The documentation is very uncertain if the path have to be absolute ornot. It
seems to be a problem with the classpath.
thanks in advance
Kai -
MANAGED SERVER NOT COMMING UP FROM ADMIN CONSOLE,
Hi All,
I can't start managed server from admin console.
The status is showing FAILED_NOT_RESTARTABLE.
below is the error it is showing in the node manager.
But i can start managed server from the back-end successfully. If i start the nodemanager then managed server is not comming up.
<May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed
_server'>
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
May 24, 2011 4:12:22 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'my_managed_server'
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Please help.
Regards,
nag.<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain'>
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out00039">
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server error log also redirected to server log>
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out'>
<May 24, 2011 4:12:22 AM> <INFO> <weblogic_domain> <my_managed_server> <Server failed during startup so will not be restarted>
<May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed_server'>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
This is what i found in nodemanager log file
Regards,
Nag. -
Start managed server from console?
If I try to start a new weblogic 10.3 managed server from the console then i get this error:
"The server myserver does not have a machine associated with it.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed."
Starting the same managed server from the dos prompt "bin/startManagedServer.bat myserver" works, so why is the weblogic console not working?Hi,
To start any managed servers from Admin Console you need to have a Machine associated with that Managed server and have to start nodemanager, then only you can start a managed server from console.
Following are the steps:
1) Create a Managed Server (MS-1)
2) Create a Machines (MachineA)
3) In the above created MachineA add the MS-1 which can be done from the below console path
Console Path:
Machines --> MachineA --> Configuration [Tab] --> Servers [Sub-Tab]
4) Now start nodemanager using the startNodeManager.sh script which can be found in the below path
Path:
wlserver_10.3/server/bin/
5) Now you can try to start your MS-1 using the Admin Console.
Note: If you still cannot start the your managed servers then would suggest you to have a look at the below post
Topic: NodeManager is not reachable
http://middlewaremagic.com/weblogic/?p=5205
Topic: Common NodeManager Issues in WebLogic
http://middlewaremagic.com/weblogic/?p=2887
Regards,
Ravish Mody
Maybe you are looking for
-
Can't boot to windows, stuck at black screen (with cursor)
Hi! I'll get straight to my problem: I can't boot to Windows (Windows 10 Technical Preview) anymore after installing VirtualBox (or rather, an Android emulator that installed VirtualBox) on my system. I get stuck, after the loading animation with the
-
Working with Multiple Videos in Logic a Pain !!!
Hi, I find that working with videos in logic is still quite primitive as compared to Protools. I like working with logic, even in post production but working with videos has been a real pain for me. In PT, you are able to add in several videos in one
-
Can't believe the 10gb of data increased
when will data costs go down. Verizon recently lowered costs in the lower gb plans but raised 10gb by $20. As cell carriers get more competitive, like AT&T data rollover, you would think Verizon would try to hold on to long time customers. I know
-
When I plug my iphone into the computer I keep getting the following message."Itunes was unable to load provider data from sync services. Reconnect or try again later." Can anyone tell me what this means and how to correct it?
-
Circular: can't install libusb-compat for `pacman-key --init` [SOLVED]
So like a lot of people on here have upgraded to pacman 4. I can't run `pacman-key --init` to update the keyring: [stuart@myhost ~]$ sudo pacman-key --init Password: gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared objec