hadoop集群格式化hdfs报错

[admi_nistrator]

自己在虚拟机上配置了一个hadoop2.2集群（6台机器），zookeeper集群（3台）已经正常启动，然后启动jounalnode并且也正常启动（jps有相关进程）。上面两步完成以后在namenode上执行 hdfs namenode -format 命令格式化hdfs，结果报错了，百度无果求大神帮忙，下面是执行格式化命令时候命令行的情况：

[root@centos01 hadoop-2.6.0]# hdfs namenode -format
15/07/06 09:36:27 INFO namenode.NameNode: STARTUP_MSG: 
/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG:   host = centos01/192.168.10.101
STARTUP_MSG:   args = [-format]
STARTUP_MSG:   version = 2.6.0
STARTUP_MSG:   classpath = /itcast/hadoop-2.6.0/etc/hadoop:/itcast/hadoop-2.6.0/share/hadoop/common/lib/protobuf-java-2.5.0.jar:/itcast/hadoop-2.6.0/share/hadoop/common/lib/paranamer-2.3.jar............/itcast/hadoop-2.6.0/contrib/capacity-scheduler/*.jar
STARTUP_MSG:   build = Unknown -r Unknown; compiled by 'root' on 2014-12-23T03:59Z
STARTUP_MSG:   java = 1.7.0_79
************************************************************/
15/07/06 09:36:27 INFO namenode.NameNode: registered UNIX signal handlers for [TERM, HUP, INT]
15/07/06 09:36:27 INFO namenode.NameNode: createNameNode [-format]
Formatting using clusterid: CID-156e895b-86b8-447a-9191-cd75f03c8fb9
15/07/06 09:36:29 INFO namenode.FSNamesystem: No KeyProvider found.
15/07/06 09:36:29 INFO namenode.FSNamesystem: fsLock is fair:true
15/07/06 09:36:29 INFO blockmanagement.DatanodeManager: dfs.block.invalidate.limit=1000
15/07/06 09:36:29 INFO blockmanagement.DatanodeManager: dfs.namenode.datanode.registration.ip-hostname-check=true
15/07/06 09:36:29 INFO blockmanagement.BlockManager: dfs.namenode.startup.delay.block.deletion.sec is set to 000:00:00:00.000
15/07/06 09:36:29 INFO blockmanagement.BlockManager: The block deletion will start around 2015 Jul 06 09:36:29
15/07/06 09:36:29 INFO util.GSet: Computing capacity for map BlocksMap
15/07/06 09:36:29 INFO util.GSet: VM type       = 64-bit
15/07/06 09:36:29 INFO util.GSet: 2.0% max memory 966.7 MB = 19.3 MB
15/07/06 09:36:29 INFO util.GSet: capacity      = 2^21 = 2097152 entries
15/07/06 09:36:29 INFO blockmanagement.BlockManager: dfs.block.access.token.enable=false
15/07/06 09:36:29 INFO blockmanagement.BlockManager: defaultReplication         = 3
15/07/06 09:36:29 INFO blockmanagement.BlockManager: maxReplication             = 512
15/07/06 09:36:29 INFO blockmanagement.BlockManager: minReplication             = 1
15/07/06 09:36:29 INFO blockmanagement.BlockManager: maxReplicationStreams      = 2
15/07/06 09:36:29 INFO blockmanagement.BlockManager: shouldCheckForEnoughRacks  = false
15/07/06 09:36:29 INFO blockmanagement.BlockManager: replicationRecheckInterval = 3000
15/07/06 09:36:29 INFO blockmanagement.BlockManager: encryptDataTransfer        = false
15/07/06 09:36:29 INFO blockmanagement.BlockManager: maxNumBlocksToLog          = 1000
15/07/06 09:36:29 INFO namenode.FSNamesystem: fsOwner             = root (auth:SIMPLE)
15/07/06 09:36:29 INFO namenode.FSNamesystem: supergroup          = supergroup
15/07/06 09:36:29 INFO namenode.FSNamesystem: isPermissionEnabled = true
15/07/06 09:36:29 INFO namenode.FSNamesystem: Determined nameservice ID: ns1
15/07/06 09:36:29 INFO namenode.FSNamesystem: HA Enabled: true
15/07/06 09:36:29 INFO namenode.FSNamesystem: Append Enabled: true
15/07/06 09:36:30 INFO util.GSet: Computing capacity for map INodeMap
15/07/06 09:36:30 INFO util.GSet: VM type       = 64-bit
15/07/06 09:36:30 INFO util.GSet: 1.0% max memory 966.7 MB = 9.7 MB
15/07/06 09:36:30 INFO util.GSet: capacity      = 2^20 = 1048576 entries
15/07/06 09:36:30 INFO namenode.NameNode: Caching file names occuring more than 10 times
15/07/06 09:36:30 INFO util.GSet: Computing capacity for map cachedBlocks
15/07/06 09:36:30 INFO util.GSet: VM type       = 64-bit
15/07/06 09:36:30 INFO util.GSet: 0.25% max memory 966.7 MB = 2.4 MB
15/07/06 09:36:30 INFO util.GSet: capacity      = 2^18 = 262144 entries
15/07/06 09:36:30 INFO namenode.FSNamesystem: dfs.namenode.safemode.threshold-pct = 0.9990000128746033
15/07/06 09:36:30 INFO namenode.FSNamesystem: dfs.namenode.safemode.min.datanodes = 0
15/07/06 09:36:30 INFO namenode.FSNamesystem: dfs.namenode.safemode.extension     = 30000
15/07/06 09:36:30 INFO namenode.FSNamesystem: Retry cache on namenode is enabled
15/07/06 09:36:30 INFO namenode.FSNamesystem: Retry cache will use 0.03 of total heap and retry cache entry expiry time is 600000 millis
15/07/06 09:36:30 INFO util.GSet: Computing capacity for map NameNodeRetryCache
15/07/06 09:36:30 INFO util.GSet: VM type       = 64-bit
15/07/06 09:36:30 INFO util.GSet: 0.029999999329447746% max memory 966.7 MB = 297.0 KB
15/07/06 09:36:30 INFO util.GSet: capacity      = 2^15 = 32768 entries
15/07/06 09:36:30 INFO namenode.NNConf: ACLs enabled? false
15/07/06 09:36:30 INFO namenode.NNConf: XAttrs enabled? true
15/07/06 09:36:30 INFO namenode.NNConf: Maximum size of an xattr: 16384
15/07/06 09:36:30 FATAL namenode.NameNode: Failed to start namenode.
java.lang.IllegalArgumentException: Unable to construct journal, qjournal://contos04:8485;centos05:8485;centos06:8485/ns1
        at org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1593)
        at org.apache.hadoop.hdfs.server.namenode.FSEditLog.initJournals(FSEditLog.java:276)
        at org.apache.hadoop.hdfs.server.namenode.FSEditLog.initJournalsForWrite(FSEditLog.java:241)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:935)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1379)
        at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1504)
