item_prototypes.png
items.png
[ZBX-4376] Quoted spec symbols in lld via proxy Created: 2011 Nov 22 Updated: 2017 May 30 Resolved: 2012 Feb 21 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 1.9.8 (beta) |
| Fix Version/s: | 1.8.10, 1.9.9 (beta) |
| Type: | Incident report | Priority: | Blocker |
| Reporter: | Alexey Pustovalov | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | trivial | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
item_prototypes.png
items.png
|
| Description |
|
24917:20111122:233650.539 In DCmass_proxy_add_history() "{#SNMPVALUE}":"GigabitEthernet0 /10"}, { "{#SNMPINDEX} ":10111, ":"GigabitEthernet0 and we have incorrect item key in zabbix server. Ex.: |
| Comments |
| Comment by Alexander Vladishev [ 2011 Nov 30 ] |
|
It's normal. All low level discovery data is stored and processed in JSON format. Slashes (/) in JSON strings should be escaped. (www.json.org) Please attach a screenshot, if you have a problem with LLD. |
| Comment by Alexey Pustovalov [ 2011 Dec 01 ] |
|
screenshots |
| Comment by Alexander Vladishev [ 2011 Dec 01 ] |
|
What database you are using on server and proxy side? |
| Comment by Alexander Vladishev [ 2011 Dec 01 ] |
|
Confirmed, when using mysql on proxy side. |
| Comment by Alexander Vladishev [ 2011 Dec 01 ] |
|
Could repeat only once. After setting additional debug-information in the code and compilation of a proxy the problem hasn't repeated. Try to recompile a proxy too using these commands: ./bootstrap.sh |
| Comment by Alexey Pustovalov [ 2011 Dec 01 ] |
|
problem remains with last trunk proxy on PostgreSQL. |
| Comment by Alexey Pustovalov [ 2011 Dec 01 ] |
|
on debian with mysql the problem hasn't repeated. |
| Comment by Alexander Vladishev [ 2011 Dec 01 ] |
|
Fixed in the development branch svn://svn.zabbix.com/branches/dev/ZBX-4376 |
| Comment by Alexey Pustovalov [ 2011 Dec 01 ] |
|
working. Thanks |
| Comment by dimir [ 2011 Dec 01 ] |
|
Do we really want to "set standard_conforming_strings to off;" ? |
| Comment by Alexander Vladishev [ 2011 Dec 01 ] |
|
You are right! It is the bad idea. In version PostgreSQL 8.1 this variable only for reading. I re-open this problem for finishing. |
| Comment by Alexander Vladishev [ 2011 Dec 01 ] |
|
Has been fixed by another way. Please retest r23707. |
| Comment by dimir [ 2011 Dec 02 ] |
|
I like it! |
| Comment by Alexander Vladishev [ 2011 Dec 02 ] |
|
Fixed in version pre-1.9.9, revision 23728. Backported to pre-1.8.10, revision 23729. |
| Comment by richlv [ 2014 Jan 30 ] |
|
note that json standard does not require escaping of slashes (only doublequotes and backslashes). from http://www.ietf.org/rfc/rfc4627.txt : "All Unicode characters may be placed within the quotation marks except for the characters that must be escaped: quotation mark, reverse solidus, and the control characters (U+0000 through U+001F)."
|
