Zabbix Jabber alerts and Openfire

sheen · April 22, 2010, 3:13pm

Hi all !

I got issues with Zabbix and Openfire, Zabbix is working like a charm and Openfire too, but it’s impossible to get them working together

Zabbix offers possibility to send alerts throught Email and Jabber, you have to configure a Jabber account for Zabbix, and from this account Zabbix will send alerts to another Jabber account

Zabbix has been compiled with “–with-jabber” flag, and tell me that alerts have been sent to Jabber successfully, but I don’t receive any alert : /

I don’t think that the issue comes from zabbix, because all seems ok when I’m looking to the log.

At the opposite I can see strange think into Openfire debug.log, things like this :

2010.04.22 17:03:20 LdapManager: In LdapManager.checkAuthentication(userDN, password), userDN is: CN=“Zabbix”,OU=“Location”,OU=“Corporate”…
2010.04.22 17:03:20 LdapManager: Created context values, attempting to create context…
2010.04.22 17:03:20 LdapManager: … context created successfully, returning.
2010.04.22 17:03:20 AuthorizationManager: Trying Default Mapping.map(zabbix)
2010.04.22 17:03:20 DefaultAuthorizationMapping: No realm found
2010.04.22 17:03:20 AuthorizationManager: Trying Default Policy.authorize(zabbix , zabbix)
2010.04.22 17:03:20 DefaultAuthorizationPolicy: Checking authenID realm
2010.04.22 17:03:20 LdapManager: Trying to find a user’s DN based on their username. sAMAccountName: zabbix, Base DN: ou=“domain”,dc=“domain”,dc=“local”…
2010.04.22 17:03:20 LdapManager: Creating a DirContext in LdapManager.getContext()…
2010.04.22 17:03:20 LdapManager: Created hashtable with context values, attempting to create context…
2010.04.22 17:03:20 LdapManager: … context created successfully, returning.
2010.04.22 17:03:20 LdapManager: Starting LDAP search…
2010.04.22 17:03:20 LdapManager: … search finished
2010.04.22 17:03:20 LdapManager: Trying to find a user’s DN based on their username. sAMAccountName: zabbix, Base DN: ou=“domain”,dc=“domain”,dc=“local”…
2010.04.22 17:03:20 LdapManager: Creating a DirContext in LdapManager.getContext()…
2010.04.22 17:03:20 LdapManager: Created hashtable with context values, attempting to create context…
2010.04.22 17:03:20 LdapManager: … context created successfully, returning.
2010.04.22 17:03:20 LdapManager: Starting LDAP search…
2010.04.22 17:03:20 LdapManager: … search finished
2010.04.22 17:03:20 LdapManager: Creating a DirContext in LdapManager.getContext()…
2010.04.22 17:03:20 LdapManager: Created hashtable with context values, attempting to create context…
2010.04.22 17:03:20 LdapManager: … context created successfully, returning.
2010.04.22 17:03:20 001735 (01/05/00) - Connection #7 tested: OK
2010.04.22 17:03:20 001736 (01/05/00) - Connection #7 tested: OK
2010.04.22 17:03:20 001736 (01/05/00) - Connection #8 tested: OK
2010.04.22 17:03:20 001737 (01/05/00) - Connection #8 tested: OK
2010.04.22 17:03:20 001737 (01/05/00) - Connection #9 tested: OK
2010.04.22 17:03:20 001738 (01/05/00) - Connection #9 tested: OK
2010.04.22 17:03:20 LocalOutgoingServerSession: OS - Trying to connect to openfire.domain.local:5269(DNS lookup: openfire.domain.local:5269)
2010.04.22 17:03:20 Connect Socket[addr=/127.0.1.1,port=49503,localport=5269]
2010.04.22 17:03:20 LocalOutgoingServerSession: OS - Plain connection to openfire.domain.local:5269 successful
2010.04.22 17:03:20 Connexion clÃ´turÃ©e avant l Ã©tablissement de la session
Socket[addr=/127.0.1.1,port=49503,localport=5269]
2010.04.22 17:03:20 LocalOutgoingServerSession: OS - Going to try connecting using server dialback with: openfire.domain.local
2010.04.22 17:03:20 ServerDialback: OS - Trying to connect to openfire.domain.local:5269(DNS lookup: openfire.domain.local:5269)
2010.04.22 17:03:20 ServerDialback: OS - Connection to openfire.domain.local:5269 successful
2010.04.22 17:03:20 Connect Socket[addr=/127.0.1.1,port=49504,localport=5269]
2010.04.22 17:03:20 ServerDialback: OS - Sent dialback key to host: openfire.domain.local id: 492b7191 from domain: domain.local
2010.04.22 17:03:20 ServerDialback: RS - Received dialback key from host: domain.local to: openfire.domain.local
2010.04.22 17:03:20 ServerDialback: RS - Error, hostname not recognized: openfire.domain.local
2010.04.22 17:03:20 Connexion clÃ´turÃ©e avant l Ã©tablissement de la session
Socket[addr=/127.0.1.1,port=49504,localport=5269]
2010.04.22 17:03:20 ServerDialback: OS - Unexpected answer in validation from: openfire.domain.local id: 492b7191 for domain: domain.local answer:<stream:error xmlns:stream=“http://etherx.jabber.org/streams”></stream:error>
2010.04.22 17:03:20 RoutingTableImpl: Failed to route packet to JID: zabbix@domain.local/ZABBIX packet:

2010.04.22 17:03:20 RoutingTableImpl: Failed to route packet to JID: zabbix@domain.local packet:

2010.04.22 17:03:20 OutgoingSessionPromise: Error sending packet to remote server:

Server7 is unreachable: OK Server7 is unreachable: OK java.lang.Exception: Failed to create connection to remote server at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.sendPa cket(OutgoingSessionPromise.java:252) at org.jivesoftware.openfire.server.OutgoingSessionPromise$PacketsProcessor.run(Ou tgoingSessionPromise.java:216) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java: 886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619)

I don’t understand what’s the problem, Openfire server got a DNS name which is responding in all our local network.

Any ideas please ?

Thanks