Ad Widget

Collapse

phantom items on templates

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • antik
    Junior Member
    Zabbix Certified Specialist
    • Feb 2015
    • 4

    #1

    phantom items on templates

    Zabbix 2.2.7

    Current issue started after "successful" LLD with missing filesystem filter macro- imagine all detected filesystems like /proc, /sys, /dev, etc. Removed discovery rules from Template OS Linux and can't add them back through other template.

    Error message:
    Code:
    Item prototype "vfs.fs.inode[{#FSNAME},pfree]" already exists on
    "testhost2", inherited from another template.
    Also can't add discovery rules back to Template OS Linux:

    Code:
    Item with key "vfs.fs.size[{#FSNAME},free]" already exists on "Template OS Linux".
    Phantom items on templates?

    In what database table those orphaned items are stored?
    They does not show up in any template.
    Or should I wait 24h after auto-discovery rule removal, so generated items will expire (Keep lost resources period (in days)=1)?
  • ingus.vilnis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Mar 2014
    • 908

    #2
    Hi,

    You can try to set Keep lost resources period (in days)=0 which means the items will be deleted upon next LLD update interval. You can also temporary set it to like 60 seconds so you don't have to wait till text run.

    Then check if the items are removed and try linking the prototype to that other template. Don't dig into cleaning DB tables directly yet.

    Best Regards,
    Ingus

    Comment

    • antik
      Junior Member
      Zabbix Certified Specialist
      • Feb 2015
      • 4

      #3
      "Keep lost resources period (in days)=0" makes no difference because all autodiscovered items does not have association to Template.

      Basically this database got lot's of foreign key errors and I have plan to re-create Zabbix on clean system.

      Current issues are accumulated since Zabbix version 1.6>1.8>2.0>2.2 upgrade with MySQL upgrades.

      Current setup is PostgreSQL now.

      Comment

      Working...