Amavis meldet Problem mit BerkeleyDB

Postfix, QMail, Sendmail, Dovecot, Cyrus, Courier, Anti-Spam
hassmann
Posts: 5
Joined: 2006-06-01 17:27

Amavis meldet Problem mit BerkeleyDB

Post by hassmann » 2006-06-01 17:33

Beim Starten von Amavisd-new erhalte ich folgende Meldung:

Code: Select all

stargate:/usr/lib64 # rcamavis start
Starting virus-scanner (amavisd-new):                                 done
stargate:/usr/lib64 # Problem in Amavis::DB or Amavis::DB::SNMP code: Can't locate BerkeleyDB.pm in @INC (@INC contains: /usr/lib/perl5/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/5.8.5 /usr/lib/perl5/site_perl/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.8.5 /usr/lib/perl5/vendor_perl) at (eval 51) line 11.
BEGIN failed--compilation aborted at (eval 51) line 11.
Asche auf mein Haupt: ich habe am laufenden System versucht, eine Open-Exchange Installation vorzunehmen. Bei der LDAP-Installation konnte das Skript die Berkeley DB nicht finden, ergo habe ich eine neue installiert - ohne zu berücksichtigen, dass bereits eine Version drauf war.
Und jetzt steh ich da :roll:

Berkeley Libraries:
/usr/local/BerkeleyDB.4.4/lib/libdb-4.2.so
/usr/local/BerkeleyDB.4.4/lib/libdb-4.3.so
/usr/local/BerkeleyDB.4.4/lib/libdb-4.4.a
/usr/local/BerkeleyDB.4.4/lib/libdb-4.4.la
/usr/local/BerkeleyDB.4.4/lib/libdb-4.4.so
/usr/local/BerkeleyDB.4.4/lib/libdb-4.so
/usr/local/BerkeleyDB.4.4/lib/libdb.a
/usr/local/BerkeleyDB.4.4/lib/libdb.so

Roger Wilco
Administrator
Administrator
Posts: 6001
Joined: 2004-05-23 12:53

Re: Amavis meldet Problem mit BerkeleyDB

Post by Roger Wilco » 2006-06-01 20:54

Installiere das Paket perl-BerkeleyDB.

hassmann
Posts: 5
Joined: 2006-06-01 17:27

Re: Amavis meldet Problem mit BerkeleyDB

Post by hassmann » 2006-06-01 23:13

habe die 4.4 er BerkeleyDB wieder runtergenommen und die vorherige Berkeley VErsion draufgelassen.

Nun kommt folgende Meldung beim Starten von Amavisd-new:

Code: Select all

stargate:/etc # Problem in Amavis::DB or Amavis::DB::SNMP code: Can't load '/usr/lib/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/auto/BerkeleyDB/BerkeleyDB.so' for module BerkeleyDB: libdb-4.2.so: cannot open shared object file: No such file or directory at /usr/lib/perl5/5.8.5/x86_64-linux-thread-multi/XSLoader.pm line 68.
 at (eval 51) line 11
Compilation failed in require at (eval 51) line 11.
BEGIN failed--compilation aborted at (eval 51) line 11.
Undefined subroutine &BerkeleyDB::Term::close_everything called at /usr/lib/perl5/vendor_perl/5.8.5/x86_64-linux-thread-multi/BerkeleyDB.pm line 1574.
END failed--call queue aborted.

Roger Wilco
Administrator
Administrator
Posts: 6001
Joined: 2004-05-23 12:53

Re: Amavis meldet Problem mit BerkeleyDB

Post by Roger Wilco » 2006-06-01 23:18

Roger Wilco wrote:Installiere das Paket perl-BerkeleyDB.
Was hat dir an dem Vorschlag nicht gefallen?

Fehlermeldungen gründlich zu lesen hat übrigens sehr oft Vorteile...

hassmann
Posts: 5
Joined: 2006-06-01 17:27

Re: Amavis meldet Problem mit BerkeleyDB

