Ad Widget

Collapse

ldap simple check fails in 4.0 -worked fine in 3.4

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • albatrosdk
    Junior Member
    • Mar 2018
    • 11

    #1

    ldap simple check fails in 4.0 -worked fine in 3.4

    Quite odd, I copied the database into a new 4.0.5 installation and everything is working fine except that it says that LDAP is not running on a LDAP server we have. I know for a fact that the server hasn't been touched, so what's going on?

    This is the expression used in the trigger: {Template App LDAP Service:net.tcp.service[ldap].max(#3)}=0

    There are no macros defined or anything else. If I ldapsearch to the LDAP server on port 389 it replies.:

    [root@pc543 ~]# ldapsearch -x -h ldapserver.nodomain.com
    # extended LDIF
    #
    # LDAPv3
    # base <> (default) with scope subtree
    # filter: (objectclass=*)
    # requesting: ALL
    #

    # search result
    search: 2
    result: 32 No such object

    # numResponses: 1
    [root@pc543 ~]#

    So, has anything changed in the ldap simple check?

    Thanks

    /A
    Last edited by albatrosdk; 07-03-2019, 09:23. Reason: nothing..
  • albatrosdk
    Junior Member
    • Mar 2018
    • 11

    #2
    Fixed. It was SELinux that blocked zabbix-server from accessing the network:

    [root@pc543 zabbix]# getsebool -a |grep zabbix
    httpd_can_connect_zabbix --> on
    zabbix_can_network --> off
    zabbix_run_sudo --> off
    [root@pc543 zabbix]# setsebool zabbix_can_network on
    [root@pc543 zabbix]# getsebool -a |grep zabbix
    httpd_can_connect_zabbix --> on
    zabbix_can_network --> on
    zabbix_run_sudo --> off

    /A

    Comment

    Working...