data_error: <<"'http://discoproject.org/chekhov.txt' ">>

[小黑米]

$ cat /etc/hosts
127.0.0.1 qeephp#master
192.168.1.195 qeephp01#slave

Master is at master(qeephp) server

First I add slave(qeephp01) to blacklisting,and run wordcount.py at
master(qeephp) side,there is no any mistake

And I add slave(qeephp01) to writelisting,add master(qeephp) to
blacklisting, then run wordcount.py at master(qeephp) side,something
wrong...
I received logs:
=INFO REPORT==== 22-Oct-2009::15:27:21 ===
"Starting a worker at "
"qeephp01"
<0.134.0>

=INFO REPORT==== 22-Oct-2009::15:27:53 ===
{"Blacklisting","qeephp01","for",600000,"ms."}

=INFO REPORT==== 22-Oct-2009::15:27:53 ===
"Worker killed"
<0.134.0>
data_error: <<"'http://discoproject.org/chekhov.txt' ">>



I can use ssh to login slave(qeephp01) from master(qeephp),also i can
use ssh to master(qeephp) from slave(qeephp01),both without
password...

My environment：
python2.6
centos
Eshell V5.6.5
OpenSSH_5.1p1 Debian-5ubuntu1, OpenSSL 0.9.8g 19 Oct 2007

[jf]

Did you check the link? It seems there is a stray single quotation
mark at the end.

[Christian]

The problem is not with the link, it is the basic test as given on the
website for the ec2 test run using the url given. Has this problem
been solved, I am encountering the same issue?

[Jared Flatow]

From the node command line can you curl the url (curl http://discoproject.org/chekhov.txt
)?

> --
>
> You received this message because you are subscribed to the Google
> Groups "Disco-development" group.
> To post to this group, send email to disc...@googlegroups.com.
> To unsubscribe from this group, send email to disco-dev+...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/disco-dev?hl=en
> .
>
>

[杨晓瑜]

Yeah,I make mistake...

The disco path isn't the same on the two pc... I make them same it works~

Thanks~!

2009/11/28 Jared Flatow <jfl...@gmail.com>

[Christian]

Yes, I looked into this further and the problem seems to be that the
worker supervisor was down. This stems from a deeper issue in that the
worker supervisor refuses to start unless a very specific set of
circumstances is met. If the keys are properly set, then the worker
supervisor should start immediately if the command "disco worker
start" is run. This does not happen. The only way I have been able to
get the worker supervisor to start is to run 'ssh localhost erl' as
given by the troubleshooting manual. If the erl command-line is left
open long enough, then the worker supervisor will start. I am
uncertain as to the cause of this.

On Nov 27, 3:01 pm, Jared Flatow <jfla...@gmail.com> wrote:
>  From the node command line can you curl the url (curlhttp://discoproject.org/chekhov.txt