falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peng (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FALCON-502) Unable to connect to Falcon server when running standalone-cluster.html
Date Wed, 09 Jul 2014 16:51:05 GMT
Peng created FALCON-502:
---------------------------

             Summary: Unable to connect to Falcon server when running standalone-cluster.html
                 Key: FALCON-502
                 URL: https://issues.apache.org/jira/browse/FALCON-502
             Project: Falcon
          Issue Type: Bug
            Reporter: Peng


My falcon server works well, however when I am running the examples. 
bin/falcon entity -submit -type cluster -file examples/entity/filesystem/standalone-cluster.xml
The result is Unable to connect to Falcon server, please check if the URL is correct and Falcon
server is up and running
java.net.SocketTimeoutException: Read timed out.

However, -bash-4.1$ ./bin/falcon-status 
Hadoop is installed, adding hadoop classpath to falcon classpath
Falcon server is running (on https://localhost:15443/) show the server runs well. Below is
the error of the log.
____________________________________________________________


Error: Invalid Execute server or port: localhost:15443
Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: Protocol message
contained-bash-4.1$ ./bin/falcon-status 
Hadoop is installed, adding hadoop classpath to falcon classpath
Falcon server is running (on https://localhost:15443/) an invalid tag (zero).; Host Details
: local host is: "treenever-dl-vm0.champ.corp.yahoo.com/10.74.91.247"; destination host is:
"localhost":15443;  (FalconWebException:67)
2014-07-09 16:33:36,234 INFO  - [30056312@qtp-31571602-8:peng:POST//entities/submit/cluster
3fd8862c-20a4-4aba-a992-5df8289f2e1c] ~ {Action:submit, Dimensions:{entityType=cluster, colo=NULL},
Status: FAILED, Time-taken:976472562633 ns} (METRIC:33)
2014-07-09 16:33:36,233 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Parsed Entity: local (EntityParser:84)
2014-07-09 16:33:36,238 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Validating read interface: hftp://localhost:50010
(ProcessEntityParser:91)
2014-07-09 16:33:36,264 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ fs.default.name is deprecated. Instead, use fs.defaultFS
(deprecation:1009)
2014-07-09 16:33:36,265 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Validating write interface: hdfs://localhost:9000
(ProcessEntityParser:98)
2014-07-09 16:33:36,284 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ fs.default.name is deprecated. Instead, use fs.defaultFS
(deprecation:1009)
2014-07-09 16:33:36,285 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Validating execute interface: localhost:9001 (ProcessEntityParser:127)
2014-07-09 16:33:36,304 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ mapred.job.tracker is deprecated. Instead, use mapreduce.jobtracker.address
(deprecation:1009)
2014-07-09 16:33:36,325 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Connecting to ResourceManager at localhost/127.0.0.1:9001
(RMProxy:92)
2014-07-09 16:33:37,328 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Retrying connect to server: localhost/127.0.0.1:9001.
Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS) (Client:841)
2014-07-09 16:33:38,329 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Retrying connect to server: localhost/127.0.0.1:9001.
Already tried 1 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS) (Client:841)
2014-07-09 16:33:39,330 INFO  - [32359056@qtp-31571602-9:peng:POST//entities/submit/cluster
bcfe7638-96ee-4d5f-a4b1-f4037e4f3bdd] ~ Retrying connect to server: localhost/127.0.0.1:9001.
Already tried 2 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10,
sleepTime=1000 MILLISECONDS) (Client:841)


Thanks,
Peng



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message