[wls8.1 sp.3] cannot remote start with node manager on another server

In this domain run on 2 physical servers in windows 2003. In machine that has admin server can start with node manager but another machine without admin server cannot remote start . when i remote start , the node manager has facing error messages as below:
# AT "node manager monitoring" in weblogic admin console
[[NodeManager:300033]Could not execute command ping on the node manager. Reason: weblogic.nodemanager.NodeManagerException: [CommandInvoker: Failed to send command: 'ping to server 'null' to NodeManager at host: 'xxx.xxx.xxx.24:5555' with exception Connection reset by peer.. Please ensure that the NodeManager is active on the target machine].]
# AT "nodemanger.log" has facing error messages as below:
<Aug 20, 2008 7:34:07 PM ICT> <Info> <[email protected]:5555> <NodeManage r started, log messages being written into file C:\bea\WEBLOG~1\common\NODEMA~1\ NodeManagerLogs\NodeManagerInternal\nm_server02_08_20_2008-19_34_03.log>
<Aug 20, 2008 7:59:58 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - 10.208.50.23 during SSL handsha ke.> <Aug 20, 2008 8:00:11 PM ICT> <Warning> <Security> <BEA-090476> <Invalid/unknown SSL header was received from peer server01 - xxx.xxx.xxx.23 during SSL handsha key.>
I would REALLY appreciate any suggestions as to what might be the cause or what i could try.
Thanks ....

Hi,
It is up to you to decide whether you want to use nodemanager or not.
It does not make any difference if the server is started via script or nodemanager.
if i want everything (AS, MS, and NM) to come up at server boot i need to set each of them up as windows services (which is what i have at the moment) but this wont allow me to use the node manager ==> Yes this statement is correct.
You can either set AS and MS as windows service (or) AS and nodemanager as service.
Thanks,
Sharmela

Similar Messages

Re: Starting a node manager with rsh

FYI,
rsh remote "start_nodemgr > /dev/null" did the trick
Even though the start_nodemgr output came back to my remote window it
seemed to tie up the remote shell.
Thanks for the help
Orsini, Francois wrote:
Hi,
Haven't you tried:
rsh remote "nohup start_nodemgr > /dev/null &"
or
rsh remote "start_nodemgr > /dev/null &"
instead of < /dev/null ....
--francois
From: Chukk Haselhorst
Sent: Thursday, April 03, 1997 1:03 PM
To: forte-users
Subject: Starting a node manager with rsh
Environment : Forte 2F2, RS6000/AIX 4.1.5
I'm trying to use rsh to start a node manager on a remote system. >>The problem that I'm experiencing is that the node manager starts but >>the rsh doesn't return. I have to Ctrl-C to end the rsh. I've tried :
rsh remote start_nodemgr
rsh remote "start_nodemgr &"
rsh remote "start_nodemgr < /dev/null"
rsh -n remote start_nodemgr
rsh "nohup start_nodemgr &"
and others. If I rlogin to the remote system and start the node mgr >> the shell tells me that I have running jobs when I try to exit even >> though the jobs command doesn't show anything running. I am able to >> exit on the second try.
What do I need to do to be able to remotely start the node manager
without logging in and logging out.
Thanks in advance
Chukk Haselhorst

I have resolved the issue buy setting NativeVersionEnabled=falase in nodemanager.properties

Starting a node manager with rsh

Environment : Forte 2F2, RS6000/AIX 4.1.5
I'm trying to use rsh to start a node manager on a remote system. The
problem that I'm experiencing is that the node manager starts but the
rsh doesn't return. I have to Ctrl-C to end the rsh. I've tried :
rsh remote start_nodemgr
rsh remote "start_nodemgr &"
rsh remote "start_nodemgr < /dev/null"
rsh -n remote start_nodemgr
rsh "nohup start_nodemgr &"
and others. If I rlogin to the remote system and start the node mgr the
shell tells me that I have running jobs when I try to exit even though
the jobs command doesn't show anything running. I am able to exit on
the second try.
What do I need to do to be able to remotely start the node manager
without logging in and logging out.
Thanks in advance
Chukk Haselhorst

I have resolved the issue buy setting NativeVersionEnabled=falase in nodemanager.properties

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

HT4137 session cannot be started with iphone

I'm running the latest itunes on a Windows 8 PC. When I connect my iphone 5, I receive a message stating that a session cannot be started with the iphone. I cannot back-up my device, as I get the same error message. I tried backing up to icloud using wi-fi, but receie a message that the backup cannot be completed. Can anyone help?

I found the answer...
Launch iTunes with your iPad connected to your Mac. Make sure the iPad is listed under Devices on the left side of the iTunes window.
From your iTunes menu bar click iTunes / Preferences then select the Devices tab.
If there is more then one backup available, delete all but one.
Restart your iPad. Press and hold the Sleep/Wake button until the red slider appears. Slide your finger across the slider to turn off iPad. To turn iPad back on, press and hold the Sleep/Wake until the Apple logo appears.
Re-sync.
From Carolyn! Love her!

Any Guidelines on Configuring Weblogic 8.1 with Node Manager

Hi All, I want to configure Weblogic 8.1 with Node Manager using 4 ports. Is there any step by step guide? Please let me know...
Currently I am referring to this link:
http://download.oracle.com/docs/cd/E13222_01/wls/docs81/adminguide/nodemgr.html
Thanks.

Hi,
Hope the below link may be little helpful: http://middlewaremagic.com/weblogic/?p=971
NOTE: you need not to follow Step8). mentioned in above link because.... WLS8.1 nmEnroll() is not available as part of WLST ...In WLS8.1 no need to start the NodeManager. You can also ignore the Clustering part in the above link ...rest all you need to follow.
Thanks
Jay SenSharma

11g node manager reachable but server does not start from admin console

I have a issue with node manager is reachable from admin console and from command prompt it is not connected and could not able to start the managed server.
If i change /config/nodemanager/nm_password.properties plain text and restart it is not reachable in admin console abut can connect from command prompt. I could not able to start the even with this scenario.
i see below error when try to check machine monitor tab.
<Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Access to domain 'dom_11gint' for user 'Ckr10ycOJN' denied".>
Ckr10ycOJN username in config.xml
node manager and managed servers are not root user process.
Please help me if have any suggestions.

Pls. make sure the following points in your environment.
1) Check '*nodemanager.domains*' file in <<WL_HOME>>\commo\nodemanager directory
     a) This file should have the entry for your domain 'dom_11gint'.
     b) Ensure the path referred in the nodemanager.domains file is correct one.
