After you have installed Content Gateway, open the Content Gateway manager (the management interface) to verify that the proxy is running. See Accessing the Content Gateway manager and Verifying that the proxy is processing Internet requests.

The presence of the /opt/WCG/config/internal/no_cop file acts as an administrative control that instructs the content_cop process to exit immediately without starting content_manager or performing any health checks. The no_cop file prevents the proxy from starting automatically when it has been stopped with the
./WCGAdmin stop command.

Without such a static control, Content Gateway would restart automatically upon system reboot. The no_cop control keeps Content Gateway off until it is restarted with the ./WCGAdmin start command.

When the no_cop file prevents Content Gateway from starting, the following message is recorded in the system log file: