Goaccess: Docker with UNRAID - GoAccess 1.2 crashed by Sig 11

[nyid]

Hello, I'm using the allinurl/goaccess container and I'm having trouble getting it running. I followed the directions regarding mapped volumes and created a simple configuration file.

UNRAID configuration

goaccess.conf which is located in /mnt/user/system/appdata/goaccess/data/
log-format COMBINED
log-file /srv/logs/nginx/access.log
output /srv/report/index.html
real-time-html true

Log Output
GoAccess - version 1.2 - Jun 29 2018 03:56:40

Config file:
==7== GoAccess 1.2 crashed by Sig 11
==7==
==7==
==7== Please report it by opening an issue on GitHub

GoAccess - version 1.2 - Jun 29 2018 03:56:40

Config file:
==7== GoAccess 1.2 crashed by Sig 11
==7==
==7==
==7== Please report it by opening an issue on GitHub

[allinurl]

Hello. Question, did you build with --enable-tcb=btree?

[nyid]

No, I did not build from source or create the image. I'm using the image from this Docker repository: https://hub.docker.com/r/allinurl/goaccess/.

[allinurl]

Are you able to follow these steps and see if you get the same issue? Thanks.

[nyid]

Hi allinurl, those are the directions that I followed when setting up the container. I set up the directories, created the configuration file, and used the prebuilt docker image. The error is reproducible every time. Not sure if this is relevant but the date and time in the logs is always the same-- "Jun 29 2018 03:56:40".

[gkelekov]

Hi allinuri. I can confirm issue nyid reported. I have the same problem. I also tied prebuild image. I'm trying to parse my NGINX logs, and have no difficulty with setup and config when running GoAccess on Linux.
Config file has configuration for log-format (my custom log as I have some special stuff added to NGINIX), log-file, output and real-time-html enabled and set.
Here is docker container log when container is started:
GoAccess - version 1.2 - Jun 29 2018 03:56:40
Config file:
==7== GoAccess 1.2 crashed by Sig 11
==7==
==7==

Might be a same problem as reported in #1168

[allinurl]

I'm looking into this. It appears to be a regression though. I'll post back as soon as I push a fix for this! Thanks!

[hank]

Bump - what ever happened here? Has this been addressed in 1.3?

[allinurl]

@nyid are you still getting this issue in 1.3? how are you running it? thanks

[nyid]

I just now installed goaccess 1.3 from Unraid Community Applications and it appears to be working right out of the box. The issue I was having earlier is no longer present.