Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Content Gateway Troubleshooting : Content Gateway command line commands do not execute
Content Gateway command line commands do not execute
Content Gateway Troubleshooting | Forcepoint Web Security | v8.4.x, v8.5.x | 29-Apr-2022
Command line commands do not execute if:
*
The content_manager process is not running.
Confirm that the content_manager process is running by entering the following command:
ps aux | grep content_manager
or, from the /opt/WCG directory:
./WCGAdmin status
If the content_manager process is not running, to start it enter the following command from the Content Gateway bin directory (/opt/WCG/bin):
./content_manager
 
* 
Important 
If you must stop Content Gateway use:
./WCGAdmin stop
To start Content Gateway use:
./WCGAdmin start
To restart Content Gateway use:
./WCGAdmin restart
*
You are not executing the command from $WCGHome/bin.
If the Content Gateway bin directory is not in your path, make your working directory /opt/WCG/bin and prepend each command with './'
For example:
./content_line -h

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Content Gateway Troubleshooting : Content Gateway command line commands do not execute
Copyright 2022 Forcepoint. All rights reserved.