Bug 157882 - cyrus-imapd exits abnormally on s390x
cyrus-imapd exits abnormally on s390x
Status: CLOSED WONTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: cyrus-imapd (Show other bugs)
4.0
s390x Linux
medium Severity medium
: ---
: ---
Assigned To: Petr Rockai
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-05-16 14:27 EDT by Ben Levenson
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-25 04:36:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ben Levenson 2005-05-16 14:27:36 EDT
Description of problem:
cyrus-imapd on s390x fails with the following messages (from maillog):
master[22137]: about to exec /usr/lib64/cyrus-imapd/lmtpd
lmtpunix[22137]: DBERROR: invalid berkeley_cachesize value, using internal default
lmtpunix[22137]: DBERROR db4: PANIC: fatal region error detected; run recovery
lmtpunix[22137]: DBERROR: critical database situation
master[6768]: process 22137 exited, status 75
master[6768]: service lmtpunix pid 22137 in READY state : terminated abnormally

Version-Release number of selected component (if applicable):
cyrus-imapd-2.2.10-1.RHEL4.1

How reproducible:
100%

Steps to Reproduce:
1. service cyrus-imapd start
2. try to connect to server with 'telnet localhost imap'
3. notice that you can't connect
4. check /var/log/maillog and notice the messages posted above
Comment 1 John Dennis 2005-05-16 14:44:00 EDT
I'm confused, the bug says it's filed against RHEL3, but cyrus-imapd was not
part of RHEL3, only RHEL4 and the rpm name says RHEL4. Was it a mistake that
RHEL3 is listed as the distribution or were you trying to run a RHEL4 package on
RHEL3?
Comment 2 Ben Levenson 2005-05-16 14:53:58 EDT
sorry about that.  should've been filed against RHEL 4.
Comment 3 Simon Matter 2005-08-16 03:03:03 EDT
And it's once again a DB4 problem. Maybe we should get rid of Berkeley DB it and
switch all backends to skiplist instead. BDB is always a PITA, just look at
other bugs like #160317
Could someone try with the following options added to /etc/imapd.conf on s390x:
duplicate_db: skiplist
tlscache_db: skiplist
Comment 5 RHEL Product and Program Management 2006-08-18 13:41:31 EDT
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.
Comment 6 Petr Rockai 2006-08-24 07:59:18 EDT
Simon's proposal (#3) sounds fair, but i am not sure we want to change 
this on upgrade. It can probably be done, but the process is going to be 
bug-prone. Votes?
Comment 8 RHEL Product and Program Management 2006-08-25 04:36:09 EDT
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request. 

Note You need to log in before you can comment on or make changes to this bug.