-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GoAccess 0.9.3 crashed by Signal 11 when loading persisted data #296
Comments
A few questions for you.
Thanks |
|
I'm looking into this, but, could you please try to replicate it in gdb? and preferably with a smaller data set.
|
Program received signal SIGSEGV, Segmentation fault. |
I've been trying to reproduce this with a similar environment, CentOS 6.7, 2.6.32-573 x86_64 and using the same config file. No crashes so far. I assume your database files were created on the same architecture as the one reading them. Does it break with a much smaller data set? e.g., creating new database files with 1000 log lines and then appending another 1000 to it? Can you please give more info on this issue? I mean how did you configure/execute it and what steps did you follow to reach here? This will help in reproducing this bug. Also, If you could try v0.9.4, it would be great! Thanks! |
I had tried with 0.9.4 it is same thing. /usr/local/bin/goaccess --html-report-title=domain -f /var/log/nginx/domain.cache.log.1 > /var/www/html/domain/index.html |
I'm starting to think this could be a data corruption on one of the database files. I just tested this with two data sets, first one a log of 50M lines and the second one with 30M, it didn't crash. BTW, does this happen only when parsing the same log file or with any log? and have you tried deleting the db files and running everything again? It would be great if you could post some additional data from gdb. However, you need to compile with debugging symbols. To do this you need to configure with
then run it through gdb:
Thanks! |
@TempleNode I pushed a commit to ensure the raw data structure is not NULL upon sorting it. Could you please pull the latest changes from upstream and see if that fixes the issue? Thanks. |
Also, please make sure to specify a debug log file and post its content in here.
|
Closing this since I wasn't able to replicate it. Several changes have been made since v0.9.3. Feel free to reopen it if needed. Thanks. |
Server is centos 6
goaccess.conf
The text was updated successfully, but these errors were encountered: