Exit Class for Inbound Mail not getting triggered
Hi Gurus,
I have created an exit class for processing the Inbound Mail that comes to SAP Inbox (SOIN).
I have set up the Inbound processing rule in transaction SO50 and set it to all recipients.
If i send a mail from any external id to the id configured in SAP then it is coming in SAP Inbox (SOIN) but the exit class for processing the email is not getting triggered.
I have made all the settings for SMTP.
Kindly guide me with the steps needed to be followed for triggering the Exit Class.
Hi
Check u have maintained ur outgoing mail server IP in SCOT transation.
Check link step to configure PO mail.
http://architectsap.com/blog/sap/sap-mm-purchasing-send-purchase-order-by-mail-to-vendor-in-sap/
Similar Messages
-
RSR_OLAP_BADI for virtual characteristics not getting triggered!!!
I am facing a strange problem and am a little pressed for time to solve the same. Any help/guidance related to this will be highly appreciated.
I am working on BI 7.0. I have two implementations of the BADI RSR_OLAP_BADI for virtual characteristics,
(1) say A, that we implemented as a proof of concept with filter as multiprovider M1
(2) say B, that in implemented with filter as multiprovider M2
Both were working fine and I was able to put breakpoints inside the code and debug whenever required. I had used it till last week and everything was fine.
Today, I had to change implementation B due to a new requirement. So a new characteristic was added to M2 and the code in B was extended at appropriate places to fill this new virtual characteristic also. However, even though the change was successfully activated and the BADI looked fine, it was not triggered when the query was executed. I checked with another query on M2 which was the query for which the implementation was initially made. For that also the BADI is not getting triggered. I put break points in the define, initialize and compute methods but none are hit during the query execution!
I further ran the queries on M1, which shud have called the implementation A. Then also the BADI is not getting triggered. Please note that implementation A, multiprovider M1 or the queries on it were not changed at all.
I really need to fix this issue at the earliest. What am I missing? Why are the BADIs not getting triggered eventhough the implementations are active, the BADIs are error free and the filters are correctly defined?
Are there any global settings that can turn off all BADIs?
Please help.
Thanks,
SarathFurther, when I created a fresh BADI implementation in a different system (a sandbox system), the BADI is working fine.
But in the Development system the BADIs are still not getting triggered. I made the exact same implementation as the one which worked in the different system.
Another point - when I see the Technical Information tab of queries from RSRT, or RSRT2 they have Virtual Characteristics/Key Figures "NO" in the development system.
For the queries in the prototype system in which the BADI is working this field in "Y".
Any idea how this is decided and how it can be changed to Y from NO?
One more strange thing is that there are other active implementation of this BADI used by other teams here and none of them are getting triggered. They are all active and were all working fine till the last few days!
Any help will be highly appreciated.
Thanks,
Sarath -
Mail not getting triggerred from Alerts in PI 7.1
Dear Freinds,
We have created alert categories and based on that created numbers of alert rules. Alerts are getting triggered and we recieve them in the Alert Inbox. We have also maintained user id's in Fixed Reciepents. But we want the same to go to email based on the user profile.
Please let us know what has to be done in order to recieve email as soon as alerts are getting triggered.
Thanks & Regards
JohnHi Kroninjer,
To send an EMAIL, assign an EMAIL ID to the corresponding user in the transaction SU01 and then set up SCOT and you can send emails when the ALERT is triggered..
Once you have configure Alerts, you will get the Alerts into ALERT INBOX in RWB of the user. To also get the email, the following needs to be done,
1. In SU01 -- Assign the Email ID for the Recipient of the ALERT.
2. In , RWB>ALERT INBOX> PERSONALIZATION--> Time Independent Delivery and Email are selected.
3. Finally, SCOT needs to be set up to send Emails. Check this for the same. You can ask your BASIS team to do this step.
http://help.sap.com/saphelp_nw04/helpdata/en/23/1edf098ea211d2b47300609419ed29/frameset.htm
Also, In ALRTCATDEF, go to SETTINGS--> CONFIGURATION. By default, the option selected is INTERNAL PROCESSING. Select the option SMTP FORWARDING AS XML and give the email id. This will enable you to send an email alert whenever an error occurs in XI.
4) Notes:
750287 XI 3.0 Runtime Workbench: Alert configuration does not start
768456 Troubleshooting Runtime Workbench XI 3.0
813703 XI RWB alert configuration is incompletely displayed
840849 XI 3.0 Runtime Workbench: SSO2 is not active in this system
824039 XI30 Runtime Workbench: Display of XI alerts in CCMS
0000906044 XI30 Alerting: Wrong hostname in the URL of the XI Alert
0000905896 XI30 Alerting: Message without recipient creates no alert
0000904825 Synchronous message processing: Error in CCMS connection
0000902022 XI30 Alertrule insensitive to Receiver Interface
0000882215 XI 3.0 Runtime Wkbnch: Java Adaptr does not generate alerts
0000876546 XI 3.0 Runtime Workbench: Missing alerts
0000870232 XI 3.0 Runtime Workbench: New Alerting functionality
But start with this one!!!
913858 XI3.0 Alerting: Troubleshooting
Hope all these will help you.....Though assuming that you have configured alerts correctly it should work as it worked for me :-).
Regards, -
Inbound mail not getting delivered - intermittent
Hi.
We are running Server 10.3.9 on an XSERVE. Ever since using mailfbr to fix a database corruption, mail is not being delivered to us by at least one sender we know about. Can't find his email in the logs or mailq, but he gets a bounce with a header indicating our mailserver has rejected his email. I have turned off all filters, repaired privileges, rerun mailfbr several times and sudo postsuper -r ALL but nothing seems to work. His emails keep bouncing.
I don't believe there are any spam or virus routines running, but I did not set the server up initially and am trying to relearn my way around unix. Any help, ideas, etc. would be greatly appreciated.Mark,
Do you see this message as sitting in your queue? (It
hasn't bounced it just wasn't delivered yet).
Not anymore.
The logs are in /var/log
look for mail.log and mailaccess.log
mailaccess.log
Feb 14 14:51:44 localhost pop3[7497]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost pop3[7497]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost pop3[7497]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost pop3[7497]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost pop3[7497]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost imap[7495]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7495]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7495]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7495]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost lmtpunix[7494]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7494]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7494]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7494]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7494 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost master[349]: service imap pid 7495 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7499]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7499]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7499]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7499]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7499]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7499]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7499]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service imap pid 7499 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7500]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7500]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7500]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7498]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7498]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7498 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost master[349]: service pop3 pid 7497 in READY state: terminated abnormally
Feb 14 14:51:44 localhost pop3[7502]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7500]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7500]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7500]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7500]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service imap pid 7500 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7503]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7503]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7503]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7501]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7501]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7501 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7503]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7503]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7503]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7503]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:44 localhost lmtpunix[7504]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:44 localhost lmtpunix[7504]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:44 localhost master[349]: service lmtpunix pid 7504 in READY state: terminated abnormally
Feb 14 14:51:44 localhost lmtpunix[7505]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost lmtpunix[7505]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost lmtpunix[7505]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost pop3[7502]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost pop3[7502]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost pop3[7502]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service pop3 pid 7502 in READY state: terminated abnormally
Feb 14 14:51:44 localhost pop3[7506]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost pop3[7506]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost pop3[7506]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost master[349]: service imap pid 7503 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7507]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7507]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7507]: DBERROR: init() on berkeley
Feb 14 14:51:44 localhost imap[7507]: DBERROR db4: environment not yet opened
Feb 14 14:51:44 localhost imap[7507]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:44 localhost imap[7507]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:44 localhost imap[7507]: Fatal error: can't read mailboxes file
Feb 14 14:51:44 localhost master[349]: service imap pid 7507 in READY state: terminated abnormally
Feb 14 14:51:44 localhost imap[7508]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:44 localhost imap[7508]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:44 localhost imap[7508]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7506]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7505]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7505]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7505]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7505]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7505 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7506]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7506]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7506]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7506 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7510]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7508]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7508]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7508]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7508]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7508 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7511]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7511]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7511]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7510]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7510]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7510]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7510 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7512]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7512]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7512]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7512]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7512 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7513]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7509]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7509]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7509 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7513]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7514]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7514]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7514 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7511]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7511]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7511]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7511]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7511 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7516]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7516]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7516]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7513]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7513]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7513 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7517]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7515]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7515]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7515 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7517]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7517]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7517]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7517 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7519]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7519]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7519]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7519]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7519 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7520]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7520]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7520]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7520]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7520 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7521]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7518]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7518]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7518 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7522]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7522]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost imap[7516]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7516]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7516]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7516]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7516 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7523]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7523]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7523]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7521]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7522 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7521]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7521]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7521 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7525]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:45 localhost lmtpunix[7524]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:45 localhost lmtpunix[7524]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:45 localhost master[349]: service lmtpunix pid 7524 in READY state: terminated abnormally
Feb 14 14:51:45 localhost lmtpunix[7526]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost lmtpunix[7526]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost lmtpunix[7526]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7525]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7523]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7523]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7523]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7523]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7523 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7527]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7527]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7527]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost pop3[7525]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost pop3[7525]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service pop3 pid 7525 in READY state: terminated abnormally
Feb 14 14:51:45 localhost pop3[7528]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost pop3[7528]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost pop3[7528]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7527]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7527]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7527]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7527]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7527 in READY state: terminated abnormally
Feb 14 14:51:45 localhost imap[7529]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:45 localhost imap[7529]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:45 localhost imap[7529]: DBERROR: init() on berkeley
Feb 14 14:51:45 localhost imap[7529]: DBERROR db4: environment not yet opened
Feb 14 14:51:45 localhost imap[7529]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:45 localhost imap[7529]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:45 localhost imap[7529]: Fatal error: can't read mailboxes file
Feb 14 14:51:45 localhost master[349]: service imap pid 7529 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7530]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7530]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7530]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7528]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7526]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7526]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7526]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7526]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7526 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7528]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7528]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7528]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7528 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7532]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7530]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7530]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7530]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7530]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7530 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7533]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7533]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7533]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7533]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7533]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7533]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7533]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7533 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7534]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7534]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7534]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7531]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7531]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7531 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7532]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7532]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7532]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7532 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7536]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7535]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7535]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7535 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7536]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7536]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7536]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7536 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7538]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7534]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7534]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7534]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7534]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7534 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7539]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7539]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7539]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7537]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7537]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7537 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7538]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7538]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7538]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7538 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7541]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7539]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7539]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7539]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7539]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost pop3[7541]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7541]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7541]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7541 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7542]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7540]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7540]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7540 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7543]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7543]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7543 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost master[349]: service imap pid 7539 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7545]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7545]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7545]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7542]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7542]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7542]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7542 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7546]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7544]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7544]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7544 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost pop3[7546]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost pop3[7546]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost pop3[7546]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service pop3 pid 7546 in READY state: terminated abnormally
Feb 14 14:51:46 localhost pop3[7548]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost pop3[7548]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost pop3[7548]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7547]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7547]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7547 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost imap[7545]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost imap[7545]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:46 localhost imap[7545]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:46 localhost imap[7545]: Fatal error: can't read mailboxes file
Feb 14 14:51:46 localhost master[349]: service imap pid 7545 in READY state: terminated abnormally
Feb 14 14:51:46 localhost imap[7550]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost imap[7550]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost imap[7550]: DBERROR: init() on berkeley
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR db4: environment not yet opened
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:46 localhost lmtpunix[7549]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:46 localhost lmtpunix[7549]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:46 localhost master[349]: service lmtpunix pid 7549 in READY state: terminated abnormally
Feb 14 14:51:46 localhost lmtpunix[7551]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:46 localhost lmtpunix[7551]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:46 localhost lmtpunix[7551]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7550]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7550]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7550]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7550]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost pop3[7548]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7548]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7548]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7548]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7548 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7552]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7551]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7551]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7551]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7551]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7551 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7552]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7552]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7552]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7552 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7554]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost master[349]: service imap pid 7550 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7555]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7555]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7555]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7553]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7553]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7553 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7555]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7554]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7554]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7555]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7555]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7555]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7555 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7557]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7557]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7557]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7557]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7557]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7557]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7557]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7557 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7558]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7558]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7558]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7558]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7558]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7558]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7558]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7558 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7559]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7559]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7559]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7556]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7556]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7556 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7560]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7560]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7560 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7554]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7554 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7562]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7561]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7561]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7561 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7559]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7559]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7559]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7559]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7559 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7564]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7564]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7564]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7562]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7562]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7562]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7562 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7565]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7563]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7563]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7563 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7565]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7565]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7565]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7565 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7567]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7567]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7567]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7567]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7567 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7568]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7564]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7564]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7564]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7564]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7564 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7569]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7569]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7569]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7566]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7566]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7566 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:47 localhost lmtpunix[7570]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:47 localhost lmtpunix[7570]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:47 localhost master[349]: service lmtpunix pid 7570 in READY state: terminated abnormally
Feb 14 14:51:47 localhost lmtpunix[7571]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost lmtpunix[7571]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost lmtpunix[7571]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7568]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7568]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7568]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7568 in READY state: terminated abnormally
Feb 14 14:51:47 localhost pop3[7572]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost imap[7569]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost imap[7569]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost imap[7569]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost imap[7569]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service imap pid 7569 in READY state: terminated abnormally
Feb 14 14:51:47 localhost imap[7573]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:47 localhost imap[7573]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:47 localhost imap[7573]: DBERROR: init() on berkeley
Feb 14 14:51:47 localhost pop3[7572]: DBERROR db4: environment not yet opened
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:47 localhost pop3[7572]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:47 localhost pop3[7572]: Fatal error: can't read mailboxes file
Feb 14 14:51:47 localhost master[349]: service pop3 pid 7572 in READY state: terminated abnormally
Feb 14 14:51:48 localhost pop3[7574]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost lmtpunix[7571]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost lmtpunix[7571]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:48 localhost lmtpunix[7571]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:48 localhost lmtpunix[7571]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:48 localhost master[349]: service lmtpunix pid 7571 in READY state: terminated abnormally
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost pop3[7574]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost pop3[7574]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost pop3[7574]: Fatal error: can't read mailboxes file
Feb 14 14:51:48 localhost master[349]: service pop3 pid 7574 in READY state: terminated abnormally
Feb 14 14:51:48 localhost pop3[7576]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:48 localhost lmtpunix[7575]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:48 localhost lmtpunix[7575]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:48 localhost master[349]: service lmtpunix pid 7575 in READY state: terminated abnormally
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: opening /var/imap/deliver.db: Invalid argument
Feb 14 14:51:48 localhost lmtpunix[7577]: DBERROR: opening /var/imap/deliver.db: cyrusdb error
Feb 14 14:51:48 localhost lmtpunix[7577]: FATAL: lmtpd: unable to init duplicate delivery database
Feb 14 14:51:48 localhost master[349]: service lmtpunix pid 7577 in READY state: terminated abnormally
Feb 14 14:51:48 localhost lmtpunix[7578]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost lmtpunix[7578]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost lmtpunix[7578]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost pop3[7576]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost pop3[7576]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost pop3[7576]: Fatal error: can't read mailboxes file
Feb 14 14:51:48 localhost master[349]: service pop3 pid 7576 in READY state: terminated abnormally
Feb 14 14:51:48 localhost pop3[7579]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost pop3[7579]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost pop3[7579]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost imap[7573]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost imap[7573]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost imap[7573]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost imap[7573]: Fatal error: can't read mailboxes file
Feb 14 14:51:48 localhost master[349]: service imap pid 7573 in READY state: terminated abnormally
Feb 14 14:51:48 localhost imap[7580]: DBERROR db4: fatal region error detected; run recovery
Feb 14 14:51:48 localhost imap[7580]: DBERROR: dbenv->open '/var/imap/db' failed: DB_RUNRECOVERY: Fatal error, run database recovery
Feb 14 14:51:48 localhost imap[7580]: DBERROR: init() on berkeley
Feb 14 14:51:48 localhost pop3[7579]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost imap[7580]: DBERROR db4: environment not yet opened
Feb 14 14:51:48 localhost imap[7580]: DBERROR: opening /var/imap/mailboxes.db: Invalid argument
Feb 14 14:51:48 localhost imap[7580]: DBERROR: opening /var/imap/mailboxes.db: cyrusdb error
Feb 14 14:51:48 localhost imap[7580]: Fatal error: can't read mailboxes f -
Trouble shooting for work flow not getting triggered
Hi everyone,
I am doin a work flow for which the zfipp-> created event is the trigeering event.
I parked a document using FB03,but still the workflow is not geeting trigered.
I checked SWEL ,i see that the event is trigered.
Also whe i simulate the event using SWU0
I see that the workflow triggeres then.
Any advice where the problem could be..
regards,
AdityaHi,
Have u done the event linkaga?
If not goto SWE2 and do the event linkage.
Thanks and Regards -
How to use inbound exit class for more than one workflow step
Hi All,
In Offline Workflow Approval Scenarios where the work items are sent to outlook of non sap users inbox through workitem exit of the respective workflow item. Based on the user reply from outlook email(either approve or reject) which sends an auto reply to Offline user . We configure an inbound exit class and assign the same in the SMICM transaction. Based on the code written using SAP_WAPI function modules in inbound class exit offline user gets the user approval result and performs the action in SAP.
My question now Is how can we use this inbound exit class for all the steps of a workflow.
For ex: In a workflow I have a decision step followed by an activity step. First I will write the work item exit for the user decision step and inbound exit code for the user decision step and offline user executed the user decision step with approve action.
followed by that I have an activity step for that I will code a work item exit for that activity level but how can I user the same inbound exit class for the activity step as well .
Quick reply would be of great help for me.
With Best Regards,
VeniFor the outbound processing you have the option of replacing the workflow exit by chancing the bsp application of the extended notification (see note 1448241 solution as an example of how to do the change) and replacing the standard links with a "mailto:...".
As far as the inbound processing, that depends on what should be done in the activity step, if for example you have a bapi which executes what the user does you can call it in the inbound class instead of the user and then the relevant wapi (complete the workitem/raise event etc.). -
IDOC - Function Exit not getting triggered
I am doing an inbound IDOC for the message type WMMBXY and using basic type WMMBID02.
This is for goods movement based on PO.
I am doing an enhancement in the includeof the function module exit EXIT_SAPLLMDE_002.
This exit is supposed to get triggered for the message type WMMBXY.
when i tested the idoc in we19 it is sucessfully getting posted. I want to check my code in EXIT_SAPLLMDE_002. I have set breakpoint and tested using we19. But this is not getting triggered. But the idoc is getting sucessfully posted but with a status message 56 An inbound partner profile could not be found( I am not sure if this has something to do with above problem).Did you attach your exit to a CMOD project and activated the same(CMOD transaction)?
The error you see regarding the partner profiles is probably due to the non existance of a partner profile for your idoc type in we20 transaction.
Maintain the inbound partner profile in we20 transacttion. -
User Exit not getting triggered
Dear all,
we are creating a workflow for PR Release which needed release strategy customization. so we are trying to set the release stratagy by changing the communciation structure CEBAN-USRC1 field.
for this, i had done the following things:
1. SMOD->M06B0005->components->EXIT_SAPLEBND_004->INCLUDE ZXM06U31 (double clicked) wrote few lines of code.
2. CMOD-> created a proj ZMM_PREL->assigned Enhancement M06B0005 under enhancements tab-> EXIT_SAPLEBND_004-> activated all
(User exit, project eveything).
Now my problem is when i create a PR, this user exit does not get triggered at all. I am working on ECC6.0 the same code which i did in Ecc5.0 for my previous client is still working fine.
Can anyone please guide me where i might have gone wrong?
Thank you,
Regards,
LakshmiHi,
HAve u verifiyed that the user-exit u r using is triggered whenever u create ou PR.?
First of all u have to put breakpoints at each and every user-exits provided for that transaction, then check which user exit is getting triggered when u carete ur PR. and thenafter write ur code in this user-exit only.
Reward is useful.
Regards,
Harsha -
User-exit not getting triggered in VA32
Hello Experts,
Iu2019ve a requirement and Iu2019m working on Change Scheduling Agreement u2018t-code VA32u2019. According to requirement I need to capture all header data and data in Sales, Item Overview, Item Detail and Ordering party tabs. Iu2019ve set the break points in almost all the user-exits but only one FM (EXIT_SAPLV45L_002) of exit u2018V45L0001u2019 is getting trigger. Even though other exits/FM has all the tables as import/export parameters which I need but they are not getting triggered. Can anybody please tell me which user-exit / BADI I should use to capture the required data?
Thanks.Hello Experts,
Thanks a lot Vijay for you reply. Iu2019ve seen user exits of MV45AFZZ include and looks like USEREXIT_SAVE_DOCUMENT_PREPARE is the correct user exit. But I havenu2019t use Includes before can you or anybody else please tell me how to write code in include. I know how to search an include in a program but not sure how to add code in the user exit.
Thanks -
Userexit not getting triggered for 0CFM_CLASS_MASTER_DATA_ATTR
Hi Experts,
I have made enhancements to 0CFM_CLASS_MASTER_DATA_ATTR & 0CFM_FI_TRA_ATTR in RSAP0001(EXIT_SAPLRSAP_001). I have set the flag to New Data entry logic(Switch for Datasource feed) to populate the Timedependent attributes in 0CFM_CLASS_MASTER_DATA_ATTR .
I kept the break point in the Userexit and ran RSA3 for the above 2 datasources but the user exit is not getting triggered.
Can you please help why the userexit is not getting triggered?
Thanks,
bwuswer14.Hi,
Thanks for ur post.issue resolved.im keeping the breakpoint in 1st user exit.After keeping the breakpoint in EXIT_SAPLRSAP_002 it got triggered.Closing the thread.
Thanks,
bwuser14 -
Event not getting triggered for a few users in production
Hi Experts!!
We have a workflow that gets triggered on the event REQUESTCREATED of BUS2089. In production, we see that for a few users the event is getting triggered and even the workflow is. But for a few users, the workflow is not getting triggered. However, we didn't check SWEQADM yet and are waiting to get auth to check the same. But before that, I need your valuable suggestions on this.
When I check SWEL, I cannot see any entries at all. Not even for the successfully processed ones.
Auth objects cannot be a reason, as all the users have same auth. Please suggest me on what else can be the reasons.
Your help is highly appreciable.Hello Srinivas !
Check in SWEQADM to know whether the event is on queue.If so, redeliver it.
If there is no event on queue, check the RFC queue( transaction SWU2 ) and ST22 for possible ABAP dumps.
Call work item list report (transaction SWI1) and check event linkages (transaction SWETYPV )of the users for whom the event is not triggered.Are you using BAdI or user- exit to trigger the workflow ? If so, check whether those are in active state.
Refresh the workflow buffers(transaction SWU_OBUF).Check either of the workflow versions are in active state.
Regards,
S.Suresh -
Issue in Production for Workflow not getting Triggered .
Hi Guys,
I have a workflow, which is properly triggering in the development and Quality but not getting triggered in the Production. Can't get the Exaact reason because by using T-code PFTC when i test the workflow independantly its working properly and even BOR does not have any problem. Please Help me guys as this is a issue in Production.
The workflow is a customized one, It getting triggered throught the funtion call in User Exit of MM01.
ThanksIt getting triggered throught the funtion call in User Exit of MM01.
1. I hope the workflow customization is done properly in production system, as you stated that if you are trying to trigger from PFTC then it is working fine, can you please try to Refresh Organizational Environment from SBWP ---> On MEnu ---> Settings --> Workflow Settings ---> Refresh Organizational Environment and secondly try to refresh the buffer from txn SWU_OBUF
2. Make sure the user exit is transported to Production.
3. Check the workflow log from the txn SWIA if you have proper authorizations for the userid. -
Output type is not getting triggered for ship to party in shippment output
Hi,
we have maintained output determination procedure for shipments. It was working fine.
We have just added new condition table to access sequence, and maintained the condition records also for condition type ZABC. I have checked in NACE, Application V7, I am able to find the condition type. checked in VV73, condition records displayed. But in VT02N/VT03N, we are unable to get print for the output type.
Why this is happening? we are able to see the procedure, condition type, access sequence, condition records in place ...why condition type ZABC is not getting triggered in the shipment output.
Please advise and let me know if you need more details....thanks in advance.
Thanks,
SSHi Noel,
Thanks for your time and reply.
We have output determination procedure for shipments, condition type ZABC, Access sequence ZABC, Condition tables 550,600,650,700 already maintained. output is working fine.we have a new requirement and created new condition table 700 with the fields" Ship to party and transportation planing point "(Condition table 700 ). we assigned the condition table 700 to access sequence ZABC. Condition type ZABC already placed in Output determination procedure.
We test the output, new condition record is not triggering in the output, even in output determination analysis also, we are unable to see the record 700 for the condition type ZABC. we are not sure what is the reason for the condition table that is not picking up ? Why condition type ZABC with condition record 700 not visible in output determination analysis.
I have checked condition records, output determination procedure. Please advise and let me know you need more details.
Thanks,
SS -
User Exit not getting Triggered in Quality Server
Hi,
In FM 'IDOC_INPUT_DESADV' Iam using an User Exit 'EXIT_SAPLEINM_006' ,
which is getting triggered in Development server.But when I moved it to Quality,
The User Exit is not getting triggered.Thou the Exit is assigned to Enhancement
and that in turn is assigned to Project, still the problem persists.
Can any one suggest me what could be the problem.
Regards,
Kiran B.Kiran,
Check the <b>Project</b> of that enhancement is active or not. not the enhancement.
<b><REMOVED BY MODERATOR></b>
Satish
Message was edited by:
Alvaro Tejada Galindo -
For the new delivery type created the Idoc is not getting triggered
Hi All,
I am facing the following problem:
For every outbound delivery getting created we have an Idoc which creates the file(sending the outbound delivery details), this file is sent to a system where the picking & packing of the goods happen. This process seems to be working fine for all the existing delivery types, but now we created a new delivery type for which the Idoc is not getting triggered.
Would like to understand what setting are we missing because of which the Idoc is not getting created for the new delivery type.
The Idoc being used is: DESADV01
Message type :DESADV
Thanks,
GeetaI believe your existing idocs are created through a output type on the delivery ? if yes, probably you need to configure an existing output type / create a new output type for your new delivery type...
Maybe you are looking for
-
Can you change the color of selected text in word?
I use Word 2010, and when I select text it is always blue, is there a way to change the color?
-
Graphical Process Monitoring in CE?
Hi there, just getting to know the new BPM Feature with in the CE 7.11 and building some Business Processes. But I'm missing a graphical monitoring tool like in the Workflow Builder in ECC (Tx SWDD) to know exactly in which activity the business proc
-
How do I athorize my PC to play my iTunes
My computer keeps saying this computer isn't authorized? Help
-
Is it just me, but do others share the view that the tree menus available by default within APEX (2.0 - haven't seen 2.2.1 or 3.0) are pretty basic. Has anyone implemented anything more elegant or even third party menu's such as:- http://www.sothink.
-
XI3.0 - Quality of service EOIO file adapter
Hi, I have a number of IDOCS that are sent from a WAS6.40 system using a qRFC queue. These IDOCS are then sent to a number of receivers and inbound interfaces. A large number of the receivers are file adapters for which I would like to be able to di