cyrus db problems

[Nikola Milutinovic]

> Jun 20 09:43:14 myhost ctl_cyrusdb[490727]: archiving database file: 
> /disk1/imap/annotations.db
> Jun 20 09:43:14 myhost ctl_cyrusdb[490727]: DBERROR: error listing log 
> files: Permission denied
> Jun 20 09:43:14 myhost ctl_cyrusdb[490727]: DBERROR: archive 
> /disk1/imap/db: cyrusdb error
> Jun 20 09:43:14 myhost ctl_cyrusdb[490727]: DBERROR: error listing log 
> files: Permission denied
> Jun 20 09:43:14 myhost ctl_cyrusdb[490727]: DBERROR: archive 
> /disk1/imap/db: cyrusdb error
> Jun 20 09:43:14 myhost ctl_cyrusdb[490727]: done checkpointing cyrus 
> databases
> Jun 20 09:43:14 myhost master[483457]: process 490727 exited, status 1


> but the permissions seems to be ok:

> drwxr-x---  11 cyrus    mail         512 Jun 20 09:43 imap

> and

> drwxr-x---  11 cyrus    mail         512 Jun 20 09:43 .
> drwxr-xr-x  20 carboni  system       512 Jun 19 21:49 ..
> -rw-------   1 cyrus    mail         144 Jun 20 09:43 annotations.db
> drwxr-xr-x   2 cyrus    mail         512 Jun 20 09:43 db
> drwx------   2 cyrus    mail         512 Jun 20 09:43 db.backup1
> drwx------   2 cyrus    mail         512 Jun 20 09:43 db.backup2
> drwxr-xr-x   2 cyrus    mail         512 Jun 19 21:52 log
> -rw-------   1 cyrus    mail         144 Jun 20 09:43 mailboxes.db
> drwxr-xr-x   2 cyrus    mail         512 Jun 19 21:52 msg
> drwxr-xr-x   2 cyrus    mail         512 Jun 20 09:45 proc
> drwxr-xr-x   2 cyrus    mail         512 Jun 19 21:52 ptclient
> drwxr-x---   2 cyrus    mail         512 Jun 19 21:50 sieve
> drwxr-xr-x   2 cyrus    mail         512 Jun 20 09:43 socket


Hmm, OK, permissions are NOT OK (they should allow only "cyrus" user any access), but they should not prevent working of Cyrus IMAP. Since this is DB error, you can try two things.

1. With server down, login/su to "cyrus" user and run "ctl_cyrusdb -r" and check the logs.
2. Run the same command under "trace": "trace -f -P -o /tmp/cyrusdb.out /usr/bin/ctl_cyrusdb -r"

The second command will give you a list of system calls that will be called during run of that command. "trace" utility is available for Tru64 UNIX, here and there. If you cannot locate it, drop me an email, I have a working version for both 4.0D and 5.1B at my previous company.

Nix.