resourcemanager-hadoop2.4.1 ResourceManager的8088 web端口无法访问

问题描述

hadoop2.4.1 ResourceManager的8088 web端口无法访问

hadoop ResourceManager的8088端口无法访问。我们的集群是部署在阿里云服务器，版本为hadoop2.4.1。希望大神门能指导一下，谢谢！

解决方案

ch查看系统日志信息

解决方案二：

日志显示没有问题

STARTUP_MSG: build = Unknown -r Unknown; compiled by 'root' on 2014-07-31T07:06Z
STARTUP_MSG: java = 1.7.0_71
************************************************************/
2015-01-09 20:03:03,258 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: registered UNIX signal handlers for [TERM, HUP, INT]
2015-01-09 20:03:03,496 INFO org.apache.hadoop.conf.Configuration: found resource core-site.xml at file:/usr/local/hadoop/hadoop-2.4.1/etc/hadoop/core-site.xml
2015-01-09 20:03:03,632 INFO org.apache.hadoop.security.Groups: clearing userToGroupsMap cache
2015-01-09 20:03:03,639 INFO org.apache.hadoop.conf.Configuration: found resource yarn-site.xml at file:/usr/local/hadoop/hadoop-2.4.1/etc/hadoop/yarn-site.xml
2015-01-09 20:03:03,712 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.RMFatalEventType for class org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMFatalEventDispatcher
2015-01-09 20:03:03,957 INFO org.apache.hadoop.yarn.server.resourcemanager.security.NMTokenSecretManagerInRM: NMTokenKeyRollingInterval: 86400000ms and NMTokenKeyActivationDelay: 900000ms
2015-01-09 20:03:03,962 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMContainerTokenSecretManager: ContainerTokenKeyRollingInterval: 86400000ms and ContainerTokenKeyActivationDelay: 900000ms
2015-01-09 20:03:03,966 INFO org.apache.hadoop.yarn.server.resourcemanager.security.AMRMTokenSecretManager: Rolling master-key for amrm-tokens
2015-01-09 20:03:03,980 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStoreEventType for class org.apache.hadoop.yarn.server.resourcemanager.recovery.RMStateStore$ForwardingEventHandler
2015-01-09 20:03:04,169 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.NodesListManagerEventType for class org.apache.hadoop.yarn.server.resourcemanager.NodesListManager
2015-01-09 20:03:04,169 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Using Scheduler: org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler
2015-01-09 20:03:04,205 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.scheduler.event.SchedulerEventType for class org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$SchedulerEventDispatcher
2015-01-09 20:03:04,207 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.rmapp.RMAppEventType for class org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationEventDispatcher
2015-01-09 20:03:04,208 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.rmapp.attempt.RMAppAttemptEventType for class org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$ApplicationAttemptEventDispatcher
2015-01-09 20:03:04,209 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeEventType for class org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$NodeEventDispatcher
2015-01-09 20:03:04,297 INFO org.apache.hadoop.metrics2.impl.MetricsConfig: loaded properties from hadoop-metrics2.properties
2015-01-09 20:03:04,394 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s).
2015-01-09 20:03:04,394 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: ResourceManager metrics system started
2015-01-09 20:03:04,402 INFO org.apache.hadoop.conf.Configuration: found resource capacity-scheduler.xml at file:/usr/local/hadoop/hadoop-2.4.1/etc/hadoop/capacity-scheduler.xml
2015-01-09 20:03:04,474 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue: root, capacity=1.0, asboluteCapacity=1.0, maxCapacity=1.0, asboluteMaxCapacity=1.0, state=RUNNING, acls=ADMINISTER_QUEUE:*SUBMIT_APPLICATIONS:*
2015-01-09 20:03:04,475 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.ParentQueue: Initialized parent-queue root name=root, fullname=root
2015-01-09 20:03:04,485 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.LeafQueue: Initializing default
capacity = 1.0 [= (float) configuredCapacity / 100 ]
asboluteCapacity = 1.0 [= parentAbsoluteCapacity * capacity ]
maxCapacity = 1.0 [= configuredMaxCapacity ]
absoluteMaxCapacity = 1.0 [= 1.0 maximumCapacity undefined, (parentAbsoluteMaxCapacity * maximumCapacity) / 100 otherwise ]
userLimit = 100 [= configuredUserLimit ]
userLimitFactor = 1.0 [= configuredUserLimitFactor ]
maxApplications = 10000 [= configuredMaximumSystemApplicationsPerQueue or (int)(configuredMaximumSystemApplications * absoluteCapacity)]
maxApplicationsPerUser = 10000 [= (int)(maxApplications * (userLimit / 100.0f) * userLimitFactor) ]
maxActiveApplications = 1 [= max((int)ceil((clusterResourceMemory / minimumAllocation) * maxAMResourcePerQueuePercent * absoluteMaxCapacity),1) ]
maxActiveAppsUsingAbsCap = 1 [= max((int)ceil((clusterResourceMemory / minimumAllocation) maxAMResourcePercent * absoluteCapacity),1) ]
maxActiveApplicationsPerUser = 1 [= max((int)(maxActiveApplications * (userLimit / 100.0f) * userLimitFactor),1) ]
usedCapacity = 0.0 [= usedResourcesMemory / (clusterResourceMemory * absoluteCapacity)]
absoluteUsedCapacity = 0.0 [= usedResourcesMemory / clusterResourceMemory]
maxAMResourcePerQueuePercent = 0.1 [= configuredMaximumAMResourcePercent ]
minimumAllocationFactor = 0.9583333 [= (float)(maximumAllocationMemory - minimumAllocationMemory) / maximumAllocationMemory ]
numContainers = 0 [= currentNumContainers ]
state = RUNNING [= configuredState ]
acls = ADMINISTER_QUEUE:*SUBMIT_APPLICATIONS: [= configuredAcls ]
nodeLocalityDelay = 40

