Ad Widget

Collapse

failed to update local proxy configuration copy: invalid table name "item_rtdata"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • miroslav
    Junior Member
    • Oct 2019
    • 4

    #1

    failed to update local proxy configuration copy: invalid table name "item_rtdata"

    Hi everyone,
    I am practically new to zabbix. We hve a template VM we use for proxy cloning it as needed. This one was copied over to a different ESX host. It worked for maybe 30 seconds and then stopped. Tried few things, but no idea how t fix it.

    6427:20191015:123729.623 Starting Zabbix Proxy (active) [PROXY-NAME]. Zabbix 4.2.7 (revision 624fb7497b).
    6427:20191015:123729.623 **** Enabled features ****
    6427:20191015:123729.623 SNMP monitoring: YES
    6427:20191015:123729.623 IPMI monitoring: YES
    6427:20191015:123729.623 Web monitoring: YES
    6427:20191015:123729.623 VMware monitoring: YES
    6427:20191015:123729.623 ODBC: YES
    6427:20191015:123729.623 SSH2 support: YES
    6427:20191015:123729.623 IPv6 support: YES
    6427:20191015:123729.623 TLS support: YES
    6427:20191015:123729.623 **************************
    6427:20191015:123729.624 using configuration file: /etc/zabbix/zabbix_proxy.conf
    6427:20191015:123729.636 current database version (mandatory/optional): 04020000/04020001
    6427:20191015:123729.636 required mandatory version: 04020000
    6427:20191015:123729.652 proxy #0 started [main process]
    6444:20191015:123729.670 proxy #13 started [poller #1]
    6446:20191015:123729.680 proxy #15 started [poller #3]
    6447:20191015:123729.691 proxy #16 started [poller #4]
    6445:20191015:123729.702 proxy #14 started [poller #2]
    6441:20191015:123729.713 proxy #10 started [history syncer #4]
    6436:20191015:123729.714 proxy #5 started [http poller #1]
    6437:20191015:123729.715 proxy #6 started [discoverer #1]
    6432:20191015:123729.725 proxy #1 started [configuration syncer #1]
    6433:20191015:123729.730 proxy #2 started [heartbeat sender #1]
    6434:20191015:123729.735 proxy #3 started [data sender #1]
    6438:20191015:123729.739 proxy #7 started [history syncer #1]
    6439:20191015:123729.740 proxy #8 started [history syncer #2]
    6440:20191015:123729.740 proxy #9 started [history syncer #3]
    6443:20191015:123729.741 proxy #12 started [task manager #1]
    6435:20191015:123729.743 proxy #4 started [housekeeper #1]
    6442:20191015:123729.743 proxy #11 started [self-monitoring #1]
    6448:20191015:123729.744 proxy #17 started [poller #5]
    6449:20191015:123729.755 proxy #18 started [unreachable poller #1]
    6450:20191015:123729.766 proxy #19 started [trapper #1]
    6453:20191015:123729.769 proxy #22 started [trapper #4]
    6456:20191015:123729.771 proxy #25 started [preprocessing manager #1]
    6455:20191015:123729.772 proxy #24 started [icmp pinger #1]
    6451:20191015:123729.772 proxy #20 started [trapper #2]
    6454:20191015:123729.775 proxy #23 started [trapper #5]
    6452:20191015:123729.777 proxy #21 started [trapper #3]
    6432:20191015:123729.828 received configuration data from server at "1.2.3.4", datalen 7403
    6432:20191015:123729.846 failed to update local proxy configuration copy: invalid table name "item_rtdata"
    6459:20191015:123730.078 proxy #28 started [preprocessing worker #3]
    6457:20191015:123730.174 proxy #26 started [preprocessing worker #1]
    6458:20191015:123730.174 proxy #27 started [preprocessing worker #2]

    I have tried removing the database and creating from scratch, re-importing schema everything. It always ends up the same. Any ideas? Thanks for your help in advance.
    Last edited by miroslav; 15-10-2019, 07:48.
  • storyteller
    Junior Member
    • Oct 2019
    • 23

    #2
    Hello,
    At first site, you have a database schema for a different zabbix version.

    Comment

    • miroslav
      Junior Member
      • Oct 2019
      • 4

      #3
      HI,
      How can you tell? I can see proxy version 4.2.7, but that's it.

      Comment

      • storyteller
        Junior Member
        • Oct 2019
        • 23

        #4
        Drop database and do it with schema for proxy version 4.2.7

        Comment

        • miroslav
          Junior Member
          • Oct 2019
          • 4

          #5
          Ok, i've dropped the db and recreated it using:
          create database zabbixproxy character set utf8 collate utf8_bin;

          Then i've imported schema:
          zcat /usr/share/doc/zabbix-proxy-mysql-4.2.7/schema.sql.gz | mysql -u zabbix -p zabbixproxy

          And i still get the same error:

          8553:20191017:164829.017 Starting Zabbix Proxy (active) [NAME]. Zabbix 4.2.7 (revision 624fb7497b).
          8553:20191017:164829.017 **** Enabled features ****
          8553:20191017:164829.017 SNMP monitoring: YES
          8553:20191017:164829.017 IPMI monitoring: YES
          8553:20191017:164829.017 Web monitoring: YES
          8553:20191017:164829.017 VMware monitoring: YES
          8553:20191017:164829.018 ODBC: YES
          8553:20191017:164829.018 SSH2 support: YES
          8553:20191017:164829.018 IPv6 support: YES
          8553:20191017:164829.018 TLS support: YES
          8553:20191017:164829.018 **************************
          8553:20191017:164829.018 using configuration file: /etc/zabbix/zabbix_proxy.conf
          8553:20191017:164829.030 current database version (mandatory/optional): 04020000/04020001
          8553:20191017:164829.030 required mandatory version: 04020000
          8553:20191017:164829.045 proxy #0 started [main process]
          8570:20191017:164829.061 proxy #13 started [poller #1]
          8572:20191017:164829.071 proxy #15 started [poller #3]
          8573:20191017:164829.082 proxy #16 started [poller #4]
          8571:20191017:164829.093 proxy #14 started [poller #2]
          8567:20191017:164829.104 proxy #10 started [history syncer #4]
          8562:20191017:164829.105 proxy #5 started [http poller #1]
          8563:20191017:164829.106 proxy #6 started [discoverer #1]
          8558:20191017:164829.116 proxy #1 started [configuration syncer #1]
          8559:20191017:164829.121 proxy #2 started [heartbeat sender #1]
          8560:20191017:164829.126 proxy #3 started [data sender #1]
          8564:20191017:164829.131 proxy #7 started [history syncer #1]
          8565:20191017:164829.131 proxy #8 started [history syncer #2]
          8566:20191017:164829.132 proxy #9 started [history syncer #3]
          8569:20191017:164829.132 proxy #12 started [task manager #1]
          8574:20191017:164829.137 proxy #17 started [poller #5]
          8561:20191017:164829.147 proxy #4 started [housekeeper #1]
          8568:20191017:164829.148 proxy #11 started [self-monitoring #1]
          8575:20191017:164829.149 proxy #18 started [unreachable poller #1]
          8579:20191017:164829.161 proxy #22 started [trapper #4]
          8582:20191017:164829.163 proxy #25 started [preprocessing manager #1]
          8581:20191017:164829.164 proxy #24 started [icmp pinger #1]
          8576:20191017:164829.164 proxy #19 started [trapper #1]
          8577:20191017:164829.167 proxy #20 started [trapper #2]
          8580:20191017:164829.170 proxy #23 started [trapper #5]
          8578:20191017:164829.172 proxy #21 started [trapper #3]
          8558:20191017:164829.276 received configuration data from server at "x.x.x.x", datalen 7403
          8558:20191017:164829.282 failed to update local proxy configuration copy: invalid table name "item_rtdata"
          8585:20191017:164830.074 proxy #28 started [preprocessing worker #3]
          8584:20191017:164830.168 proxy #27 started [preprocessing worker #2]
          8583:20191017:164830.168 proxy #26 started [preprocessing worker #1]
          [root@ZABBIX-PROXY ~]#

          Our Zabbix server is version 4.4, but proxy is the latest at 4.2.7.
          Last edited by miroslav; 17-10-2019, 23:48.

          Comment

          • Atsushi
            Senior Member
            • Aug 2013
            • 2028

            #6
            Please use the same major version of Zabbix server and Zabbix proxy. Different major versions of servers and proxies will not work properly. If the Zabbix server version you are using is 4.4, use Zabbix proxy version 4.4 as well.

            Comment

            • miroslav
              Junior Member
              • Oct 2019
              • 4

              #7
              Ok, thanks. That fixed it.

              Comment

              Working...