Well Hurricane Jeanne provided the test environment I needed this past weekend and the problem with an unreachable peer still exists despite tuning the TCP/IP, decreasing the TIME_WAIT delay to 2 minutes and allowing Imail to use ports from 1024 to 65534. My main peer (behind my mail gateways) became catatonic yesterday evening about 30 hours after the peer in Florida was taken offline. I was unable to get a netstat due to the catatonic state and had to hard cycle the power via a managed apc.

I have 7 peers in the peer group and start seeing these lines for every peer as it tried to distribute messages
Example:
Connect fail 66.185.109.244 [66.185.109.244]: address already in use


After a while the "address already in use" error turns into the no buffer space available error

Example:
Connect fail 67.95.199.242 [67.95.199.242]: no buffer space available

The log file gets huge when it goes into the no buffer space available state, it generated about 150MB worth of these error messages in the few hours it was down.

stopping and restarting the queuemanager will temporarily clear the condition as will rebooting. The higher the load the shorter the time between failure.

Could someone at Ipswitch please provide information to substantiate your claim that this is an OS issue or MS TCP/IP issue so that someone like myself can find the fix for you. The problem obviously is in the handling of a down peer since it doesn't occur in non peering setups (AFAIK)

I have service agreements for all 9 of my Imail systems and I am willing to help identify the root of this problem as I have always been. If you have a ticket archive search for my name or email address, there is plenty of technical info available.

Rick Davidson
National Systems Manager
North American Title Group
-
----- Original Message ----- From: "Rick Davidson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 24, 2004 3:17 PM
Subject: Re: [IMail Forum] D files with no Q files - Queuemanager crashes with unreachable peer (again)



That isn't an IMail issue -- Microsoft won't let IMail use ports higher than 5000, without the registry hack that you described. So if you don't use that registry hack, IMail can't use ports higher than 5000; if you do use it, IMail can use ports higher than 5000.

agreed. It is definately a MS issue.

Rick Davidson
National Systems Manager
North American Title Group


To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/





To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/

Reply via email to