Closed StianOvrevage closed 5 years ago
hi @StianOvrevage,
Great that you are testing out Humio :). You can also join our Slack via community.humio.com if you wish.
The log shows that your Humio just enters a restart loop and never starts up correctly.
We don't support running on Windows and I'm unsure if there is any issues/differences between running docker on Windows, that might be it?
If you mount in the data dir -v some/dir/on/your/host:/data/
, then you can find our debug log in some/dir/on/your/host/logs/humio-debug.log
. I would expect that you see an exception there and that it might shed some light on the reason why it crashes at boot.
Regards,
-- Peter
Thanks for the swift reply!
I got the logs and apparently my laptop did not have enough memory. It would be nice to have those logs surfaced to stderr/stdout though :) I think you can configure supervisord to redirect logs for it's child processes to stderr/stdout.
There was also these two
/run.sh: 10: /run.sh: [[: not found
/run.sh: 16: /run.sh: [[: not found
That I thought might have something to do with it, and maybe they had something to do with being on Windows. But they show up both on Windows and Ubuntu.
Running it now on a bigger VM in the cloud on Ubuntu and it seems to be working great, thanks!
Great. Yes the [[: not found
is annoying. I'll see if I can fix that.
I'll close this issue, but if you get more questions reach out to me (I'm part of the core Humio team) or join our Slack via community.humio.com.
Have a good day.
Eager to try an alternative to the hard-to-operate ELK stack, but did not get very far:
Going to localhost:8080 results in
ERR_EMPTY_RESPONSE
in Chrome.Docker for Windows:
Also tried with
--net=host
as described in https://docs.humio.com/installation/docker/ but that gives Connection refused in browser.