No handler accepted "/" #22

schell · 2014-03-31T21:11:10Z

I'm trying to make ekg accessible out in the open on a server using

forkServer anIpAddress aPort

when visiting that ip address on that port I get No handler accepted "/". Is this expected? If so, how do I use ekg remotely?

The text was updated successfully, but these errors were encountered:

schell · 2014-03-31T21:16:21Z

Also - I can get json from ekg on the server using the header "Accept: application/json".

tibbe · 2014-04-01T07:16:22Z

Just to clarify, if you do

curl http://<your ip>:<your port>/

you get No handler accepted "/"?

schell · 2014-04-01T16:01:15Z

Yes, specifically it returns

<!DOCTYPE html>
<html>
<head>
<title>Not found</title>
</head>
<body>
<code>No handler accepted "/"</code>
</body></html>

schell · 2014-04-01T16:02:45Z

I'm guessing the host in the request doesn't match the ip address? I'll do some logging and try to see whats' going on.

tibbe · 2014-04-01T16:05:14Z

That would be helpful. Thanks.

tibbe · 2014-04-08T15:23:15Z

How did you start the server? The server needs access to its data files. This should work automatically if you install ekg but if you build and run it in-tree you need to use:

cd ekg
ekg_datadir=. ./my/executable

aycanirican · 2014-05-02T09:53:46Z

Placing assets to proper place and defining ekg_datadir ekg solved my problem. Thank you @tibbe .

afiskon · 2014-07-09T07:15:40Z

Same problem here (ekg 0.4). I have all-in-one executable, which is packed in deb package. I placed assets directory in /var/lib/myproject/assets/ and modified init script the following way:

sudo -u $USER ekg_datadir=/var/lib/$NAME/assets/ $DAEMON

But it didn't solve the problem. Maybe hdaemonize could cause this?

BTW, did you consider to embed all necessary files using Template Haskell?

tibbe · 2014-07-09T08:18:50Z

Can you try

sudo -u $USER echo /var/lib/$NAME/assets/ $DAEMON

to make sure that the path expands correctly?

Using TH brings a host of other issues (cross compilation not working, etc) and since people who ship software to other machines to run there eventually will need to figure out how to ship whole packages of files (i.e. executable plus various templates, data files, etc) anyway, I don't think it's worth it.

aycanirican · 2014-07-09T08:21:34Z

I agree, please don't use TH unless it is really needed.

afiskon · 2014-07-09T08:31:46Z

@tibbe sure:

aa@aa.load:~$ sudo service auditlog start
Starting Auditlog
/var/lib/auditlog/assets/ /usr/lib/auditlog/bin/auditlog
aa@aa.load:~$ ls -la /var/lib/auditlog/assets/
total 224
drwxr-xr-x 2 auditlog auditlog  4096 Jul  9 08:29 .
drwxr-xr-x 3 auditlog auditlog  4096 Jul  9 06:44 ..
-rw-r--r-- 1 auditlog auditlog 47523 Jul  9 06:44 bootstrap-1.4.0.min.css
-rw-r--r-- 1 auditlog auditlog   803 Jul  9 06:44 chart_line_add.png
-rw-r--r-- 1 auditlog auditlog   473 Jul  9 06:44 cross.png
-rw-r--r-- 1 auditlog auditlog  3647 Jul  9 06:44 index.html
-rw-r--r-- 1 auditlog auditlog 91668 Jul  9 06:44 jquery-1.6.4.min.js
-rw-r--r-- 1 auditlog auditlog 37554 Jul  9 06:44 jquery.flot.min.js
-rw-r--r-- 1 auditlog auditlog   571 Jul  9 06:44 monitor.css
-rw-r--r-- 1 auditlog auditlog 13071 Jul  9 06:44 monitor.js
aa@aa.load:~$ ls -la /usr/lib/auditlog/bin/auditlog
-rwxr-xr-x 1 auditlog auditlog 27076209 Jul  9 06:31 /usr/lib/auditlog/bin/auditlog

tibbe · 2014-07-09T08:59:37Z

@afiskon sorry for being unclear, I meant for you to try to see if the Bash expression containing the $NAME etc variables expanded correctly in the context of sudo (as per the above command I gave), not if the directory contents is correct.

afiskon · 2014-07-09T09:13:12Z

@tibbe yes, the line above:

/var/lib/auditlog/assets/ /usr/lib/auditlog/bin/auditlog

was an output of command you asked to execute. I just wanted to make it clear that paths are OK.

And this:

ekg_datadir=/var/lib/auditlog/assets/ /usr/lib/auditlog/bin/auditlo

is a result of:

sudo -u $USER echo ekg_datadir=/var/lib/$NAME/assets/ $DAEMON

tibbe · 2014-07-09T09:19:33Z

@afiskon Alright, so we know that things are getting invoked correctly.

Could you try to add a line that logs whether the data dir is readable/exists (using e.g. System.Directory.doesDirectoryExist) right after this line in ekg https://github.com/tibbe/ekg/blob/master/System/Remote/Snap.hs#L72. Do something like:

monitor store = do
    dataDir <- liftIO getDataDir
    dataDirExists <- doesDirectoryExist dataDir
    unless dataDirExists $
        hPutStrLn stderr $ "ERROR: Data directory " ++ dataDir ++ " doesn't exist. If your data files are in a non-standard directory, you might need to set ekg_datadir."
    -- ...

ods94065 · 2016-02-27T15:43:04Z

Here's my story while running into this problem:

I'm using Stack to build a web app (including ekg) that I'm deploying inside a Docker container. In particular, I'm installing my app in a fresh container with no explicit Haskell dependencies (we'll see how that goes!). JSON API calls to EKG worked but HTML did not.

The problem was indeed that the directory of assets didn't exist in the runtime container, and ekg could not find it. This directory contains the files needed to provide the HTML interface, and Snap apparently raises this error when a file it's trying to serve can't be found (see snapframework/snap#102 ).

The problem Sean mentions in #48 bit me hard, since if his path to the assets directory was weird, mine using Stack/Docker is really weird. I don't know an easy way to magic these files into my Docker installation, so I cheated: I'm pinning the ekg version for now and copying the assets/ directory into my project.

One final note: You'll see that ekg appends </> assets to your data directory, so make sure you're not setting your data directory to the assets directory itself! I installed my stuff in /app/ekg-0.4.0.9/assets, and set ENV ekg_datadir=/app/ekg-0.4.0.9 in my Docker container. That was what did the trick.

dysinger · 2016-05-06T21:29:56Z

I just hit the same problem with stack and a docker-enabled project

dysinger · 2016-05-06T21:31:29Z

It might be better to use fileEmbed so that directories don't need to be found.

lorenzo · 2017-01-13T12:50:04Z

In case anyone is looking for a solution, I have this script for building the image:

	docker pull
	stack build
	find ~/.stack -name "assets" -exec cp -a {} shared_folder \;
	stack image container --build

This works with the following stack.yaml configuration:

docker:
    enable: true
    repo: "fpco/stack-build"
    auto-pull: true
image:
  container:
    name: image-name
    base: fpco/stack-run
    add:
        shared_folder: /build_stuff

And when executed with this ENV var:

ekg_datadir=/build_stuff

tibbe closed this as completed May 2, 2014

cgag mentioned this issue Nov 23, 2015

Use of data-files setting in Cabal is not obvious. #48

Closed

fizruk mentioned this issue Oct 4, 2017

Add Cabal flag to embed assets with TH #66

Open

viviag mentioned this issue Oct 6, 2017

Add cabal flag to allow TH, embed assets during compilation and disembed them on the spot GetShopTV/ekg#1

Open

Willburn mentioned this issue Apr 29, 2020

EKG access from outside a container IntersectMBO/cardano-node#857

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

No handler accepted "/" #22

No handler accepted "/" #22

schell commented Mar 31, 2014

schell commented Mar 31, 2014

tibbe commented Apr 1, 2014

schell commented Apr 1, 2014

schell commented Apr 1, 2014

tibbe commented Apr 1, 2014

tibbe commented Apr 8, 2014

aycanirican commented May 2, 2014

afiskon commented Jul 9, 2014

tibbe commented Jul 9, 2014

aycanirican commented Jul 9, 2014

afiskon commented Jul 9, 2014

tibbe commented Jul 9, 2014

afiskon commented Jul 9, 2014

tibbe commented Jul 9, 2014

ods94065 commented Feb 27, 2016

dysinger commented May 6, 2016

dysinger commented May 6, 2016

lorenzo commented Jan 13, 2017 •

edited

Loading

No handler accepted "/" #22

No handler accepted "/" #22

Comments

schell commented Mar 31, 2014

schell commented Mar 31, 2014

tibbe commented Apr 1, 2014

schell commented Apr 1, 2014

schell commented Apr 1, 2014

tibbe commented Apr 1, 2014

tibbe commented Apr 8, 2014

aycanirican commented May 2, 2014

afiskon commented Jul 9, 2014

tibbe commented Jul 9, 2014

aycanirican commented Jul 9, 2014

afiskon commented Jul 9, 2014

tibbe commented Jul 9, 2014

afiskon commented Jul 9, 2014

tibbe commented Jul 9, 2014

ods94065 commented Feb 27, 2016

dysinger commented May 6, 2016

dysinger commented May 6, 2016

lorenzo commented Jan 13, 2017 • edited Loading

lorenzo commented Jan 13, 2017 •

edited

Loading