Weblogic 12c - 无法访问与计算机P360DeploymentMachine关联的节点管理器

时间:2014-07-21 03:16:59

标签: weblogic12c

我正在尝试在weblogic上启动服务器以获取此错误: 无法访问与计算机P360DeploymentMachine关联的节点管理器。

这是我在WebLogic上的机器和节点管理器:

enter image description here

我收到错误:

enter image description here

9 个答案:

答案 0 :(得分:3)

Below is the solution to the problem:
1. Actually we need to make sure we add the path of domain folder like below in "nodemanager.domains" file which is present in your weblogic folder in my case its at below path "C:\weblogic\wlserver\common\nodemanager"
values in "nodemanager.domains"
base_domain=C\:\\weblogic\\user_projects\\domains\\base_domain
AbcDomain=D\:\\Projects\\Abc\\trunk\\10X\\deploy\\AbcDomain
2. Make sure "SecureListener=false" in file "nodemanager.properties" at location "C:\weblogic\wlserver\common\nodemanager" (This is mymachine to you need to find relative path in your machine.
3. Make sure the port numbers for each of the manager servers are different and correct example 80001, 8002 and so on....dont use 7001 for manager server as this is already used by admin server.
if we do this my issue was resoled and i am sure the orginal posted issue also should be resolved.

答案 1 :(得分:3)

我正面临着这个问题。尝试了几种方法后,我意识到我没有运行节点管理器服务。

要启动节点管理器服务,您需要转到

  1. C:\ Oracle \ Middleware \ Oracle_Home \ user_projects \ domains \ base_domain \ bin \ startNodeManager.cmd(特定于我的电脑)

  2. 以管理员权限运行。

  3. 它解决了我的问题。

答案 2 :(得分:1)

使用connect()连接到weblogic服务器。提供详细信息。确保使用ts协议连接到管理服务器,即t3://a.b.c.d:port

注册节点管理器。

停止节点管理器并再次启动它。这对我有用

答案 3 :(得分:1)

嗨,我遇到了类似的问题,我做了很多研究,最后通过一个非常简单的技巧对故障排除进行了测试,只需手动启动ManagedWeblogic服务器即可。

只需以admin身份在cmd中运行以下命令

cd C:\Oracle\user_projects\domains\base_domain\bin 
startManagedWebLogic.cmd ODI_server1 http://localhost:7001

答案 4 :(得分:0)

如果没有看到一些额外的配置文件,很难给出明确的答案。这些是我先检查的地方

  • 完全重启nodemanager服务(确保它干净利落)
  • 检查nodemanager正在运行的端口

其他托管服务器是否启动或者这是您构建的第一个?

如果您能提供更多信息,请尽快提供帮助

AB

答案 5 :(得分:0)

I am also facing same error with same settings as seen the snap shot shared by "Hbargujar", Please find below details on my machine and if you can help me, let me know if you need any specific details of configuration as well.
Version of weblogic: 10.3.6.0
Configured below elements:
Managed Servers:
1. ManagedServer-0
2. ManagedServer-1

Cluster: 
    cluster1

Machine:
    MachineForCluster-0

Config File has below server settings to map machine to AdminServer:
  <server>
    <name>AdminServer</name>
    <machine>MachineForCluster-0</machine>
    <listen-address>localhost</listen-address>
  </server>

Error Message: For server ManagedServer-0, the Node Manager associated with machine MachineForCluster-0 is not reachable.
Message icon - Warning 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.

I tried to start Node manager by using below command:
    startNodeManager(verbose='true',NodeManagerHome='C:\\weblogic\\wlserver\\common\    \nodemanager',ListenPort='5556',ListenAddress='localhost')
but 
its didn't start with port "5556" but if i give some other port number it starts however when i start managed server from admin console i get the same error messages as above.

Let me know i am missing anything here...

答案 6 :(得分:0)

确保您的NodeManager使用与您在AdminServer中设置的设置相同的设置。我将NodeManager设置为在AdminServer中使用普通套接字,但默认情况下实际的NodeManager在安全套接字中启动。检查NodeManager日志以确认。例如,这是我的日志

<Nov 3, 2016 9:22:45 PM EDT> <INFO> <Secure socket listener started on port 5556, host /192.168.2.3>

我收到了无法访问的错误。我在SecureListener=false中更改了参数nodemanager.properties后,我可以正常启动服务器。

答案 7 :(得分:0)

我是如何解决的:

侦听地址:删除localhost并放入FQDN - hostname + domain_name

转到&gt;&gt; nodemanager / nodemanager.properties(在Weblogic Server中) 编辑ListenAddress = to hostanme + domain_name。

重新启动托管服务。

答案 8 :(得分:0)

当我关闭我的一台服务器(在Summary of Servers -> Control选项卡上)时,这发生在我身上,如何重新启动它也不是显而易见的。

在我特定的情况下,这实际上非常简单:使用Windows服务管理单元(Start -> Run -> services.msc)重新启动。我在WebLogic中配置的每个服务器都存在一个服务。 (请注意,启动服务后,WebLogic控制台中的状态可能需要几分钟才能反映出RUNNING状态。)

在这种情况下,无需配置节点管理器!