At 12:23 PM -0700 10/3/01, Justin Ainsworth wrote: >Oct 3 11:11:47 diamond /usr/local/sbin/popper[30335]: jda at >209.142.14.11 (209.142.14.11): -ERR [SYS/TEMP] Unable to open Bulletin >database; contact your administrator > >Occasionally I get this error. It appears to be happening randomly, >and for no apparent reason. > >I am running Qpopper 4.0.3, compiled with the following options: > >./configure > --silent > --enable-bulletins=/etc/bulletins > --enable-bulldb=/etc/bulletins > --enable-temp-drop-dir=/tmp/mspool > --enable-cache-dir=/tmp/mcache > --enable-spool-dir=/var/spool/mail > --with-pam=qpopper > --enable-trim-domain > --enable-downcase-user > --disable-reverse-lookup > --enable-timeout=200 > --enable-statistics > --enable-fast-update > --enable-standalone > --enable-servermode > --disable-old-uidl > --enable-optimizations > --disable-debugging > --disable-low-debug > --enable-log-facility=LOG_LOCAL0 > >Any help you can give would be very appreciated. > > .~. > /v\ >-- // \\ >JA /( )\ > ^`~`^ > L I N U X >[-----------------------------------------------------------] > Justin Ainsworth Systems Administrator & > PHONE: (530) 879-5660x108 Technical Support Supervisor > FAX: (530) 879-5676 Sunset Net LLC > WEB: http://www.sunset.net 1915 Mangrove Ave > EMAIL: [EMAIL PROTECTED] Chico, CA 95926 >[-----------------------------------------------------------]
Most likely it's a contention issue on the bulletin database. The current architecture requires each session to obtain an exclusive lock on the bulldb for a short time. With many simultaneous connections, some won't be able to do so before they time out. This is discussed in the Administrator's Guide. You can (a) increase the number of attempts each session makes, (b) turn on 'bulldb-nonfatal' option, or (c) stop using a database to store the last seen bulletin. (One long-term solution would be to have a Qpopper bulletin database process which owns the lock and serves requests by the other Qpopper processes.) --
