Refine does not start

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download google refine for Linux
2. Extract
3. Change to directory and run ./refine

What is the expected output? What do you see instead?
Expected output is refine starting on http://127.0.0.1:3333/. However, I get 
the message "Google Refine is already running." on the command line.

What version of the product are you using? On what operating system?
google-refine-2.0-r1836. Ubuntu 10.04 32 bit. Kernel 2.6.32-26-generic

Please provide any additional information below.

Original issue reported on code.google.com by devshree.sane on 28 Nov 2010 at 5:58

[GoogleCodeExporter]

Is it?  Running, that is.  Do you have something else running which is 
responding to HTTP requests on port 3333?

Can you run the following two commands in a shell and post the output?

ps ax | grep refine
netstat | grep 3333

Original comment by tfmorris on 28 Nov 2010 at 6:12

[GoogleCodeExporter]

Output

laptop:~$ ps ax | grep refine
12553 pts/0    S+     0:00 grep --color=auto refine

laptop:~$ netstat | grep 3333
laptop:~$ 
(nothing on 3333)

Original comment by devshree.sane on 28 Nov 2010 at 6:23

[GoogleCodeExporter]

Thanks for the additional data.  There's not chance that you've got REFINE_HOST 
pointed somewhere else (perhaps for previous testing), is there?  What the 
script does is use either curl or wget to fetch 
"http://${REFINE_HOST}:${REFINE_PORT}" where REFINE_HOST is 127.0.0.1 by 
default and REFINE_PORT is 3333.

I don't see any obvious way that the GET can succeed unless there's a web 
server running on that port and host.

Perhaps the developer who wrote the startup script will have more insight into 
a possible failure mode that matches your symptoms.

Original comment by tfmorris on 29 Nov 2010 at 12:13

[GoogleCodeExporter]

@tfmorris: Thanks. Issue resolved. It was a proxy problem.

I am behind a proxy and hence, I require an http proxy username and password to 
connect to the "outside" world. (Although refine runs on localhost, wget/curl 
still require the username,password) I have set the value of $http_proxy 
variable, and I can now run refine. Perhaps the developers would like to add 
this issue to the FAQ/troubleshooting pages.

How do I mark this as resolved?

Original comment by devshree.sane on 29 Nov 2010 at 4:25

[GoogleCodeExporter]

Thanks for the update.  Glad to hear that you're up and running.

I'm going to leave this open for the time being in hopes that we can improve 
the handling of this situation.  The startup script isn't checking the contents 
of the page it fetches.  I presume it's getting some kind of response from the 
proxy/firewall and assuming that it's the Refine homepage.  Perhaps we can add 
some type of sanity check for this kind of situation.

Original comment by tfmorris on 29 Nov 2010 at 4:52

[GoogleCodeExporter]

I added more solid running checks to r1958 so I think we can close this

Original comment by stefa...@google.com on 24 Dec 2010 at 10:22

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by tfmorris on 9 Jun 2011 at 8:05

• Added labels: Milestone-2.1

[GoogleCodeExporter]

I had a similar problem with r2136.  Anyone with a similar issue should set the 
$no_proxy environment variable in the same place they've set $http_proxy etc.

$ env | grep -i proxy
http_proxy=http://proxy:8080/
HTTP_PROXY=http://proxy:8080/

$ ./refine
[: 816: /tmp/refine.uR8M9NT: unexpected operator
Something is already running on http://127.0.0.1:3333/ but doesn't seem to be 
Google Refine

$ curl -I http://localhost:3333/
HTTP/1.1 502 Proxy Error ( Connection refused )
Via: 1.1 KISA01
...

$ export no_proxy="localhost,127.0.0.1"

$ ./refine
[: 816: /tmp/refine.REhMrIl: unexpected operator
Starting Google Refine at 'http://127.0.0.1:3333/'

Original comment by m...@blissett.me.uk on 7 Nov 2011 at 4:54

[GoogleCodeExporter]

thank you matt; setting the no_proxy environment variable worked for me.

Original comment by lighton.phiri@gmail.com on 22 Nov 2011 at 6:07

[GoogleCodeExporter]

Thanks.. the no_proxy sace my life :D

Original comment by thomaslc...@gmail.com on 24 Jan 2012 at 6:55

[GoogleCodeExporter]

In r2438 I've added

no_proxy="localhost,127.0.0.1"

to the default refine.ini file which will hopefully mitigated these problems in 
the future.

Original comment by tfmorris on 27 Jan 2012 at 10:08

[GoogleCodeExporter]

setting the no_proxy environment variable worked for me

Original comment by julianbr...@gmail.com on 11 Jul 2013 at 3:48