Ad Widget

Collapse

Zabbix 3.0.1 | Proxy | Latin1 database

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • phil57
    Junior Member
    • Mar 2016
    • 3

    #1

    Zabbix 3.0.1 | Proxy | Latin1 database

    Hi,

    We are using one Zabbix server with 2 proxies. Some of our checks are in French, so they have accents (mostly é and è).
    Our main database is in Latin1, and our proxies are too. It's how the thing was set up a long long time ago.

    This did not gave us any issues until we recently upgraded from Zabbix 2.4.6 to 3.0.1
    Our main Zabbix server is fine, but our proxies don't work anymore for items having accents in the key. Looking into Mysql, accents are replaced by ? (ex perf_counter["\Disque physique(3 H\?critures disque, octets/s"])

    I've tried several time to recreate correctly the DB on the proxies, but nothing works.
    Proxies with Latin1: accents are replaced with ?
    Proxies with UTF-8: the proxy can't insert the data in the table, so it fails in an even worse way.

    I guess one solution would be to drop the main Zabbix server DB, recreate it in utf-8 and import a dump so that everything is in utf-8. But our db is big (160GB dump), so that's not really a solution.

    As it used to work fine in 2.4 (and earlier), what has changed with Zabbix 3 ?

    Do you have any idea how to fix this issue ?

    Thanks.
  • phil57
    Junior Member
    • Mar 2016
    • 3

    #2
    Nobody has an idea ?

    It has been working randomly these last few days, fine for a few days, then it started producing issues again, then working, ....

    We are currently using latin1 databases, and accents are sometimes replaced by ?
    Attached Files

    Comment

    • phil57
      Junior Member
      • Mar 2016
      • 3

      #3
      This as be fixed in Zabbix 3.0.3

      Comment

      • glebs.ivanovskis
        Senior Member
        • Jul 2015
        • 237

        #4
        Probably was related to this issue.

        Glad to hear that it's working for you again, but anyway, it's a good idea to change encoding of databases to UTF-8. Just in case.

        Comment

        Working...