Caused by: java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
        at org.apache.hadoop.hdfs.server.namenode.FSEditLog.createJournal(FSEditLog.java:1591)
        ... 5 more
Caused by: java.lang.NullPointerException
        at org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannelMetrics.getName(IPCLoggerChannelMetrics.java:107)
        at org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannelMetrics.create(IPCLoggerChannelMetrics.java:91)
        at org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannel.<init>(IPCLoggerChannel.java:178)
        at org.apache.hadoop.hdfs.qjournal.client.IPCLoggerChannel$1.createLogger(IPCLoggerChannel.java:156)
        at org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.createLoggers(QuorumJournalManager.java:367)
        at org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.createLoggers(QuorumJournalManager.java:149)
        at org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.<init>(QuorumJournalManager.java:116)
        at org.apache.hadoop.hdfs.qjournal.client.QuorumJournalManager.<init>(QuorumJournalManager.java:105)
        ... 10 more
15/07/06 09:36:30 INFO util.ExitUtil: Exiting with status 1
15/07/06 09:36:30 INFO namenode.NameNode: SHUTDOWN_MSG: 
/************************************************************
SHUTDOWN_MSG: Shutting down NameNode at centos01/192.168.10.101
************************************************************/

有知道怎么解决的或遇到过相同问题的帮忙看一下吧。。。
现在手上没分了。。。有分的话一定多给

[Q446512799]

[hadoop@localhost subdir0]$ jps 6644 NodeManager 5445 Jps 6184 DataNode 3668 ResourceManager 2940 NameNode 3519 SecondaryNameNode 我前面进程有些没起来后来发现是配置文件不对造成的，我也刚学

[章牧之]

我也遇到了相同的问题，那位大神能帮忙一下呢？