Ad Widget

Collapse

tile data model service has not been started notifications

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • conehead
    Junior Member
    • Nov 2019
    • 9

    #1

    tile data model service has not been started notifications

    Hi,
    I migrated from zabbix 6 lts to 7 and now i am getting the errors that the tile data model server is not running. When i look at te configuration of the inherited macro's for that specific host i see that it should ignore the folowing services.

    HTML Code:
    ^(?:RemoteRegistry|MMCSS|gupdate|clr_optimization_ v.+|sppsvc|gpsvc|MapsBroker|IntelAudioService|Inte l\(R\) TPM Provisioning Service|dbupdate|DoSvc|CDPUserSvc_.+|WpnUserServic e_.+|OneSyncSvc_.+|WbioSrvc|BITS|GISvc|ShellHWDete ction|TrustedInstaller|TabletInputService|CDPSvc|w uauserv|Google*|Tile*|til*)$
    I am gone of the Google errors and i even put Tile* and til* just to be sure but the notifications keeps coming for the tile data model. Is there another place i can look?


  • cyber
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2006
    • 4811

    #2
    That item/trigger is already created by discovery. If you now add to macros and discovery runs again, it should mark those items as "not discovered any more" and removes them when "keep lost resources" timer runs out.. it is by default pretty long timeout, like 30d or so...Those should be marked with yellow "!" marker under hosts item config list... But until that happens, they continue to work.
    So you can either set that period to 0, which will remove those lost resources with next discovery, or you can remove related items manually...

    Comment

    • conehead
      Junior Member
      • Nov 2019
      • 9

      #3
      Hi,

      Thanks for the reply, as you mentioned it was indeed the case when i took a closer look that it mentioned that those services were not being discovered in the future but the strange thing was i deleted them en for 4 servers they kepped being retrieved and imediately mentioned that they were not in the discovery anymore and that they will be deleted within 30 days. Since i tried to delete them several times but allways came back after a new discovery for this host i just disabled them. No clue why those services kept being disovered over and over again when they clearly notice that there is a rule not to discover them anymore...

      Comment

      Working...