- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Update: I switched back to t3.micro. An email came in from the same sender and to the same gmail destination. The same error occurred, but instead of sitting in the queue for a day or more, it went through in six minutes.
Now to switch back to t3a.micro and see what happens. Like I said - VERY strange.
Update. I let the machine run for another day, as these inbound emails are once per day.
Message in question came in, and was forwarded straight out to gmail, no TLS errors.
I have now switched back to t3a.micro and will report back the results, which I'm reasonably confident will show the same failure mode.
If this does fail again, it points to some sort of issue between t3.micro and t3a.micro architecture. At worst I sell my 3yr/upfront reserved and go back to t3.micro, but it does leave dangling a peculiar problem.
Digging deeper, I've found instances of this 'Error in pull function' going back as far as August. However, those errors were one-offs, which would delay messages for minutes, not hours or days.
However, with that sort of evidence - and the inconsistency of same, I'm going to have to declare this a wild goose chase. Since resuming the t3a, there have still been the pull function errors - but they likewise are only delaying messages a few minutes, not hours or days.
I'll mark this answered. I'm unsure whether I should just delete the whole thread, since the evidence doesn't support the theory, so my bloviations are unlikely to be helpful to anyone else...???
Digging deeper, I've found instances of this 'Error in pull function' going back as far as August. However, those errors were one-offs, which would delay messages for minutes, not hours or days.
However, with that sort of evidence - and the inconsistency of same, I'm going to have to declare this a wild goose chase. Since resuming the t3a, there have still been the pull function errors - but they likewise are only delaying messages a few minutes, not hours or days.
I'll mark this answered. I'm unsure whether I should just delete the whole thread, since the evidence doesn't support the theory, so my bloviations are unlikely to be helpful to anyone else...???
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa