Ad Widget

Collapse

it says "Apache is not running on {HOSTNAME}" but it is running

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • walterg74
    Junior Member
    • Aug 2007
    • 14

    #16
    Originally posted by iYRe
    Then this
    Should read:


    If the process isnt called apache2, then it wont be able to find it. The httpd process is usually apache 1.3, and not apache2 btw.
    ??? Maybe if you install through a package or something, we have several 2.0.54 and 2.0.58 apaches and the process is still httpd....

    Besides, I'm kinda dumb but not THAT dumb, the item has httpd as a parameter (and also, I'm testing this localy entering the parameter manually as well...)

    Comment

    • iYRe
      Junior Member
      • Jul 2007
      • 4

      #17
      Well, I dont know whether you are dumb or not :P But you gotta start at the lowest common denominator.

      But, I cant help any further, its beyond me.

      Comment

      • chakatz
        Junior Member
        • Nov 2007
        • 4

        #18
        Originally posted by walterg74
        I tried to run locally a test, such as: zabbix_agentd -t num.proc[httpd] and it returns 0 !!
        What could be wrong???
        Try zabbix_agentd -t proc.num[httpd]

        (Switch around the "proc" and the "num")

        I'm kind of new to this but "num.proc" doesn't seem to exist and several of the commands in this thread that didn't work used that.
        Last edited by chakatz; 05-12-2007, 14:00.

        Comment

        Working...