License Limit Exceeded error returned for Reporter 9 and log processing has stopped Getting an alert in Reporter 9 stating "License Limit Exceeded" and all log processing has stopped. Error: ALERT raised: Licensed DB requests has reached or climbed above the 50000000 DB requests warning threshold -- currently 50871300 of 50000000 DB requests Reporter 9 has stopped processing all my logs. How to get it to start processing my logs again? Access log processing on Blue Coat Reporter 9 stopped. Why? Reporter 9 stops processing log files
Reporter 9.x has three available licenses:
Standard (default) - Installing and running Reporter requires no license; however, the default mode (also known as the Standard License) limits log processing to 50 million concurrent log lines. If log processing reaches this limit, Reporter halts processing until lines are removed from the databases (or you install a higher level license).
Enterprise - Purchasing and installing an Enterprise License enables Reporter to process up to 2.5 billion concurrent log lines.
Premium - Purchasing and installing an Premium License enables Reporter to process up to 20 billion log lines.
When navigating within the Reporter Management Console, go to Administration > System Overview > Reporter System Information > System Event Log. In the System Event Log there may be an event similar to the following message:
"ALERT raised: Licensed DB requests has reached or climbed above the 50000000 DB requests warning threshold -- currently 50871300 of 50000000 DB requests"
The use of the current value stated relative to the license limits shown above to give an idea which license to purchase. There may also be a way to be able to remedy the problem by simply limiting database log lines. This means expiring database data more frequently. So instead of keeping the last 30 days of data in the database, it means there may be need to keep only 20 days worth of data in the database.
Follow the steps below to expire records contained in the Reporter database:
Navigate to Administration > General Settings > Reporter Settings > Data Settings > Databases
From the database(s) in question, click on the Actions drop-down arrow and select "Set Expiration".
Ensure that a check is placed in the box for "Expire database data older than".
Enter a value for the amount of days (Blue Coat's recommendation is 30-60 days but a lower value may be needed).
Set the Frequency (default is daily - Keep in mind that if using weekly or monthly, the database data will exceed the number of days set for that duration).
Set the execution time. By default, Reporter will expire data at 12:00 am. If not wanting to wait until the default execution time, kindly change the execution time accordingly.
If multiple databases, repeat steps 2 to 6 for each database.
NOTE: If there is a need to access expired data, it is possible to create a new database to reprocess the access logs for the pertinent dates, provided there has been saved access logs (this does not apply to the direct stream transfer method from the ProxySG to Reporter or if a post processing action of delete).
Upon completing these steps the log reader will not automatically start. To manually start the log reader, please do the following steps:
Navigate to Administration > General Settings > Reporter Settings > Data Settings > Log Sources
From the log source(s) in question, click on the Actions drop-down arrow and select "Start Log Source".
Imported Document ID: 000012156
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.