Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Getting Started with Content Gateway > Starting and stopping Content Gateway on the command line
Starting and stopping Content Gateway on the command line
Help | Content Gateway | v8.5.x
To stop or start Content Gateway from the command line:
1.
su
2.
3.
*
./WCGAdmin start
*
./WCGAdmin stop
*
./WCGAdmin restart
*
./WCGAdmin status
The no_cop file
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:
content_cop[16056]: encountered "config/internal/no_cop" file...exiting
 

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Getting Started with Content Gateway > Starting and stopping Content Gateway on the command line
Copyright 2023 Forcepoint. All rights reserved.