Ad Widget

Collapse

User defined UserParamter not working on all clients

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dernwine
    Junior Member
    • Mar 2010
    • 10

    #1

    User defined UserParamter not working on all clients

    Good morning! (or afternoon as the case may be)

    I am having an issue with a user defined UserParameter that is working on ALL but one client. On the one client that it will not work on the item goes into "Not Supported" mode after a few minutes. I have tried everything I can think of and scoured through the forums for something that might be amiss.

    On the client, the UserParamter looks like:

    UserParameter=MFPAg,ps -ef | grep DomainDaemon | grep -v "grep" | wc -l | awk '{print $1}'

    It works, and returns a value:

    root@xxxxxxxx# ps -ef | grep DomainDaemon | grep -v "grep" | wc -l | awk '{print $1}'
    1

    From the Zabbix server, I can get the value:

    zabbix@lparmon ~ $ zabbix_get -s xx.xx.xx.xx -k MFPAg
    1
    zabbix@lparmon ~ $

    The zabbix server log shows:

    1298:20120601:093323.150 item [QA - MFP:MFPAg] became supported
    1296:20120601:094153.968 item [TEST - MFP:MFPAg] became not supported: Not supported by Zabbix Agent


    This exact key/item/trigger works on several other systems with the same OS level/patch level. Same release of the zabbix server, etc.

    Using following version of zabbix:

    1149:20120531:105137.594 Starting Zabbix Server. Zabbix 1.8.13 (revision 27486).
    1149:20120531:105137.594 ****** Enabled features ******
    1149:20120531:105137.594 SNMP monitoring: YES
    1149:20120531:105137.594 IPMI monitoring: NO
    1149:20120531:105137.594 WEB monitoring: YES
    1149:20120531:105137.594 Jabber notifications: NO
    1149:20120531:105137.594 Ez Texting notifications: YES
    1149:20120531:105137.594 ODBC: NO
    1149:20120531:105137.594 SSH2 support: NO
    1149:20120531:105137.594 IPv6 support: NO
    1149:20120531:105137.594 ******************************


    Any insight into how I can narrow down this issue further?


    Thanks in advance,
  • GArmao
    Zabbix Certified Specialist
    Zabbix Certified Trainer
    Zabbix Certified Specialist
    • Mar 2010
    • 135

    #2
    try enabling debug logging (Debug=4) on the zabbix agent for the server that's giving you the issue, it may give you more information on what's going on.

    Comment

    • dernwine
      Junior Member
      • Mar 2010
      • 10

      #3
      Resolved - No idea why except possible user error

      I removed the server from zabbix, and all associated groups. Then I reinstalled ther server, restarted the zabbix agents/daemons.

      Everything now works.

      Thanks for everyones input

      Comment

      • flako
        Member
        • Sep 2011
        • 40

        #4
        Originally posted by dernwine
        Everything now works.
        Hello, just in case .. did not know him, you can do the same with the item proc.num [DomainDaemon] and you use UserParameter nows on all clients.

        Greetings.

        Comment

        Working...