Open tumluliu opened 7 years ago
That's strange, for the live demo, where there're ~700K, it's consuming ~170MiB. However, it's not running SSL, so I wonder if that could be the issue. Can you please try restarting and see if the mem consumption is about the same after the restart? Thanks
I have restarted it. The mem consumption becomes normal:
Please keep it up for about the same time you had the other instance opened and let me know how it goes. Feel free to access the report as you did before too.
Also, if mem goes up again, please try restarting it without SSL/TLS. I'm thinking that could be the issue. Let me know. Thanks.
no problem. I will show the mem status after perhaps a couple of days. Tks!
The trend is not very good. After ~4 days, goaccess is consuming ~23% mem and ~60% cpu on my server. I have to restart it because it's already used too much resource. But I should note that I am using the on-disk storage (btree) because my team members would not be happy if the history data is lost again after the restart.
I will restart it with no SSL enabled, and observe its mem usage for a couple of days.
Any updates on this?
The goaccess service was disabled by our sysadmin because of the high mem usage. And according to my last observation 2 weeks ago, the mem usage was better without SSL. So I can only say that the abnormal mem usage was most probably caused by the SSL setting. I am sorry that I can only provide such limited information. Wish that can help.
I ran into the same issue. I have provided some info in next section info
.
I have restarted the goaccess service at the turning point in monitor chart below.
it seems that goaccess takes normal memory when started, and take more and more mem as time goes on.
here's my memory usage monitor in last 14 days.
@narrowizard Thanks for posting this. Just curious, are you running the latest version? Could you please post the exact command you are running? Also, I see that every few days the mem usage goes down, are you restarting goaccess? and last, could you please run it with the most minimal settings and without geoip support? e.g.,
goaccess --no-global-config access.log --log-format=COMBINED
Thanks
Actually, I ran goaccess in docker container. With Dockerfile here, build in master branch of this repo.
I do restart goaccess once few days.
As your suggestion, I will run goaccess without geoip, and post another report in next days.
Thanks for your reply. @allinurl
after a week's test, i think this issue is something about geoip support. here is my system monitor(not exactly, but never reappear this issue) after disable geoip support.
Do you have any idea about that? @allinurl
@narrowizard Good to hear it ran fine w/o geoip. I've never seen this before, although, I usually test with GeoIP legacy, so I'm guessing it could be mmdb. Could you please try running geoip legacy instead and post back? Thanks.
I have started the goaccess daemon for one week with this command:
And the mem usage of goaccess is as follows.
The number of requests has been processed by goaccess is ~560,000. It's not so many. But is it normal for goaccess to eat up ~2G mem? Will it consume more and more mem if I keep running it as a service? Should I restart it with the on-disk B+ tree database? What are the best practices of using goaccess as a long-term running service?