Ad Widget

Collapse

AJAX request error creating discovery rule check

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jmusbach
    Member
    • Sep 2013
    • 37

    #1

    AJAX request error creating discovery rule check

    Hello, I am trying to setup a install of Zabbix 2.0.8 and as a part of that would like to create some discovery rules to import new hosts that have gotten the agent installed on them. However I have hit a road block in doing so as in adding a check condition for the discovery rule I get a AJAX request error. The values I'm submitting for the check are:

    Check type: ZABBIX agent
    Port range: 10050
    Key: System.hostname

    The Chrome javascript console outputs this possibly related error:

    Code:
    POST http://<box>.<us>.com/zabbix/jsrpc.php?output=json-rpc jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:1435
    Ajax.Request.Class.create.request jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:1435
    Ajax.Request.Class.create.initialize jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:1399
    (anonymous function) jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:338
    klass jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:92
    RPC.Call.Class.create.call jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:7022
    RPC.Call.Class.create.initialize jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:6992
    (anonymous function) jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:338
    klass jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1:92
    checker.check jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1&files[]=servercheck.js:45
    checkStatus jsLoader.php?ver=2.0.8&lang=en_GB&showGuiMessaging =1&files[]=servercheck.js:76
    Any idea what could cause this or what I'm doing wrong? Or perhaps how to debug this in more detail? Thanks.
    Last edited by jmusbach; 01-10-2013, 01:50.
  • jmusbach
    Member
    • Sep 2013
    • 37

    #2
    I solved my problem, turns out it was a issue with the apache/php build that was causing warnings to be printed and those seemed to cause the ajax request to error out. Once those warnings were resolved the ajax requests succeeded.

    Comment

    Working...