Ad Widget

Collapse

Jabber notifications debugging?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • k.rink
    Junior Member
    • Sep 2015
    • 1

    #1

    Jabber notifications debugging?

    Folks;

    slowly starting into zabbix 2.4.6, I fail pretty early by trying to set up notifications via Jabber. Setup: We use zabbix as well as an openfire 2.x XMPP server in a local network. There's a DNS SRV entry for the XMPP server, and there is a user that can send messages through. Using sendxmpp (command line) as well as some other clients works pretty well, however in zabbix XMPP notifications will fail. Messages off the zabbix server log in debug mode:

    Code:
      7195:20150907:132546.304 JABBER: In lookup_jabber() server:'www.xxxxx.eu' port:5222
      7195:20150907:132546.305 JABBER: End of lookup_jabber() real_server:'www.xxxxx.eu' real_port:5222
      [...]
      7195:20150907:132546.403 JABBER: End of disconnect_jabber()
      7195:20150907:132546.403 JABBER: [[email protected]] sasl authentication failed
    I am unsure where to look for help, next. There doesn't seem to be more output than that, and likewise I do not see any other configuration options for XMPP. So to ask:

    - Does that message make sense to anyone? Any help on that?

    - Is there a documented way of including external scripts such as sendxmpp into zabbix 2.4.x? I found some solutions to that on the 'net but none of them seemed to work for me, and in order to debug them, I failed to actually find out which arguments zabbix provides to the script, or how the user name and message gets in there.

    - Is there a general way on how to debug notifications in zabbix? Sending out e-mails also doesn't work for me, but unlike XMPP (where at least I see the dump posted above when in debug mode), e-mail just quietly fails without producing any output (on zabbix), and (on the MX) I can't see any attempts of zabbix host connecting...

    Many thanks in advance and all the best,
    Kristian
  • jamesNJ
    Senior Member
    • Jun 2015
    • 103

    #2
    For debugging, make sure the script can be run by the zabbix user, and it will help to write debug data to an external file which is writable by user zabbix (/tmp is usually a convenient area).

    A common issue is with a script getting fed parameters that contain spaces, and then the script seeing these as separate parameters. For example an e-mail subject line usually includes spaces, but if not escaped properly an action script could see that subject as a series of separate parameters.

    Comment

    Working...