Last week we enabled cbpolicy in our two server Zimbra 7.1.4 running under CentOS 5.8 x64.
We had to do some investigation and trying since we coudn't find more information about enabling cbpolicy in a multi-server install, but finally (we thought) we got it.
The morning right after the install Zimbra was not working, and we discovered it was due to the rotation of logs and restart of the server that is done everynight.

Testing since then we discovered that cbpolicyd is unable to start after one other start and stop. I mean, if works ok starting from a stopped server or from a complete reboot of the system, but once it has been 'up and runing' if it's stopped it won't start any more and Zimbra will stop delivering mail.

We have another development zimbra server working perfect, but it's a single server install.

To install in the two server environment we had to install an Apache web server on the SMTP in order to been able to use the webui to configure the policies for the cbpolicyd.

On a failed start logs don't show much:

zmconfigd.log:
2012-10-29 04:20:23,489 zmconfigd WARNING [3839-SIGTERM handler] Shutting down. Received signal 15
2012-10-29 04:21:01,197 zmconfigd CRITICAL [17550-MainThread] zmconfigd started on smtp.cac.com.es with loglevel=3 pid=17550
2012-10-29 04:21:01,233 zmconfigd WARNING [17550-MainThread] Fetching All configs
2012-10-29 04:21:04,150 zmconfigd WARNING [17550-MainThread] All configs fetched in 2.92 seconds
2012-10-29 04:21:05,562 zmconfigd WARNING [17550-rewrites] Rewrote: /opt/zimbra/cyrus-sasl-2.1.23.3z/etc/saslauthd.conf with mode 440 (0.04 sec)
2012-10-29 04:21:05,757 zmconfigd WARNING [17550-rewrites] Rewrote: /opt/zimbra/conf/mta_milter_options with mode 440 (0.19 sec)
2012-10-29 04:21:05,819 zmconfigd WARNING [17550-rewrites] Rewrote: /opt/zimbra/postfix/conf/master.cf with mode 440 (0.06 sec)
2012-10-29 04:21:05,855 zmconfigd WARNING [17550-rewrites] Rewrote: /opt/zimbra/conf/postfix_header_checks with mode 440 (0.04 sec)
2012-10-29 04:21:06,197 zmconfigd WARNING [17550-rewrites] Rewrote: /opt/zimbra/conf/stats.conf with mode 440 (0.34 sec)
2012-10-29 04:21:06,299 zmconfigd WARNING [17550-rewrites] Rewrote: /opt/zimbra/conf/cbpolicyd.conf with mode 440 (0.10 sec)
2012-10-29 04:21:06,802 zmconfigd WARNING [17550-rewrites] Rewrote: /opt/zimbra/conf/amavisd.conf with mode 440 (0.50 sec)
2012-10-29 04:21:09,244 zmconfigd WARNING [17550-MainThread] All rewrite threads completed in 3.77 sec
2012-10-29 04:21:09,249 zmconfigd WARNING [17550-MainThread] All restarts completed in 0.00 sec
2012-10-29 04:22:09,413 zmconfigd WARNING [17550-MainThread] Fetching All configs
2012-10-29 04:22:10,437 zmconfigd WARNING [17550-MainThread] All configs fetched in 1.02 seconds
2012-10-29 04:22:11,240 zmconfigd ERROR [17550-MainThread] Executed: /opt/zimbra/bin/zmcbpolicydctl status norewrite returned 1 (24 - 13) (0.44 sec)
2012-10-29 04:22:11,242 zmconfigd CRITICAL [17550-MainThread] Tracking service cbpolicyd
2012-10-29 04:22:12,540 zmconfigd CRITICAL [17550-MainThread] Tracking service mta
2012-10-29 04:22:12,542 zmconfigd WARNING [17550-MainThread] Watchdog: service mta now available for watchdog.
2012-10-29 04:22:12,717 zmconfigd CRITICAL [17550-MainThread] Tracking service sasl
2012-10-29 04:22:12,720 zmconfigd WARNING [17550-MainThread] Watchdog: service sasl now available for watchdog.
2012-10-29 04:22:12,805 zmconfigd CRITICAL [17550-MainThread] Tracking service snmp
2012-10-29 04:22:12,808 zmconfigd WARNING [17550-MainThread] Watchdog: service snmp now available for watchdog.
2012-10-29 04:22:13,385 zmconfigd CRITICAL [17550-MainThread] Tracking service stats
2012-10-29 04:22:13,388 zmconfigd WARNING [17550-MainThread] Watchdog: service stats now available for watchdog.
2012-10-29 04:22:13,390 zmconfigd WARNING [17550-MainThread] Watchdog: skipping service antivirus. Service not yet available for restarts.
2012-10-29 04:22:13,756 zmconfigd WARNING [17550-MainThread] All rewrite threads completed in 0.00 sec
2012-10-29 04:22:13,757 zmconfigd WARNING [17550-MainThread] All restarts completed in 0.00 sec

cbpolicyd.log:
[2012/10/29-04:20:27 - 4992] [CORE] NOTICE: 2012/10/29-04:20:27 Server closing!
[2012/10/29-04:21:34 - 17899] [CORE] NOTICE: Process Backgrounded
[2012/10/29-04:21:34 - 17899] [CORE] ERROR: 2012/10/29-04:21:34 Pid_file "/opt/zimbra/log/cbpolicyd.pid" not created.
[2012/10/29-04:21:34 - 17899] [CORE] NOTICE: 2012/10/29-04:21:34 Server closing!

We have been testing about cbpolicyd.pid permissions, and its parent folder with no change. We have also been messing with 'apache' permissions on those files, since this is the user that runs the webserver. We tried also with the serverver on and off,... After one week we have run out of ideas.

If you need it y can also submit the installation and configuration process of the cbpolicy.

Any help or ideas will be greatly appreciated. Thanks a lot.