I tried to kill the job manager manually in the terminal and start it again but 
no luck. Also could you tell me if it’s possible to change webclient’s port 
(8080) ?

> On Feb 24, 2015, at 1:41 PM, Stephan Ewen <se...@apache.org> wrote:
> 
> Hey Dulaj!
> 
> As a contributor, I would go against the latest version, which is
> 0.9-SNAPSHOT.
> 
> It may be in your case that the JobManager actor is down, but the process
> still lingers. (BTW: I have a patch pending that makes sure the process
> disappears when the actor via down).
> 
> Could you have a look at the log "flink-<user>-jobmanager-<host>-.log" and
> see if there are any errors logged?
> 
> Greetings,
> Stephan
> Am 24.02.2015 06:29 schrieb "Dulaj Viduranga" <vidura...@icloud.com>:
> 
>> The JobManager seems to run fine. I don't know. When I tried to run
>> start-local.sh again, It shows the PID of the running JobManager and also
>> :8081 runs fine. I want to contribute to the project and I could get a
>> little boost if I could see the capabilities of FLINK. :)
>> Will it be OK to use 0.8.1 as a developer?
>> 
>> On Feb 24, 2015, at 04:15 AM, Stephan Ewen <se...@apache.org> wrote:
>> 
>> Hi Dulaj,
>> 
>> That error message indicates that the JobManager is not running. Are you
>> sure that the JobManager runs properly? Anything in the JobManager logs?
>> 
>> BTW: The 0.9 branch is under heavy development / changes. That is why it
>> may behave a bit different on different days right now. I would recommend
>> to use the 0.8.1 release for a stable experience.
>> 
>> Greetings,
>> Stephan
>> 
>> 
>> On Mon, Feb 23, 2015 at 7:39 PM, Robert Metzger <rmetz...@apache.org>
>> wrote:
>> 
>> Thank you for the quick reply.
>> 
>> The log you've send is from the webclient. Can you also send the log of the
>> 
>> JobManager?
>> 
>> On Mon, Feb 23, 2015 at 7:28 PM, Dulaj Viduranga <vidura...@icloud.com>
>> 
>> wrote:
>> 
>>> Yes. It seams it is not a problem with the arguments. I tried two days
>> 
>> but
>> 
>>> different error occurs. It seams the web client can’t connect to the job
>> 
>>> manager although it is running
>> 
>>> Right now, I can’t even get the webclient to run.
>> 
>> ./bin/start-webclient.sh
>> 
>>> executes fine but I cannot connect to localhost:8080 (even with telnet or
>> 
>>> curl)
>> 
>>> Here is the log for jobManager
>> 
>>> 
>> 
>>> 23:22:31,933 INFO org.apache.flink.client.web.WebInterfaceServer
>> 
>>> - Setting up web frontend server, using web-root directory
>> 
>>> 
>> 
>> 'jar:
>> file:/Users/Vidura/Documents/Development/flink/flink-dist/target/flink-0.9-SNAPSHOT-bin/flink-0.9-SNAPSHOT/lib/flink-clients-0.9-SNAPSHOT.jar!/web-docs
>> '.
>> 
>>> 23:22:31,934 INFO org.apache.flink.client.web.WebInterfaceServer
>> 
>>> - Web frontend server will store temporary files in
>> 
>>> '/var/folders/3_/7gzbv7ks7q71lpm5d9hzrw2c0000gn/T', uploaded jobs in
>> 
>>> '/var/folders/3_/7gzbv7ks7q71lpm5d9hzrw2c0000gn/T/webclient-jobs',
>> 
>>> plan-json-dumps in
>> 
>>> '/var/folders/3_/7gzbv7ks7q71lpm5d9hzrw2c0000gn/T/webclient-plans'.
>> 
>>> 23:22:31,934 INFO org.apache.flink.client.web.WebInterfaceServer
>> 
>>> - Web-frontend will submit jobs to nephele job-manager on
>> 
>> localhost,
>> 
>>> port 6123.
>> 
>>> 23:22:32,580 INFO akka.event.slf4j.Slf4jLogger
>> 
>>> - Slf4jLogger started
>> 
>>> 23:22:32,625 INFO Remoting
>> 
>>> - Starting remoting
>> 
>>> 23:22:32,838 INFO Remoting
>> 
>>> - Remoting started; listening on addresses :[akka.tcp://
>> 
>> 
>>> JobsInfoServletActorSystem@127.0.0.1:51517]
>> 
>>> 23:23:48,119 WARN Remoting
>> 
>>> - Tried to associate with unreachable remote address [akka.tcp://
>> 
>> 
>>> flink@10.218.98.169:6123]. Address is now gated for 5000 ms, all
>> 
>> messages
>> 
>>> to this address will be delivered to dead letters. Reason: Operation
>> 
>> timed
>> 
>>> out: /10.218.98.169:6123
>> 
>>> 23:23:48,124 ERROR org.apache.flink.client.WebFrontend
>> 
>>> - Unexpected exception: Could not find job manager at specified
>> 
>>> address akka.flink@10.218.98.169:6123/user/jobmanager'>tcp://
>> flink@10.218.98.169:6123/user/jobmanager.
>> 
>>> java.lang.RuntimeException: Could not find job manager at specified
>> 
>>> address akka.flink@10.218.98.169:6123/user/jobmanager'>tcp://
>> flink@10.218.98.169:6123/user/jobmanager.
>> 
>>> at
>> 
>>> 
>> 
>> org.apache.flink.client.web.JobsInfoServlet.<init>(JobsInfoServlet.java:82)
>> 
>>> at
>> 
>>> 
>> 
>> 
>> org.apache.flink.client.web.WebInterfaceServer.<init>(WebInterfaceServer.java:158)
>> 
>>> at org.apache.flink.client.WebFrontend.main(WebFrontend.java:74)
>> 
>>> 
>> 
>>> 
>> 
>>>> On Feb 23, 2015, at 11:46 PM, Robert Metzger <rmetz...@apache.org>
>> 
>>> wrote:
>> 
>>>> 
>> 
>>>> Hi,
>> 
>>>> you said in the other email thread that the error only occurs for
>> 
>>>> Wordcount, not for Kmeans.
>> 
>>>> Can you copy me the commands for both examples?
>> 
>>>> I can not really believe that there is a difference between the two
>> 
>> jobs.
>> 
>>>> 
>> 
>>>> Can you also send us the contents of the jobmanager log file?
>> 
>>>> 
>> 
>>>> Best,
>> 
>>>> Robert
>> 
>>>> 
>> 
>>>> 
>> 
>>>> On Mon, Feb 23, 2015 at 6:04 PM, Dulaj Viduranga <vidura...@icloud.com
>> 
>> 
>>> 
>> 
>>>> wrote:
>> 
>>>> 
>> 
>>>>> I’m getting "Could not build up connection to JobManager.” When i
>> 
>> tried
>> 
>>> to
>> 
>>>>> run the wordCount example. Can anyone help?
>> 
>>>>> 
>> 
>>>>> Dulaj
>> 
>>> 
>> 
>>> 
>> 
>> 

Reply via email to