Sponsored Content
Full Discussion: Awstats webserver analyser
Special Forums UNIX and Linux Applications Infrastructure Monitoring Awstats webserver analyser Post 302914189 by ajayram_arya on Friday 22nd of August 2014 12:42:44 PM
Old 08-22-2014
RedHat Awstats webserver analyser

Need assistance in troubleshooting

I have configured awstats 7.3 version on RedHat linux and I am stuck at getting the updates from the website . Please let me know if anybody can give me some inputs

I can see the webpages but it gives "Never updated (See 'Build/Update' on awstats_setup.html page)"

Code:
/local/tools/perl-5.18/bin/perl awstats.pl -config=awstats.webstats.conf -update
Create/Update database for config "./awstats.webstats.conf" by AWStats version 7.3 (build 20140126)
From data in log file "/local/tools/awstats-7.3/var/log/access.log"...
Phase 1 : First bypass old records, searching new record...
Searching new records 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.

 

3 More Discussions You Might Find Interesting

1. BSD

can't install AWStats

I am running FreeBSD 6.3 and trying to install AWStats. I found this site with some instructions: Installing AWStats on FreeBSD however, the pkg install doesn't work. This is the error I get: dl1-3# pkg_add install -r awstats pkg_add: can't stat package file 'install' pkg_add: can't stat... (3 Replies)
Discussion started by: jasonfrost
3 Replies

2. UNIX for Advanced & Expert Users

Building a performance static analyser

I was wondering if someone could let me know if tools exist that check for performance degrading coding practices. There is of course the well known Valgrind (Valgrind Home), but the question is more if it is possible at a fundamental level. Do generic test cases exist for checking statically for... (9 Replies)
Discussion started by: figaro
9 Replies

3. OS X (Apple)

Text mode AF spectrum analyser.

Well guys, this MUST be a first. This is DEMO code only and has NO error detection or correction, nor out of bounds checking. I have succumbed to Python and scipy to do the FFT heavy lifting as I have absolutely no idea where to start do such a thing using AWK. This is a taster for me to... (7 Replies)
Discussion started by: wisecracker
7 Replies
EVENTLOGADM(8)                                              System Administration tools                                             EVENTLOGADM(8)

NAME
eventlogadm - push records into the Samba event log store SYNOPSIS
eventlogadm [-d] [-h] -o addsource EVENTLOG SOURCENAME MSGFILE eventlogadm [-d] [-h] -o write EVENTLOG eventlogadm [-d] [-h] -o dump EVENTLOG RECORD_NUMBER DESCRIPTION
This tool is part of the samba(1) suite. eventlogadm is a filter that accepts formatted event log records on standard input and writes them to the Samba event log store. Windows client can then manipulate these record using the usual administration tools. OPTIONS
-d The -d option causes eventlogadm to emit debugging information. -o addsource EVENTLOG SOURCENAME MSGFILE The -o addsource option creates a new event log source. -o write EVENTLOG The -o write reads event log records from standard input and writes them to the Samba event log store named by EVENTLOG. -o dump EVENTLOG RECORD_NUMBER The -o dump reads event log records from a EVENTLOG tdb and dumps them to standard output on screen. -h Print usage information. EVENTLOG RECORD FORMAT
For the write operation, eventlogadm expects to be able to read structured records from standard input. These records are a sequence of lines, with the record key and data separated by a colon character. Records are separated by at least one or more blank line. The event log record field are: o LEN - This field should be 0, since eventlogadm will calculate this value. o RS1 - This must be the value 1699505740. o RCN - This field should be 0. o TMG - The time the eventlog record was generated; format is the number of seconds since 00:00:00 January 1, 1970, UTC. o TMW - The time the eventlog record was written; format is the number of seconds since 00:00:00 January 1, 1970, UTC. o EID - The eventlog ID. o ETP - The event type -- one of "INFO", "ERROR", "WARNING", "AUDIT SUCCESS" or "AUDIT FAILURE". o ECT - The event category; this depends on the message file. It is primarily used as a means of filtering in the eventlog viewer. o RS2 - This field should be 0. o CRN - This field should be 0. o USL - This field should be 0. o SRC - This field contains the source name associated with the event log. If a message file is used with an event log, there will be a registry entry for associating this source name with a message file DLL. o SRN - The name of the machine on which the eventlog was generated. This is typically the host name. o STR - The text associated with the eventlog. There may be more than one string in a record. o DAT - This field should be left unset. EXAMPLES
An example of the record format accepted by eventlogadm: LEN: 0 RS1: 1699505740 RCN: 0 TMG: 1128631322 TMW: 1128631322 EID: 1000 ETP: INFO ECT: 0 RS2: 0 CRN: 0 USL: 0 SRC: cron SRN: dmlinux STR: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly) DAT: Set up an eventlog source, specifying a message file DLL: eventlogadm -o addsource Application MyApplication | \ %SystemRoot%/system32/MyApplication.dll Filter messages from the system log into an event log: tail -f /var/log/messages | \ my_program_to_parse_into_eventlog_records | \ eventlogadm SystemLogEvents VERSION
This man page is correct for version 3.0.25 of the Samba suite. AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. Samba 3.5 06/18/2010 EVENTLOGADM(8)
All times are GMT -4. The time now is 05:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy