Ad Widget

Collapse

UserParameter don't work? Or I do it wrong :)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • lippoliv
    Junior Member
    • Oct 2011
    • 15

    #1

    UserParameter don't work? Or I do it wrong :)

    Hey there,
    I'am really new to Zabbix.

    I have 2 Servers. One "big" and one really small who's just tracking the big ones performace

    Now I would like to track an running screen-process, so i Added to the big server in the zabbix_agentd.conf the line
    Code:
    UserParameter=screen.num[*], screen -list | grep -c $1
    Then on the small server in ZAbbix I added an Item to the big server
    Code:
    screen.num[minecraft_server]
    But it didn't work. Allways it is returning 0. I also can't choose the item, i have to type it on my own.

    For Tutorial I have chosen this one : http://www.zabbix.com/documentation/...ser_parameters

    What did I do wrong?
    Thanks for your time
  • Colttt
    Senior Member
    Zabbix Certified Specialist
    • Mar 2009
    • 878

    #2
    try this (without blanks):
    Code:
    UserParameter=screen.num[*],screen -list | grep -c $1
    Debian-User

    Sorry for my bad english

    Comment

    • lippoliv
      Junior Member
      • Oct 2011
      • 15

      #3
      Hey There...

      Code:
      UserParameter=screen.num[*],screen -list|grep -c $1
      this even don't work :/

      any ideas? I start to love Zabbix, but this has to work...

      Comment

      • Colttt
        Senior Member
        Zabbix Certified Specialist
        • Mar 2009
        • 878

        #4
        hello,

        ehm would it work direct in the shell??
        screen -list|grep -c minecraft_server
        Debian-User

        Sorry for my bad english

        Comment

        • lippoliv
          Junior Member
          • Oct 2011
          • 15

          #5
          of course it displays a 1.

          thats why i'am asking here ...

          Comment

          • Colttt
            Senior Member
            Zabbix Certified Specialist
            • Mar 2009
            • 878

            #6
            ok, so change the log level to debug(4) and take a look into the log-files..

            tomorrow i will check this in my enviroment..
            Debian-User

            Sorry for my bad english

            Comment

            Working...