Possible --persist bug in GoAccess+NPMplus?

[UncleNet41]

Hello and thanks for the wonderful project!

I'm using GoAccess version 1.10.2 with NPMplus version 2026-06-11-b1, which comes with GoAccess prebundled, in a docker compose enviroment.

It seems like it fails to persist data on disk even when passed with the correct commands.

My NPMplus compose (relevant parts only):

- "GOA=true" # Enables goaccess (and overrides LOGROTATE to true), default false --- if you download the GeoLite2-Country.mmdb, GeoLite2-City.mmdb AND GeoLite2-ASN.mmdb file from MaxMind and place them in /opt/npmplus/goaccess/geoip it will automatically enable GeoIP in goaccess after restarting NPMplus (no need to change GOACLA below), you may also enable the geoipupdate container below (please change the timezone)
- "GOACLA=--agent-list --real-os --double-decode --keep-last=30 --with-output-resolver --no-query-string --exclude-ip 192.168.1.1-192.168.1.150 --exclude-ip 192.168.1.1-192.168.70.70 --exclude-ip 127.0.0.1 --exclude-ip 172.16.0.0-172.50.0.0 --restore --persist --db-path=/data/goaccess/data --num-tests=0

despite the persist and db-path options, every container restart it starts anew.

checking the db-path folder inside the container while running reveals it's empty.

let me know what i can do to help you troubleshoot whether it's a bug in GoAccess or an interaction between GoAccess and NPMplus; not sure what i can actually do, but i'll try :)

[allinurl]

I don't see any issues with the flags. Are you sure that /data/goaccess/data exists?

To troubleshoot this, I'd recommend running GoAccess directly on the host machine, outside of NPMPlus and the Docker Compose environment. That will help determine whether the issue is with GoAccess itself or something in one of those layers.

Let me know if you get the same result when running it directly.

[UncleNet41]

ok, i'll try. installed bare metal and configured to parse the logs. I'll let you know after letting it run some time!

sorry for the question stupid question but i'm not the most goaccess savy person around, so

goaccess access.log --persist --db-path=/etc/goaccess/persist --real-time-html --daemonize

is that the correct command to let it run continuosly in the background?

[UncleNet41]

Ok, in the meanwhile situation as follows:

• after configuring the log format, i launched GoAccess from baremetal with goaccess access.log --persist --db-path=/etc/goaccess/persist in /opt/npmplus/data/nginx: it reads the logs just fine, and checking the persist folder is correctly populated with a lot of .db files. at this point the NPMplus container is running.
• i tried to take the container down, and launched goaccess access.log --restore --persist --db-path=/etc/goaccess/persist, to no avail
• tried to up the container again, and relaunched the original command: it reads the logs just generated, not persisting anything
• tried to launch goaccess --restore alone and it displays an empty file

anything else i can try?