Ad Widget

Collapse

external scripts

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mrmurdock
    Member
    • Aug 2009
    • 85

    #1

    external scripts

    zabbix-1.6.6 - I have created a external script to retrieve the OS version a unix host has (I simply dont want to enter 150 hosts information in a Profile). I have added the item, created the trigger, and added it to the a template (template_aix).
    By hand the script works great, the proper information is returned.
    If I add this external script as a "script" to the zabbix interface (admistration --> scrpts --> add a script), it reads the file, but I see no output from the execution of the script in the GUI popup. the path to the file and file name is correct. The mode to the file is 755.

    Key called os.version[]. Trigger called OS Version and I added to the OS section of the host.
    the external script does a case statement eval of which os is being pulled, and echo's the information either from a simple uname -X for solaris or a "oslevel" for AIX.
  • MrKen
    Senior Member
    • Oct 2008
    • 652

    #2
    If you're using the template_aix, which uses Zabbix agent, why not just use 'system.uname'?

    MrKen
    Disclaimer: All of the above is pure speculation.

    Comment

    • mrmurdock
      Member
      • Aug 2009
      • 85

      #3
      I dont want to have to read backwards and have my end users try to understand.

      # uname -a
      AIX aix240 1 4 004705A04C00

      # oslevel
      4.1.5.0

      Comment

      • mrmurdock
        Member
        • Aug 2009
        • 85

        #4
        Update - I have been able to get Zabbix to read the file from the Server, but, when I go to execute it on other hosts (the ibm as a test case), It still only reads the file from the zabbix serer.
        Also, I cannot get it to add permenantly to the triggers (after I create the OS Version item, it says its available), then try to add a trigger using that item, the eventhough the trigger creatopm says succesfull, its not in the template. Then I check the item, it has reverted back to un-supported.

        Comment

        Working...