2) Ensure the following remote server startup parameters are passed properly.
     a) In the Admin Console, Navigate Servers --> <<SERVER_NAME>> -->Configuration --> Server Start
     b) Pass the required Class Path, Arguments, User Name, Password(User name and Password to boot the managed servers)

Getting started with Learning Management

I am just starting with learning management implementation in R12.
Can anyone tell me what are the responsibilities for learning management ?
Does Learning Management require separte licence? We have Oracle HRMS and Self-Service already implemented in our system.
When I use the responsibilities
1. Oracle Learning management Administrator
2. Learning Administrator
I see only Reports and Other Requests menu and Submit Report and View report function inside it ? I am not able to see the Catalogue, Resources, Setup functions inside the above two responsibilities.
Any help will be highly appreciated.
Thanks,
-Deb

Hi Deb,
Further to the other responses -
You need to use the responsibility Learning Administrator.
When you go into User Management assign the role of Learning Administrator to your user (make sure you pick the one which has the code UMX|OTA_LRNG_ADMIN)
In Learning Management, the role control what a user can see and do.
You can link the Responsibility to the Role (this will mean that when the Resp is assigned to the user, the Role will automatically be assigned).
You do this in User Management. Find the responsibility 'Learning Administrator' (code =FND_RESP|OTA|OTA_LEARNING_ADMINISTRATOR|STANDARD) and click 'View in Hierarchy'. Then click 'Add Node'. Search for the role Learning Administrator (code UMX|OTA_LRNG_ADMIN) and click 'Quick Select'.
Hope this helps

Start the node manager and rerun the command

Seeing the following in weblogic server log. When will I get this error? And how to retun node manager ?
The node manager at host ....and port 5555 seems to be down. Start the node manager and rerun the command.

You will get this message when the machine's NodeManager was not started.
Take a look at the following links to see how to install and start the Node Manager:
http://e-docs.bea.com/wls/docs81/adminguide/nodemgr.html#1150128
http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html#1142955

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

Starts servers with node manager

How to configure the node manager to start admin server and SOA services in the background in linux.

How to configure the node manager to start admin server and SOA services in the background in linux.

Server state failed when starting through node manager

Hi,
I'm getting the below error while starting the managed server through node manager
<Sep 14, 2010 3:49:34 PM> <Warning> <Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server
output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
I have checked the server logs and it shows the below error code
./admin-stdout.log:<Sep 15, 2010 4:15:56 PM PDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server ms01 : Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server output log for more details.>
I have also checked WebLogic documentation for BEA-300048. It says "Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration".
but I'm using Java based node manager
All this is coming up when I enable StartScriptEnabled to true in nodemanager.properties.
What could be reason for failure?

Hi.
If you are not using the latest service pack (sp2) please do so. If you are and are still seeing this
problem please open a case with support.
Thanks
Michael
Tim Dawson wrote:
I get this message whenever I try to use the console to start a managed server
on a remote system.
<Jan 12, 2002 8:18:26 AM PST> <Emergency> <WebLogicServer> <Unable to create a
server socket for: weblogic2.dev.wamnet.com/172.17.27.84, port: 7001. java.net.BindException:
Cannot assign requested address: JVM_Bind Perhaps the address weblogic2.dev.wamnet.com/172.17.27.84
is incorrect or another process is using port 7001.>
I've checked and checked and the only thing running on that box is the node manager!
The console will start a managed server on the local system (i.e. the system
that the admin server is running on) without any complaints.
Any ideas? Thanks,
Tim--
Michael Young
Developer Relations Engineer
BEA Support

