Forum Discussion
NimbostratusBIGpipe class operation error
After add a new monitor into my configuration with Webclient, i executed "b load" to reload configuration files, but the problem starts.
Executing "b load":
[root@bigip:Active] config b
load
Reading configuration from
/defaults/config_base.conf.
Reading configuration from
/config/bigip_base.conf.
Reading configuration from
/config/bigip_sys.conf.
Reading configuration from
/usr/bin/monitors/builtins/base_monitors.conf.
Reading configuration from
/config/profile_base.conf.
Reading configuration from
/config/daemon.conf.
Reading configuration from
/config/bigip.conf.
Reading configuration from
/config/bigip_local.conf.
Loading the configuration
...
BIGpipe class operation
error:
01070712:3:
Caught configuration exception (0), Invalid string query key field, too long,
length:99746 class:class_string_item key:class_tree field:value -
EdbQueryKey.cpp, line 247.
Thank you for your help
14 Replies
mferpan_60559Hi iRuleYou !
Line 247 refers a node monitor and is irrelevant...
It's like this:
node xxx.xxx.xxx.xxx {
dynamic ratio 10
monitor check_load
screen yyyyyyyyyy
}
Before making changes on this file (bigip.conf) this node was the same as now
I tried to find the file EdbQueryKey.cpp, but i can't find it.
I understand that the error is "Invalid query string key field" it seems too big ...
i'm looking for this file to understand the query on line 247
Thank you- mferpan_60559Could anyone help me ?
Thank you 
richard_77048I ran into this once. In my case it was caused by a know issue, CR 123363, where escaped quotes in a class will cause an extra backslashes to be added on a save. This will cause the class file to grow until it exceeds the 65523 character limit. Do you have any classes with escaped quotes in them? In my case everything worked fine, all the while the class file was growing and growing. Then one day it got too big and I got the error. If you have classes defined, look at the old ones; they may be the problem.
The way I got around this was to base64 encode my classes and decode them when I served them up. I used uuencode to encode them and then uploaded them to my units. I used the b64decode function to decode them in my irule. Here is the wiki page for b64decode: http://devcentral.f5.com/wiki/default.aspx/iRules/b64decode.html- mferpan_60559Thank you so much Richard.
You are right, the error was due a .class file with a lot of \\\\ characters located into /var/class directory. In my case this file is error_page.class
Now everything is OK !!!!
Best reagards
