Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[prem]

Hi team,

Do you have that kind of errors connecting to gmail smtp?

2015-10-22 16:17:22 Error connecting from ......  to gmail-smtp-in.l.google.com (74.125.133.26) for gmail.com/vmta1: I/O interrupted

I receive a lot of messages like this. I use a big server with a lot of memory&connections so even could be a network problem. But, that error comes mainly from gmail remote smtp.

thank you

[ReyM]

Take a look at the errors before this error message... usually it means that GMail is throttling you or for some other reason dropped the connection. They've dropped you, not you dropping them.

Hi team,

Do you have that kind of errors connecting to gmail smtp?

2015-10-22 16:17:22 Error connecting from ......  to gmail-smtp-in.l.google.com (74.125.133.26) for gmail.com/vmta1: I/O interrupted

I receive a lot of messages like this. I use a big server with a lot of memory&connections so even could be a network problem. But, that error comes mainly from gmail remote smtp.

thank you

[CaLViN]

Hello,
have you checked your disk read / write status ?

[Port25-Admin2]

Here is one of the previous responses given in regards to this error;

https://forum.port25.com/powermta-support/io-interrupted-while-connecting/msg1729/#msg1729

[prem]

Hi team,
Let me answer all of you:

Here is one of the previous responses given in regards to this error;

https://forum.port25.com/powermta-support/io-interrupted-while-connecting/msg1729/#msg1729

----------

This error indicates that PowerMTA forcibly closed an active connection, either due to;

- you shutting down the PowerMTA service
- you running a command (like the delete command) to abruptly break active connections
- using queue-priorities, which has PowerMTA breaking active connections to a low priority queue in order to give a higher priority queue resources needed to make the delivery attempt

1) This is happening everytime,suddenly, so it look like more to a timeout or a forced closed connection by any actor of the communication (port25 or remote server). I discovered yesterday activating transient errors that this is not a gmail issue. It is also yahoo issue, so it makes me thinking about a local problem rather than gmail problem

Referring to the post:
- shutdown is not happening in this moment
- i didn't use any command like delete or list
- I use queue priority, this is a good hint.. i'm trying now to test without it :-) ... keep in touch!


2) To CalVin: Yes, i checked this. i've a good system monitor for this. The disk is in a low busy state. is a set of SSD disk with a very good performance.

3) to ReyM: i have not special previous errors related to this connection. At least i didn't see it :-/

4) To all: i run with enough resources, no socket problem, no max-file problem

My nexts steps are
- disable queue priorities
- check network issues (like timeouts in system)

[prem]

Hi team,
Let me answer all of you:

Here is one of the previous responses given in regards to this error;

https://forum.port25.com/powermta-support/io-interrupted-while-connecting/msg1729/#msg1729

----------

This error indicates that PowerMTA forcibly closed an active connection, either due to;

- you shutting down the PowerMTA service
- you running a command (like the delete command) to abruptly break active connections
- using queue-priorities, which has PowerMTA breaking active connections to a low priority queue in order to give a higher priority queue resources needed to make the delivery attempt

1) This is happening everytime,suddenly, so it look like more to a timeout or a forced closed connection by any actor of the communication (port25 or remote server). I discovered yesterday activating transient errors that this is not a gmail issue. It is also yahoo issue, so it makes me thinking about a local problem rather than gmail problem

Referring to the post:
- shutdown is not happening in this moment
- i didn't use any command like delete or list
- I use queue priority, this is a good hint.. i'm trying now to test without it :-) ... keep in touch!


2) To CalVin: Yes, i checked this. i've a good system monitor for this. The disk is in a low busy state. is a set of SSD disk with a very good performance.

3) to ReyM: i have not special previous errors related to this connection. At least i didn't see it :-/

4) To all: i run with enough resources, no socket problem, no max-file problem

My nexts steps are
- disable queue priorities
- check network issues (like timeouts in system)

Hi team,
The problem was the "queue priorities". The message gone when i disabled them.

Thank you all  for your quick and effective support!