Node manager issue

Hi guruz,
I m new to weblogic,installed weblogic 10.3.3 on solaris Sparc.
I have started the admin server using the following command
sh startweblogic.sh
Adminserver server starts up properly
now when i try starting node manger using
sh startnodemanager.sh
I neva get listening to a particular port(previously i used to get listening to 5556)
i tried even this command
sh startnodemanager <ip-address> 5556
But stil the same thing.
I logged on to the console.
Checked node manager status-->inactive
Problem description: weblogic.nodemanager.NMConnectException
i got the error in admin server logs
<Feb 23, 2011 6:47:03 PM IST> <Error> <NodeManager> <BEA-300033> <Could not execute command "getVersion" on the node manager. Reason: "Connection refused. Could not connect to NodeManager. Check that it is running at 172.30.0.7:5556.".>
pls help,
Thanks in advance
Regards
Fabian

hi jay,
Thanks for all the help
i followed your 2nd and 3rd step
These are my node manager logs.
<Feb 26, 2011 1:23:45 PM> <INFO> <Loading domains file: /weblogic/Oracle11g_home/wlserver_10.3/common/nodemanager/nodemanager.domains>
<Feb 26, 2011 1:23:45 PM> <INFO> <Loaded node manager configuration properties from '/weblogic/Oracle11g_home/wlserver_10.3/common/nodemanager/nodemanager.properties'>
<Feb 26, 2011 1:23:45 PM> <INFO> <weblogic_domain> <ManagedServer_2> <Startup configuration properties loaded from "/weblogic/Oracle11g_home/user_projects/domains/weblogic_domain/servers/ManagedServer_2/data/nodemanager/startup.properties">
<Feb 26, 2011 1:23:45 PM> <INFO> <weblogic_domain> <test> <Startup configuration properties loaded from "/weblogic/Oracle11g_home/user_projects/domains/weblogic_domain/servers/test/data/nodemanager/startup.properties">
i neva got any security related exceptions.
After making these changes i reastarted my adnmin server and node manager(Still inactive),tried starting managed server from admin console got the following error
For server ManagedServer_2, the Node Manager associated with machine UnixMachine_1 is not reachable.
Right now i just start my managed servers from foreground and keep in runnin 24*7.but still want to know why im gettin inactive in node manager status
Thanks in advance
Regards
Fabian

Similar Messages

OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

Hi,
Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
To get it activated I bounced services and when I try to start Node Manager it gives below error --
<Aug 30, 2011 2:02:42 PM CDT> <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>
<Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
+ set +x
I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
Cherrish Vaidiyan
Edited by: Cherrish on Aug 30, 2011 3:14 PM

Hi,
There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
Cherrish Vaidiyan

Concurrent Manager Node Name Issue

Hi All,
Recently one of EBS 11i (11.5.10.2 + RHEL 4.7) Node (VM Node) has been cloned to another node. So i had to change the Host name for the cloned application. I followed the meta link note 338003.1 and 341322.1. I am successfully changed the host name and able to access the application as well. When i check the Concurrent manager process's status, its showing Actual-1 and Target -1. B*ut the problem is some of process's node name is showing the previous node name (the name of the node from where cloned).* For example Output Post Processor's node name is showing the previous one and its status showing Actual - 0 and Target - 1. Please let me know why this has happened and also how can i solve this issue?
Thanks,
Mani

Please run cmclean.sql script as per (Concurrent Processing - CMCLEAN.SQL - Non Destructive Script to Clean Concurrent Manager Tables [ID 134007.1]) and check then.
If you still have the same issue, update FND_CONCURRENT_QUEUES table (TARGET_NODE column) -- Troubleshooting the "Error Occurred While Attempting to Establish an Applications File Server Connection" [ID 117012.1]
Please also see (Concurrent Processing - CCM.sql Diagnostic Script to Diagnose Common Concurrent Manager Issues [ID 171855.1]).
Thanks,
Hussein

Configuration issue in node manager ( Oracle Weblogics 11g )

Hello Everyone,
We have developed an Admin server and a Managed server. Both are working fine. When we tried to implement node manager concept in it, we were partially unsuccessful to make this task completed.
Under Environment -> Machines -> machine_name -> Under Monitoring tab
     We could see status as inactive.
