Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
31
Information / Re: User control panel not working either
« on: April 05, 2025, 03:53:06 PM »
Incidently, this also happened on the morning on Feb 28. There was no report. But the next morning, I had Mar 1 report but no Feb 28 report. This is why I think it is an update issue.
32
Information / Re: User control panel not working either
« on: April 05, 2025, 03:36:15 PM »
I dont see any cron jobs for root or user other than ssl. So have not run cron.
I am able to run go access from shell generate a single report.html from my existing server. The report is comprehensive without single domains.
I just spun up another linode with alma8 this morning so I have a reference. It has goaccess 1.3. I ran it from user panel and got a report for the single domain that exists and of course it was empty.
When I run shell goaccess status from todays new server, I get an error that says
But I dont want to discuss the new server.
On both there seems to be some confusion about the access file name. goaccess assumes access.log, when in fact with cwp its access_log. I can deal with that I think.
But my problem is no goaccess reports parsed any more automatically. In addition, the nice graphical user bandwidth has also stopped displaying. It sounds to me like a cron problem. I still think its an cwp update issue. Shouldnt I be seeing crons for goaccess and bandwidth?
I am able to run go access from shell generate a single report.html from my existing server. The report is comprehensive without single domains.
I just spun up another linode with alma8 this morning so I have a reference. It has goaccess 1.3. I ran it from user panel and got a report for the single domain that exists and of course it was empty.
When I run shell goaccess status from todays new server, I get an error that says
Code: [Select]
Fatal error has occurred
Error occurred at: src/parser.c - read_log - 2728
Unable to open the specified log file. No such file or directoryBut I dont want to discuss the new server.
On both there seems to be some confusion about the access file name. goaccess assumes access.log, when in fact with cwp its access_log. I can deal with that I think.
But my problem is no goaccess reports parsed any more automatically. In addition, the nice graphical user bandwidth has also stopped displaying. It sounds to me like a cron problem. I still think its an cwp update issue. Shouldnt I be seeing crons for goaccess and bandwidth?
33
Information / Re: User control panel not working either
« on: April 05, 2025, 11:28:00 AM »
No one has anything to say about user bandwidth consumption disappearing?
34
Information / User control panel not working either
« on: April 04, 2025, 10:27:06 AM »
So I thought it was goaccess that quit working. But also the the graph of bandwidth consumption has also stopped working since March 31. March 30 was the last time any data was saved. So this might be a cron issue after cwp update. I can run go access from shell but daily records are not happening. I can see all data prior to march 31 in both goaccess and bandwidth consumption. Houston we have a problem.
35
Information / Re: Goaccess stopped working
« on: April 03, 2025, 02:48:57 PM »
FWIW goaccess 1.9.4 uses access.log as the source file to parse and not access_log
36
Information / Re: Goaccess stopped working
« on: April 03, 2025, 12:32:25 PM »
I tried running a report manually and I am getting this time error:
This is the line # 2431 referenced above:
And this is the goaccess.conf file pertaining to time:
Code: [Select]
Fatal error has occurred
Error occurred at: src/parser.c - parse_log - 2431
No time format was found on your conf file.This is the line # 2431 referenced above:
Code: [Select]
/* verify that we have the required formats */
if ((err_log = verify_formats ()))
FATAL ("%s", err_log);And this is the goaccess.conf file pertaining to time:
Code: [Select]
#
time-format %H:%M:%S
#
# Google Cloud Storage or
# The time in microseconds since the Unix epoch.
#
#time-format %f
# Squid native log format
#
#time-format %s
######################################
# Date Format Options (required)
######################################
#
# The date-format variable followed by a space, specifies
# the log format date containing any combination of regular
# characters and special format specifiers. They all begin with a
# percentage (%) sign. See `man strftime`
#
# The following date format works with any of the
# Apache/NGINX's log formats below.
#
date-format %d/%b/%Y
#
# AWS | Amazon CloudFront (Download Distribution)
# AWS | Elastic Load Balancing
# W3C (IIS)
#
#date-format %Y-%m-%d37
Information / Re: Goaccess stopped working
« on: April 03, 2025, 11:21:22 AM »
After uninstall and install of 1.94 of goaccess, this morning there is still no statistics data since march 30. Ugg.
38
Information / Re: Goaccess stopped working
« on: April 02, 2025, 05:16:49 PM »
Something weird happened when I downloaded the source file to usr/local/src......ownership:group was user:opendkim I tried user fix permissions but nothing changed.
39
Information / Re: Goaccess stopped working
« on: April 02, 2025, 04:20:55 PM »Have you checked to see if your log files haven't ballooned in size to be too large to process? Are you using logrotate to keep them a manageable size?
I posted update instructions in another thread, but here it is again:Also, can goaccess be updated? server version is 1.2 from 2017. Latest is 1.9Nothing prevents you from updating if you so desire. Remove CWP's GoAccess and install prerequisite (MaxMind GeoIP library):Code: [Select]yum -y remove goaccessDownload and compile GoAccess, install to replace the current 1.2 version:
yum install libmaxminddb-devel.x86_64Code: [Select]cd /usr/local/src
wget https://tar.goaccess.io/goaccess-1.9.3.tar.gz
tar -xzvf goaccess-1.9.3.tar.gz
cd goaccess-1.9.3/
./configure --prefix= --enable-debug --enable-utf8 --enable-geoip=mmdb --with-getline --with-openssl
make
make install
make threw an error -->threw an error no target found
40
Information / Re: Goaccess stopped working
« on: April 02, 2025, 04:13:09 PM »
fwiw I am reading on line that if one log file is empty then goaccess will not generate a report. Not sure what they are talking about. access file is never zero. And what other log files are they talking about.
41
Information / Re: Goaccess stopped working
« on: April 02, 2025, 02:27:23 PM »
I couldnt find any necessary requisites for installing goaccess. Im on C7 with php 8 something.
On an unrelated subject. I want to add my ip to whitelist on modsec. I seem to remember a filed dedicated to whitelist and a file for blacklist. I cant find them now. What file do I add the ip whitelist to. Not the rules file is it?
On an unrelated subject. I want to add my ip to whitelist on modsec. I seem to remember a filed dedicated to whitelist and a file for blacklist. I cant find them now. What file do I add the ip whitelist to. Not the rules file is it?
42
Information / Re: Goaccess stopped working
« on: April 02, 2025, 02:12:55 PM »
How can you remember all of the posts you have made?
43
Information / Re: Goaccess stopped working
« on: April 02, 2025, 02:10:54 PM »
I was thinking file was too large also. 25MBfor the access log. 780MB for the error log
44
Information / Goaccess stopped working
« on: April 02, 2025, 12:44:58 PM »
For the past 2 days goaccess has not parsed any reports. Any ideas?
Also, current version is 1.2 on my server. Is it possible to update?
Also, current version is 1.2 on my server. Is it possible to update?
45
Apache / Re: How to disable directory listing
« on: March 22, 2025, 12:28:07 PM »
I tried adding .htaccess file to public_html and usr local apache htdocs directories and that did nothing. But I did edit apache config file to delete indexes form followsymlink line. And that fixed it.
