Skip to content
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

Closed
Mattifyed opened this issue Nov 9, 2022 · 17 comments
Closed

AxiosError — Frequent error when querying listmonk dB. #1019

Mattifyed opened this issue Nov 9, 2022 · 17 comments
Assignees
Labels
needs-investigation Potential bug. Needs investigation

Comments

@Mattifyed
Copy link

image

I frequently see this error when loading listmonk pages that query the subscriber dB. For example the /campaigns page and the /subscribers page.

@knadh knadh added the needs-investigation Potential bug. Needs investigation label Nov 9, 2022
@knadh knadh self-assigned this Nov 9, 2022
@knadh
Copy link
Owner

knadh commented Nov 9, 2022

504 = timeout. Large amounts of data, queries slowing down. Will investigate this.

@knadh knadh closed this as completed Nov 20, 2022
@knadh knadh reopened this Nov 20, 2022
@profmatheuspassos
Copy link

Same happening here.

@knadh
Copy link
Owner

knadh commented Feb 26, 2023

@profmatheuspassos how many subscribers and campaigns do you have, roughly?

@profmatheuspassos
Copy link

profmatheuspassos commented Feb 27, 2023 via email

@knadh
Copy link
Owner

knadh commented Feb 27, 2023

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.

@profmatheuspassos
Copy link

profmatheuspassos commented Feb 27, 2023 via email

@profmatheuspassos
Copy link

profmatheuspassos commented Feb 27, 2023 via email

@knadh
Copy link
Owner

knadh commented Feb 27, 2023

The logs you tried to embed in the above comment didn't come through.

@profmatheuspassos
Copy link

Sorry - here it goes

Screenshot 2023-02-27 at 12 25 13
Screenshot 2023-02-27 at 12 27 21
Screenshot 2023-02-27 at 12 29 37
Screenshot 2023-02-27 at 12 31 20
Screenshot 2023-02-27 at 12 31 24
Screenshot 2023-02-27 at 12 32 57

@knadh
Copy link
Owner

knadh commented Feb 27, 2023

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.

@profmatheuspassos
Copy link

Strange - it's all on the same server (using cloudron)

@knadh
Copy link
Owner

knadh commented Feb 27, 2023

Maybe something to do with the Docker environment (assuming that's what it is).

@gramakri
Copy link

gramakri commented Feb 27, 2023

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).

@gramakri
Copy link

@Mattifyed are you also on Cloudron?

@knadh
Copy link
Owner

knadh commented Feb 27, 2023

Don't think it's a memory issue. EOF, "connection reset by peer" indicate the upstream connection being closed abruptly by the SMTP.

@profmatheuspassos
Copy link

@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!

@profmatheuspassos
Copy link

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!

@knadh knadh closed this as completed in 5a3664a Jan 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-investigation Potential bug. Needs investigation
Projects
None yet
Development

No branches or pull requests

4 participants