Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
FAQs and Troubleshooting Tips > Troubleshooting tips > No cop file message in the system log file
The file config/internal/no_cop 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 or the stop_content_gateway commands. 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 or the start_content_gateway command.
The Content Gateway installation script creates a no_cop file so that Content Gateway does not start automatically. After you have completed installation and configuration, and have rebooted the operating system, use the
./WCGAdmin start or the start_content_gateway command to start Content Gateway. See Getting Started, for information on starting and stopping Content Gateway.

Go to the table of contents Go to the previous page Go to the next page Go to the index View or print as PDF
FAQs and Troubleshooting Tips > Troubleshooting tips > No cop file message in the system log file