1 Topic by bjmc (edited by bjmc 2014-04-29 10:54:15)

  • bjmc
  • Member
  • Offline
  • Registered: 2014-04-29
  • Posts: 2

Topic: cbpolicyd drives load way up

======== Required information ====
- iRedMail version: 0.8.6
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL
- Linux/BSD distribution name and version: CentOS release 6.5 (Final) Linux 2.6.32-042stab084.14
- Related log if you're reporting an issue:
====

I believe this might be a duplicate of http://www.iredmail.org/forum/topic4983 … 0-cpu.html

Notice that load is low (0.00) until I start cbpolicyd, but it just keeps going up and up until I stop the daemon again. This is running on a VPS under Virtuozzo.

[bjmc@mail ~]$ uptime
 22:45:41 up 18 min,  1 user,  load average: 0.00, 0.68, 1.02
[bjmc@mail ~]$ sudo service cbpolicyd start
[sudo] password for bjmc: 
Starting cbpolicyd:                                        [  OK  ]
[bjmc@mail ~]$ uptime
 22:48:05 up 20 min,  1 user,  load average: 1.80, 0.91, 1.03
[bjmc@mail ~]$ sudo service cbpolicyd stop
Shutting down cbpolicyd:                                   [  OK  ]
[bjmc@mail ~]$ uptime
 22:49:26 up 22 min,  1 user,  load average: 0.54, 0.73, 0.96

Any suggestions you can give would be greatly appreciated. Thanks.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by bjmc (edited by bjmc 2014-04-29 11:28:30)

  • bjmc
  • Member
  • Offline
  • Registered: 2014-04-29
  • Posts: 2

Re: cbpolicyd drives load way up

Some more information, this is in /var/log/cbpolicyd.log

Can't connect to data source 'ARRAY(0x267e4f0)' because I can't work out what driver to use (it doesn't seem to contain a 'dbi:driver:' prefix and the DBI_DRIVER env var is not set) at /usr/lib64/policyd-2.0/cbp/dbilayer.pm line 119

Edit:

I was able to solve this by editing /etc/policyd/cluebringer.conf

Initially, it looked like this:

[database]
DSN=DBI:Pg:host=127.0.0.1;database=cluebringer;user=cluebringer;password=#########
#DSN=DBI:SQLite:dbname=policyd.sqlite
DSN=DBI:mysql:host=127.0.0.1;database=cluebringer;user=cluebringer;password=#########
Username=cluebringer
Password=#########

I commented out the line that starts DSN=DBI:Pg, and now it's working correctly without any abnormal load.

I suspect this glitch happened because I initially thought about using a Postgres backend, but then switched to using MySQL. I ran the "clear_iredmail.sh" script, but perhaps it left part of the postgres configuration behind.