Ad Widget

Collapse

[Z3003] no connection to the database

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • pbbunny
    Junior Member
    • Jan 2015
    • 2

    #1

    [Z3003] no connection to the database

    I'm getting the following error when running a discovery rule:

    30581:20150113:121732.808 [Z3003] no connection to the database
    30581:20150113:121732.808 invalid discovery rule ID [23682]

    I'm trying to perform a Simple Check icmpping within the host's Discovery Rules. The rule is only set to send 5 packets, all other settings are set to default/blank. When the discovery rule is set to enable, the zabbix_server.log would show the above error message repeatedly until I disable the rule again. The database is local and is accessible, and all other items and hosts are working and polling accordingly. The only other observation I have is that this is only happening on the network on the secondary interface of the zabbix server. I can directly ping and connect to services of other hosts from the OS level using the secondary interface, but the zabbix server doesn't seem to recognize this and is giving the above error.
  • ingus.vilnis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Mar 2014
    • 908

    #2
    Hi,

    Not sure, but just for a test you can check and try to disable your SELinux settings.
    Code:
    setenforce 0
    If your discovery works after that, try to figure out how to bypass the check through SELinux.

    Best Regards,
    Ingus

    Comment

    • pbbunny
      Junior Member
      • Jan 2015
      • 2

      #3
      Hi Ingus, SELinux is disabled on both the zabbix server and the host.

      [root@CentOS zabbix]# setenforce --help
      setenforce: SELinux is disabled

      I have found that the Discovery rules under Configuration > Hosts and then creating a Discovery Rules within the Hosts setting is the one that's not working and is potentially triggering the error message on the log. When I create a Discovery rule under Configuration, it works, and is able to perform the discovery action.

      Comment

      Working...