Multiplexer or Bridge Service is not running or not responding
Multiplexer receives log data from Filtering Service and forwards it to the Bridge Service and to Log Server. Bridge Service then forwards data to the Cloud App Service and, when SIEM integration is enabled on the page, to the SIEM Connector. Log Server forwards log data to the Log Database for use in reporting.
Multiplexer receives log data from Filtering Service and forwards it to the Bridge Service and to Log Server. When SIEM integration is enabled on the page, Bridge Service forwards SIEM data for processing. Log Server processes log data into the Log Database for use in reporting and copies the data to a specific folder for Cloud Apps Service to process into the Log Database.
If Multiplexer is not running or not available, a failover feature ensures that Filtering Service passes log data directly to Log Server, but data is not forwarded to the Bridge Service.
When Bridge Service is not receiving data, is stopped, or is not responding, no cloud app or SIEM data can be forwarded to the appropriate service. SIEM logs and the Cloud Applications report do not show data for transactions logged while either of these services is stopped or not responding.
To resolve an issue with Multiplexer:
- Windows: Use the Windows Services tool to start Websense Multiplexer.
- Linux: Use the /opt/Websense/WebsenseDaemonControl command to start Multiplexer.
- On an appliance: Use the CLI command to start Multiplexer. See the Forcepoint Appliances CLI Guide.
To resolve an issue with Bridge Service:
- Windows: Use the Windows Services tool to start Websense Bridge Service.
- Linux: Use the /opt/Websense/WebsenseDaemonControl command to start Bridge Service.
- On an appliance: Use the CLI command to start Bridge Service. See the Forcepoint Appliances CLI Guide.