Ad Widget

Collapse

Postfix & Clamd Templates

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dougs@dawnsign.com
    Junior Member
    • Apr 2015
    • 4

    #1

    Postfix & Clamd Templates

    Recently I upgraded our Zabbix server from 4.4 to 5.0 on FreeBSD 12.2. All of the templates worked fine thereafter except for two. These are the "Template App Postfix" and the "Template App Clamd" templates from which I believe to be the Zabbix Share portal. Are there any templates related to Postfix and clamd that work on Zabbix 5.0 platform?
  • dougs@dawnsign.com
    Junior Member
    • Apr 2015
    • 4

    #2
    Originally posted by cyber
    But fixing, what's not working is not an option?
    I'm not sure I understand. I don't understand why it stopped working. How can I go about troubleshooting the templates? Are there guides/pointers to how one can understand how to modify templates so that these work again?

    Thanks in advance for your help.

    ~Doug

    Comment

    • dougs@dawnsign.com
      Junior Member
      • Apr 2015
      • 4

      #3
      More specifically, the errors basically states that both postfix and clamd services are down. That isn't true as evidenced by this:

      Code:
      [root@mailfilter 27.Jan 2:55pm /var/log]# service clamav-clamd status
      clamav_clamd is running as pid 37088.
      [root@mailfilter 27.Jan 2:55pm /var/log]# service postfix status
      postfix is running as pid 45564.
      [root@mailfilter 27.Jan 2:55pm /var/log]#
      The binary name clamd matches the one in the template trigger description for detection of clamd. i.e.:

      {Template App ClamAVroc.num[clamd].last(0)}=0

      Likewise for the postfix binary:

      {Template App Postfix Serviceroc.num[,postfix].last(0,10)}=0

      These templates worked fine in version 4.4 but aren't in version 5.0. The postfix and clamd binary names remain unchanged.

      What am I missing?

      ~Doug

      Comment

      • dougs@dawnsign.com
        Junior Member
        • Apr 2015
        • 4

        #4
        I figured it out. I needed to enable RootAllow=1 in the agent configuration file. Both these two templates are working fine now.

        ~Doug

        Comment

        • cyber
          Senior Member
          Zabbix Certified SpecialistZabbix Certified Professional
          • Dec 2006
          • 4807

          #5
          But fixing, what's not working is not an option?

          Comment

          Working...