You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If have searched for that space and it isn't present in the sources. This suggests it's something that has been done by accident at some point, which will stop the variable translation working properly.
I guess it is not in the sources. Probably |query_ifSpeed| (note the trailing space) was input by mistake. The space should not trigger any weird behavior though IMHO. Are all inputs trimmed by the code before storing in the DB? Or are they at least trimmed before processing?
Inputs may be trimmed but inner spaces are not. So if you had entered "|query_ifSpeed| " (with space), that may have lost the trailing space. But inside the text it would be impossible to know if it was a valid space or not.
It's clear that bad spaces in the middle of a string cannot be recognized.
But in this case, adding a trailing space (doesn't even need to be after a variable) breaks certain things.
If I input |query_ifSpeed| (note the trailing space) then RRDtool Tune Info complains: RRD maximum for Data Source 'traffic_out' should be '4294967295 ' ... /usr/bin/rrdtool tune /srv/www/vhosts/cacti/cacti/rra/9/437.rrd --maximum traffic_out:4294967295
In that case the message is totally confusing because:
The RRD already contains "4294967295" (albeit without a space, obviously, since that is not possible)
The variable in question does not even contain 4294967295 but 40000000000.
If I proceed with removing the trailing space then the message is correct: RRD maximum for Data Source 'traffic_out' should be '40000000000' ... /usr/bin/rrdtool tune /srv/www/vhosts/cacti/cacti/rra/9/437.rrd --maximum traffic_out:40000000000
That is correct since the actual RRD contents are this: