JMS message not getting delivered

I'm trying to create a simple MDB with JDeveloper 10.1.3.2.
I've tried to configure the sender and receiver to use the embedded OC4J message service.
The code compiles and runs without any errors but the message doesn't seem to get delivered to the MDB.
How could I debug message delivery in this case?
What could be causing the message delivery to fail?
Here's the code from a session bean that sends the message:
@Resource(mappedName="jms/Topic/testTCF") private ConnectionFactory connectionFactory;
@Resource(mappedName="jms/Topic/testTopic") private Topic topic;
public void sendMessage() {
try {
Connection con = connectionFactory.createConnection();
Session session = con.createSession(true, 0);
MessageProducer producer = session.createProducer(topic);
TextMessage msg = session.createTextMessage();
msg.setText("hello");
producer.send(msg);
con.close();
} catch (JMSException e) { }
MDB:
@MessageDriven(activationConfig = {
@ActivationConfigProperty(propertyName="connectionFactoryJndiName", propertyValue="jms/Topic/testTCF"),
@ActivationConfigProperty(propertyName="destinationName", propertyValue="jms/Topic/testTopic"),
@ActivationConfigProperty(propertyName="destinationType", propertyValue="javax.jms.Topic")
public class MessageReceiver1Bean implements MessageListener {
public void onMessage(Message message) {
System.out.println("hello");
Message service configuration:
<jms-server port="9227">
<queue location="jms/Queue/testQueue" name="queue"/>
<queue-connection-factory location="jms/Queue/testQCF"/>
<topic location="jms/Topic/testTopic" name="topic"/>
<topic-connection-factory location="jms/Topic/testTCF"/>
<log><file path="../log/jms.log"/></log>
</jms-server>

          A few questions to better understand your case,
          1) are you using pub/sub (topics) or ptp (queues) ?
          2) are you producing inside a transaction (either use JTA or jms transacted session)
          3) do you use/set TimeToDeliver parameter ?
          4) when you monitor, do you see your messages under pending count ?
          "Rajiv Kadayam" <[email protected]> wrote:
          >
          >I'm having trouble with the 6.1sp5 version of weblogic specifically with
          >the JMS
          >server not quite notifying my message listeners whenever a new message
          >is received
          >in the queue. I can see the messages via the console by way of clicking
          >"monitor
          >all desitinations". I don't see any exceptions at all. This piece of
          >code does
          >work in Weblogic 7 and it did work on weblogic 6.1sp4. I'm not quite
          >using MDBs
          >and my publishers are CORBA services and there are no EJB components
          >involved.
          >
          >The trouble is there are no exceptions and my message listeners are just
          >waiting.
          >any tips or ideas would be greatly appreciated.
          >
          >thanks
          >rajiv
          

Similar Messages

  • Message not getting delivered

    Hi,
    I have created a simple application which sends messages to the channel.
    Here is my channel :
    <?xml version="1.0"?>
    <!--
    A sample channel file
    Change "channelPrefix" and <channel/> elements to customize
    The following namespaces are used in this sample file. These
    namespaces refer to schemas that must be present in a schema
    directory.
    - xmlns:eg=http://www.bea.com/wli/eventGenerator" is used
    for event generator metadata references
    - xmlns:dp="http://www.bea.com/wli/control/dynamicProperties" is
    used by the file event generator to pass payload for pass-by-filename
    - xmlns:oagpo="http://www.openapplications.org/003_process_po_007" is
    used for a sample payload description
    -->
    <channels xmlns="http://www.bea.com/wli/broker/channelfile"
    channelPrefix="/test" >
    <channel name ="test" messageType="string">
    <!-- A simple channel passing XML -->
    <!--
    <channel name ="SampleXmlChannel" messageType="xml"/>
    -->
    <!-- A simple channel passing rawData -->
    <!--
    <channel name ="SampleRawDataChannel" messageType="rawData"/>
    -->
    <!-- A simple channel passing a string -->
    <!--
    <channel name ="SampleStringChannel" messageType="string"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in
    the oagpo namespace -->
    <!--
    <channel name ="SampleOAGPOChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"/>
    -->
    <!-- A channel passing rawData, the rawData is mapped by the
    StockQuotes.mfl file in the schema directory -->
    <!--
    <channel name ="SampleRawDataChannel" messageType="rawData"
    qualifiedRawDataMessageType="urn:StockQuotes.mfl"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element FileEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGFileChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:FileEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element dp:FileControlProperties
    in the po namespace, and the metadata is element FileEventGenerator
    in the eg namespace
    (this is the XML payload used for pass-by-filename in the
    file event generator) -->
    <!--
    <channel name ="SampleEGFileChannel" messageType="xml"
    qualifiedMessageType="dp:FileControlProperties"
    qualifiedMetadataType="eg:FileEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element JmsEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGJmsChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:JmsEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element EmailEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGEmailChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:EmailEventGenerator"/>
    -->
    <!-- A channel passing XML, the XML is element PROCESS_PO_007 in the
    oagpo namespace, and the metadata is element TimerEventGenerator
    in the eg namespace -->
    <!--
    <channel name ="SampleEGTimerChannel" messageType="xml"
    qualifiedMessageType="oagpo:PROCESS_PO_007"
    qualifiedMetadataType="eg:TimerEventGenerator"/>
    -->
    </channel>
    </channels>
    Issue is whenever I run my application I get following excpetion , please
    let me know what I am missing . I am running weblogic 8.
    Thanks
    Veresh
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <Transaction Rolled
    back in response to exception occurred during async error processing
    javax.ejb.TransactionRolledbackLocalException: Exception in ejbLoad:; nested
    exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLExce
    ption: Lock time out; try later.
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Lock
    time out; try later.
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handleJDBCObjectResponse(Unknown Source)
    at com.pointbase.net.netJDBCPreparedStatement.executeQuery(Unknown
    Source)
    at
    weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:124)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean$GenericTableAccess.doLoad(BMPContainerBean.java:495)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbLoad(BMPContainerBean.java:1724)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.ejbLoad(ProcessContainerBean.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_Impl.ejbLoad(PersistentContainer_2ktjqj_Impl.java:136)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:324)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:228)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    javax.ejb.EJBException: nested exception is: java.sql.SQLException: Lock
    time out; try later.
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.ejbLoad(BMPContainerBean.java:1776)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.ejbLoad(ProcessContainerBean.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_Impl.ejbLoad(PersistentContainer_2ktjqj_Impl.java:136)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.getReadyBean(ExclusiveEntityManager.java:324)
    at
    weblogic.ejb20.manager.ExclusiveEntityManager.preInvoke(ExclusiveEntityManager.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:228)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    javax.ejb.TransactionRolledbackLocalException: Exception in ejbLoad:; nested
    exception is: javax.ejb.EJBException: nested exception is: java.sql.SQLExce
    ption: Lock time out; try later.
    at
    weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledbackLocal(EJBRuntimeUtils.java:247)
    at
    weblogic.ejb20.internal.BaseEJBLocalHome.handleSystemException(BaseEJBLocalHome.java:246)
    at
    weblogic.ejb20.internal.BaseEJBLocalObject.preInvoke(BaseEJBLocalObject.java:233)
    at
    weblogic.ejb20.internal.EntityEJBLocalObject.preInvoke(EntityEJBLocalObject.java:72)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.invoke(PersistentContainer_2ktjqj_ELOImpl.java:190)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:93)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at
    com.bea.wlw.runtime.core.bean.AsyncErrorBean.onMessage(AsyncErrorBean.java:225)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <A message was
    unable to be delivered from a WLW Message Queue. Attempting to deliver the
    onAsyn
    cFailure event>
    <Jun 19, 2005 12:37:25 AM EDT> <Error> <WLI-Core> <BEA-481028> <Failed to
    lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy16.publish(Unknown Source)
    at processes.event1.responsePublishPublish(event1.jpd:119)
    at processes.event1_wf$ImplControlSend4.invoke(event1_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event1_wf$_ProcessState.processMessage(event1_wf.java:177)
    at processes.event1_wf.event1Subscribe_onMessage(event1_wf.java:146)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy17.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event1BMPContImpl.event1Subscribe$callback(event1BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_4po8lm_ELOImpl.event1Subscribe$callback(PersistentContainer_4po8lm_ELOImpl.java:153)
    at
    com.bea.wlwgen.event1BMPContAdpt.invokeOnBean(event1BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Error> <WLI-Core> <BEA-481028> <Failed to
    lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    >
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000>
    <Id=responsePublishEvent; Method=processes.responsePublishEvent.publish();
    Failure=weblogic.jws.
    control.ControlException: [WLI-Core:489317]Failed to publish message to the
    Message Broker due to: com.bea.wli.broker.RepositoryException: [WLI-Core:481
    028]Failed to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    [[WLI-Core:481028]Failed to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)
    at
    com.bea.wli.broker.JDBCRepository.dispatchDynamicSubscriptions(JDBCRepository.java:1087)
    at
    com.bea.wli.broker.MessageBroker.publishMessage(MessageBroker.java:944)
    at
    com.bea.control.PublishControlImpl.doPublish(PublishControlImpl.jcs:196)
    at
    com.bea.control.PublishControlImpl.invoke(PublishControlImpl.jcs:306)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
    at $Proxy13.publish(Unknown Source)
    at processes.event2.responsePublishEventPublish(event2.jpd:113)
    at processes.event2_wf$ImplControlSend4.invoke(event2_wf.java:61)
    at com.bea.wli.bpm.runtime.Perform.execute(Perform.java:32)
    at com.bea.wli.bpm.runtime.Receive.messageDelivery(Receive.java:91)
    at
    com.bea.wli.bpm.runtime.Receive.messageDeliveryAction(Receive.java:71)
    at
    com.bea.wli.bpm.runtime.ProcessState.processMessage(ProcessState.java:166)
    at
    processes.event2_wf$_ProcessState.processMessage(event2_wf.java:177)
    at processes.event2_wf.event2Subscribe_onMessage(event2_wf.java:157)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:423)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:396)
    at
    com.bea.wlw.runtime.core.container.Invocable.fireEvent(Invocable.java:612)
    at
    com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:412)
    at $Proxy14.onMessage(Unknown Source)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at
    com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:371)
    at
    com.bea.wlw.runtime.jcs.container.JcsContainer.invoke(JcsContainer.java:99)
    at
    com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:319)
    at
    com.bea.wlw.runtime.core.bean.BaseContainerBean.invokeBase(BaseContainerBean.java:224)
    at
    com.bea.wlw.runtime.core.bean.BMPContainerBean.invoke(BMPContainerBean.java:2033)
    at
    com.bea.wli.bpm.runtime.ProcessContainerBean.invoke(ProcessContainerBean.java:163)
    at
    com.bea.wlwgen.event2BMPContImpl.event2Subscribe$callback(event2BMPContImpl.java:40)
    at
    com.bea.wlwgen.PersistentContainer_2ktjqj_ELOImpl.event2Subscribe$callback(PersistentContainer_2ktjqj_ELOImpl.java:45)
    at
    com.bea.wlwgen.event2BMPContAdpt.invokeOnBean(event2BMPContAdpt.java:87)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.runAsInvoke(BaseDispatcherBean.java:153)
    at
    com.bea.wlw.runtime.core.bean.BaseDispatcherBean.invoke(BaseDispatcherBean.java:54)
    at
    com.bea.wlw.runtime.core.bean.AsyncDispatcherBean.onMessage(AsyncDispatcherBean.java:248)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:370)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:262)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2678)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2598)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
    ]>
    <Jun 19, 2005 12:37:25 AM EDT> <Warning> <WLW> <000000> <Id=responsePublish;
    Method=processes.responsePublish.publish(); Failure=weblogic.jws.control.Co
    ntrolException: [WLI-Core:489317]Failed to publish message to the Message
    Broker due to: com.bea.wli.broker.RepositoryException:
    [WLI-Core:481028]Failed
    to lookup dynamic subscription(s)
    java.sql.SQLException: Lock time out; try later.
    at com.pointbase.net.netJDBCPrimitives.handleResponse(Unknown
    Source)
    at
    com.pointbase.net.netJDBCPrimitives.handlePrimitiveResponse(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.fetchData(Unknown Source)
    at com.pointbase.net.netJDBCResultSet.next(Unknown Source)
    at
    weblogic.jdbc.wrapper.ResultSet_com_pointbase_net_netJDBCResultSet.next(Unknown
    Source)

    Same problem here with and I've done everything shy of a total reset which I also find unacceptable. This problem exists on all iMessage platforms (iPhone, iPad, and Mac) so I don't see how restoring my iPhone would help the problem.

  • Why is my text message not being delivered

    Why is my messages not being delivered?

    1. Messages on the iPad can only be sent to other iDevices
    2. The receiving party must also be registered with iMessage
    Note: The two above conditions must be met.

  • App testing phase: Push notifications are not getting delivered to certain devices (iphone 4S/ios7.0.4 and ios7.0.3 - Push never worked for these two devices for this app). Received OK responses from Apple PUSH services, but notifications not delivered

    We are testing an app at work and Push notifications are not getting delivered to certain devices (iphone 4S/ios7.0.4 and ios7.0.3 - Push never worked for these two devices for this app). Received OK responses from Apple PUSH services, but notifications not delivered to these tow devices.
    PUSH notification were delivered to some of the other iOS devices: (iPhone5 / iOS 6.1.4 and iPhone5 / iOS 7.0.3)

    Sounds like you have a battry issue but don't want to believe it.
    If a car was running fine on one tank of gas, then you filled it up with another tank of gas and it began to run funny, one might suspect that tank of gas. But let's just say coincidence blew a valve-- would you think the new tank of gas was the culprit?
    BUT WAIT!! It just might have been! The gas could have been of higher octane and put more more strain on the valves; you know, like going from 87 octane (OS6) to 93 octane (OS7) and showing you the engine was on the edge of compromise.
    Sometimes you have to go with common sense. If everything else is ruled out, it must be the battery. And if it runs fine one moment in OS6 but immediately ***** in OS7, I'd believe my battery was suspect-- though comfy-- in OS6 but the OS7 showed its true power.
    Moreover, if you had the answer-- or didn't want to believe someone's more competent advice-- why did you even call?  You've already shown that you don't know much when you asked if you could go backwards after setting up the new OS as a new phone.
    Additonally, if you're such the know-it-all, but yourself the $29 battery and put it in yourself. It's a piece of cake.
    <Edited By Host>

  • JMS messages not being redelivered correctly ..

    Hi Folks
    I am having this weird problem with JMS using workshop/weblogic 8.1 SP2. I am
    using a JMS control from within my pageflow to post a JMS message to a predefined
    JMS queue (created by workshop for every web project . Mine is called testweb.queue.AsyncDispatcher
    as my web project is called testweb). Since pageflows cannot receive asysnchronus
    callbacks , I have not implemented the callback handler for teh JMS control as
    I just need to be able to post from my Pageflow . So far so good.
    I have an MDB listening to testweb.queue.AsyncDispatcher and that basically tries
    to open a URL connection to a thirdparty web site and if connect is not successful
    it should keep trying after every 10 seconds. I have the MDB throw an EJBException
    (to simulate message redelivery) . The problem is that the message is redelivered
    exactly 8 times and then I get the below message on the console :-
    <May 24, 2004 10:18:00 AM EDT> <Error> <WLW> <F1234PiyushK> <cgServer> <ExecuteThread:
    '14' for queue: 'weblogic.kernel.Default'> <<anonymous>> <BEA1-001D75CA6E6EB041A149>
    <000000> <onMessageException: java.lang.Exception: Unexpected message format>
    I also have an MDB listening to the error queue testweb.queue.AsyncDispatcher_error
    but its onMessage is never executed .
    I am stuck on this for the last efw days so appreciate any help. Should I post
    a message to the JMS queue directly from a session bean insetad of from a page
    flow ?
    my JMS queue config parameters are mentioned below :-
    Time To Deliver Delivery 5000
    Delivery Mode Override - No Override
    Expiration Policy - Redirect
    Redelivery Delay Override - 5000
    Redelivery Delay Override - 10
    Error Destination - testweb.queue.AsyncDispatcher_error
    The other parameter values are the default values and I have not changed them

    I am having the same problem with a simple WLI timer channel that posts a string message called myMessage every 20 seconds (what I defined in the WLI console).
    This works like a charm.
    In my process.jpd file, the timer subscription is followed by a JMS control, with a sendTextMessage(myMessage) which sends the message to a queue
    @jc:jms
    send-type="queue" send-jndi-name="JmsTimerProcessWeb.queue.AsyncDispatcher"
    receive-type="queue" receive-jndi-name="NightlySiteProcess.queue.AsyncDispatcher"
    connection-factory-jndi-name="weblogic.jws.jms.QueueConnectionFactory"
    All goes well while sending but the messages tell otherwise:
    === Timer sent message = This is the WLI message
    === JMS sent message = This is the WLI message
    <Aug 24, 2005 1:19:30 PM MDT> <Error> <WLW> <000000> <onMessageException: java.lang.Exception: Unexpected message format>
    What does this mean?
    I tried to add a project with a Message-bean, I cannot get the string message. I tried with an ObjectMessage, the same scenario everytime.
    Any suggestions?

  • JMS messaging not working with LCDS and Fiorano

    Hi there,
    Been struggling at this all day with no luck. I have a finished Flex application which uses JMS messaging, and it has worked just fine on my Tomcat server while using ActiveMQ. As soon as I switched to using the JMS provider Fiorano however, my application can no longer use JMS resources. It fails whenever the application tries to subscribe or publish to a JMS topic. I made all the appropriate JMS related changes to messaging-config.xml.
    In the tomcat log, I turned on LCDS debugging and saw this error whenever a publisher or subscriber was trying to start:
    "JMS invocation caught exception: SECURITY_EXCEPTION :: Security exception occurred while trying to perform operation :: CreateSubscriber failed,creation of Non-durable Subscriber NOT allowed."
    I am passing my JMS security credentials via messaging-config.xml AND even tried doing it via the Flex application (setRemoteCredentials(..)). I know they are correct because I have a working Java application with the exact same credentials and other JMS settings working just fine. It seems only the Flex application fails using the same JMS credentials/settings.
    Is there some other file that needs modification other than messaging-config.xml to get a new JMS provider to work? Any idea what may be going on?
    Thanks!

    A large number of messages, or messages large in size, basically total size of all messages can hang things up.  Back up your messages with a GPStore app.  Erase them.  Lower your message character size.  IF it still continues, its the recipients phone.  Both of you should power down, remove SIM, reinsert, power up.

  • Text message not being delivered.

    iPhone 4S with IOS  7.06  showing text message sent but does not show message delivered.
    The Reciepent does not get the text message.

    NikonCameraguy wrote:
    Blue
    Start with this article:
    http://support.apple.com/kb/ts2755

  • 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

  • SMS Messages not being delivered

    For the past 4 days now my SMS messages will not deliver. They say sent, but will not deliver, The person that is suppose to get them says they are not being recieved either so what are we supposed to do? Please attend to this immediately or at least tell us what to do. Thanks so much  [edited for privacy]  would appreciate response to this e mail address.  thanks again  

    Same problem here,it say the SMS sent,but for the last 50 min.  it's not been delivered yet.I have to mention the money went out from my account for it.I logged out and back in,changed status in hope will get it done somehow,but still nothing.
             Why do we have to pay for a service that doesn't work? It's  supposed to be fast and reliable(none of the abobe).My message is kinda too late now,and I doubt that I'll get my money back.
    And yes..I did put the right number and the country code and so on,it's not the first time I use Skype for this.
    Shame !

  • Problem in BADI, error message not getting displayed

    Hello Experts,
    I am facing a strange problem in BADI.
    The requirement is that the user should not be allowed to change the plant field
    on the screen of standard MM transctions for PO/PR amendment.
    I have written the code in separate BADIs for PO and PR.
    I am displaying an error message if the user tries to change the field.
    For PO, it is working fine.But for PR, the same code is not working.
    The control is going over to the BADI for PR and rest of the code is working fine.
    But the error message is not getting displayed for PR amendment.
    Can anybody please suggest the possible cause of problem and some solution to it.
    Thanks in advance.

    Hi
    See the sample BADI code for PR which raises an exceptions and do accordingly
    BAdI Name: ZPUR_RFQ (Implementation name) Purchase Requisitions
    Definition Name: ME_REQ_POSTED
    Interface Name : IF_EX_ME_REQ_POSTED
    Implementing Class: ZCL_IM_PUR_REQ
    Method :            POSTED
    METHOD if_ex_me_req_posted~posted .
      DATA : v_mtart TYPE mtart.
      DATA l_s_eban TYPE ueban.
      LOOP AT im_eban INTO l_s_eban.
        IF l_s_eban-estkz NE 'B'.
          CLEAR v_mtart.
          SELECT SINGLE  mtart INTO v_mtart FROM mara WHERE matnr = l_s_eban-matnr.
          IF v_mtart EQ 'ZERS' OR v_mtart EQ 'FHMI' OR v_mtart EQ 'UNBW'.
            MESSAGE e000(zm_msg) WITH 'You are not allowed' 'to create PR for stock items'.
          ENDIF.
        ENDIF.
        IF  l_s_eban-knttp NE 'F' OR l_s_eban-pstyp NE '9'.
          IF l_s_eban-knttp NE 'A'.
            IF ( l_s_eban-pstyp NE '9' AND l_s_eban-pstyp NE 'D' ) 
               AND l_s_eban-matnr EQ space.
              MESSAGE e000(zm_msg) WITH 'You cannot create'
                'a PR without material number'.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDMETHOD.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Messages not getting displayed in BADI

    Hi experts,
    I have implemented a BADI for automating FB50 in MIGO. Atlast i am using
    CALL FUNCTION 'MESSAGE_TEXT_BUILD'
      EXPORTING
        msgid                     = WA_MESSTAB-MSGID
        msgnr                     = WA_MESSTAB-MSGNR
       MSGV1                     = WA_MESSTAB-MSGV1
       MSGV2                     = WA_MESSTAB-MSGV2
       MSGV3                     = WA_MESSTAB-MSGV3
       MSGV4                     = WA_MESSTAB-MSGV4
    IMPORTING
       MESSAGE_TEXT_OUTPUT       = WA_TEXTOUT
    MESSAGE WA_TEXTOUT TYPE 'I'.
    But after this message is executed...the MIGO transaction's message is getting triggered immediately. So my message is not popping up.
    What to do?

    When i debug the program...
    I get the following things..
    wa_messtab-msgid = F5
    wa_messtab-msgnr = 312
    wa_messtab-msgv1 = 100128404
    wa_messtab-msgv2 = XYZ
    wa_textout = Document 100128404 was posted in company code XYZ
    and when i say
    message wa_textout type 'i'.
    at the output a popup window should display information in wa_textout.
    But this is not happening and message of type 'S' is getting displayed...that is standard msg of MIGO
    which is - Material document 5000115652 posted
    I want my custom msg in wa_textout to be displayed first. before the standard MIGO msg.

  • Message not getting displayed in BTE 1030

    I am displaying a message in functional module implemented for BTE 1030.
    The message is not getting diplayed. I have changed the message tyto 'S, I. W, E but still it does not display.  The sy-subrc is 0 after passing the messga statement.
    (The functional module is called normally and not in background)

    Just check your settings in transaction FIBF, and make sure you have choose the right Process Modules(Ususally we choose "of an SAP Application"), and if you have set some other limitation on Country ISO code or Application Indicator, pls make sure all of them have been satisfied.

  • Complete error message not getting displayed

    Hi All,
    I've built a custom webadi integrator which loads into a custom staging table.
    All fine with the webadi but the error messages are getting truncated to only 45 characters. The variable size is 4000 characters and a debug message before RAISE_APPLICATION_ERROR indicates there is no truncation of the message in the PL SQL package.
    Where and how is my message getting truncated?
    Any pointers highly appreciated !

    Hi
    See the sample BADI code for PR which raises an exceptions and do accordingly
    BAdI Name: ZPUR_RFQ (Implementation name) Purchase Requisitions
    Definition Name: ME_REQ_POSTED
    Interface Name : IF_EX_ME_REQ_POSTED
    Implementing Class: ZCL_IM_PUR_REQ
    Method :            POSTED
    METHOD if_ex_me_req_posted~posted .
      DATA : v_mtart TYPE mtart.
      DATA l_s_eban TYPE ueban.
      LOOP AT im_eban INTO l_s_eban.
        IF l_s_eban-estkz NE 'B'.
          CLEAR v_mtart.
          SELECT SINGLE  mtart INTO v_mtart FROM mara WHERE matnr = l_s_eban-matnr.
          IF v_mtart EQ 'ZERS' OR v_mtart EQ 'FHMI' OR v_mtart EQ 'UNBW'.
            MESSAGE e000(zm_msg) WITH 'You are not allowed' 'to create PR for stock items'.
          ENDIF.
        ENDIF.
        IF  l_s_eban-knttp NE 'F' OR l_s_eban-pstyp NE '9'.
          IF l_s_eban-knttp NE 'A'.
            IF ( l_s_eban-pstyp NE '9' AND l_s_eban-pstyp NE 'D' ) 
               AND l_s_eban-matnr EQ space.
              MESSAGE e000(zm_msg) WITH 'You cannot create'
                'a PR without material number'.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.
    ENDMETHOD.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Message not getting refreshed in bsp pages.

    Hi experts,
    An error message which is getting displayed should be removed on leaving the page. I mean the meassage area is not getting refreshed on leaving the page. Everytime i need to refresh the page to remove it. Please help.
    Abhi.

    hello Friend,
    Please clear the internal table / work are used to show message in OnInitialization method of the BSP page.
    now It is not getting cleared at the time leaving the page and data stays in memory...
    Thanks
    K.

  • Support messages not getting displayed in Messages Tab - Solar01/02

    Hi,
    I am having an issue in displaying the support messages under the message tab of Solar01 and Solar02. If I try to create a new message, the notification pops up and also gets saved. But the message does not get displayed under the tab.
    I can find that the message is properly created through transaction monitor.Even if I try to manually assign the support message number in Messages tab it gives an error saying the number does not exist.We are using SOLMAN 4.0 SP 11.
    Please help. Points will be awarded for useful answers.
    Regards,
    J.Prabananth

    Dear Prabanath,
           I am not too sure you will be able to assign numbers to support messages. Run the report CRM_DNO_MONITOR and get the full number from the report and insert the ticket number in issue messages tab and click on save and go back one screen, it will ask you if you want to save, select yes.
       That worked for me. Recently I have strugged to resolve this. We are on Solman 4.0 SP12. Check if you have all necessary permissions for you and do you have any thing in sm21 or st22 by any chance if the issue is related to support pack ?
         Let me know if there are any issues. I might be able to help you.
    N

Maybe you are looking for

  • Changing value in JcomboBox

    hi, i am new learner in java programming language. i trying to develop a Greenwich inn resort reservation system. i am adding 2 JCombobox in the JFrame and adding 2 Action listener to the 2 created JCombobox in oder to reset the value in Jcombobox. j

  • Exporting to h.264 causes video to be half frame out sync

    Whenever I compress a ProRes quicktime to an h.264, using the standard vimeo presets, the result is always a half of frame out sync. Has this happened to anyone else?

  • Reg : Context-switching for built-in functions -

    Hi Experts, Asking this question just out of curiosity to know the internal concepts. In a SQL query often we use the in-built Oracle functions like LOWER, UPPER, etc. In this case, does context-switch happen? Will I be able to look into the code of

  • How to automate managed beans.xml update

    I am using JSC 2.0 ea and am trying to add a "loginBean" based on the example in java studio creator field guide. The process explained in the book, ie right-click "source package" add java package, right-click newly created package and add "managed

  • Resetting PMU, PRAM and SMU does not stop freezes

    Resetting all these things does nothing to stop either just plain not starting at all, or system freezes on startup. For the benefit of anybody reading this who uses ProTools, I'm running 7.4 LE. This is the only non-Apple app on the machine, which i