Environment
REDLINE 2.5x, 3.x
Situation
What is the information gathered in the gwcheck logs that are configured for Redline? Where is all the data from the Redline reports on the post offices and users coming from?
Resolution
Below is a description of each of the three scheduled gwcheck events that should have been created during initial configuration of Redline by the user. These scheduled tasks are completed at least once daily, and are put on disk in the post office directory ../wpcsout/chk. After completion the files output are sent to the Control Center by the Redline Agent for processing where they will be placed in one or more of the Redline databases. The Redline Agent gathers the files, named "gwaudit.log, gwstats.log, or mbstats.log", for each post office in the GroupWise System. It then sends them to the Redline Control Center for processing. The Control Center places the relevant data into the a database where it can be queried to produce various reports about all users licenses and activity in the GroupWise system. Once Redline retrieves these files they are removed from the disk. Administrators can then query these databases through the Redline web interface to generate reports and gather statistical information about the GroupWise system and its users.
The three tasks output the following basic reports; gwaudit.log, gwstats.log, and mbstats.log. Details about each of these are listed below.
GWAUDIT.LOG
Redline requires a scheduled nightly task called an audit report. This report contains the following information about a post office:
1) shows which mailboxes require full client licenses and which mailboxes require limited client licenses
2) shows which mailboxes are active (have been accessed at least one time)
3) shows which mailboxes have never been active
4) shows which mailboxes have been inactive for a specified period of time.
Here is an example of what might be seen in an audit report:
----- Audit report for user (mjohnson) on database /opt/novell/groupwise/furya/ofuser/user5g5.db
Last activity time - 08/07/08 13:10
Full client license
PROCESSING COMPLETED- total processing time: 0:00:00 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ---------------------------------------------------------------------
Audit report for user (linuxadmin) on database /opt/novell/groupwise/furya/ofuser/user6te.db
Last activity time not available
Limited client license User is inactive
PROCESSING COMPLETED- total processing time: 0:00:00 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
GWSTATS.LOG
Redline requires a scheduled nightly task called Mailbox Statistics by GroupWise. When Redline is initially configured, a scheduled report is setup, and is output as "gwstats.log". This report gives individual user statistics about client mailboxes and includes the following:
1) Number of records in the client mailbox
2) How many messages in the Inbox, Outbox, and Trash
3) The size of the client mailbox
4) How close to the threshold (if there is one set) the mailbox is.
5) Provides a record check for the messages In addition, this report gives overall GroupWise System information such as:
a) Number of users, mailboxes, and post offices
b) Number of normal, forwarded, replied to, read, unread messages in the system
c) Distribution list statistics
d) Average message sizes
e) Number of low, standard, high priority messages
Here is an example of what is contained in the Mailbox Statistics gwcheck report: ===== TASK LOG - 2 (489af789.ckl)
====Checking user = mjohnson (5g5) 146432 bytes, 08/07/08 13:10 ( mike [])
CONTENTS VERIFICATION/STATISTICS analysis of db /opt/novell/groupwise/furya/ofuser/user5g5.db - 88 records found, last DRN = 93 - checking Data records 36
ITEM_RECORD check- MAIL record 37
ITEM_RECORD check- MAIL record 38
ITEM_RECORD check- MAIL record 39
ITEM_RECORD check- MAIL record 40
ITEM_RECORD check- MAIL record 41
ITEM_RECORD check- MAIL record 42
ITEM_RECORD check- MAIL record 43
ITEM_RECORD check- MAIL record 44
ITEM_RECORD check- MAIL record 45
ITEM_RECORD check- MAIL record 46
ITEM_RECORD check- MAIL record 47
ITEM_RECORD check- MAIL record 48
ITEM_RECORD check- MAIL record 49
ITEM_RECORD check- MAIL record 50
ITEM_RECORD check- MAIL record 51
ITEM_RECORD check- MAIL record 52
ITEM_RECORD check- MAIL record 53
ITEM_RECORD check- MAIL record 54
ITEM_RECORD check- MAIL record 72
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 73
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 74
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 75
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 76
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 77
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 78
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 92
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item 93
ITEM_RECORD check- MAIL record - found 1 recipient(s) for outbox item
User stats: 21 InBox, 11 OutBox, 0 WasteBasket
Disk space management values: Size Limit - 0KB, Threshold - 0% 247028 kbytes in use by user's mail
PROCESSING COMPLETED- total processing time: 0:00:00 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GroupWise System Information
Number of Users............... 5
Number of Post Offices......... 1
Number of Mailboxes........... 5 ------------------------------------------------------------------------------
Item statistics:
TOTAL /MBOX Mailbox statistics:
TOTAL /MBOX normal items........ 185 37.0 Boxes with mail....... 5 forwarded items..... 15 3.0 IN box entries: reply items......... 0 0.0 read................ 32 6.4 total items......... 200 40.0 unread.............. 0 0.0 new................. 140 28.0 Distribution statistics: total............... 172 34.4 to single user...... 19 3.8 Boxes over IN limit. 0 to <= 3 users....... 25 5.0 OUT box entries: to many users....... 3 0.6 total............... 28 5.6 sent encrypted (%).. 0 Boxes over OUT limit 0 Schedule statistics: Average item length.... 1522KB Boxes with schedules.. 0 INcoming appointments: Items w/ attachments... 0 read................ 0 0.0 Average number attach.. 0 unread.............. 0 0.0 Average attach length.. 0 new................. 0 0.0 total............... 0 0.0 Items hidden by rcvr... 0 OUTgoing appointments: Items in trashcan...... 0 0.0 total............... 0 0.0 Items counts:
TOTAL /MBOX ----- ----- mail 200 40.0 appointment 0 0.0 note 0 0.0 task 0 0.0 phone 0 0.0 profile 0 0.0 others 0 0.0 Items breakdown:
IN OUT PERS DRAFT | TOTAL ----- ----- ----- ----- + ----- mail.................. 172 28 0 0 | 200 appointment........... 0 0 0 0 | 0 note.................. 0 0 0 0 | 0 task.................. 0 0 0 0 | 0 phone................. 0 0 0 0 | 0 ----------------------------- + ------ total................. 172 28 0 0 | 200 Priority breakdown:
LOW NORM HIGH | TOTAL ----- ----- ----- | ----- mail.................. 0 200 0 | 200 appointment........... 0 0 0 | 0 note.................. 0 0 0 | 0 task.................. 0 0 0 | 0 ----------------------+------ total................. 0 200 0 | 200 Security breakdown:
NORM PROP CONF SECR TSEC FYEO | TOTAL ----- ----- ----- ----- ----- ----- | ----- mail.................. 200 0 0 0 0 0 | 200 appointment........... 0 0 0 0 0 0 | 0 note.................. 0 0 0 0 0 0 | 0 task.................. 0 0 0 0 0 0 | 0 ----------------------------------------------|------ total................. 200 0 0 0 0 0 | 200
Return Receipt Requests: OPEN ACCEPT DELETE ----- ----- ----- mail.................. 0 n/a 0 appointment........... 0 0 0 note.................. 0 n/a 0 task.................. 0 n/a 0 --------------------- total................. 0 0 0
MBSTATS.LOG
Redline requires a scheduled nightly task called an Mailbox Statistics report. This can be used to get the size of each mailboxes and suggest voluntary cleanup. It can be beneficial for e-mail retention and provide such data as:
1) The number of messages and appointments in the post office
2) Age of messages
3) Size of user databases.
4) Display any user mailboxes that have more than a specified number of items. This can help determine which users might be using an excessive amount of file server disk space. Here is an example of what may be seen in this statistical report:
========== mjohnson (5g5 / 176) 88 ( 93) 0 6 146432 ( mike []) Return from GetBoxBackupAndRetentionSettings = 0xDF06 Items older than 60 days: Downloaded items older than 30 days: Items larger than 1024000 bytes: 247028 kbytes in use by user's mail Type From To Date Size Drn ------ ---------------- ---------------- -------------- --------------- ---
PROCESSING COMPLETED- total processing time: 0:00:00 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =====
JOB LOG SUMMARY (489af793.ckl) =========================================== ================================================================================
*** User databases found: 5 *** Total recs in all dbs: 462 data 0 deleted 31 setup 2675712 bytes *** Average recs per user: 92 data 0 deleted 6 setup 535142 bytes Processing completed
Additional Information
This article was originally published in the GWAVA knowledgebase as article ID 370.