Bug #12867 “cyrus21-common: Fails to start on hppa, ctl_cyrusdb ...” : Bugs : cyrus21-imapd package : Ubuntu

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-13:

#1

Automatically imported from Debian bug report #295076 http://bugs.debian.org/295076

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-13:

#2

Download full text (11.7 KiB)

Message-Id: <email address hidden>
Date: Sun, 13 Feb 2005 15:14:25 +0100
From: Alexander Barton <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

Package: cyrus21-common
Version: 2.1.17-3
Severity: grave
Justification: renders package unusable

When I start Cyrus 2.1 on Debian on HPPA, ctl_cyrusdb (which is started
automatically as configured in /etc/cyrus.conf) hangs forever. The same is
true when I start it manually.

Using strace I get the following trace:

execve("/usr/sbin/ctl_cyrusdb", ["/usr/sbin/ctl_cyrusdb", "-r"], [/* 22 vars */]) = 0
newuname({sys="Linux", node="C3600", ...}) = 0
brk(0) = 0x47000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40000000
open("/etc/ld.so.preload", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 32274, PROT_READ, MAP_PRIVATE, 3, 0) = 0x400b7000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/lib/libsasl2.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0@l"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 165480, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40236000
mprotect(0x4024e000, 67176, PROT_NONE) = 0
mmap(0x4025d000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x17000) = 0x4025d000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/libresolv.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0.p"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 150128, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40371000
mprotect(0x40383000, 76400, PROT_NONE) = 0
mmap(0x40392000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x11000) = 0x40392000
mmap(0x40394000, 6768, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40394000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/lib/libdb3.so.3", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\001"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 1036232, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4068b000
mprotect(0x40775000, 77768, PROT_NONE) = 0
mmap(0x40784000, 16384, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0xe9000) = 0x40784000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/lib/libssl.so.0.9.7", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0\245"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 286528, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4028a000
mprotect(0x402bd00...

Message-Id: <20050213141425.B0F351584@Arthur.Ath.CX>
Date: Sun, 13 Feb 2005 15:14:25 +0100
From: Alexander Barton <alex@arthur.ath.cx>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

Package: cyrus21-common
Version: 2.1.17-3
Severity: grave
Justification: renders package unusable

When I start Cyrus 2.1 on Debian on HPPA, ctl_cyrusdb (which is started
automatically as configured in /etc/cyrus.conf) hangs forever. The same is
true when I start it manually.

Using strace I get the following trace:

execve("/usr/sbin/ctl_cyrusdb", ["/usr/sbin/ctl_cyrusdb", "-r"], [/* 22 vars */]) = 0
newuname({sys="Linux", node="C3600", ...}) = 0
brk(0)                                  = 0x47000
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40000000
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 32274, PROT_READ, MAP_PRIVATE, 3, 0) = 0x400b7000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/usr/lib/libsasl2.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0@l"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 165480, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40236000
mprotect(0x4024e000, 67176, PROT_NONE)  = 0
mmap(0x4025d000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x17000) = 0x4025d000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/libresolv.so.2", O_RDONLY)   = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0.p"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 150128, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40371000
mprotect(0x40383000, 76400, PROT_NONE)  = 0
mmap(0x40392000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x11000) = 0x40392000
mmap(0x40394000, 6768, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40394000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/usr/lib/libdb3.so.3", O_RDONLY)  = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\001"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 1036232, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4068b000
mprotect(0x40775000, 77768, PROT_NONE)  = 0
mmap(0x40784000, 16384, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0xe9000) = 0x40784000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/usr/lib/libssl.so.0.9.7", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0\245"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 286528, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4028a000
mprotect(0x402bd000, 77632, PROT_NONE)  = 0
mmap(0x402cc000, 16384, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x32000) = 0x402cc000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/usr/lib/libcrypto.so.0.9.7", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\3\275"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 1273084, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40a88000
mprotect(0x40b98000, 158972, PROT_NONE) = 0
mmap(0x40ba7000, 86016, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x10f000) = 0x40ba7000
mmap(0x40bbc000, 11516, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40bbc000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/libc.so.6", O_RDONLY)        = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\1\365"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40001000
mmap(NULL, 1445472, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40f5b000
mprotect(0x410a3000, 101984, PROT_NONE) = 0
mmap(0x410b2000, 32768, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x147000) = 0x410b2000
mmap(0x410ba000, 7776, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x410ba000
close(3)                                = 0
access("/etc/ld.so.nohwcap", F_OK)      = -1 ENOENT (No such file or directory)
open("/lib/libdl.so.2", O_RDONLY)       = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\0#H"..., 512) = 512
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 76976, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40357000
mprotect(0x4035a000, 64688, PROT_NONE)  = 0
mmap(0x40369000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 3, 0x2000) = 0x40369000
close(3)                                = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40002000
munmap(0x400b7000, 32274)               = 0
geteuid()                               = 107
brk(0)                                  = 0x47000
brk(0x68000)                            = 0x68000
brk(0)                                  = 0x68000
open("/etc/imapd.conf", O_RDONLY)       = 3
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40003000
read(3, "# Debian Cyrus imapd.conf\n# See "..., 4096) = 4096
read(3, "\n# connected to the imap/pop ser"..., 4096) = 4096
read(3, "/ssl/private/cyrus-lmtp.key\n\n# F"..., 4096) = 2652
read(3, "", 4096)                       = 0
close(3)                                = 0
munmap(0x40003000, 4096)                = 0
umask(077)                              = 022
newuname({sys="Linux", node="C3600", ...}) = 0
time([1108297797])                      = 1108297797
open("/etc/localtime", O_RDONLY)        = 3
fstat64(3, {st_mode=0, st_size=0, ...}) = 0
mmap(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40003000
read(3, "TZif\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10"..., 131072) = 837
close(3)                                = 0
munmap(0x40003000, 131072)              = 0
getpid()                                = 14384
rt_sigaction(SIGPIPE, {0x410b6a7a, [], 0}, {SIG_DFL}, 8) = 0
socket(PF_FILE, SOCK_DGRAM, 0)          = 3
fcntl64(3, F_SETFD, FD_CLOEXEC)         = 0
connect(3, {sa_family=AF_FILE, path="/dev/log"}, 16) = 0
send(3, "<21>Feb 13 13:29:57 cyrus/ctl_cy"..., 72, 0) = 72
rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0
time(NULL)                              = 1108297797
open("/var/lib/cyrus/db/skipstamp", O_RDWR|O_CREAT, 0644) = 4
ftruncate(4, 0)                         = 0
write(4, "B\17HE", 4)                   = 4
close(4)                                = 0
time(NULL)                              = 1108297797
getpid()                                = 14384
open("/var/lib/cyrus/db/DB_CONFIG", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
stat64("/var/tmp", {st_mode=0, st_size=0, ...}) = 0
open("/var/lib/cyrus/db/__db.001", O_RDWR|O_LARGEFILE) = -1 ENOENT (No such file or directory)
open("/var/lib/cyrus/db", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 4
fstat64(4, {st_mode=0, st_size=459561500680, ...}) = 0
fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
mmap(NULL, 135168, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40003000
getdents64(4, /* 3 entries */, 131072)  = 80
getdents64(4, /* 0 entries */, 131072)  = 0
munmap(0x40003000, 135168)              = 0
close(4)                                = 0
unlink("/var/lib/cyrus/db/__db_lock.share") = -1 ENOENT (No such file or directory)
unlink("/var/lib/cyrus/db/__db_log.share") = -1 ENOENT (No such file or directory)
unlink("/var/lib/cyrus/db/__db_mpool.share") = -1 ENOENT (No such file or directory)
unlink("/var/lib/cyrus/db/__db_txn.share") = -1 ENOENT (No such file or directory)
open("/var/lib/cyrus/db/DB_CONFIG", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
stat64("/var/tmp", {st_mode=0, st_size=0, ...}) = 0
open("/var/lib/cyrus/db/__db.001", O_RDWR|O_CREAT|O_EXCL|O_LARGEFILE, 0644) = 4
fcntl64(4, F_SETFD, FD_CLOEXEC)         = 0
open("/var/lib/cyrus/db/__db.001", O_RDWR|O_CREAT|O_LARGEFILE, 0644) = 5
fcntl64(5, F_SETFD, FD_CLOEXEC)         = 0
_llseek(5, 0, [0], SEEK_END)            = 0
_llseek(5, 0, [0], SEEK_CUR)            = 0
write(5, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 8192) = 8192
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_SHARED, 5, 0) = 0x40eca000
close(5)                                = 0
_newselect(0, NULL, NULL, NULL, {0, 1000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 2000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 4000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 8000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 16000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 32000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 64000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 128000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 256000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {0, 512000}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
[... repeating endlessly ...]
_newselect(0, NULL, NULL, NULL, {1, 0}) = 0 (Timeout)
_newselect(0, NULL, NULL, NULL, {1, 0}) = -514 (left {0, 14000})
--- SIGINT (Interrupt) @ 0 (0) ---
+++ killed by SIGINT +++

After starting/killing ctl_cyrusdb /var/lib/cyrus/db looks like this:

drwx------  2 cyrus mail  104 Feb 13 15:10 ./
drwxr-x---  9 cyrus mail  216 Feb 13 14:09 ../
-rw-------  1 cyrus mail 8192 Feb 13 15:10 __db.001
-rw-------  1 cyrus mail    4 Feb 13 15:10 skipstamp

Now, when I run "db3_verify __db.001" I get this:

db_verify: unable to join the environment
db_verify: Bad magic number: 0
db_verify: Bad page size: 0
db_verify: __db.001: Invalid argument
db_verify: DB->verify: __db.001: Invalid argument

Okay. Don't now what else I can try ...

Any hints/suggestions?

Is this a problem with Berkeley DB 3 on HPPA?

Regards
Alex

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: hppa (parisc)
Kernel: Linux 2.6.11-rc3-pa5
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages cyrus21-common depends on:
ii  adduser         3.59                     Add and remove users and groups
ii  debconf [debcon 1.4.30.11                Debian configuration management sy
ii  dpkg            1.10.26                  Package maintenance system for Deb
ii  gawk            1:3.1.4-2                GNU awk, a pattern scanning and pr
ii  libc6           2.3.2.ds1-20             GNU C Library: Shared libraries an
ii  libdb3          3.2.9-20                 Berkeley v3 Database Libraries [ru
ii  libsasl2        2.1.19-1.5               Authentication abstraction library
ii  libsnmp4.2      4.2.5-5                  NET SNMP (Simple Network Managemen
ii  libssl0.9.7     0.9.7e-2                 SSL shared libraries
ii  libwrap0        7.6.dbs-6                Wietse Venema's TCP wrappers libra
ii  libzephyr3      2.1.20010518.SNAPSHOT-11 The original "Instant Message" sys
ii  netbase         4.19                     Basic TCP/IP networking system
ii  perl            5.8.4-6                  Larry Wall's Practical Extraction 
ii  postfix [mail-t 2.1.5-5                  A high-performance mail transport

-- debconf information:
  cyrus21-common/removespools: false
  cyrus21-common/warnbackendchange:

Revision history for this message

In Debian Bug tracker #295076, Henrique de Moraes Holschuh (hmh) wrote on 2005-02-13: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

#3

tags 295076 + unreproducible moreinfo
thanks

On Sun, 13 Feb 2005, Alexander Barton wrote:
> When I start Cyrus 2.1 on Debian on HPPA, ctl_cyrusdb (which is started
> automatically as configured in /etc/cyrus.conf) hangs forever. The same is
> true when I start it manually.

This usually means the db environment is gone. kaput. corrupted. busted.

> Is this a problem with Berkeley DB 3 on HPPA?

Probably.

Stop cyrus. Make sure (thorough ps, etc) that it is really stopped. cd to
/var/lib/cyrus.

Now, run db3_recover. Does it hang? if yes, you're in trouble, and you will
have to rm ALL the dbs and ALL the logs. There is a backup of the mailboxes db
in /var/backups which can be used to restore the mailboxes database using
ctl_mboxlist. You will lose some information.

If db3_recover worked, rm the deliver.db and tls_sessions.db databases, and
make sure all files have owner "cyrus". Then start Cyrus again (and good
luck).

Did it work? BTW, have you experienced any power outages, cyrus crashes,
memory failures or anything else that could have corrupted a db3
environment? It is damn difficult to corrupt it on ia32, at least...

Look at the db3 changelogs, see if there are any suspicious changes listed
for hppa.

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-13:

#4

Message-ID: <email address hidden>
Date: Sun, 13 Feb 2005 15:36:31 -0200
From: Henrique de Moraes Holschuh <email address hidden>
To: Alexander Barton <email address hidden>, <email address hidden>
Subject: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

tags 295076 + unreproducible moreinfo
thanks

On Sun, 13 Feb 2005, Alexander Barton wrote:
> When I start Cyrus 2.1 on Debian on HPPA, ctl_cyrusdb (which is started
> automatically as configured in /etc/cyrus.conf) hangs forever. The same is
> true when I start it manually.

This usually means the db environment is gone. kaput. corrupted. busted.

> Is this a problem with Berkeley DB 3 on HPPA?

Probably.

Stop cyrus. Make sure (thorough ps, etc) that it is really stopped. cd to
/var/lib/cyrus.

Now, run db3_recover. Does it hang? if yes, you're in trouble, and you will
have to rm ALL the dbs and ALL the logs. There is a backup of the mailboxes db
in /var/backups which can be used to restore the mailboxes database using
ctl_mboxlist. You will lose some information.

If db3_recover worked, rm the deliver.db and tls_sessions.db databases, and
make sure all files have owner "cyrus". Then start Cyrus again (and good
luck).

Did it work? BTW, have you experienced any power outages, cyrus crashes,
memory failures or anything else that could have corrupted a db3
environment? It is damn difficult to corrupt it on ia32, at least...

Look at the db3 changelogs, see if there are any suspicious changes listed
for hppa.

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Revision history for this message

In Debian Bug tracker #295076, Jochen Friedrich (jochen) wrote on 2005-02-13: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

#5

Hi Alexander,

db3 on hppa had a bug (#2666685) which caused this exact behaviour. Please
make sure you have at least db3 version 3.2.9-21 installed.

Thanks,
Jochen

> tags 295076 + unreproducible moreinfo
> thanks
>
> On Sun, 13 Feb 2005, Alexander Barton wrote:
> > When I start Cyrus 2.1 on Debian on HPPA, ctl_cyrusdb (which is started
> > automatically as configured in /etc/cyrus.conf) hangs forever. The same is
> > true when I start it manually.
>
> This usually means the db environment is gone. kaput. corrupted. busted.
>
> > Is this a problem with Berkeley DB 3 on HPPA?
>
> Probably.
>
> Stop cyrus. Make sure (thorough ps, etc) that it is really stopped. cd to
> /var/lib/cyrus.
>
> Now, run db3_recover. Does it hang? if yes, you're in trouble, and you will
> have to rm ALL the dbs and ALL the logs. There is a backup of the mailboxes db
> in /var/backups which can be used to restore the mailboxes database using
> ctl_mboxlist. You will lose some information.
>
> If db3_recover worked, rm the deliver.db and tls_sessions.db databases, and
> make sure all files have owner "cyrus". Then start Cyrus again (and good
> luck).
>
> Did it work? BTW, have you experienced any power outages, cyrus crashes,
> memory failures or anything else that could have corrupted a db3
> environment? It is damn difficult to corrupt it on ia32, at least...
>
> Look at the db3 changelogs, see if there are any suspicious changes listed
> for hppa.
>
> --
> "One disk to rule them all, One disk to find them. One disk to bring
> them all and in the darkness grind them. In the Land of Redmond
> where the shadows lie." -- The Silicon Valley Tarot
> Henrique Holschuh
>
>
>

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-13:

#6

Message-ID: <Pine.LNX.4.58.0502132204410.1911@localhost>
Date: Sun, 13 Feb 2005 22:07:45 +0100 (CET)
From: Jochen Friedrich <email address hidden>
To: Henrique de Moraes Holschuh <email address hidden>,
<email address hidden>
Cc: Alexander Barton <email address hidden>
Subject: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb
hangs forever

Hi Alexander,

db3 on hppa had a bug (#2666685) which caused this exact behaviour. Please
make sure you have at least db3 version 3.2.9-21 installed.

Thanks,
Jochen

> tags 295076 + unreproducible moreinfo
> thanks
>
> On Sun, 13 Feb 2005, Alexander Barton wrote:
> > When I start Cyrus 2.1 on Debian on HPPA, ctl_cyrusdb (which is started
> > automatically as configured in /etc/cyrus.conf) hangs forever. The same is
> > true when I start it manually.
>
> This usually means the db environment is gone. kaput. corrupted. busted.
>
> > Is this a problem with Berkeley DB 3 on HPPA?
>
> Probably.
>
> Stop cyrus. Make sure (thorough ps, etc) that it is really stopped. cd to
> /var/lib/cyrus.
>
> Now, run db3_recover. Does it hang? if yes, you're in trouble, and you will
> have to rm ALL the dbs and ALL the logs. There is a backup of the mailboxes db
> in /var/backups which can be used to restore the mailboxes database using
> ctl_mboxlist. You will lose some information.
>
> If db3_recover worked, rm the deliver.db and tls_sessions.db databases, and
> make sure all files have owner "cyrus". Then start Cyrus again (and good
> luck).
>
> Did it work? BTW, have you experienced any power outages, cyrus crashes,
> memory failures or anything else that could have corrupted a db3
> environment? It is damn difficult to corrupt it on ia32, at least...
>
> Look at the db3 changelogs, see if there are any suspicious changes listed
> for hppa.
>
> --
> "One disk to rule them all, One disk to find them. One disk to bring
> them all and in the darkness grind them. In the Land of Redmond
> where the shadows lie." -- The Silicon Valley Tarot
> Henrique Holschuh
>
>
>

Message-ID: <Pine.LNX.4.58.0502132204410.1911@localhost>
Date: Sun, 13 Feb 2005 22:07:45 +0100 (CET)
From: Jochen Friedrich <jochen@scram.de>
To: Henrique de Moraes Holschuh <hmh@debian.org>,
	295076@bugs.debian.org
Cc: Alexander Barton <alex@arthur.ath.cx>
Subject: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb
    hangs forever

Hi Alexander,

db3 on hppa had a bug (#2666685) which caused this exact behaviour. Please
make sure you have at least db3 version 3.2.9-21 installed.

Thanks,
Jochen

> tags 295076 + unreproducible moreinfo
> thanks
>
> On Sun, 13 Feb 2005, Alexander Barton wrote:
> > When I start Cyrus 2.1 on Debian on HPPA, ctl_cyrusdb (which is started
> > automatically as configured in /etc/cyrus.conf) hangs forever. The same is
> > true when I start it manually.
>
> This usually means the db environment is gone. kaput. corrupted. busted.
>
> > Is this a problem with Berkeley DB 3 on HPPA?
>
> Probably.
>
> Stop cyrus. Make sure (thorough ps, etc) that it is really stopped. cd to
> /var/lib/cyrus.
>
> Now, run db3_recover.  Does it hang? if yes, you're in trouble, and you will
> have to rm ALL the dbs and ALL the logs.  There is a backup of the mailboxes db
> in /var/backups which can be used to restore the mailboxes database using
> ctl_mboxlist.  You will lose some information.
>
> If db3_recover worked, rm the deliver.db and tls_sessions.db databases, and
> make sure all files have owner "cyrus".  Then start Cyrus again (and good
> luck).
>
> Did it work?  BTW, have you experienced any power outages, cyrus crashes,
> memory failures or anything else that could have corrupted a db3
> environment?  It is damn difficult to corrupt it on ia32, at least...
>
> Look at the db3 changelogs, see if there are any suspicious changes listed
> for hppa.
>
> --
>   "One disk to rule them all, One disk to find them. One disk to bring
>   them all and in the darkness grind them. In the Land of Redmond
>   where the shadows lie." -- The Silicon Valley Tarot
>   Henrique Holschuh
>
>
>

Revision history for this message

In Debian Bug tracker #295076, Alexander Barton (alex-barton) wrote on 2005-02-13: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

#7

Am 13. Feb 2005 um 22:07 Uhr schrieb Jochen Friedrich:

> db3 on hppa had a bug (#2666685) which caused this exact behaviour.
> Please
> make sure you have at least db3 version 3.2.9-21 installed.

Okay, I installed 3.2.9-22 from unstable and reinstalled cyrus21-xxx.
Now Cyrus seems to work as expected. Thanks a lot!

Sorry for blaming the Cyrus packages for this Berkeley DB bug :-)

Regards
Alex

--
Alexander Barton, Freiburg, Germany
http://www.barton.de/, <email address hidden>

Revision history for this message

In Debian Bug tracker #295076, Henrique de Moraes Holschuh (hmh) wrote on 2005-02-13:

#8

On Mon, 14 Feb 2005, Alexander Barton wrote:
> Okay, I installed 3.2.9-22 from unstable and reinstalled cyrus21-xxx.
> Now Cyrus seems to work as expected. Thanks a lot!

Ok. Closing the bug, then...

> Sorry for blaming the Cyrus packages for this Berkeley DB bug :-)

It's not a problem...

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-14:

#9

Message-Id: <email address hidden>
Date: Mon, 14 Feb 2005 00:45:26 +0100
From: Alexander Barton <email address hidden>
To: Jochen Friedrich <email address hidden>
Cc: Henrique de Moraes Holschuh <email address hidden>,
<email address hidden>, Alexander Barton <email address hidden>
Subject: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

Am 13. Feb 2005 um 22:07 Uhr schrieb Jochen Friedrich:

> db3 on hppa had a bug (#2666685) which caused this exact behaviour.
> Please
> make sure you have at least db3 version 3.2.9-21 installed.

Okay, I installed 3.2.9-22 from unstable and reinstalled cyrus21-xxx.
Now Cyrus seems to work as expected. Thanks a lot!

Sorry for blaming the Cyrus packages for this Berkeley DB bug :-)

Regards
Alex

--
Alexander Barton, Freiburg, Germany
http://www.barton.de/, <email address hidden>

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-02-14:

#10

Message-ID: <email address hidden>
Date: Sun, 13 Feb 2005 21:58:38 -0200
From: Henrique de Moraes Holschuh <email address hidden>
To: Alexander Barton <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#295076: cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

On Mon, 14 Feb 2005, Alexander Barton wrote:
> Okay, I installed 3.2.9-22 from unstable and reinstalled cyrus21-xxx.
> Now Cyrus seems to work as expected. Thanks a lot!

Ok. Closing the bug, then...

> Sorry for blaming the Cyrus packages for this Berkeley DB bug :-)

It's not a problem...

--
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

Revision history for this message

Martin Pitt (pitti) wrote on 2005-02-22:

#11

Not a bug in cyrus, and only affects hppa.

Bug Watch Updater (bug-watch-updater) on 2006-09-27

Changed in cyrus21-imapd:
status:	Unknown → Fix Released

Affects		Status	Importance	Assigned to	Milestone
	cyrus21-imapd (Debian)	Fix Released	Unknown	debbugs #295076
	cyrus21-imapd (Ubuntu)	Invalid	High	Unassigned

Ubuntu
cyrus21-imapd package

cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

Bug Description

Other bug subscribers

Remote bug watches

Ubuntucyrus21-imapd package

cyrus21-common: Fails to start on hppa, ctl_cyrusdb hangs forever

Bug Description

Other bug subscribers

Remote bug watches

Ubuntu
cyrus21-imapd package