[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::mailworks-unix

Title:	Mailworks-unix
Notice:	V2.0.4 now available -- see Note 4.375
Moderator:	TAMARA::NEUMAN::Neumann

Created:	Wed Jun 02 1993
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	1384
Total number of notes:	5851

1350.0. "Run out of swap space" by KERNEL::16.42.64.84::houldingj () Tue Feb 18 1997 08:10

Hi

MAILWorks for UNIX V2.0

A customer reported a problem this morning where his MAILWorks system ran 
out of swap space. His system has 256MB RAm and 600MB Swap space allocated.

He has now got the system running again by using lazy swap but he is 
concerned about what caused this excessive use of swap space and how he can 
prevent it in the future.

He noticed that there were a great many /DMW/bin/deferd processes running 
(one for each user on the system) and doesn't understand why - nor do I?

He said that a message was sent out a couple of days ago to all users on 
the system with an expiry date of 18-Feb. Could the excessive number of 
processes have been a result of the deletion of the expired message?

Does anyone have any ideas?

Cheers

Jill

T.R	Title	User	Personal Name	Date	Lines
1350.1		KOALA::ANKAN	Idle words waste time	`Tue Feb 18 1997 10:10`	14
	>He has now got the system running again by using lazy swap but he is >concerned about what caused this excessive use of swap space and how he can >prevent it in the future. Good. How many users do they have? >He noticed that there were a great many /DMW/bin/deferd processes running >(one for each user on the system) and doesn't understand why - nor do I? Do they use the MAPI client? >He said that a message was sent out a couple of days ago to all users on >the system with an expiry date of 18-Feb. Could the excessive number of >processes have been a result of the deletion of the expired message? That is exactly what deferd is designed to do. What client did the sender of the message use?
1350.2	Clients used	KERNEL::uvodhcp23.uvo.dec.com::houldingj		`Wed Feb 19 1997 06:59`	17
	Thanks for your response. There are about 1000 users on this system. The clients are a mixture of SUN Motif Mailworks clients and TeamLinks V2.5. The client which sent the message with the expiry date was sent from TeamLinks. I spoke to the customer this morning and explained to him that the deferd processes do manage the deletion of expired messages. He is not too happy that with a large number of users the cleanup effectively brought their mail system down. I suggested to him that I log an IPMT to get the impact of the problem logged. Anyone have any ideas how to get round this? Cheers Jill
1350.3	2.0.2	UTRTSC::SCHOLLAERT	Ajax: World Champions 1995	`Thu Feb 20 1997 02:34`	12
	Hi Jill, 600MB Swap isn't that much... Version 2.0.2 is supposed to fix a number of memory leaks. The release notes have detailed information concerning this issue. Cheers, Jan
1350.4	Similar problem	NETRIX::"[email protected]"	Petr Sindelar	`Fri Mar 21 1997 09:21`	37
	Hello, It seems be a similar problem that we have. We have a customer that reported a problem with Mailworks V2.0.2 consuming a high amount of swap space ( X488grecv processes). The customer investigated a following scenario that causes the reported problem. A TeamLinks user X sets an autoforwarding e-mail address in his Mail profile (in TeamLinks V2.5) equal to the e-mail address of TeamLinks user Y and vice versa. Such scenario triggers oscillating of one message and causing Mailworks server is consuming a high amount of swap space. This continues up to 100% of swap and crash of the process. The solution is to stop x488 processes and deleting the message from MTA queue, but our customer is unsatisfied with such solution. So, is it possible to detect or prevent to oscillating of such messages or is it a way to disable autoforwarding in user Mail profile? The configuration of our customer is MAILworks V2.0.2, MB400 MTA V2.0, Digital UNIX V3.2D, DECnet/OSI V3.2B. MAILworks server and MTA are on the same machine. The other problem which customer indicates is the very long delay (cca 3-10minutes) on Server side in case that Teamlinks user attaches attachement bigger than 2.5MB. There is no network problems and it is indicated more than 80% server resources consuming by MailWorks process in manipulation with this message. I'd be happy if someone would help me with solving these problems. I'll appreciate any information. Regards Petr Sindelar, Digital Prague, CZ [Posted by WWW Notes gateway]