Sequence of Steps we followed:-
     - Create new Machine ( Environment -> machine )
     - added Managed Server to the Machine
     - In Managed Server, Environment variable is set. Invoked WLST. Enrolled domain_home to wls_home/common/nodemanager

This is the scenario which i followed, kindly read it . . you will get clear idea. .
Machine 1 - Admin Server
Machine 2 - Managed Server
In Admin server, Environments -> server -> Machine 2 has been added. I am able to start and stop managed services.
Node Manager:-
In Machine 1 ( Admin server ) - Environments -> machine -> create -> In listener address ( gave ip address of machine 2 ) -> in listerner port -> 5556.
     - Environments -> machine -> select - created machine ->configuration -> servers -> add maanged server - machine 2.
In Machine 2 ( Managed Server ) - In WLS_HOME/server/bin -> ./setENV**.sh -> Invoke wlst -> Used connect cmd to get connect admin url in WLST -> executed enroll cmd
     - Then executed ./startnodemanager.sh script
We assume that now under Environment -> Machine -> Machine_Name -> monitoring -> status should be reachable but for me its inactive. I found this message - weblogic.nodemanager.NMConnectException.
=================================================================================================================
Now below you will find node manager logs and properties file
Log viewed when ./startnodemanager.sh is executed
+ CLASSPATH=/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:/home/oracle/oracle11g/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_oepe180/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/patch_adfr1111/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/oracle/oracle11g/Middleware/jdk160_29/lib/tools.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.jar:/home/oracle/oracle11g/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/webservices.jar:/home/oracle/oracle11g/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/home/oracle/oracle11g/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/home/oracle/oracle11g/Middleware
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ export CLASSPATH
+ export PATH
+ cd /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
+ set -x
+ '[' '' '!=' '' ']'
+ '[' '' '!=' '' ']'
+ /home/oracle/oracle11g/Middleware/jdk160_29/bin/java -client -Xms32m -Xmx200m -XX:MaxPermSize=128m -Dcoherence.home=/home/oracle/oracle11g/Middleware/coherence_3.7 -Dbea.home=/home/oracle/oracle11g/Middleware -Xverify:none -Xverify:none -Djava.security.policy=/home/oracle/oracle11g/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.nodemanager.javaHome=/home/oracle/oracle11g/Middleware/jdk160_29 weblogic.NodeManager -v
<Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServerConfig initDomainsMap
INFO: Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
<Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'>
Oct 12, 2012 4:01:52 PM weblogic.nodemanager.server.NMServer <init>
INFO: Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.properties'
Node manager v10.3
Configuration settings:
NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
ListenAddress=
ListenPort=5556
ListenBacklog=50
SecureListener=false
AuthenticationEnabled=true
NativeVersionEnabled=true
CrashRecoveryEnabled=false
JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
StartScriptEnabled=false
StopScriptEnabled=false
StartScriptName=startWebLogic.sh
StopScriptName=
LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogLevel=INFO
LogLimit=0
LogCount=1
LogAppend=true
LogToStderr=true
LogFormatter=weblogic.nodemanager.server.LogFormatter
DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
DomainsFileEnabled=true
StateCheckInterval=500
UseMACBroadcast=false
DomainRegistrationEnabled=false
DomainsDirRemoteSharingEnabled=false
Domain name mappings:
TestDomain -> /home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
<Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
Oct 12, 2012 4:01:54 PM weblogic.nodemanager.server.Listener run
INFO: Plain socket listener started on port 5556
nodemanager.log
<Oct 12, 2012 4:01:52 PM> <INFO> <Loading domains file: /home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains>
<Oct 12, 2012 4:01:52 PM> <INFO> <Loaded node manager configuration properties from '/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.prop
erties'>
<Oct 12, 2012 4:01:54 PM> <INFO> <Plain socket listener started on port 5556>
more nodemanager.properties
#Sun Oct 07 06:39:50 BST 2012
DomainsFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/home/oracle/oracle11g/Middleware/jdk160_29
AuthenticationEnabled=true
NodeManagerHome=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager
JavaHome=/home/oracle/oracle11g/Middleware/jdk160_29/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=false
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=false
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=false
LogFile=/home/oracle/oracle11g/Middleware/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50
-bash-3.2$
more nodemanager.domains#
#Fri Oct 12 16:00:36 BST 2012
TestDomain=/home/oracle/oracle11g/Middleware/user_projects/domains/TestDomain
-bash-3.2$
All these were found in Admin Server. . . Kindly provide ur suggestions . .

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

