-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AxiosError — Frequent error when querying listmonk dB. #1019
Comments
|
Same happening here. |
@profmatheuspassos how many subscribers and campaigns do you have, roughly? |
Ah, the DB bottleneck should only be visible when there are several million subscribers. EOF and timeout is on sending e-mails or page loads? EOF typically happens when the SMTP server abruptly terminates connections. If that's the case, you could try adjusting the send rates in Performance setttings. |
Sorry - I wasn’t clear on my previous answer :P
The axious message usually appears when I open the “Campaign/all campaigns” panel, and only after I start a new campaign.
EOF and time out are happening while sending e-mails - although it was with 10 concurrency and 10 message rate, and 100 batch size. In SMTP settings I use 10 max connections, 2 retries, 2 min idle timeout and 5 min wait timeout.
Using listmonk via Cloudron (automatic install).
… On 27. Feb 2023, at 09:56, Kailash Nadh ***@***.***> wrote:
Ah, the DB bottleneck should only be visible when there are several million subscribers.
EOF and timeout is on sending e-mails or page loads? EOF typically happens when the SMTP server abruptly terminates connections. If that's the case, you could try adjusting the send rates in Performance setttings.
—
Reply to this email directly, view it on GitHub <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fknadh%2Flistmonk%2Fissues%2F1019%23issuecomment-1445860390&data=05%7C01%7C%7Ccaa228300ca34838660c08db189816fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638130813716683523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0aWyKqv5%2FHsr%2FGS3FKwdbu0hHTq%2Fars%2BmaXUrduL848%3D&reserved=0>, or unsubscribe <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJRWNO6OUVHUYZHF2GW3XHTWZRMZTANCNFSM6AAAAAAR3DTASY&data=05%7C01%7C%7Ccaa228300ca34838660c08db189816fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638130813716683523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LY2kbw6vlLa7BF572RVcnvrxBOY0iCod8Shrc8uQHMA%3D&reserved=0>.
You are receiving this because you were mentioned.
|
Just as a follow-up.
Just ran a campaign to a list with 809 subscribers.
1) As soon as I started the campaign, I noticed the “axios” error again (but wasn’t able to print screen).
2) While running the campaign, here are some of the logs. The campaign stopped frequently (because I asked it to do so, in settings). I was following the campaign and it seems that as soon as listmonk receives an error, it stops sending the e-mails. Please note that before I took these prints with the settings, the max erros was set up to 100, but it stopped sending e-mails although the campaign continued “alive”.

Thanks!
… On 27. Feb 2023, at 09:56, Kailash Nadh ***@***.***> wrote:
Ah, the DB bottleneck should only be visible when there are several million subscribers.
EOF and timeout is on sending e-mails or page loads? EOF typically happens when the SMTP server abruptly terminates connections. If that's the case, you could try adjusting the send rates in Performance setttings.
—
Reply to this email directly, view it on GitHub <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fknadh%2Flistmonk%2Fissues%2F1019%23issuecomment-1445860390&data=05%7C01%7C%7Ccaa228300ca34838660c08db189816fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638130813716683523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0aWyKqv5%2FHsr%2FGS3FKwdbu0hHTq%2Fars%2BmaXUrduL848%3D&reserved=0>, or unsubscribe <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJRWNO6OUVHUYZHF2GW3XHTWZRMZTANCNFSM6AAAAAAR3DTASY&data=05%7C01%7C%7Ccaa228300ca34838660c08db189816fb%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638130813716683523%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=LY2kbw6vlLa7BF572RVcnvrxBOY0iCod8Shrc8uQHMA%3D&reserved=0>.
You are receiving this because you were mentioned.
|
The logs you tried to embed in the above comment didn't come through. |
This is definitely a network issue. EOF, timeout, "connection reset by peer". It could be the upstream or a firewall or something else in between. |
Strange - it's all on the same server (using cloudron) |
Maybe something to do with the Docker environment (assuming that's what it is). |
I am the author of the Cloudron package. @profmatheuspassos Have you already tried giving PostgreSQL more memory (under Services -> PostgreSQL -> bump memory limit) and the app as well (in the Resources view) ? Otherwise, I can invesitgate if there is an issue in the Cloudron package itself. I suspect the database is not having enough memory (from the logs you posted, it seems listmonk loses connection to the database). |
@Mattifyed are you also on Cloudron? |
Don't think it's a memory issue. EOF, "connection reset by peer" indicate the upstream connection being closed abruptly by the SMTP. |
@gramakri I increased the memory to 512 (instead of the standard 256). But haven't changed the Postgre more memory. Just did that (to 1GB) and I'll run another campaign in the same format in the next 2-3 days, then come back to you if the problem continues. Many thanks! |
Hey guys, this is a follow-up: The problem was with my e-mail server. I switched to smtp2go, and it worked fine. I even changed the performance settings to the original ones, and "voilà" everything worked as it should. Thanks for your attention! |
I frequently see this error when loading listmonk pages that query the subscriber dB. For example the /campaigns page and the /subscribers page.
The text was updated successfully, but these errors were encountered: