I recently switched over to a separate dbmail front end server and database server. When I set the new front end server up I used debian sarge. Since that time I have been having huge problems with load being caused by dbmail-pop3d. It appears to attempt to use all the available cpu while transferring messages to the client. I had never seen this before when running the front end and database on the same server.
Does anyone have any clues? This is where the logs are at when it is taking 100% cpu: Oct 6 12:02:52 destiny dbmail/pop3d[20773]: pop3():RETR command, retrieving message Oct 6 12:02:52 destiny dbmail/pop3d[20773]: pop3(): RETR command, selecting message Oct 6 12:02:52 destiny dbmail/pop3d[20773]: db_send_message_lines(): request for [-2] lines Oct 6 12:02:52 destiny dbmail/pop3d[20773]: db_send_message_lines(): executing query [SELECT * FROM messageblks WHERE message_idnr=2458388 ORDER BY messageblk_idnr ASC] Oct 6 12:02:52 destiny dbmail/pop3d[20773]: db_query(): executing [SELECT * FROM messageblks WHERE message_idnr=2458388 ORDER BY messageblk_idnr ASC] Oct 6 12:02:52 destiny dbmail/pop3d[20773]: db_send_message_lines(): sending [-2] lines from message [2458388] Oct 6 12:02:52 destiny dbmail/pop3d[20773]: db_send_message_lines(): getting nextblock [1] I am running the latest CVS version available, and still seeing this issue. -- Bret Baptist Systems and Technical Support Specialist [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services ------------------------------------------ Today is the tomorrow you worried about yesterday.