ALSB2.6/WLS9.2 Node Manager Monitoring Issue

Hi,
We have configured a java based node manager on weblogic 9.2 platform, using our customized scripts, for ALSB domain.
Node manager uses a customized server startup script to start the servers. This start-up script does some custom tasks and then starts the weblogic managed server with java options specified in this start-up script.
We are able to start / stop the managed servers from admin console but the node manager is not able to monitor the health of the managed servers. Node manager's log file also shows that server is in failed state whereas the managed servers log files show running state.
Can you please help how can we make the java based node manager (which uses a script to start the server) to monitor/check health of the managed server.
Also we've noticed a change in the way parameters are passed to server start-up script (which is called by the node manager ) between WLS8.1 and 9.2.
In 8.1 arguments were passed to the script in$1,$2,$3 and $4 ($4 pointing to the pid file of managed server). However these arguments are no longer available in 9.2.

I think when nodemanager.properties runs at the start of node manager, there is one line in it, i.e.
StartScriptName=startWeblogic.cmd
now there are few lines in the startWeblogic.cmd, those are:
@REM Set IP Mask.
if NOT "%NetMask%"=="" (
set IPMASK=%NetMask%
) else (
set IPMASK=
@REM Perform IP Migration if SERVER_IP is set by node manager.
if NOT "%SERVER_IP%"=="" (
call "%WL_HOME%\common\bin\wlsifconfig.cmd" -addif "%IFNAME%" "%SERVER_IP%" "%IPMASK%"
now I think that's why everytime the node manager tries to start the server the IP address is changed or masked to different one in startup.properties file, what I have mentioned in previous post...and what is indicated in log file...
any guru...plz

Where do I find the "Node Manager" service?

Can anyone tell me where to find the "Node Manager Service" In Call Manager 5.1.2 or IPCC 4.5?
My db_CRA database in IPCC is not updating the real time ICD statistics table and Bug CSCsc09160 seems to indicate that stopping and starting the "Node Managers" may fix the issue.
From the bug report:
Symptom:
Under the db_cra two tables (RtCSQsSummary and RtICDStatistics) are not updating. They stop updating concurrently with engine failovers and reboots. Only a hard reboot or a
service failover brings them back into an active state.
When the RtCSQsSummary and RtICDStatistics tables do update on the
primary DB they do not update on the secondary DB and the data on them
doesnt get refreshed.
Conditions:
stopping Node manager on node 1, data fails to be written to node 2. Then when we start NM back up on node 1 data is still not written to either data store
Workaround:
Not much as a workaround, because the solution requirs stop on both Node
Managers and bring up node 1 first and the data starts writing to DB
again.
Thanks,
Brian

Post Author: jsanzone
CA Forum: Authentication
Sven,
The reference to Session Manager is more of a concept of operations versus an entity. The portion of code that you copied and pasted in your post is actually part of the verbiage used in an ASP script that BusinessObjects expects you to create in order for you to obtain your objective. You can use this coding to create your own customized script or you might be able to search around on the web for a more complete solution.

After I do Node Manager nmConnect(...) I can no longer start a managed svr

I am running 10.3.2 on both windown and redhat
I have a domain with AdminServer and one managed server.
I can start AdminServer from the shell with startWebLogic.cmd
I can log into the web based 'console'
I can go to Environment -> Servers and start/shutdown the managed server.
If I use WLST and...
connect('user', 'pass', 't3://localhost:7001')
nmEnroll('fullPathToDomainDir')
I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
I stop running the AdminServer from the shell - it is no longer running.
Now, I want to start the AdminServer with Node Manager, so (with WLST)...
nmConnect('user','pass','localhost','5556','domainName)
I get the error...
'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
username=user
password=pass
I go back to WLST, now nmConnect works!!!
I can then do..
nmStart('AdminServer')
The AdminServer start, I go to the web console, and I try to start the managed server, I get...
'For server managedServer, the Node Manager associated with machine machineName is not reachable'
So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
Anyone know about this issue?
Regards

There are a couple of things you need to keep in mind:
-- There is one and only one valid username / passwrod for connecting to the node manager.
-- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
-- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
That is why you have a situation, oen of the two works but never both at the same time.
What you need to do is:
-- Log in to the WL Console.
-- in the Domain Tree, click at teh root level, which is the domain name.
-- Under the security tab, under advanced there is a node manager username / password.
-- Click on "Lock and edit", and change those to match what you are using through WLST.
-- Activate changes.
-- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
StartScriptEnabled=false
to
StartScriptEnabled=true
This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
You would need to bounce the node manager for this change t take effect
Hope this helps.

I can not start a remote server via Node Manager

There is a workaround to this problem. The issue seems to be
that when the node manager tries to start the managed server
it can not find java.exe in the system path. So please go to
Control Panel->System->...->Environment, and modify your PATH
system environment variable to include the java bin directory
in it.
Then try using the node manager again to start the managed
servers and you should have no problems.
We are aware of the issue and working on having a fix for it.
Savvas
"Rakesh Chauhan" <[email protected]> wrote:
>
Hey Guys!
I am using WLS6.1 on WIN2000 boxes. And I am getting the same error on
the Admin
console when I try to start any of the two
managed servers.
<Sep 25,2001 1:39:12 PM EDT> <Info> <[email protected]:7002><WindowsProcessControl:
online successfully invoked on server 'server90', pid: 0> The interesting thing is that when I start managed server of its own,
it is started
successfully and you can Stop the managed
server from the Admin Console.
Really frusted, I hope I have configured everything correctly. Can somebody
help
me out ?
Thanks Rakesh
"Martin Matthews" <[email protected]> wrote:
This message is simply a message from the Admin Server saying that it
has asked
NodeManager on the remote machine to start a certain server.
To see the logs for server startup then you can find these either on
the Admin
machine at WL_HOME/config/NodeManagerClientLogs/<ManagedServerName>/*.log
or on the remote machine at
WL_HOME/config/NodeManagerLogs/<ManagedServerName>/*.log
Cheers
Martin
"Paul Nixon" <[email protected]> wrote:
I also would like to know the answer to the question below from Vincent.
I am getting
this message in the Admin console from either of my two managed servers
whenever
the console has successfully contacted the Node Manager in managed
server
host.
The Node Manager logs themselves also report "online successful". What
doesn't
seem to happen is WebLogic startup and I haven't found any error log
that explains
why.
I have set the Remote Startup parameters correctly [I think] for both
managed
servers so cannot see what further is required.
Any input appreciated.
Paul.
"Vincent Ducret" <[email protected]> wrote:
Hi everybody,
When I try to start a remote WLS 6.1 server from my computer, I receive
the message
below in my WLS administration console. The Node manager is runningon
the remote
machine and correctly configured, I hope!
What does this message mean ???
Thanks for your help
Vincent
<21 aoÃ»t 01 10:19:17 CEST> <Info> <[email protected]:5555>
<WindowsProcessControl:
online successfully invoked on server 'testserver', pid: 0>

Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

Hello,
I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
Can someone help me resolve this issue?
<Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
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.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

Can you see what listen address you have given to Node Manager in console or in config.xml?
<machine xsi:type="unix-machineType">
<name>Servername</name>
<node-manager>
<name>Servername</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
Another way to start Managed server is to use startManaged.sh script.

Node Manager not starting UCM Server automatically

Hi All,
I have configured Node Manager to start and stop UCM 11g server.
But whenever, I am restarting the host OS - Windows server 2003 64 bit, it does not start the UCM managed server, automatically.
I am running two managed servers on the same host OS, the first UCM manages server, starts automatically on every restart.
The second managed UCM server, does not start. I need to then manually start the managed server. There are no errors logged, and the manual start of the managed server happens without any issues.
As a workaround, I tried starting the managed server from Windows scheduler, but it does not start the server as well. I wrote a script like -
Myscript.cmd
call E:\..\user_projects\domains\prod_domain\bin\setDomainEnv.cmd
java weblogic.WLST c:\start....\ServerStart.py
scheduled the script (myscript.cmd) to run from the Windows Scheduler.
Any pointers would be very helpful. Are there any known issues, if there are two managed servers, and one starts automatically, which affects the starting of the second managed server?
I see the following error in the log file -
<14/10/2011 6:35:22 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<14/10/2011 6:35:33 PM EST> <Info> <Management> <BEA-141223> <The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.>
<14/10/2011 6:35:33 PM EST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
weblogic.management.ManagementException: [Management:141223]The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {PRDAdminServer,PRD_UCM_server1,PRD_IBR_server1}.
at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
at weblogic.Server.main(Server.java:71)
Regards
Avi

Hi Avi,
Give a cross check to your ServerStart.py
As the error states The server name PRD_UCM_Server1 specified with -Dweblogic.Name does not exist
In your ServerStart.py you might have specified as follows
sh start MAnagedWeblogic.sh server=PRD_UCM_Server1
While these are the list of Server you have in your weblogic
PRDAdminServer,
PRD_UCM_server1,(You have Specified in your command PRD_UCM_Server1
PRD_IBR_server1
The Command should be as follows
sh start ManagedWeblogic.sh server=PRD_UCM_server1
This should help
Regards
Fabian

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

Grid installtion failing with error Cannot connect to Node Manager. : Conf

I am trying to install Grid, however its failing with following error
I installed Weblogic server 10.3.4 and 11g R2 database
==============================================================
Code of Exception: Error occured while performing nmConnect : Cannot connect to Node Manager. : Configuration error while reading domain directory
Use dumpStack() to view the full stacktrace
Thu Mar 03 21:49:03 IST 2011
<traceback object at 1>
Connecting to Node Manager ...
This Exception occurred at Thu Mar 03 21:49:03 IST 2011.
Thu Mar 03 21:49:03 IST 2011
SEVERE: Exception: during stop of admin server
Thu Mar 03 21:49:03 IST 2011
Name of Exception: main.WLSTException
Thu Mar 03 21:49:03 IST 2011
Code of Exception: Error occured while performing nmConnect : Cannot connect to Node Manager. : Configuration error while reading domain directory
Use dumpStack() to view the full stacktrace
Thu Mar 03 21:49:03 IST 2011
<traceback object at 2>
Connecting to Node Manager ...
This Exception occurred at Thu Mar 03 21:49:03 IST 2011.
Thu Mar 03 21:49:03 IST 2011
Node Manager is not running
Mar 3, 2011 9:49:03 PM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand
INFO: error messages of the command :
weblogic.nodemanager.NMException: Configuration error while reading domain directory
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:301)
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClient.java:314)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:249)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:200)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:206)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:53)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:179)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:173)
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 org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
at org.python.pycode._pyx2.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.pycode._pyx41.stopManagedServer$6(/u02/oracle/Oracle/Middleware/oms11g/sysman/omsca/scripts/wls/start_server.py:142)
at org.python.pycode._pyx41.call_function(/u02/oracle/Oracle/Middleware/oms11g/sysman/omsca/scripts/wls/start_server.py)
at org.python.core.PyTableCode.call(Unknown Source)

I am still getting error, even after installing Weblogic server 10.3.2
ar 4, 2011 10:44:42 AM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand
INFO: error messages of the command :
weblogic.nodemanager.NMConnectException: Connection refused. Could not connect to NodeManager. Check that it is running at node1.slksoft.com:7,403.
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:525)
at weblogic.nodemanager.client.SSLClient.createSocket(SSLClient.java:38)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.java:227)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerClient.java:205)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.java:52)
at weblogic.management.scripting.NodeManagerService.verifyConnection(NodeManagerService.java:175)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManagerService.java:168)
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 org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
and also i am getting below error.
oracle@node1 grid]$ export ORACLE_SID=prod
[oracle@node1 grid]$ emctl status agent
EM Configuration issue. /u01/oracle/product/11.2.0/db_1/node1.soft.com_prod not found.
[oracle@node1 grid]$

NPE while starting Node Manager in SOA 11.1.1.5

I have installed SOA Suite 11g (11.1.1.5) as per Oracle Quick Start Guide for SOA Suite 11.1.1.5.
I start the database and Weblogic admin server. When I try to start the node manager, I am getting following error:
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~3\WLSERV~1
.3\common\NODEMA~1\nodemanager.properties' not found. Using default settings.
<1 Nov, 2011 9:23:28 AM> <INFO> <Saving node manager configuration properties to
'C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1\nodemanager.properties'>
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~3\WLSERV
~1.3\common\NODEMA~1\nodemanager.properties'
<1 Nov, 2011 9:23:28 AM> <SEVERE> <Fatal error in node manager server>
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>goto finish
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
C:\Oracle\Middleware\wlserver_10.3\server\bin>
I checked "C:\Oracle\Middleware\wlserver_10.3\common\nodemanager" directory. There is no nodemanager.properties file there. Do I need to create it manually?
Please advise.
Thanks,
Vivek

I cut and paste the description of the note. There is a statement with the cause that states
"This issue happens only when the display name of a NIC configured for migration in nodemanager is null"
and it is a little ambigious. It implies there is a workaround of setting the display name, but doesn't discuss how to apply this workaround; the display name it refers to generated by a code call to the NetworkInterface.getDisplayName() method from the JDK.
I assume that the display name here is the parameter called Interface within the nodemanger.properties, but there is nothing within the note that confirms this, nor if setting this to the NICE name will fix this issue. here is a full list of the nodemanger.propertes file -> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
I'd download and try the patch in your place; it's a WLS patch (as nodemanager is part of WLS) so shouldn't affect SOA Suite. Failing that, open a SR.

WLST - Failing to run nmConnect() command / node manager becomes unreachabl

Hello guys,
I'm facing some issues to setup some configurations of one application that I've deployed on weblogic 10.3.3.0.
One of the needed steps in order to configure this applications is open the WLST in offline mode an run 2 commands:
*/bea/mytrack/wlserver_10.3/common/bin/wlst.sh*
Then I try to connect in the nodemanager:
* wls:/offline> nmConnect('admin30800','weblogic_password',port='30801',domainName='track30800')*
The following error returns:
Connecting to Node Manager ...
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Jul 13, 2011 2:23:45 PM CDT> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node Manager. : Access to domain 'track30800' for user 'admin30800' denied
I did some research and found this thread here: http://kr.forums.oracle.com/forums/thread.jspa?threadID=788163
that solves the initial problem, however after I performed the nmConnect and a storeUserConfig() command, I exit() from the WLST and restart the node manager with success, the node manager becomes unreachable.
I used the WL adm console and access -> appdomain -> environments -> machines -> monitoring -> node manager status to check the unreachable status.
Thanks in advance,
Davinod

Nice it worked!!
However when I try to start the servers controlled by this node manager I got this error:
-sh-3.2$ <Jul 14, 2011 8:43:42 AM> <WARNING> <Exception while starting server 'track30800-01'>
java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
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:619)
Jul 14, 2011 8:43:42 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'track30800-01'
java.io.FileNotFoundException: /u01/track30800/user_projects/domains/track30800/servers/track30800-01/data/nodemanager/boot.properties (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at weblogic.nodemanager.server.ServerManager.saveBootIdentity(ServerManager.java:495)
at weblogic.nodemanager.server.ServerManager.saveStartupConfig(ServerManager.java:438)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:301)
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:619)
<Jul 14, 2011 8:43:42 AM CDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server track30800-01 : Exception while starting server 'track30800-01'>
Edited: Should I change the chmod for 777 for this file in order to check that all users have write permission?
-rw-r--r-- 1 root iluser 193 Jun 24 11:05 boot.properties
Did I miss a step?
Thanks,
Davinod
Edited by: davinod on Jul 14, 2011 6:58 AM

Node manager issue

Similar Messages

Maybe you are looking for