Error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication" on SQL Server 2008 R2 Enterprise Edition 64-bit SP2 clustered instance

Hi there,
I have a Windows 2008 R2 Enterprise x64 SP2 cluster which has 2 SQL Server 2008 R2 Enterprise Edition x64 SP2
instances.
A domain account "Domain\Login" is administrator on both physcial nodes and "sysadmin" on both SQL Server instances.
Currently both instances are running on same node.
While logging on to SQL Server instance 2 thru "Domain\Login" using "IP2,port2", I get error 18452 "Login failed. The login is from an untrusted domain and cannot be used with Windows authentication". This happened in the past
as well but issue resolved post insatllation of SQL Server 2008R2 SP2. This has re-occurred now. But it connects using 'SQLVirtual2\Instance2' without issue.
Same login with same rights is able to access Instance 1 on both 'SQLVirtual1\Instance1' and "IP1,port1" without any issue.
Please help resolve the issue.
Thanks,
AY

Hello,
I Confirm that I encountred the same problem when the first domain controller was dow !!
During a restarting of the first domain controller, i tried to failover my SQL Server instance to a second node, after that I will be able to authenticate SQL Server Login but Windows Login returns Error 18452 !
When the firts DC restart finishied restarting every thing was Ok !
The Question here : Why the cluster instance does'nt used the second DC ???
Best Regards
J.K

Timezone issue with Node manager

Hi
We have a strange problem in our Weblogic manager server as below.
We started the manage server & Node manager in Jan 2011, when the daylight saving was on., then when time zone changed to winter time to summer time, node manager was unable to pick the time zone change.
It was still printing log files with wintertime in April 2011.
But after we restart the node manager & manage server, we found that then it has pick the summer time.
So want to know how to avoid such problems, that node manager & manage server should pick the current timezone (even when it change to summer to winter or vice versa) without restarting the servers.
Please can anyone guide me on this such strange problem & solution of it.
regards,
jay

Hi
My OS is Linux box and is able to pick the time correctly, but nodemanager & manage server which are started before time zone change is not able to pick the timezone change and continue running with timezone where it has started and the same time OS (date command) shows that it is changed to summer time.
Do i need to specify any configuration for nodemanger & manage server for picking the time when time zone is changed.
regards,
Jay
Edited by: user13160729 on May 23, 2011 11:07 PM

Server stop problem with node manager

Hi ,
I get this error often when I try to stop a managed server via the nodemanager
from the admin console or from the weblogic.Admin command. The server does not
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N e Manager
- reason: [__COMMAND_EXCEPTION__Request: failed to execute command ' utdown' on
server 'xxx - reason: '[Unable to send shutdown request to server.> ].]
[java] Start server side stack trace: [java] weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager - reason:
[__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' on server 'xxx
- reason: '[Unable o send shutdown request to server.]'> ].] [java] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] at weblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method) [java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(D amicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicM anImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl ava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

Hi Anil,
A little more information might be helpful. Which version are you talking
about ? What is the server state when you issue the command ? Is the server
very busy. Are you able to get the server state from the nodemanager when
the server is running ? Are you able to communicate from admin server ->
nodemanager <-> managed server ?
cheers,
gaurav.
"Anil Jacob" <[email protected]> wrote in message
news:3fb16b7c$[email protected]..
>
Hi ,
I get this error often when I try to stop a managed server via thenodemanager
from the admin console or from the weblogic.Admin command. The server doesnot
stop and it goes into an unknown state and I have to do a force shutdown
[java] Error: [Could not execute command shutdown for server xxx via the N
e Manager> - reason: [__COMMAND_EXCEPTION__Request: failed to execute command 'utdown' on> server 'xxx - reason: '[Unable to send shutdown request to server.> .]
[java] Start server side stack trace: [java]weblogic.nodemanager.NodeManagerException:
[Could not execute comman shutdown for server xxx via the Node Manager -
reason:> [__COMMAND_EXCEPTION__ quest: failed to execute command 'shutdown' onserver 'xxx> - reason: '[Unable o send shutdown request to server.'> ].] [java] atweblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeMa
gerRuntime.java:472) [java] atweblogic.nodemanager.NodeManagerRuntime.shutdown(NodeManagerR
time.java:86) [java] at java.lang.reflect.Method.invoke(Native Method)[java]
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DamicMBeanImpl.java:732)
[java] at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicManImpl.java:714)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1557)
[java] at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImplava:1525)
[java] at weblogic.management.internal.RemoteMBeanServerImpl.invoke(Rem

[wls8.1 sp.3] cannot remote start with node manager on another server

Similar Messages

Maybe you are looking for