Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Other reporting issues for web protection solutions > Real-Time Monitor is not responding
Real-Time Monitor is not responding
Administrator Help | Forcepoint Web Security and Forcepoint URL Filtering | v8.4.x
If Real-Time Monitor is installed on a different machine from the Forcepoint Security Manager, use the ping command to make sure that the 2 machines can communicate across the network. Also verify that the management server machine can communicate with Real-Time Monitor on port 9445 (for user interface display).
In addition, Real-Time Monitor must be able to communicate with:
*
Usage Monitor on port 55835
*
Policy Server on port 55836 (encrypted communication) or 55856 (non-encrypted communication)
If there is not a network communication problem, Real-Time Monitor may be experiencing resource constraints.
*
Check memory, CPU usage, and available disk space on the Real-Time Monitor machine.
Note that the RTM Database can hold a maximum of 10,000 records, which should help to limit its impact on available disk space.
*
The database may be receiving too many requests, or be unable to accept additional connections.
If the Windows Event Viewer shows Websense RTM Database errors, you can restart the service to address the problem.
Note that when the database is restarted, all records are cleared, so older data is lost. Data that is not available for display in Real-Time Monitor is still stored in the Log Database, and can be seen in investigative and presentation reports.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Troubleshooting > Other reporting issues for web protection solutions > Real-Time Monitor is not responding
Copyright 2017 Forcepoint. All rights reserved.