hartmut.woehrle@mail.pcom.de
2006-Dec-05 06:46 UTC
[Ocfs2-users] OCFS2 and berkeley database files
Hello Forum,
when trying to install a mailserver on a shared SAN Device with ocfs2, I
realized some strange problems with Berkeley .db files:
Trying to install OpenLDAP:
Dec 1 16:16:56 server_1 slapd[18497]: bdb_db_init: Initializing BDB database
Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): mmap:
Invalid argument
Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_open: dbenv_open failed:
Invalid
argument (22)
Dec 1 16:16:56 server_1 slapd[18498]: backend_startup: bi_db_open failed!
(22)
Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):
DB_ENV->lock_id_free interface requires an environment configured for th
e locking subsystem
Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):
txn_checkpoint interface requires an environment configured for the tran
saction subsystem
Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_destroy: txn_checkpoint failed:
Invalid argument (22)
Dec 1 16:17:50 server_1 slapd[18525]: bdb_db_init: Initializing BDB database
Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): mmap:
Invalid argument
Dec 1 16:17:50 server_1 slapd[18526]: bdb_db_open: dbenv_open failed:
Invalid
argument (22)
Dec 1 16:17:50 server_1 slapd[18526]: backend_startup: bi_db_open failed!
(22)
Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):
DB_ENV->lock_id_free interface requires an environment configured for th
e locking subsystem
Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):
txn_checkpoint interface requires an environment configured for the tran
saction subsystem
.....
When installing on a standard ext3 - no problems.
When installing cyrus (initial start after creation of cyrus admin account):
Dec 5 04:15:01 server_1 ctl_mboxlist[29435]: IOERROR:
mapping /var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 ctl_cyrusdb[32679]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 idled[32680]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 idled[32680]: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32684]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32684]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32685]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32685]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32691]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32691]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32690]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32690]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32693]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32693]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32694]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32694]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32695]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32695]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32697]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32697]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32698]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32698]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32701]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32701]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 sieve[32686]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 sieve[32692]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32696]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32696]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
....
and so on.
With google I didn?t find that anything about this problem. Is it unknown,
already solved or something concerned with my setup??
Server is a DELL Poweredge with EMC CLARiiON SAN
System SuSE SLES9 SP3+
-> 2.6.5-7.244-smp Kernel with (...> modinfo ocfs2):
license: GPL
author: Oracle
version: 1.1.7-SLES 5AF01E6455FC04917FE52FB
description: OCFS2 1.1.7-SLES Tue Nov 1 14:45:27 PST 2005 (build sles)
depends: ocfs2_nodemanager,ocfs2_dlm,jbd
supported: yes
vermagic: 2.6.5-7.244-smp SMP gcc-3.3
and in addition
DELL/EMC PowerPath 4.5.1 for Linux
to use the multiple path environment (not GPL multipath)
Thanks
Hartmut Woehrle
--
==========================================
Hartmut Woehrle
EMail: hartmut.woehrle@mail.pcom.de
I remember discussion in suse mailing list - they had a problem running LDAP
on ReiserFS (until something have been patched).
----- Original Message -----
From: <hartmut.woehrle@mail.pcom.de>
To: <Ocfs2-users@oss.oracle.com>
Sent: Tuesday, December 05, 2006 6:46 AM
Subject: [Ocfs2-users] OCFS2 and berkeley database files
Hello Forum,
when trying to install a mailserver on a shared SAN Device with ocfs2, I
realized some strange problems with Berkeley .db files:
Trying to install OpenLDAP:
Dec 1 16:16:56 server_1 slapd[18497]: bdb_db_init: Initializing BDB
database
Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): mmap:
Invalid argument
Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_open: dbenv_open failed:
Invalid
argument (22)
Dec 1 16:16:56 server_1 slapd[18498]: backend_startup: bi_db_open failed!
(22)
Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):
DB_ENV->lock_id_free interface requires an environment configured for th
e locking subsystem
Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):
txn_checkpoint interface requires an environment configured for the tran
saction subsystem
Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_destroy: txn_checkpoint
failed:
Invalid argument (22)
Dec 1 16:17:50 server_1 slapd[18525]: bdb_db_init: Initializing BDB
database
Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): mmap:
Invalid argument
Dec 1 16:17:50 server_1 slapd[18526]: bdb_db_open: dbenv_open failed:
Invalid
argument (22)
Dec 1 16:17:50 server_1 slapd[18526]: backend_startup: bi_db_open failed!
(22)
Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):
DB_ENV->lock_id_free interface requires an environment configured for th
e locking subsystem
Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):
txn_checkpoint interface requires an environment configured for the tran
saction subsystem
.....
When installing on a standard ext3 - no problems.
When installing cyrus (initial start after creation of cyrus admin account):
Dec 5 04:15:01 server_1 ctl_mboxlist[29435]: IOERROR:
mapping /var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 ctl_cyrusdb[32679]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 idled[32680]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 idled[32680]: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32684]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32684]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32685]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32685]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32691]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32691]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32690]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32690]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32693]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32693]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32694]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32694]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32695]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32695]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3[32697]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32697]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32698]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32698]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 pop3s[32701]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3s[32701]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
Dec 5 14:14:43 server_1 sieve[32686]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 sieve[32692]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32696]: IOERROR:
mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument
Dec 5 14:14:43 server_1 pop3[32696]: Fatal error: failed to
mmap /communication/var/lib/imap/mailboxes.db file
....
and so on.
With google I didn?t find that anything about this problem. Is it unknown,
already solved or something concerned with my setup??
Server is a DELL Poweredge with EMC CLARiiON SAN
System SuSE SLES9 SP3+
-> 2.6.5-7.244-smp Kernel with (...> modinfo ocfs2):
license: GPL
author: Oracle
version: 1.1.7-SLES 5AF01E6455FC04917FE52FB
description: OCFS2 1.1.7-SLES Tue Nov 1 14:45:27 PST 2005 (build sles)
depends: ocfs2_nodemanager,ocfs2_dlm,jbd
supported: yes
vermagic: 2.6.5-7.244-smp SMP gcc-3.3
and in addition
DELL/EMC PowerPath 4.5.1 for Linux
to use the multiple path environment (not GPL multipath)
Thanks
Hartmut Woehrle
--
==========================================
Hartmut Woehrle
EMail: hartmut.woehrle@mail.pcom.de
_______________________________________________
Ocfs2-users mailing list
Ocfs2-users@oss.oracle.com
http://oss.oracle.com/mailman/listinfo/ocfs2-users
You are on a very old release of OCFS2. The OCFS2 homepage and FAQ both list a SLES9 kernel version newer than the one you are using. But that may not be the reason for the error. My bet is that bdb is attempting to create a shared writeable mmap that ocfs2 1.2 does not support. hartmut.woehrle@mail.pcom.de wrote:> Hello Forum, > > when trying to install a mailserver on a shared SAN Device with ocfs2, I > realized some strange problems with Berkeley .db files: > > Trying to install OpenLDAP: > Dec 1 16:16:56 server_1 slapd[18497]: bdb_db_init: Initializing BDB database > Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): mmap: > Invalid argument > Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_open: dbenv_open failed: > Invalid > argument (22) > Dec 1 16:16:56 server_1 slapd[18498]: backend_startup: bi_db_open failed! > (22) > Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): > DB_ENV->lock_id_free interface requires an environment configured for th > e locking subsystem > Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): > txn_checkpoint interface requires an environment configured for the tran > saction subsystem > Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_destroy: txn_checkpoint failed: > Invalid argument (22) > Dec 1 16:17:50 server_1 slapd[18525]: bdb_db_init: Initializing BDB database > Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): mmap: > Invalid argument > Dec 1 16:17:50 server_1 slapd[18526]: bdb_db_open: dbenv_open failed: > Invalid > argument (22) > Dec 1 16:17:50 server_1 slapd[18526]: backend_startup: bi_db_open failed! > (22) > Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): > DB_ENV->lock_id_free interface requires an environment configured for th > e locking subsystem > Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): > txn_checkpoint interface requires an environment configured for the tran > saction subsystem > > > > ..... > > When installing on a standard ext3 - no problems. > > When installing cyrus (initial start after creation of cyrus admin account): > > Dec 5 04:15:01 server_1 ctl_mboxlist[29435]: IOERROR: > mapping /var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 ctl_cyrusdb[32679]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 idled[32680]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 idled[32680]: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32684]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32684]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32685]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32685]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32691]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32691]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32690]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32690]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32693]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32693]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32694]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32694]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32695]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32695]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32697]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32697]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32698]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32698]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32701]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32701]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 sieve[32686]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 sieve[32692]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32696]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32696]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > > .... > and so on. > > With google I didn?t find that anything about this problem. Is it unknown, > already solved or something concerned with my setup?? > > Server is a DELL Poweredge with EMC CLARiiON SAN > System SuSE SLES9 SP3+ > -> 2.6.5-7.244-smp Kernel with (...> modinfo ocfs2): > license: GPL > author: Oracle > version: 1.1.7-SLES 5AF01E6455FC04917FE52FB > description: OCFS2 1.1.7-SLES Tue Nov 1 14:45:27 PST 2005 (build sles) > depends: ocfs2_nodemanager,ocfs2_dlm,jbd > supported: yes > vermagic: 2.6.5-7.244-smp SMP gcc-3.3 > > and in addition > DELL/EMC PowerPath 4.5.1 for Linux > to use the multiple path environment (not GPL multipath) > > Thanks > Hartmut Woehrle > > > >
It is IMHO not a good idea (not needed, less reliable, much slower) to cluster LDAP servers like that. Just use a local file system on each server and use replication. Gruss Bernd -----Original Message----- From: ocfs2-users-bounces@oss.oracle.com [mailto:ocfs2-users-bounces@oss.oracle.com] On Behalf Of Sunil Mushran Sent: Wednesday, December 06, 2006 12:46 AM To: hartmut.woehrle@mail.pcom.de Cc: Ocfs2-users@oss.oracle.com Subject: Re: [Ocfs2-users] OCFS2 and berkeley database files You are on a very old release of OCFS2. The OCFS2 homepage and FAQ both list a SLES9 kernel version newer than the one you are using. But that may not be the reason for the error. My bet is that bdb is attempting to create a shared writeable mmap that ocfs2 1.2 does not support. hartmut.woehrle@mail.pcom.de wrote:> Hello Forum, > > when trying to install a mailserver on a shared SAN Device with ocfs2, > I realized some strange problems with Berkeley .db files: > > Trying to install OpenLDAP: > Dec 1 16:16:56 server_1 slapd[18497]: bdb_db_init: Initializing BDB > database Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): mmap: > Invalid argument > Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_open: dbenv_open failed: > Invalid > argument (22) > Dec 1 16:16:56 server_1 slapd[18498]: backend_startup: bi_db_open failed! > (22) > Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): > DB_ENV->lock_id_free interface requires an environment configured for > th e locking subsystem Dec 1 16:16:56 server_1 slapd[18498]: > bdb(ou=users,dc=mycomp,dc=de): > txn_checkpoint interface requires an environment configured for the > tran saction subsystem Dec 1 16:16:56 server_1 slapd[18498]: > bdb_db_destroy: txn_checkpoint failed: > Invalid argument (22) > Dec 1 16:17:50 server_1 slapd[18525]: bdb_db_init: Initializing BDB > database Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): mmap: > Invalid argument > Dec 1 16:17:50 server_1 slapd[18526]: bdb_db_open: dbenv_open failed: > Invalid > argument (22) > Dec 1 16:17:50 server_1 slapd[18526]: backend_startup: bi_db_open failed! > (22) > Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): > DB_ENV->lock_id_free interface requires an environment configured for > th e locking subsystem Dec 1 16:17:50 server_1 slapd[18526]: > bdb(ou=users,dc=mycomp,dc=de): > txn_checkpoint interface requires an environment configured for the > tran saction subsystem > > > > ..... > > When installing on a standard ext3 - no problems. > > When installing cyrus (initial start after creation of cyrus admin account): > > Dec 5 04:15:01 server_1 ctl_mboxlist[29435]: IOERROR: > mapping /var/lib/imap/mailboxes.db file: Invalid argument Dec 5 > 14:14:43 server_1 ctl_cyrusdb[32679]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 idled[32680]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 idled[32680]: failed to mmap > /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 server_1 > pop3[32684]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3[32684]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3s[32685]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3s[32685]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3s[32691]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3s[32691]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3[32690]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3[32690]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3[32693]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3[32693]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3s[32694]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3s[32694]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3s[32695]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3s[32695]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3[32697]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3[32697]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3s[32698]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3s[32698]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 pop3s[32701]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3s[32701]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file Dec 5 14:14:43 > server_1 sieve[32686]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 sieve[32692]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3[32696]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid > argument Dec 5 14:14:43 server_1 pop3[32696]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > > .... > and so on. > > With google I didn?t find that anything about this problem. Is it > unknown, already solved or something concerned with my setup?? > > Server is a DELL Poweredge with EMC CLARiiON SAN System SuSE SLES9 > SP3+ > -> 2.6.5-7.244-smp Kernel with (...> modinfo ocfs2): > license: GPL > author: Oracle > version: 1.1.7-SLES 5AF01E6455FC04917FE52FB > description: OCFS2 1.1.7-SLES Tue Nov 1 14:45:27 PST 2005 (build sles) > depends: ocfs2_nodemanager,ocfs2_dlm,jbd > supported: yes > vermagic: 2.6.5-7.244-smp SMP gcc-3.3 > > and in addition > DELL/EMC PowerPath 4.5.1 for Linux > to use the multiple path environment (not GPL multipath) > > Thanks > Hartmut Woehrle > > > >_______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
It really try to create a shared writable MMAP. And it already cause numerous problems with another file systems. ----- Original Message ----- From: "Sunil Mushran" <Sunil.Mushran@oracle.com> To: <hartmut.woehrle@mail.pcom.de> Cc: <Ocfs2-users@oss.oracle.com> Sent: Tuesday, December 05, 2006 3:45 PM Subject: Re: [Ocfs2-users] OCFS2 and berkeley database files You are on a very old release of OCFS2. The OCFS2 homepage and FAQ both list a SLES9 kernel version newer than the one you are using. But that may not be the reason for the error. My bet is that bdb is attempting to create a shared writeable mmap that ocfs2 1.2 does not support. hartmut.woehrle@mail.pcom.de wrote:> Hello Forum, > > when trying to install a mailserver on a shared SAN Device with ocfs2, I > realized some strange problems with Berkeley .db files: > > Trying to install OpenLDAP: > Dec 1 16:16:56 server_1 slapd[18497]: bdb_db_init: Initializing BDBdatabase> Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de):mmap:> Invalid argument > Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_open: dbenv_open failed: > Invalid > argument (22) > Dec 1 16:16:56 server_1 slapd[18498]: backend_startup: bi_db_open failed! > (22) > Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): > DB_ENV->lock_id_free interface requires an environment configured for th > e locking subsystem > Dec 1 16:16:56 server_1 slapd[18498]: bdb(ou=users,dc=mycomp,dc=de): > txn_checkpoint interface requires an environment configured for the tran > saction subsystem > Dec 1 16:16:56 server_1 slapd[18498]: bdb_db_destroy: txn_checkpointfailed:> Invalid argument (22) > Dec 1 16:17:50 server_1 slapd[18525]: bdb_db_init: Initializing BDBdatabase> Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de):mmap:> Invalid argument > Dec 1 16:17:50 server_1 slapd[18526]: bdb_db_open: dbenv_open failed: > Invalid > argument (22) > Dec 1 16:17:50 server_1 slapd[18526]: backend_startup: bi_db_open failed! > (22) > Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): > DB_ENV->lock_id_free interface requires an environment configured for th > e locking subsystem > Dec 1 16:17:50 server_1 slapd[18526]: bdb(ou=users,dc=mycomp,dc=de): > txn_checkpoint interface requires an environment configured for the tran > saction subsystem > > > > ..... > > When installing on a standard ext3 - no problems. > > When installing cyrus (initial start after creation of cyrus adminaccount):> > Dec 5 04:15:01 server_1 ctl_mboxlist[29435]: IOERROR: > mapping /var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 ctl_cyrusdb[32679]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 idled[32680]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 idled[32680]: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32684]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32684]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32685]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32685]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32691]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32691]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32690]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32690]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32693]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32693]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32694]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32694]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32695]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32695]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3[32697]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32697]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32698]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32698]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 pop3s[32701]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3s[32701]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > Dec 5 14:14:43 server_1 sieve[32686]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 sieve[32692]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32696]: IOERROR: > mapping /communication/var/lib/imap/mailboxes.db file: Invalid argument > Dec 5 14:14:43 server_1 pop3[32696]: Fatal error: failed to > mmap /communication/var/lib/imap/mailboxes.db file > > .... > and so on. > > With google I didn?t find that anything about this problem. Is it unknown, > already solved or something concerned with my setup?? > > Server is a DELL Poweredge with EMC CLARiiON SAN > System SuSE SLES9 SP3+ > -> 2.6.5-7.244-smp Kernel with (...> modinfo ocfs2): > license: GPL > author: Oracle > version: 1.1.7-SLES 5AF01E6455FC04917FE52FB > description: OCFS2 1.1.7-SLES Tue Nov 1 14:45:27 PST 2005 (build sles) > depends: ocfs2_nodemanager,ocfs2_dlm,jbd > supported: yes > vermagic: 2.6.5-7.244-smp SMP gcc-3.3 > > and in addition > DELL/EMC PowerPath 4.5.1 for Linux > to use the multiple path environment (not GPL multipath) > > Thanks > Hartmut Woehrle > > > >_______________________________________________ Ocfs2-users mailing list Ocfs2-users@oss.oracle.com http://oss.oracle.com/mailman/listinfo/ocfs2-users
hartmut.woehrle@mail.pcom.de
2006-Dec-06 02:33 UTC
[Ocfs2-users] OCFS2 and berkeley database files
Am Mi, 6.12.2006, 09:35, schrieb Michael Wood:> > Berkeley DB does have problems with certain filesystems (e.g. > NFS) so maybe this is a similar issue. (Just a wild guess.) >Yes I found the Orcale FAQ. So it is s structural problem with a "simple" DB and then trying to open it more than once> > OpenLDAP supports various different backends. Maybe one of the > others will work better? >Perhaps, but my guess is, that the funktionality of an cluster filesystem always uses an access to every file, even if it is not connected to a service. So I think it will not work if theses files are not able to handle more than one access at one time.> > > Cyrus also supports various different database types for its > databases. Maybe try one of the others. I have never used either OpenLDAP > or Cyrus on ocfs2, so I can't guarantee anything :)Same as above> > >> Server is a DELL Poweredge with EMC CLARiiON SAN >> System SuSE SLES9 SP3+ >> -> 2.6.5-7.244-smp Kernel with (...> modinfo ocfs2): >> license: GPL >> author: Oracle >> version: 1.1.7-SLES 5AF01E6455FC04917FE52FB >> description: OCFS2 1.1.7-SLES Tue Nov 1 14:45:27 PST 2005 (build >> sles) depends: ocfs2_nodemanager,ocfs2_dlm,jbd >> supported: yes >> vermagic: 2.6.5-7.244-smp SMP gcc-3.3 >> > [snip] > > > 2.6.5-7.244 was released with SLES9 SP3. You might want to > patch your box to 2.6.5-7.282 (which I think is the latest.) > > The 7.282 version of the SLES9 SP3 kernel comes with ocfs2 > version 1.2.1-SLES.Yes, but this EMC multipath software installs some kernelmodules (binaries, no sources) and they only match with the kernels in the list. So I have to wait for the next release :(((> > On the ocfs2 homepage it says: > > > SuSE Linux Exterprise Server 9: OCFS2 1.2.1 is bundled > with the SLES9 SP3 (2.6.5-7.257 and later) release. SLES9 users must > upgrade to the latest SP3 kernel (2.6.5-7.257 or later) and install > ocfs2-tools and ocfs2console packages. For more on OCFS2 bundling with > SLES9, refer to the Novell SLES9 section in the FAQ >See above> > -- > Michael Wood <michael.wood@uct.ac.za> > >
Am Mittwoch, 6. Dezember 2006 01:04 schrieben Sie:> It is IMHO not a good idea (not needed, less reliable, much slower) to > cluster LDAP servers like that. Just use a local file system on each server > and use replication. >Of course, but if you want to setup a failover cluster with an active-passive configuration, it is a possibility to use a setup with a shared volume without sync.> Gruss > Bernd >Gr?sse aus dem S?den Hartmut -- ========================================== Hartmut Woehrle EMail: hartmut.woehrle@mail.pcom.de