Goaccess stopped working

Code: [Select]

/usr/local/apache/domlogs/*.log {      <<<  Tells logrotate all files ending in .log in the domlog directory
    missingok   <<< continue log rotation without reporting any error if any of the specified log files are missing.
    notifempty   <<< ensures that log files are not rotated if they are empty. If a log file is empty, it won't trigger rotation.
    sharedscripts    <<< ensures that the commands or scripts specified in the prerotate or postrotate directive are executed only once, regardless of the number of log files being rotated.
    daily  <<<  Run every day
    rotate 7    <<< Keep 7 days of logs
    postrotate    <<<<  reload httpd once the logs are rotated
        /sbin/service httpd reload > /var/log/httpd-rotate.log 2>&1 || true
    endscript
    compress   <<<< GZIP the log files to save space
}

Thanks.  Now a followup question mr. president.

Would that screw up goaccess monthly reports.  Or is go access only using the access_log file which would not be trimmed by the log rotation.

The beauty of customizability -- my domlogs look like this. I got away from _log a long time ago in favor of .log, which is more easily read in external log reader & stats programs:

Code: [Select]

-rw-r--r--   1 nobody root        0 Apr 11 14:23 domain.com.error.log
-rw-r--r--   1 nobody root        0 Apr 11 14:23 domain.com.log
-rw-r--r--   1 nobody root        0 Apr 10 14:23 domain.bytes
-rw-r--r--   1 nobody root      202 Mar 31 02:51 domain.com.error.log-20250331.gz
-rw-r--r--   1 nobody root      286 Apr  1 01:37 domain.com.error.log-20250401.gz
-rw-r--r--   1 nobody root      294 Apr  3 01:42 domain.com.error.log-20250403.gz
-rw-r--r--   1 nobody root     4129 Apr  5 02:33 domain.com.error.log-20250405.gz
-rw-r--r--   1 nobody root      856 Apr  6 20:20 domain.com.error.log-20250407.gz
-rw-r--r--   1 nobody root      767 Apr  8 00:20 domain.com.error.log-20250408.gz
-rw-r--r--   1 nobody root      432 Apr  9 19:06 domain.com.error.log-20250410.gz
-rw-r--r--   1 nobody root      121 Mar 31 02:51 domain.com.log-20250331.gz
-rw-r--r--   1 nobody root      196 Apr  1 01:37 domain.com.log-20250401.gz
-rw-r--r--   1 nobody root      262 Apr  3 01:42 domain.com.log-20250403.gz
-rw-r--r--   1 nobody root    11656 Apr  5 02:33 domain.com.log-20250405.gz
-rw-r--r--   1 nobody root     6594 Apr  6 20:20 domain.com.log-20250407.gz
-rw-r--r--   1 nobody root     6507 Apr  8 00:20 domain.com.log-20250408.gz
-rw-r--r--   1 nobody root     5983 Apr  9 19:06 domain.com.log-20250410.gz


The beauty of customizability -- my domlogs look like this. I got away from _log a long time ago in favor of .log, which is more easily read in external log reader & stats programs:

Code: [Select]

-rw-r--r--   1 nobody root        0 Apr 11 14:23 domain.com.error.log
-rw-r--r--   1 nobody root        0 Apr 11 14:23 domain.com.log
-rw-r--r--   1 nobody root        0 Apr 10 14:23 domain.bytes
-rw-r--r--   1 nobody root      202 Mar 31 02:51 domain.com.error.log-20250331.gz
-rw-r--r--   1 nobody root      286 Apr  1 01:37 domain.com.error.log-20250401.gz
-rw-r--r--   1 nobody root      294 Apr  3 01:42 domain.com.error.log-20250403.gz
-rw-r--r--   1 nobody root     4129 Apr  5 02:33 domain.com.error.log-20250405.gz
-rw-r--r--   1 nobody root      856 Apr  6 20:20 domain.com.error.log-20250407.gz
-rw-r--r--   1 nobody root      767 Apr  8 00:20 domain.com.error.log-20250408.gz
-rw-r--r--   1 nobody root      432 Apr  9 19:06 domain.com.error.log-20250410.gz
-rw-r--r--   1 nobody root      121 Mar 31 02:51 domain.com.log-20250331.gz
-rw-r--r--   1 nobody root      196 Apr  1 01:37 domain.com.log-20250401.gz
-rw-r--r--   1 nobody root      262 Apr  3 01:42 domain.com.log-20250403.gz
-rw-r--r--   1 nobody root    11656 Apr  5 02:33 domain.com.log-20250405.gz
-rw-r--r--   1 nobody root     6594 Apr  6 20:20 domain.com.log-20250407.gz
-rw-r--r--   1 nobody root     6507 Apr  8 00:20 domain.com.log-20250408.gz
-rw-r--r--   1 nobody root     5983 Apr  9 19:06 domain.com.log-20250410.gz


I agree!  That does look might handsome!  But how did you do it?

With the logrotate conf I posted earlier. Does your default (or other) Apache vhost conf look like this under the log section:

   

Code: [Select]

CustomLog /usr/local/apache/domlogs/%domain%.bytes bytes
CustomLog /usr/local/apache/domlogs/%domain%.log combined
ErrorLog /usr/local/apache/domlogs/%domain%.error.log

FYI

AL9 has:
 goaccess                    x86_64                    1.9.3-2.el9                    @epel                    1.4 M

Just created the http conf, will let you know how it goes.

Well it did something weird on AL9, says it ran, but the report for 2025-04-13 is missing, and all the logs have been reset that are in /usr/local/apache/domlogs/

Do have:
domain.com.error.log
domain.com.log
domain.bytes

But nothing showing a date afterwards showing it rotated.

logrotate or GoAccess?

@overseer

Look like it is working, but it's doing filenames like:

elrepo.nl.ssimn.org.log.1.gz
elrepo.nl.ssimn.org.log.2.gz


What am I missing that it not assigning the date?

Thanks

/etc/logrotate.conf

Code: [Select]

# use date as a suffix of the rotated file
dateext