Post by hassmann » 2006-06-01 23:21

ich habe seitdem posting bereits weiter probiert, sorry.
hielt es für das beste die ausgangslage wiederherzustellen, da ja bereits vorher alles lief.

perl-BerkeleyDB ist auch installiert gewesen bei der ausgangslage.

gründlich lesen - mag sein - wenn man aber nicht so sehr viel erfahrungen mit linux hat - hilft einem das auch nicht sehr viel *heul*

hassmann
Posts: 5
Joined: 2006-06-01 17:27

Re: Amavis meldet Problem mit BerkeleyDB

Post by hassmann » 2006-06-01 23:42

ist dass denn normal?

Code: Select all

Jun  1 23:39:58 stargate postfix/qmgr[5798]: F14061174C5: to=<info@localhost.bitwerk.local>, orig_to=<info@localhost>, relay=none, delay=55912, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]: Connection refused)
info@localhost.bitwerk.local???

stimmt das so?

der server heißt stargate,
die domain stargate.bitwerk.local....

hassmann
Posts: 5
Joined: 2006-06-01 17:27

Re: Amavis meldet Problem mit BerkeleyDB

Post by hassmann » 2006-06-06 15:53

berkeleydb 4.4 habe ich nun soweit am laufen.

ldap läuft nun auch:
Code:

Code: Select all

ldapsearch -x -D "cn=Manager,dc=stargate,dc=bitwerk,dc=local" -w secret -h localhost
ergibt

Code: Select all

# extended LDIF
#
# LDAPv3
# base <> with scope sub
# filter: (objectclass=*)
# requesting: ALL
#

# stargate.bitwerk.local
dn: dc=stargate,dc=bitwerk,dc=local
objectClass: dcObject
objectClass: organization
dc: stargate
o: Bitwerk Gmbh & Co. KG

# OxObjects, stargate.bitwerk.local
dn: ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
objectClass: top
objectClass: organizationalUnit
ou: OxObjects

# Users, OxObjects, stargate.bitwerk.local
dn: ou=Users,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
objectClass: top
objectClass: organizationalUnit
ou: Users

# Groups, OxObjects, stargate.bitwerk.local
dn: ou=Groups,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
objectClass: top
objectClass: organizationalUnit
ou: Groups

# ResourceObjects, OxObjects, stargate.bitwerk.local
dn: ou=ResourceObjects,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
objectClass: top
objectClass: organizationalUnit
ou: ResourceObjects

# ResourceGroups, ResourceObjects, OxObjects, stargate.bitwerk.local
dn: ou=ResourceGroups,ou=ResourceObjects,ou=OxObjects,dc=stargate,dc=bitwerk,d
 c=local
objectClass: top
objectClass: organizationalUnit
ou: ResourceGroups

# Resources, ResourceObjects, OxObjects, stargate.bitwerk.local
dn: ou=Resources,ou=ResourceObjects,ou=OxObjects,dc=stargate,dc=bitwerk,dc=loc
 al
objectClass: top
objectClass: organizationalUnit
ou: Resources

# AdminObjects, OxObjects, stargate.bitwerk.local
dn: ou=AdminObjects,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
objectClass: top
objectClass: organizationalUnit
ou: AdminObjects

# SMTPObjects, AdminObjects, OxObjects, stargate.bitwerk.local
dn: ou=SMTPObjects,ou=AdminObjects,ou=OxObjects,dc=stargate,dc=bitwerk,dc=loca
 l
objectClass: top
objectClass: organizationalUnit
ou: SMTPObjects

# DNSObjects, AdminObjects, OxObjects, stargate.bitwerk.local
dn: ou=DNSObjects,ou=AdminObjects,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
objectClass: top
objectClass: organizationalUnit
ou: DNSObjects

# AddressBook, OxObjects, stargate.bitwerk.local
dn: o=AddressBook,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
objectClass: top
objectClass: organization
o: AddressBook

