Already twice it happened during shipping that the server became increasingly slow and at some point stopped responding. (not tested with 23.10.000.152)
If we schedule an email more than an hour in advance, the production of the email does not start and therefore the sending does not start either. (not tested with 23.10.000.152)
After saving mailings and templates, a 500 error occurs, you are logged out but the content was saved.
I found this in the logs: IP address of client is not allowed for current session - invalidating session XXX (session: /[my IP], client: /[Server IP]
1. With shipping you mean the dispatch of the mailings? This is probably caused by AWS throttling the output of emails.
2. We will check this.
3. The error means that your IP address has changed during a session. This should not happen. However if this is caused by AWS and you know the IP addresses being used, you may enter them manually in table login_whitelist_tbl.
maschoff wrote: ↑Wed Jan 24, 2024 7:19 pm
1. With shipping you mean the dispatch of the mailings? This is probably caused by AWS throttling the output of emails.
One mailing went smoothly. For the others it worked without any problems after a restart. In one case, the crash happened at night, and after the restart in the morning, all emails that were scheduled during that time were sent in one go (approx. 40k) and there were no problems. (we have over 200k recipients for some mailings and send them at 10k per hour)
maschoff wrote: ↑Wed Jan 24, 2024 7:19 pm
3. The error means that your IP address has changed during a session. This should not happen. However if this is caused by AWS and you know the IP addresses being used, you may enter them manually in table login_whitelist_tbl.
It is the IP address of the server, it looks like there is an internal call somewhere with the SessionID. I have the same problem when I try to generate a PDF of an email, in the PDF you only see the login and I was logged out. (Does it try to generate a preview image when saving and that's the problem? I only see a placeholder in the list when I mouse over)
maschoff wrote: ↑Thu Jan 25, 2024 5:22 pm
#2 fixed in 23.10.000.159, available via OMT.
I can confirm that it worked now.
But again I had the problem that the server became extremely slow and I ended up resetting the server using the AWS console.
I saw that the log was spammed with exceptions:
2024-01-31 00:01:09,809: ERROR [https-jsse-nio-8443-exec-143] com.agnitas.emm.core.unsubscribe.ComUnsubscribe - Exception during one-click unsubscription
org.agnitas.emm.core.commons.uid.parser.exception.UIDParseException: No registered parser could handle the UID. See log messages above for more details
There were no other log messages matching these exceptions
the log before was:
2024-01-30 23:54:44,220: ERROR [https-jsse-nio-8443-exec-169] com.agnitas.emm.core.userform.web.UserFormExecuteController - execute()
org.apache.catalina.connector.ClientAbortException: org.apache.coyote.CloseNowException: Connection [becb], Stream [1], This stream is in state [CLOSED_RST_RX] and is not writable
