Ad Widget

Collapse

simple check tcp,10000 not working in beta5

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Mark Rijckenberg
    Junior Member
    • Jan 2006
    • 3

    #1

    simple check tcp,10000 not working in beta5

    Hi all,

    I have the following problem on a MEPIS Debian desktop pc (Linux mepis1 2.6.12-1-586tsc #1 Sat Oct 29 08:01:24 EDT 2005 i686 GNU/Linux)

    I am using kernel 2.6.12, Apache 2, MySQL 5 and PHP 5.

    All simple checks work, except the tcp,port (port=10000) simple check. The check displays a working graph, where the data value remains 0, but should be 1. I tested this both at work on a different MEPIS pc and on my home PC. Both give the same problem. Can someone show me a working item configuration where tcp,port works? I must be using the tcp,port check incorrectly, but have no clue why. The server is listening on port 10050. (listening on default 10051 gives same problem) Do I have to use PHP 4 instead?

    My item config looks like this:

    CONFIGURATION OF ITEMS Group Host
    Id Key Description Update interval History Trends Type Status Error Actions

    17223 icmppingsec icmppingsec 30 90 365 Simple check Active Change
    17249 tcp,10000 tcp,10000 30 90 365 Simple check Active Change
    17248 tcp,3306 tcp,3306 30 90 365 Simple check Active Change

    Thanks for any possible help,

    Regards,

    Mark
  • Mark Rijckenberg
    Junior Member
    • Jan 2006
    • 3

    #2
    issue 'solved' by using Debian binaries + PHP4 instead of PHP5

    Hi all,

    I 'solved' the tcp,port issue by using the Debian precompiled Zabbix binaries (v1.1alpha7 I believe) and by removing PHP5 from my PC and using PHP4 instead. Apparently, PHP5 is not yet entirely compatible with Zabbix.

    I would love to see the Zabbix beta5 source .tar.gz fully work on my Debian-based Linux pc, but the tcp,port simple check fails when compiling Zabbix from source.

    Does anyone have a better solution than downgrading Zabbix?

    Regards,

    Mark

    Comment

    • Alexei
      Founder, CEO
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2004
      • 5654

      #3
      Use net.tcp.port[<ip>,port]. For example: net.tcp.port[,23].
      Alexei Vladishev
      Creator of Zabbix, Product manager
      New York | Tokyo | Riga
      My Twitter

      Comment

      • jamkad
        Junior Member
        • Sep 2005
        • 27

        #4
        net.tcp.port[<ip>,port] does not work with windows agents
        and it is not working as simple check either. Am i right?
        ...or atleast i didn't get it to work.

        So is there any way to monitor ports on windows server with b5?

        Comment

        Working...