Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-2911

Network map titles corruption with PostgreSQL, DM and non-ASCII characters

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Major Major
    • 1.8.5
    • 1.8.3
    • Server (S)
    • None
    • CentOS 5.5, PostgreSQL 8.4.4, Zabbix 1.8.3.

      ???????? ?????????????? ????????. ??????????? ?? ??????-. ????? ????? ???? ??????????? ????. ??????? ? ???????? ???? ?? ??????? ?????. ???????? ?????. ???????? ????? ?? ????????. ??????? ????? ??????????, ????????, "??????" ???????????? ? "???".
      ???????? ??????? ? ?????????????, ??????????, ???????? UTF8 ? ?????? Zabbix + Postgres.

      8546:20100819:110333.221 NODE 2: Received history from node 3 for node 3 datalen 1010
      28546:20100819:110333.247 NODE 2: Received history_uint from node 3 for node 3 datalen 398
      28546:20100819:110345.214 NODE 2: Received configuration changes from slave node 3 for node 3 datalen 464
      28546:20100819:110345.300 [Z3005] Query failed: [0] PGRES_FATAL_ERROR:ERROR: invalid byte sequence for encoding "UTF8": 0xd027
      HINT: This error can also happen if the byte sequence does not match the encoding expected by the server, which is controlled by "client_encoding".
      [update sysmaps set name='???' where sysmapid=300200000000001;
      update sysmaps_elements set label='?????' where selementid=300200000000001;
      update user_history set title1='S_CONFIGURATION_OF_NETWORK_MAPS',url1='sys map.php?sysmapid=300200000000001' where userhistoryid=300300000000001;
      ]
      28546:20100819:110347.994 NODE 2: Sending configuration changes to slave node 3 for node 3 datalen 48
      28550:20100819:110352.859 NODE 2: Received history from node 3 for node 3 datalen 1840
      28550:20100819:110352.926 NODE 2: Received history_uint from node 3 for node 3 datalen 945

            Unassigned Unassigned
            sire Sergey Syreskin
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: