MRatWork Forum by Mustafa Ramadhan
Sawo Project - Kloxo-MR Discussions => Kloxo-MR Technical Helps => Topic started by: WISTFUL on 2013-07-03, 11:31:06
-
When I check my Awstats on kloxo, it redirects me to 'http://domain.com/awstats/awstats.pl?config=domain.com' and below error:
Not Found
The requested URL /awstats/awstats.pl was not found on this server.
Apache/2.2.24 (CentOS) Server at domain.com Port 80
And following results are from '# du -sk *' for below directories:
'/home/kloxo/httpd/awstats/dirdata/domain.com'
du: cannot access `*': No such file or directory
'/home/httpd/domain.com/stats'
0 domain.com-custom_log
20 domain.com-custom_log-20130317.gz
20 domain.com-custom_log-20130318.gz
8 domain.com-custom_log-20130319.gz
24 domain.com-custom_log-20130320.gz
20 domain.com-custom_log-20130321.gz
16 domain.com-custom_log-20130322.gz
16 domain.com-custom_log-20130323.gz
16 domain.com-custom_log-20130324.gz
12 domain.com-custom_log-20130325.gz
16 domain.com-custom_log-20130326.gz
16 domain.com-custom_log-20130327.gz
12 domain.com-custom_log-20130328.gz
12 domain.com-custom_log-20130329.gz
20 domain.com-custom_log-20130330.gz
20 domain.com-custom_log-20130331.gz
8 domain.com-custom_log-20130401.gz
12 domain.com-custom_log-20130402.gz
8 domain.com-custom_log-20130403.gz
20 domain.com-custom_log-20130404.gz
16 domain.com-custom_log-20130405.gz
20 domain.com-custom_log-20130406.gz
20 domain.com-custom_log-20130407.gz
20 domain.com-custom_log-20130408.gz
32 domain.com-custom_log-20130409.gz
1344 domain.com-custom_log-20130628.gz
8 domain.com-custom_log-20130629.gz
12 domain.com-custom_log-20130630.gz
8 domain.com-custom_log-20130701.gz
16 domain.com-custom_log-20130702.gz
12 domain.com-custom_log-20130703.gz
0 domain.com-error_log
4 domain.com-error_log-20130311.gz
4 domain.com-error_log-20130404.gz
4 domain.com-error_log-20130408.gz
4 domain.com-error_log-20130409.gz
4 domain.com-error_log-20130628.gz
4 domain.com-error_log-20130629.gz
4 domain.com-error_log-20130630.gz
4 domain.com-error_log-20130701.gz
4 domain.com-error_log-20130702.gz
4 domain.com-error_log-20130703.gz
-
Awstats not able to read nginx. Nginx-proxy use Apache to read stats.
Too make sure awstats, try 'yum list installed kloxo-stats-*'.
-
Awstats not able to read nginx. Nginx-proxy use Apache to read stats.
Too make sure awstats, try 'yum list installed kloxo-stats-*'.
# yum list installed kloxo-stats-*
Loaded plugins: fastestmirror, priorities, protectbase, replace, security
Loading mirror speeds from cached hostfile
* base: ftp.plusline.de
Excluding mirror: centos.copahost.com
* extras: ftp.plusline.de
Excluding mirror: mirror.de.leaseweb.net
Excluding mirror: mirror.nl.leaseweb.net
* kloxo-mr-epel: mirrors.n-ix.net
* kloxo-mr-ius: mirrors.ircam.fr
* updates: centos.mirror.linuxwerk.com
base | 3.7 kB 00:00
extras | 3.4 kB 00:00
kloxo-mr-centalt | 951 B 00:00
kloxo-mr-centosec | 2.9 kB 00:00
kloxo-mr-epel | 4.2 kB 00:00
kloxo-mr-ius | 2.2 kB 00:00
kloxo-mr-ius-centos5 | 2.2 kB 00:00
kloxo-mr-ius-centos5/primary_db | 123 kB 00:00
kloxo-mr-nginx | 2.9 kB 00:00
kloxo-mr-release-neutral-arch | 1.9 kB 00:00
kloxo-mr-release-neutral-noarch | 1.9 kB 00:00
kloxo-mr-release-version-arch | 1.9 kB 00:00
kloxo-mr-release-version-noarch | 1.9 kB 00:00
kloxo-mr-varnish-3.0 | 951 B 00:00
updates | 3.4 kB 00:00
0 packages excluded due to repository protections
Error: No matching Packages to list
-
Sorry, I mean 'yum list kloxomr-stats*'.
-
# yum list kloxomr-stats*
Loaded plugins: fastestmirror, priorities, protectbase, replace, security
Loading mirror speeds from cached hostfile
* base: mirror.optimate-server.de
Excluding mirror: centos.copahost.com
* extras: mirror.optimate-server.de
Excluding mirror: mirror.de.leaseweb.net
Excluding mirror: mirror.nl.leaseweb.net
* kloxo-mr-epel: mirrors.n-ix.net
* kloxo-mr-ius: mirrors.ircam.fr
* updates: centos.mirror.linuxwerk.com
0 packages excluded due to repository protections
Available Packages
kloxomr-stats-awstats.noarch 7.1-4.mr kloxo-mr-release-neutral-noarch
-
So, it's look like not install.
Install all kloxomr packages with 'yum install kloxomr*'
-
So, it's look like not install.
Install all kloxomr packages with 'yum install kloxomr*'
Thanks, solved.
-
I enabled 'Stats Page Protection' and all things was right.
But after I switch to 'webalizer', every one can access to http://www.domain.com/stats/ (http://www.domain.com/stats/) without any Authorization Required!
-
Different thing with awstats and webalizer, awstats using perl and not work in nginx. And if using nginx-proxy, awstat handling by apache. Otherwise, webalizer using html (static file) and make simple for nginx for handling it. So, webalizer handling by nginx directly (for nginx and nginx-proxy).
It's maybe something wrong with dirprotect in nginx/nginx-proxy.
-
Thanks for your information, but do you know how can I fix it?
-
Try re-dirprotect.
-
Try re-dirprotect.
I enter new pass in 'Stats Page Protection' and re Update it but still I have access to 'http://www.domain.com/stats/'
-
according this GitHub update (https://github.com/mustafaramadhan/kloxo/commit/f61da2454f08a1ac353e18ecb970a487880fef7a) I make that changes on my domains.conf.tpl and dirprotect issue solved.
Now my problem is that "Unresolved/Unknown" appeared as 70% of my total country visits.
According step 7 of this instruction (http://www.webalizer.org/faq.html) I think DNS lookups must used on web server configuration.
I find "/home/nginx/conf/globals/webalizer.conf" but I do not know what to do with it.
-
How can I turn on reverse DNS lookups in kloxo-mr's apache?
-
It's not related to dns lookups but webalizer itself. Maybe geolizer (webalizer patch for GEOIP) will be fix this issue. But it's the same as change webalizer to geolizer.
-
I switch to Awstats but 90% of my (Domains/Countries) is Unknown from [ip] and other (10%) are from [net], [com], [de] and [uk]
-
It seems the automatic awstats update does not work, Also I try execute "Run Stats" manually but does not work!
-
I can see below line in top of my Awstats result page but no any stats recorded on "13 Jul 2013"
Last Update: 14 Jul 2013 - 03:57
Also you can see same issue on bellow stats:
http://hostspectra.com/awstats/awstats.pl/ (http://hostspectra.com/awstats/awstats.pl/)
I've found one answer there: http://www.webtalkforums.com/control-pa ... ating.html (http://www.webtalkforums.com/control-panels/17151-awstats-not-updating.html)
If your server runs at a high load for a few days the stats will not run as they are generally given a lower priority. This will cause the log file to hit it's max limit, and no further logs/stats will be recorded until that log is run by Awstats.
Can you fix this issue on kloxo-mr?
-
Last Update: 14 Jul 2013 - 03:57
09 Jul 2013 125 8,081 11,789 77.22 MB
10 Jul 2013 12 67 178 2.01 MB
11 Jul 2013 0 0 0 0
12 Jul 2013 35 1,999 2,840 18.56 MB
13 Jul 2013 0 0 0 0
14 Jul 2013 0 0 0 0
15 Jul 2013 0 0 0 0
16 Jul 2013 0 0 0 0
Mustafa, please answer...
-
Same for webalizer. I've fixed this with manual cron entry /script/scavenge.
-
Same for webalizer. I've fixed this with manual cron entry /script/scavenge.
Yes! It was related to kloxo internal cron because kloxo self backup not created after 14 jul (/home/kloxo/selfbackup/self/__backup)
Before adding "/script/scavenge" on cron I try to run it by SSH but it hanged up on below line:
Dead Quota: In client-admin mysqldb_usage equals xx.x
-
Before adding "/script/scavenge" on cron I try to run it by SSH but it hanged up on below line:
Dead Quota: In client-admin mysqldb_usage equals xx.x
I'll just had to wait for the scavenge to finish...
-
I try to add "/script/scavenge" to server's "Cron Scheduled Tasks" but get below error:
Alert: Adding crontab has failed due to . Please delete it and add it again.
-
Use crontab -e inside shell
ten insert
type what you need
then wq!
-
Use crontab -e inside shell
ten insert
type what you need
then wq!
Thanks spacedust!
What do you think about this?
viewtopic.php?f=5&t=19103 (http://forum.mratwork.com/viewtopic.php?f=5&t=19103)
-
Use crontab -e inside shell
ten insert
type what you need
then wq!
/etc/crontab
/var/spool/cron/root
Where is better for below?
30 0 * * * /script/scavenge
-
I've added '/script/scavenge' on root's cron file by every day period.
Good news:
kloxo self backup issue solved.
Bad news:
Still below result appeared in awstats:
Last Update: 19 Jul 2013 - 03:57
13 Jul 2013 0 0 0 0
14 Jul 2013 0 0 0 0
15 Jul 2013 0 0 0 0
16 Jul 2013 0 0 0 0
17 Jul 2013 0 0 0 0
18 Jul 2013 0 0 0 0
19 Jul 2013 0 0 0 0
20 Jul 2013 0 0 0 0
-
http://awstats.sourceforge.net/docs/aws ... ILD_UPDATE (http://awstats.sourceforge.net/docs/awstats_setup.html#BUILD_UPDATE)
# perl /home/kloxo/httpd/awstats/wwwroot/cgi-bin/awstats.pl -config=domain.com -update
Create/Update database for config "/etc/awstats/awstats.domain.com.conf" by AWStats version 7.1 (build 1.982)
From data in log file "/home/httpd/domain.com/stats/domain.com-custom_log"...
Phase 1 : First bypass old records, searching new record...
Direct access to last remembered record is out of file.
So searching it from beginning of log file...
Jumped lines in file: 0
Parsed lines in file: 0
Found 0 dropped records,
Found 0 comments,
Found 0 blank records,
Found 0 corrupted records,
Found 0 old records,
Found 0 new qualified records.
# ls -lt /home/httpd/domain.com/stats/
total 14468
-rw-r--r-- 1 apache apache 339 Jul 20 03:14 domain.com-error_log-20130720.gz
-rw-r--r-- 1 apache apache 0 Jul 20 03:14 domain.com-error_log
-rw-r--r-- 1 apache apache 287099 Jul 20 03:14 domain.com-custom_log-20130720.gz
-rw-r--r-- 1 apache apache 0 Jul 20 03:14 domain.com-custom_log
-rw-r--r-- 1 apache apache 160 Jul 19 03:43 domain.com-error_log-20130719.gz
-rw-r--r-- 1 apache apache 6513 Jul 19 03:43 domain.com-custom_log-20130719.gz
-rw-r--r-- 1 apache apache 1483 Jul 15 03:50 domain.com-error_log-20130715.gz
-rw-r--r-- 1 apache apache 442096 Jul 15 03:50 domain.com-custom_log-20130715.gz
-rw-r--r-- 1 apache apache 666 Jul 14 03:42 domain.com-error_log-20130714.gz
-rw-r--r-- 1 apache apache 443228 Jul 14 03:42 domain.com-custom_log-20130714.gz
-rw-r--r-- 1 apache apache 964 Jul 13 03:34 domain.com-error_log-20130713.gz
-rw-r--r-- 1 apache apache 404581 Jul 13 03:34 domain.com-custom_log-20130713.gz
-rw-r--r-- 1 apache apache 2622 Jul 12 03:41 domain.com-error_log-20130712.gz
-rw-r--r-- 1 apache apache 425798 Jul 12 03:41 domain.com-custom_log-20130712.gz
-rw-r--r-- 1 apache apache 3624 Jul 11 03:30 domain.com-error_log-20130711.gz
-rw-r--r-- 1 apache apache 637688 Jul 11 03:30 domain.com-custom_log-20130711.gz
-rw-r--r-- 1 apache apache 1256 Jul 10 03:37 domain.com-error_log-20130710.gz
-rw-r--r-- 1 apache apache 454351 Jul 10 03:37 domain.com-custom_log-20130710.gz
-rw-r--r-- 1 apache apache 1898 Jul 9 03:24 domain.com-error_log-20130709.gz
-rw-r--r-- 1 apache apache 1308657 Jul 9 03:24 domain.com-custom_log-20130709.gz
-rw-r--r-- 1 apache apache 1322 Jul 6 03:08 domain.com-error_log-20130706.gz
-rw-r--r-- 1 apache apache 605017 Jul 6 03:08 domain.com-custom_log-20130706.gz
-rw-r--r-- 1 apache apache 254 Jul 4 03:26 domain.com-error_log-20130704.gz
-rw-r--r-- 1 apache apache 176499 Jul 4 03:26 domain.com-custom_log-20130704.gz
-rw-r--r-- 1 apache apache 125 Jul 3 03:45 domain.com-error_log-20130703.gz
-rw-r--r-- 1 apache apache 358958 Jul 3 03:45 domain.com-custom_log-20130703.gz
-rw-r--r-- 1 apache apache 892 Jul 2 04:36 domain.com-error_log-20130702.gz
-rw-r--r-- 1 apache apache 411803 Jul 2 04:36 domain.com-custom_log-20130702.gz
-rw-r--r-- 1 apache apache 171 Jul 1 03:36 domain.com-error_log-20130701.gz
-rw-r--r-- 1 apache apache 446127 Jul 1 03:36 domain.com-custom_log-20130701.gz
-rw-r--r-- 1 apache apache 2055 Jun 30 03:33 domain.com-error_log-20130630.gz
-rw-r--r-- 1 apache apache 306860 Jun 30 03:33 domain.com-custom_log-20130630.gz
-rw-r--r-- 1 apache apache 138 Jun 29 03:22 domain.com-error_log-20130629.gz
-rw-r--r-- 1 apache apache 272054 Jun 29 03:22 domain.com-custom_log-20130629.gz
-rw-r--r-- 1 apache apache 16327 Jun 28 03:41 domain.com-error_log-20130628.gz
-rw-r--r-- 1 apache apache 3817474 Jun 28 03:41 domain.com-custom_log-20130628.gz
-rw-r--r-- 1 apache apache 1220 Apr 9 01:25 domain.com-error_log-20130409.gz
-rw-r--r-- 1 apache apache 374887 Apr 9 01:25 domain.com-custom_log-20130409.gz
-rw-r--r-- 1 apache apache 13265 Apr 8 01:43 domain.com-error_log-20130408.gz
-rw-r--r-- 1 apache apache 304883 Apr 8 01:43 domain.com-custom_log-20130408.gz
-rw-r--r-- 1 apache apache 433850 Apr 7 01:39 domain.com-custom_log-20130407.gz
-rw-r--r-- 1 apache apache 308965 Apr 6 01:27 domain.com-custom_log-20130406.gz
-rw-r--r-- 1 apache apache 279644 Apr 5 01:51 domain.com-custom_log-20130405.gz
-rw-r--r-- 1 apache apache 328794 Apr 4 01:20 domain.com-custom_log-20130404.gz
-rw-r--r-- 1 apache apache 298 Apr 3 02:49 domain.com-error_log-20130403.gz
-rw-r--r-- 1 apache apache 259306 Apr 3 02:49 domain.com-custom_log-20130403.gz
-rw-r--r-- 1 apache apache 143927 Apr 2 01:50 domain.com-custom_log-20130402.gz
-rw-r--r-- 1 apache apache 933 Apr 1 01:39 domain.com-error_log-20130401.gz
-rw-r--r-- 1 apache apache 254660 Apr 1 01:39 domain.com-custom_log-20130401.gz
-rw-r--r-- 1 apache apache 206588 Mar 31 01:38 domain.com-custom_log-20130331.gz
-rw-r--r-- 1 apache apache 219429 Mar 30 02:10 domain.com-custom_log-20130330.gz
-rw-r--r-- 1 apache apache 602 Mar 29 02:32 domain.com-error_log-20130329.gz
-rw-r--r-- 1 apache apache 349483 Mar 29 02:32 domain.com-custom_log-20130329.gz
-rw-r--r-- 1 apache apache 1289 Mar 28 02:47 domain.com-error_log-20130328.gz
-rw-r--r-- 1 apache apache 337208 Mar 28 02:47 domain.com-custom_log-20130328.gz
-rw-r--r-- 1 apache apache 1031 Mar 27 02:47 domain.com-error_log-20130327.gz
-rw-r--r-- 1 apache apache 1136 Mar 25 02:10 domain.com-error_log-20130325.gz
-rw-r--r-- 1 apache apache 1980 Mar 23 02:50 domain.com-error_log-20130323.gz
-rw-r--r-- 1 apache apache 494 Mar 18 02:38 domain.com-error_log-20130318.gz
-rw-r--r-- 1 apache apache 266 Mar 16 02:24 domain.com-error_log-20130316.gz
-rw-r--r-- 1 apache apache 291 Mar 14 02:16 domain.com-error_log-20130314.gz
-rw-r--r-- 1 apache apache 976 Mar 13 00:16 domain.com-error_log-20130313.gz
-
Sorry to bump.
I am having exact problem.
When I navigate to domain.tld/stats/ it will redirect me to domain.tld/awstats/awstats.pl/, which is showing error 404 (Hiawatha Server as frotnend, Apache 2.3 as backend).
When I tried to go to domain.tld/awstats it will show me a login screen.
after a successful login, it shows me error 403 instead of awstats page.
I have done these:
1. Doing yum list kloxomr-stats* shows that kloxomr-stats is already installed.
2. I have tried to set up scavenge time to 0:15 but nothing happened
3. I have tried to run 'sh /script/fixtraffic --day=30', nothing happened
4. I have tried to run 'sh /script/fix-all; sh /script/restart-all', nothing happened
A. Control Panel:
- Kloxo-MR: 7.0.0.b-2016012103
- Web: hiawatha-10.0.0-f.6.mr.el6.x86_64
- PHP: php54s-5.4.45-2.w6 (cgi mode)
B. Plateform:
- OS: CentOS release 6.7 (Final) x86_64
- Hostname: *
C. Services:
1. MySQL: MariaDB-server-10.0.23-1.el6.x86_64
2. PHP:
- Branch: php54-cli-5.4.45-1.ius.el6.x86_64
- Multiple:
* php52m-5.2.17-102.mr.el6
* php53m-5.3.29-1.ius.el6
* php54m-5.4.45-2.w6
* php55m-5.5.30-1.ius.el6
* php56m-5.6.16-1.ius.el6
* php70m-7.0.2-1.w6
- Used: php54m
3. Httpd: httpd-2.2.31-1.mr.el6.x86_64
- PHP Type: php-fpm_event
4. Lighttpd: --uninstalled--
5. Hiawatha: --used--
6. Nginx: --uninstalled--
7. Cache: --uninstalled--
8. Dns: nsd-4.1.7-3.el6.x86_64
9. Qmail: qmail-toaster-1.03-1.3.55.mr.el6.x86_64
- with: courier-imap-toaster-4.1.2-1.3.18.mr.el6.x86_64
-
Depend on your website applications that maybe 'takeover' for 'stats' dir.
-
So there should be stats dir on every domain?
I have tree domains under three users, all of them is showing exact behavior.
what should I do next? Should I reinstall awstats or do you have better recommendations?
-
If you access to http://domain.com/stats that will redirect to awstats.
-
If I go to domain.tl/stats, it redirects me to domain.tld/awstats/awstats.pl
It shows me white/blank page.
If I try to go to domain.tld/awstats >> Error 404
-
Use webalizer.
-
I've managed to make it work.
The problem is with Hiawathaproxy. after I changed to nginxproxy, all problems were solved.
Is this kind of behavior normal with hiawathaproxy?