GWVSTATS

Stats are working.

The GWVSTATS Module keeps data that is used for statistics on the following:

Dashboard

Reports

Message tracker

Level 1

The statistics configuration is located under Server/Interface Management | Server | Server Management | Configure server | Additional statistics configuration.

- Enable Statistics = if this box is enabled GWAVA will keep track of the statistics

- Statistics queue directory (relative to root) = if you enter a path here then it will be used instead of the default path of /opt/beginfinite/gwava/services/stats/in_queue

- Days to retain statistics = default setting is 30 days. This can be lowered if you find the stats db is too large.

- Prune information from statistics database = if this is checked then data will be pruned from the stats db

- Statistics database maintenance time = hour that maintenance is performed such as pruning.

- Number of counter records to delete per batch = default is set to 1000

- Enable statistics nighlty reindex = this is enabled by default, it checks the database each night for errors, during maintenance

- Enable statistics nightly database vacuum = this is disabled by default, if this this enabled it will vacuum the db to shrink it, during maintenance.

- Enable statistics weekly database analyze = this is enabled by default

- Enable statistics database integrity check = this is disabled by default, if the db fails the integrity check then an alert is sent to the admin

- Statistics database size warning threshold (in megabytes) = default is set to 2000 (2GB), an alert will go out to the admin if the db is larger then the threshold

- Statistics batch processing buffer size = default is set to 1 MB

- Statistics role = default is set to Master, slave is used if you are sharing stats on a different GWAVA server

- Statistics parent server (when in slave mode) = this needs to be set to the server that you want stats to be stored on

- [custom] Statistics master address = where you can enter a customer master server address

- [custom] Statistics master login name = where you can enter a customer master server login name

- [custom] Statistics master password = where you can enter a customer master server password

Level 2

The stats module is called gwvstats.

To unload GWVSTATS only:

For Linux type: rcgwavaman stop gwvstats

For Windows: from Services find GWAVA Stats, right click and choose stop

To load GWVSTATS only:

For Linux type: rcgwavaman start gwvstats

For Windows: from Services find GWAVA Stats, right click and choose start

To check the status of GWVSTATS only:

For Linux type: rcgwavaman start gwvstats

For Windows: from Services find GWAVA Stats, right click and choose start

<insert linux commands.jpg>

<insert wincommands.jpg>

The Stats directory is located:

- on Linux: /opt/beginfinite/gwava/services/stats

- on Windows: drive installed on/program files/gwava/gwava/services/stats

The stats directory is as follows: Data: Backup: Stores 7 days worth of backups of the stats_data.db

Db_setup: various xml files for db's

Err: DB error files are stored here

Scripts: stats scripts are stored here

Storage: Data files for each message that goes through GWAVA is stored here, in the structure of YR|Mnth|Day|Hr.

Forward: Queue for messages forwarded

Http: Where stats templates and Image files are stored

In_queue: Queue for stats messages waiting to be processed into the stats_data.db and storage directories.

Slave_in_queue: Queue for stats messages if sharing a stats server with another server, which is the master server.

Slave_out_queue: Outbound queue for stats messages if sharing a stats server with another server, which is the master server.

Temp: where temp files are stored

Running.txt: Stats shutdown integrity check file. Do not delete this file.

If a gwvstats_data.db gets too large for the server to handle or becomes malformed you may see Script Errors on the Dashboard or reports that are emailed out. You may also see high utilization on gwvstats.

Here is a TID on how to handle this if it is too large: http://support.gwava.com/kb/?View=entry&EntryID=2105

Stats_data.db can become malformed if the db is too large and doesn't shut down in the allotted time. The default wait time is 60 seconds.

Do the following if you feel you need to increase the time GWAVA allows gwvstats to shut down before killing it (to prevent it becoming malformed:

1) Edit /etc/init.d/gwavaman

2) Search for: gwvstats

You should find the following section: prog=${subArray[1]//${GWAVA_LOCATION}/}

  if [ "$prog" == 'gwavaqms' -o "$prog" == 'gwavaman' -o "$prog" == 'qms2' -o "$prog" == 'gwvstats' ]
  then
      subArray[1]="${BIN_PATH}${subArray[1]//${STANDARD_GWAVA_BIN}/}"					
      echo -n "Shutting down ${subArray[1]}"
      killproc -TERM -t60 ${subArray[1]} >& /dev/null
  if [ `echo $?` -ne "0" ]
  then
      killproc -TERM -t60 ${subArray[1]}.old >& /dev/null
  fi

3) Change -t60 to -t120. This will increase the time it waits, before killing gwvstats and qms2, from 60 seconds to 120 seconds.

4) Save the changes.

To learn more about web scanning, check out the GWVICAP Module.