# AddressAdmins, AddressBook, OxObjects, stargate.bitwerk.local
dn: cn=AddressAdmins,o=AddressBook,ou=OxObjects,dc=stargate,dc=bitwerk,dc=loca
 l
objectClass: top
objectClass: groupOfNames
cn: AddressAdmins
member: uid=mailadmin,ou=Users,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
member: uid=mhassmann,ou=Users,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local

# search result
search: 2
result: 0 Success

# numResponses: 13
# numEntries: 12


Hier das Protokoll vom Start des openxchange-Dienstes:

Code: Select all

Jun 06 15:40:14 localhost openexchange: Netline Application Server [NAS 5.0]
Jun 06 15:40:14 localhost openexchange: (c) Netline Internet Service GmbH
Jun 06 15:40:14 stargate openexchange: Linux i386 2.6.8-24-default
Jun 06 15:40:14 stargate openexchange: 1.4.2_10-b03
Jun 06 15:40:14 stargate openexchange: VM Total Memory       : 20.352 KB
Jun 06 15:40:14 stargate openexchange: VM Free Memory        : 19.826 KB
Jun 06 15:40:14 stargate openexchange: VM Used Memory        : 526 KB
Jun 06 15:40:14 stargate openexchange: System version : Open-Xchange Server [0.8.2] initializing ...
Jun 06 15:40:14 stargate openexchange: Using path: /usr/local/open-xchange/
Jun 06 15:40:14 stargate openexchange: Loglevel set to: 5
Jun 06 15:40:14 stargate openexchange: No LDAP Addressbook Config-file found!
Jun 06 15:40:14 stargate openexchange: Setting timeout           : 60000
Jun 06 15:40:14 stargate openexchange: Setting start_server      : 1
Jun 06 15:40:14 stargate openexchange: Setting thread_pool       : 0
Jun 06 15:40:14 stargate openexchange: Setting db_pool           : 5
Jun 06 15:40:14 stargate openexchange: Allow non pooled threads  : true
Jun 06 15:40:14 stargate openexchange: Setting upload directory  : /tmp/
Jun 06 15:40:15 stargate openexchange: INFO: DefaultEncoding : UTF-8
Jun 06 15:40:15 stargate openexchange: INFO: UserCanSelectEncoding : false
Jun 06 15:40:15 stargate openexchange: INFO: UseServerSearch : false
Jun 06 15:40:15 stargate openexchange: INFO: UseServerSort   : false
Jun 06 15:40:15 stargate openexchange: INFO: DateFormat[DE]  : EEE dd.MM.yyyy HH:mm
Jun 06 15:40:15 stargate openexchange: INFO: DateFormat[EN]  : MMM dd, yyyy hh:mm aaa
Jun 06 15:40:15 stargate openexchange: INFO: Use Html-Editor : true
Jun 06 15:40:15 stargate openexchange: INFO: Mail list style : SEARCH:SCROLL:SORT:LIST:MOVECOPY:DELETE
Jun 06 15:40:15 stargate openexchange: INFO: Max. entries    : 500
Jun 06 15:40:15 stargate openexchange: INFO: Address book display name : ${lastname}, ${firstname}
Jun 06 15:40:15 stargate openexchange: INFO: Entries on page : 10,15,20,25,50,75,100,125,150,175,200,250,500
Jun 06 15:40:15 stargate openexchange: INFO: Quoted Colors   : #a14044,#917722,#599351,#516193,#666666
Jun 06 15:40:15 stargate openexchange: INFO: Disp. size lim. : 1000000 bytes
Jun 06 15:40:15 stargate openexchange: INFO: Autocomplete max. Entries : 50
Jun 06 15:40:15 stargate openexchange: INFO: Quota Warn      : 90%
Jun 06 15:40:15 stargate openexchange: INFO: Hide Empty Folder Button : false
Jun 06 15:40:15 stargate openexchange: INFO: User can select default addr : true
Jun 06 15:40:15 stargate openexchange: INFO: Content Type Selection Filter : application/.*
Jun 06 15:40:15 stargate openexchange: INFO: Fax Enabled : false
Jun 06 15:40:15 stargate openexchange: INFO: Internal Addressbook disabled : false
Jun 06 15:40:15 stargate openexchange: INFO: SenderName : ${firstname} ${lastname}
Jun 06 15:40:15 stargate openexchange: INFO: Folder Message Count View : (${TOTAL}/${UNSEEN}) (TOTAL: true, RECENT: false, UNSEEN: true)
Jun 06 15:40:15 stargate openexchange: INFO: Message Fetch Limit : 1000
Jun 06 15:40:15 stargate openexchange: INFO: Reload time : 300000
Jun 06 15:40:15 stargate openexchange: INFO: Put parameter 'seq-serial_id=SELECT nextval ('serial_id')' to GlobalConfig store
Jun 06 15:40:15 stargate openexchange: INFO: Put parameter 'sql-fieldmapname-usrdata_delete=delete' to GlobalConfig store
Jun 06 15:40:15 stargate openexchange: INFO: Read webmail.properties: default.sent=INBOX/Sent
Jun 06 15:40:15 stargate openexchange: INFO: Read webmail.properties: default.trash=INBOX/Trash
Jun 06 15:40:15 stargate openexchange: INFO: Read webmail.properties: default.drafts=INBOX/Drafts
Jun 06 15:40:15 stargate openexchange: INFO: Read webmail.properties: default.spam=INBOX/Spam
Jun 06 15:40:15 stargate openexchange: INFO: Read webmail.properties: default.folder.autocreate=false
Jun 06 15:40:16 stargate openexchange: INTERNAL TLS Support: OFF
Jun 06 15:40:16 stargate openexchange: bind to port 4445
Jun 06 15:40:16 stargate openexchange: upload bind to port 4447

Mein Problem habe ich nun immer noch beim Einloggen über des Webinterface:

Code: Select all

Jun 06 15:40:10 localhost openexchange: Sessiond init (localhost:33333) objectstream=false
Jun 06 15:40:10 localhost openexchange: INTERNAL TLS Support: OFF
Jun 06 15:40:10 localhost openexchange: Sessiond init (localhost:33335) objectstream=true
Jun 06 15:44:34 localhost openexchange: NamingException: ldap-master.stargate.bitwerk.local:666
Jun 06 15:44:34 localhost openexchange: findUser: java.lang.NullPointerException
java.lang.NullPointerException
        at com.openexchange.sessiond.SocketHandler.findUser(SocketHandler.java:295)
        at com.openexchange.sessiond.SocketHandler.access$2(SocketHandler.java:72)
        at com.openexchange.sessiond.SocketHandler$SessionThread.run(SocketHandler.java:440)
        at java.lang.Thread.run(Thread.java:534)
Jun 06 15:44:34 localhost openexchange: ERROR: Authentification failed
Jun 06 15:44:34 localhost openexchange: ERROR: Authentification failed


Ein ldappadd zuvor hat jedoch ohne meckern funktioniert:

Code: Select all

./adduser_ox --username=test --passwd=testpasswort --name=Marcus --sname=Hassmann --maildomain=smtp.bitwerk.de --ox_timezone=Europe/Berlin
ldapsearch -H ldap://localhost/ -D cn=Manager,dc=stargate,dc=bitwerk,dc=local -w secret -x -b ou=Users,ou=OxObjects,dc=stargate,dc=bitwerk,dc=local
LDAP Success
SQL Success

Die Zeile "NamingException: ldap-master.stargate.bitwerk.local:666" scheint ja wohl ausschlaggebend zu sein.
In der Datei ldap.conf habe ich aber die URL ausgeklammert, geändert, danach ldap und openexchange bereits neu gestartet. Derselbe Effekt jeweils.

Hat da jemand eventuell einen Hinweis?