2015-01-09 20:03:04,485 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Initialized queue: default: capacity=1.0, absoluteCapacity=1.0, usedResources=, usedCapacity=0.0, absoluteUsedCapacity=0.0, numApps=0, numContainers=0
2015-01-09 20:03:04,485 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Initialized queue: root: numChildQueue= 1, capacity=1.0, absoluteCapacity=1.0, usedResources=usedCapacity=0.0, numApps=0, numContainers=0
2015-01-09 20:03:04,485 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Initialized root queue root: numChildQueue= 1, capacity=1.0, absoluteCapacity=1.0, usedResources=usedCapacity=0.0, numApps=0, numContainers=0
2015-01-09 20:03:04,485 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Initialized CapacityScheduler with calculator=class org.apache.hadoop.yarn.util.resource.DefaultResourceCalculator, minimumAllocation=<>, maximumAllocation=<>, asynchronousScheduling=false, asyncScheduleInterval=5ms
2015-01-09 20:03:04,523 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.RMAppManagerEventType for class org.apache.hadoop.yarn.server.resourcemanager.RMAppManager
2015-01-09 20:03:04,528 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.amlauncher.AMLauncherEventType for class org.apache.hadoop.yarn.server.resourcemanager.amlauncher.ApplicationMasterLauncher
2015-01-09 20:03:04,530 INFO org.apache.hadoop.yarn.server.resourcemanager.RMNMInfo: Registered RMNMInfo MBean
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,533 INFO org.apache.hadoop.yarn.event.AsyncDispatcher: Registering class org.apache.hadoop.yarn.server.resourcemanager.ahs.WritingHistoryEventType for class org.apache.hadoop.yarn.server.resourcemanager.ahs.RMApplicationHistoryWriter$ForwardingEventHandler
2015-01-09 20:03:04,534 INFO org.apache.hadoop.util.HostsFileReader: Refreshing hosts (include/exclude) list
2015-01-09 20:03:04,544 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Transitioning to active state
2015-01-09 20:03:04,549 INFO org.apache.hadoop.yarn.server.resourcemanager.security.AMRMTokenSecretManager: Rolling master-key for amrm-tokens
2015-01-09 20:03:04,549 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMContainerTokenSecretManager: Rolling master-key for container-tokens
2015-01-09 20:03:04,552 INFO org.apache.hadoop.yarn.server.resourcemanager.security.NMTokenSecretManagerInRM: Rolling master-key for nm-tokens
2015-01-09 20:03:04,552 INFO org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager: Updating the current master key for generating delegation tokens
2015-01-09 20:03:04,553 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMDelegationTokenSecretManager: storing master key with keyID 1
2015-01-09 20:03:04,553 INFO org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager: Starting expired delegation token remover thread, tokenRemoverScanInterval=60 min(s)
2015-01-09 20:03:04,554 INFO org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager: Updating the current master key for generating delegation tokens
2015-01-09 20:03:04,554 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMDelegationTokenSecretManager: storing master key with keyID 2
2015-01-09 20:03:04,586 INFO org.apache.hadoop.ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue
2015-01-09 20:03:04,599 INFO org.apache.hadoop.ipc.Server: Starting Socket Reader #1 for port 8031
2015-01-09 20:03:04,620 INFO org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl: Adding protocol org.apache.hadoop.yarn.server.api.ResourceTrackerPB to the server
2015-01-09 20:03:04,620 INFO org.apache.hadoop.ipc.Server: IPC Server Responder: starting
2015-01-09 20:03:04,620 INFO org.apache.hadoop.ipc.Server: IPC Server listener on 8031: starting
2015-01-09 20:03:04,644 INFO org.apache.hadoop.ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue
2015-01-09 20:03:04,650 INFO org.apache.hadoop.ipc.Server: Starting Socket Reader #1 for port 8030
2015-01-09 20:03:04,661 INFO org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl: Adding protocol org.apache.hadoop.yarn.api.ApplicationMasterProtocolPB to the server
2015-01-09 20:03:04,662 INFO org.apache.hadoop.ipc.Server: IPC Server Responder: starting
2015-01-09 20:03:04,666 INFO org.apache.hadoop.ipc.Server: IPC Server listener on 8030: starting
2015-01-09 20:03:04,759 INFO org.apache.hadoop.ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue
2015-01-09 20:03:04,760 INFO org.apache.hadoop.ipc.Server: Starting Socket Reader #1 for port 8032
2015-01-09 20:03:04,764 INFO org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl: Adding protocol org.apache.hadoop.yarn.api.ApplicationClientProtocolPB to the server
2015-01-09 20:03:04,765 INFO org.apache.hadoop.ipc.Server: IPC Server Responder: starting
2015-01-09 20:03:04,765 INFO org.apache.hadoop.ipc.Server: IPC Server listener on 8032: starting
2015-01-09 20:03:04,776 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Transitioned to active state
2015-01-09 20:03:04,843 INFO org.mortbay.log: Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
2015-01-09 20:03:04,847 INFO org.apache.hadoop.http.HttpRequestLog: Http request log for http.requests.resourcemanager is not defined
2015-01-09 20:03:04,858 INFO org.apache.hadoop.http.HttpServer2: Added global filter 'safety' (class=org.apache.hadoop.http.HttpServer2$QuotingInputFilter)
2015-01-09 20:03:04,860 INFO org.apache.hadoop.http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context cluster
2015-01-09 20:03:04,860 INFO org.apache.hadoop.http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context static
2015-01-09 20:03:04,860 INFO org.apache.hadoop.http.HttpServer2: Added filter static_user_filter (class=org.apache.hadoop.http.lib.StaticUserWebFilter$StaticUserFilter) to context logs
2015-01-09 20:03:04,863 INFO org.apache.hadoop.http.HttpServer2: adding path spec: /cluster/*
2015-01-09 20:03:04,864 INFO org.apache.hadoop.http.HttpServer2: adding path spec: /ws/*
2015-01-09 20:03:04,877 INFO org.apache.hadoop.http.HttpServer2: Jetty bound to port 8090
2015-01-09 20:03:04,877 INFO org.mortbay.log: jetty-6.1.26
2015-01-09 20:03:04,901 INFO org.mortbay.log: Extract jar:file:/usr/local/hadoop/hadoop-2.4.1/share/hadoop/yarn/hadoop-yarn-common-2.4.1.jar!/webapps/cluster to /tmp/Jetty_hadoop1_8090_cluster____t9zxpd/webapp
2015-01-09 20:03:05,183 INFO org.mortbay.log: Started SelectChannelConnector@hadoop1:8090
2015-01-09 20:03:05,183 INFO org.apache.hadoop.yarn.webapp.WebApps: Web app /cluster started at 8090
2015-01-09 20:03:05,549 INFO org.apache.hadoop.yarn.webapp.WebApps: Registered webapp guice modules
2015-01-09 20:03:05,580 INFO org.apache.hadoop.ipc.CallQueueManager: Using callQueue class java.util.concurrent.LinkedBlockingQueue
2015-01-09 20:03:05,580 INFO org.apache.hadoop.ipc.Server: Starting Socket Reader #1 for port 8033
2015-01-09 20:03:05,583 INFO org.apache.hadoop.yarn.factories.impl.pb.RpcServerFactoryPBImpl: Adding protocol org.apache.hadoop.yarn.server.api.ResourceManagerAdministrationProtocolPB to the server
2015-01-09 20:03:05,584 INFO org.apache.hadoop.ipc.Server: IPC Server Responder: starting
2015-01-09 20:03:05,584 INFO org.apache.hadoop.ipc.Server: IPC Server listener on 8033: starting
2015-01-09 20:03:07,104 INFO org.apache.hadoop.yarn.util.RackResolver: Resolved hadoop1 to /default-rack
2015-01-09 20:03:07,112 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: NodeManager from node hadoop1(cmPort: 53678 httpPort: 8042) registered with capability: , assigned nodeId hadoop1:53678
2015-01-09 20:03:07,114 INFO org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: hadoop1:53678 Node Transitioned from NEW to RUNNING
2015-01-09 20:03:07,116 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Added node hadoop1:53678 clusterResource:
2015-01-09 20:03:07,487 INFO org.apache.hadoop.yarn.util.RackResolver: Resolved hadoop4 to /default-rack
2015-01-09 20:03:07,488 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: NodeManager from node hadoop4(cmPort: 41495 httpPort: 8042) registered with capability: , assigned nodeId hadoop4:41495
2015-01-09 20:03:07,488 INFO org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: hadoop4:41495 Node Transitioned from NEW to RUNNING
2015-01-09 20:03:07,488 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Added node hadoop4:41495 clusterResource:
2015-01-09 20:03:07,667 INFO org.apache.hadoop.yarn.util.RackResolver: Resolved hadoop2 to /default-rack
2015-01-09 20:03:07,668 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: NodeManager from node hadoop2(cmPort: 57559 httpPort: 8042) registered with capability: , assigned nodeId hadoop2:57559
2015-01-09 20:03:07,668 INFO org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: hadoop2:57559 Node Transitioned from NEW to RUNNING
2015-01-09 20:03:07,668 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Added node hadoop2:57559 clusterResource:
2015-01-09 20:03:07,719 INFO org.apache.hadoop.yarn.util.RackResolver: Resolved hadoop3 to /default-rack
2015-01-09 20:03:07,720 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: NodeManager from node hadoop3(cmPort: 33124 httpPort: 8042) registered with capability: , assigned nodeId hadoop3:33124
2015-01-09 20:03:07,720 INFO org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: hadoop3:33124 Node Transitioned from NEW to RUNNING
2015-01-09 20:03:07,720 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Added node hadoop3:33124 clusterResource:
2015-01-09 20:03:07,937 INFO org.apache.hadoop.yarn.util.RackResolver: Resolved hadoop5 to /default-rack
2015-01-09 20:03:07,937 INFO org.apache.hadoop.yarn.server.resourcemanager.ResourceTrackerService: NodeManager from node hadoop5(cmPort: 59848 httpPort: 8042) registered with capability: , assigned nodeId hadoop5:59848
2015-01-09 20:03:07,937 INFO org.apache.hadoop.yarn.server.resourcemanager.rmnode.RMNodeImpl: hadoop5:59848 Node Transitioned from NEW to RUNNING
2015-01-09 20:03:07,938 INFO org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler: Added node hadoop5:59848 clusterResource:
2015-01-10 20:03:04,549 INFO org.apache.hadoop.yarn.server.resourcemanager.security.AMRMTokenSecretManager: Rolling master-key for amrm-tokens
2015-01-10 20:03:04,552 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMContainerTokenSecretManager: Rolling master-key for container-tokens
2015-01-10 20:03:04,552 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMContainerTokenSecretManager: Going to activate master-key with key-id -1944612366 in 900000ms
2015-01-10 20:03:04,552 INFO org.apache.hadoop.yarn.server.resourcemanager.security.NMTokenSecretManagerInRM: Rolling master-key for nm-tokens
2015-01-10 20:03:04,552 INFO org.apache.hadoop.yarn.server.resourcemanager.security.NMTokenSecretManagerInRM: Going to activate master-key with key-id -1234669175 in 900000ms
2015-01-10 20:03:06,085 INFO org.apache.hadoop.security.token.delegation.AbstractDelegationTokenSecretManager: Updating the current master key for generating delegation tokens
2015-01-10 20:03:06,085 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMDelegationTokenSecretManager: storing master key with keyID 3
2015-01-10 20:18:04,552 INFO org.apache.hadoop.yarn.server.resourcemanager.security.RMContainerTokenSecretManager: Activating next master key with id: -1944612366
2015-01-10 20:18:04,552 INFO org.apache.hadoop.yarn.server.resourcemanager.security.NMTokenSecretManagerInRM: Activating next master key with id: -1234669175

解决方案三：

同求解答，google了很多说是防火墙的问题，但关了防火墙还是无法访问，重新配置了yarn-site.xml, 把8088换成别的端口号也不行。

时间： 2024-04-16 05:24:30

resourcemanager-hadoop2.4.1 ResourceManager的8088 web端口无法访问的相关文章

集群-Hbase web界面不能访问

问题描述 Hbase web界面不能访问 刚开始 hadoop的集群都是在root用户下创建的,一切都正常,web界面也可以正常访问. 为了安全起见,把整个hadoop集群改用普通用户hadoop来管理.切换用户后,Hbase 的web界面不可以访问,但是hadoop的web界面是可以正常访问的. hadoop集群包含:Zookeeper3.4.6 hadoop2.6.0 Hbase1.0 公司环境:跪求答案,谢谢!!!!!!!1 解决方案 从楼主的描述,应该是用户权限问题吧. hbase日志中

Oray什么是WEB端口穿透

WEB端口穿透是Oray针对自组服务器用户提出的一项解决方案,就目前市场情况看,在较长的时间内,由端口问题导致自组服务器用户的WEB服务接口无法被访问将一直存在.为此,Oray正式推出端口穿透功能,帮助解决端口问题.

Oray如何开通WEB端口穿透服务

请使用护照密码登录http://www.oray.com依次打开[我的控制台]-[产品管理]-[WEB端口穿透]进入管理页面. 在WEB端口穿透管理页面点击"新建端口穿透",进入开通端口穿透服务的流程. 首先选择需要开通的服务时间以及流量,选择完毕以后点击下一步. 进入任务设置这一步很关键,请您务必认真填写,如下图的设置选项说明需求:http://zengkebing.gicp.net:81是服务器原本的访问地址,通过ORAY的WEB端口穿透服务来实现用www.liujingyi.co

java-JAVA SSH开放的web项目 IE访问出现400错误

问题描述 JAVA SSH开放的web项目 IE访问出现400错误 用JAVA 开放的一套软件,基于SSH框架,Tomcat容器,服务器用的是Lniux 现在遇到问题,当客户端用IE使用系统的时候,IE会出现无法找到该网页,不局限于一个模块,多个模块在访问的时候都有遇到,但是不常出现,通过后台记录访问地址,访问地址贴到IE浏览器里面是可以正常使用的.请各位大神帮忙看看,IE版本 IE8 . 解决方案 400是服务器端的错误,但不能进一步明确是什么问题. 把日志代码贴出来.

关于myeclipse里web工程公网访问src下servlet的问题！急!!!

问题描述 关于myeclipse里web工程公网访问src下servlet的问题!急!!! 我将myeclipse的8080端口与花生壳的8080端口绑定了,花生壳给的外网访问地址:qq362656437.imwork.net:32581.请问怎么访问我src目录下的CoreServlet???急! 解决方案 玩盗链?人家有反盗链嘞- 解决方案二: 不应该把项目打包放服务器上么,比如Tomcat,JBoss~ 解决方案三: 我将myeclipse的8080端口与花生壳的8080端口绑定了,花生壳

Web Services的访问方式

目前对于云计算的全部关注中,存储更多的被视为最基础的平台.时至今日,许多云计算提供的仅仅局限于CPU内核的集合,还特别为之定制了内存分配,低转速的存储,或者还有一些可以面向互联网的IP技术.最近,出现了有趣的关于云的新技术,特别是对于使用 Web Services的访问方式,从而使访问存储不再受限于文件或者NFS加载点了. 通俗的数据存储和管理的"企业级特征"在IT架构创新上不断更新.存储架构师意识到这些特征对于关键业务和生产应用特别重要,但目前的云计算还缺少这些特征.本篇白皮书的目标

《渐进增强——跨平台用户体验设计》一1.7　提升Web的可访问性

1.7 提升Web的可访问性 Tim关于Web的看法是:任何Web页面,我们都可以把它看成一个文档.同样内容的文档,我们只需要保留一份就够了.不论用户通过何种浏览器或设备访问,内容是唯一的,不同的只是呈现形式.这样做的好处显而易见--Web世界是由"超媒体"[17]联系起来的庞大网络,我在一个页面中添加了一个超链接,却不能预料到用户是通过什么设备访问并点击的这个链接.如果文档是唯一的,那么入口链接也一定是唯一的.我只需要添加一个链接,用户无论从任何设备点击它,都能获得最佳的访问体验.

Java Web开发之访问路径问题分析_JSP编程

本文实例讲述了Java Web开发之访问路径问题.分享给大家供大家参考.具体如下: Web应用是由大量的文件组成的,系统等运行主要是靠文件之间的相互调用来完成,调用就是根据文件的位置来确定的.如果你在访问某个文件的时候,系统报下面这样的错误,如果你的文件名没有写错,就是路径出错了. 为了说明路径问题,我们假设有以下的文档结构: 这是JBuilder2006下的一个截图,应用的名字是filepathweb,有两个文件夹,aa和bb,其中aa下有a_a.jsp和a_b.jsp两个文件,bb下有b_a

（转）利用个人电脑搭建网站WEB服务器域名访问

本文转载:http://www.cnblogs.com/fangpage/archive/2011/11/22/prowebserver.html 今天看到有人问我用个人电脑能否可以做网站服务器使用,并让internet通过域名访问吗?答案是肯定可以的,不过我是2M的ADSL+路由,访问的速度着实不是很理想,如果只想尝尝鲜,体验下,或者你的网站又不想备案,你家用的光纤,有足够的带宽,不妨按照我说的步骤玩玩看. 下面的这些工作是用我家的ADSL+路由器+花生壳+方配网站服务器的环境为例来搭建一台网