Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP AFM, APM, ASM, AVR, PEM, PSM, SWG
Known Affected Versions:
11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.1 HF10, 11.5.1 HF11, 11.5.2, 11.5.2 HF1, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5
Fixed In:
11.6.0 HF6, 11.5.3
Opened: Sep 15, 2014 Severity: 3-Major Related Article:
K16894
When you apply a hotfix on an already configured and working volume, many errors are logged in the monpd/ltm logs. Note: The system uses the monpd process in conjunction with the avrd process (Analytics) for reporting application performance data. As a result of this issue, you may encounter one or more of the following symptoms: In the /var/log/ltm file, you observe error messages similar to the following example: err DB[10860]: monpd|ERR|Jan 01 09:00:00.123|12345| [DB::mysql_query_safe, query failed] Error (error number 1243) executing SQL string : EXECUTE stmt_select_table_with_too_many_partitions USING @table_name,@table_name Because : Unknown prepared statement handler (stmt_select_table_with_too_many_partitions) given to EXECUTE err DB[10860]: monpd|ERR|Sep 02 09:00:00.123|12345| [DB::run_sql_query, mysql_query_safe] Error executing SQL query: EXECUTE stmt_select_table_with_too_many_partitions USING @table_name,@table_name Because : Unknown prepared statement handler (stmt_select_table_with_too_many_partitions) given to EXECUTE In the /var/log/avr/monpd.log file, you observe error messages similar to the following example: monpd|ERR|Jan 1 09:00:00.123|12345| [DB::mysql_query_safe, query failed] Error (error number 1243) executing SQL string : EXECUTE stmt_select_table_with_too_many_partitions USING @table_name,@table_name Because : Unknown prepared statement handler (stmt_select_table_with_too_many_partitions) given to EXECUTE monpd|ERR|Jan 1 09:00:00.123|12345| [DB::run_sql_query, mysql_query_safe] Error executing SQL query: EXECUTE stmt_select_table_with_too_many_partitions USING @table_name,@table_name Because : Unknown prepared statement handler (stmt_select_table_with_too_many_partitions) given to EXECUTE
The BIG-IP system consumes a small amount of additional disk space. These are cosmetic, benign errors.
This issue occurs when all of the following conditions are met: -- You have provisioned the Application Visibility and Reporting module. -- You have recently installed a software hotfix. -- You have rebooted the BIG-IP system into the newly hotfixed boot location. -- You have provisioned one of the following modules: AFM, APM, ASM, AVR, CGN, DNS, FPS, PEM, PSM, SWG, or vCMP.
There is no workaround for this issue. However, you can stop the system from logging the monpd errors by rebuilding the Application Visibility and Reporting database. To do so, perform the following procedure: Impact of workaround: The following procedure does not disable monpd logging. Normal monpd log entries will continue to be written to the /var/log/avr/monpd.log file. Log in to the BIG-IP command line. Type the following command: mysql -p`perl -MPassCrypt -nle 'print PassCrypt::decrypt_password($_)' /var/db/mysqlpw` AVR < /var/avr/avr_srv_code.sql To restart the monpd process, type the following command: bigstart restart monpd
None