How to turn on CT logging in GWAVA

  • 7019831
  • 15-Sep-2014
  • 07-Aug-2017

Environment

GWAVA 6.5 B35

Situation

GWAVA has a lot of unable to connect to signature spam engine errors in the logs. What does this mean and how do you resolve it?

Resolution


There is a connectivity issue where the anti-spam functionality fails to talk to the data centers. GWAVA has the ability to enable specialized logging for this issue. To enable this additional logging, do the following:

1) Stop GWAVA
Linux: rcgwavaman stop gwava

Windows: Stop the GWAVA process in Services
2) Edit startup options
Linux: Edit the services.conf file. The file is located in /opt/beginfinite/gwava/assets/conf

Edit the file to look like this:
[gwava]
program    ! gwava
arguments  ! /ctlog
Windows: The windows service needs to be edited. This edit needs to be done in the registry. Follow the instructions in this article here. Edit the GWAVA service and add /ctlog
3) Start GWAVA
Linux: rcgwavaman start gwava

Windows: Start the GWAVA service in Services
There should now be a new directory in the ../logs/gwava/support directory called ct. This folder will log any connection issues with the spam engine. The files in this directory and not zipped up or removed during maintenance. This feature should only be temporary until a new stable patch can be released.

If there are any issues applying these things then please contact GWAVA support

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2363.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.