Ad Widget

Collapse

Zabix 3.2 -> 3.4 import

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • JanCZ
    Junior Member
    • Jan 2018
    • 22

    #1

    Zabix 3.2 -> 3.4 import

    Hello, anyone has idea why iam getting this "error" while trying to import one template to clear zabbix.
    Its from 3.2.2 postgres 9.4 -> 3.4.6 postgres 10.1

    I dont even know where to start troubleshoot since the error message doesn't say much to me
    After this i dont see any new template added or anything, i tried other templates and import worked fine.

    I would attach the export xml itself but its size is bit over the limit here

    Created: Item "Simple Ping" on "Template DWDM".
    Created: Item "DWDM - Loss of frame" on "Template DWDM".
    Created: Item "DWDM - Upload failed" on "Template DWDM".
    Created: Item "DWDM - SES Threshold Exceeded" on "Template DWDM".
    Created: Item "Rx invalid CE VLAN id 15 min threshold exceeded" on "Template DWDM".
    Created: Item "DWDM - Near End Loopback" on "Template DWDM".
    Created: Item "DWDM - Low Received Optical Power" on "Template DWDM".
    Created: Item "DWDM - High Received Optical Power" on "Template DWDM".
    Created: Item "DWDM - FCS Errors Threshold Exceeded" on "Template DWDM".
    Created: Item "Ping in sec" on "Template DWDM".
    Created: Item "DWDM - Far End Loopback Enabled" on "Template DWDM".
    Created: Item "DWDM PM traps" on "Template DWDM".
    Created: Item "DWDM - ES Threshold Exceeded" on "Template DWDM".
    Created: Item "DWDM - Configuration has not been saved" on "Template DWDM".
    Created: Item "DWDM - BBE Threshold Exceeded" on "Template DWDM".
    Created: Item "DWDM - Link up" on "Template DWDM".
    Created: Item "DWDM - Link down" on "Template DWDM".
    Created: Item "Subrack temperature" on "Template DWDM".
    Updated: Item "CPU_utilization" on "CIsco".
    Updated: Item "Simple Ping" on "CIsco".
    Updated: Item "Ping in sec" on "CIsco".
    Incorrect value for field "lifetime": a time unit is expected.
    Last edited by JanCZ; 24-01-2018, 16:58.
  • JanCZ
    Junior Member
    • Jan 2018
    • 22

    #2
    The error was that fore some reason one of values in lifetime was .1 instead of 1...but since zabbix was complaining about time unit it self, and 3.4 uses 1d instead of simply 1 as in 3.2, we thought thats the issue and simply added "d". It started to produce another errors. Mabye it would be worth it to have "invalid value" instead of "invalid unit" which is actually really the difference between 3.2 and 3.4 exported XML. And 3.4 dont care about it, and simply import it even without "proper unit".

    Well, for future.

    Comment

    Working...