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

Bug: <describe the error> #420

Closed
zisequkuai opened this issue Nov 29, 2023 · 8 comments
Closed

Bug: <describe the error> #420

zisequkuai opened this issue Nov 29, 2023 · 8 comments
Labels
bug Categorizes issue or PR as related to a bug.

Comments

@zisequkuai
Copy link

What happened?

Problems with not being able to log in?

What did you expect to happen?

The installation was successful using docker, but I went to http://127.0.0.1:11002/login

After typing in my username and password and clicking log in there was no feedback,

then I went to check the docker logs

alertmanager | ts=2023-11-29T09:32:22.071Z caller=notify. go:745 level=warn component=dispatcher receiver=email integration=email[0] aggrGroup={}:{} msg="Notification attempt failed, will retry later" attempts=4 err="Creating SMTP client: 554 IP rejected, smtp auth error limit exceeded, 163 zwqz-smtp-mta-g2-1,_____wDH7q0mBWdlsx32EA --. 39760S0 1701250342"
alertmanager | ts=2023-11-29T08:18:23.676Z caller=notify.go:745 level=warn component=dispatc”

What needs to be done to fix this?

How can we reproduce it (as minimally and precisely as possible)?

docker log:

alertmanager | ts=2023-11-29T08:27:30.858Z caller=dispatch.go:352 level=error component=dispatcher msg="Notify for alerts failed" num_alerts=14 err="email/email[0]: notify retry canceled after 7 attempts: create SMTP client: 554 IP is rejected, smtp auth error limit exceed,163 zwqz-smtp-mta-g2-4,_____wDHzjLt9WZlFXupEA--.34747S0 1701246446"
alertmanager | ts=2023-11-29T08:27:31.008Z caller=notify.go:745 level=warn component=dispatcher receiver=email integration=email[0] aggrGroup={}:{} msg="Notify attempt failed, will retry later" attempts=1 err="create SMTP client: 554 IP is rejected, smtp auth error limit exceed,163 zwqz-smtp-mta-g3-4,_____wD3X93y9WZl5DwPBQ--.6421S0 1701246450"
alertmanager | ts=2023-11-29T08:27:31.629Z caller=notify.go:745 level=warn component=dispatcher receiver=email integration=email[0] aggrGroup={}:{} msg="Notify attempt failed, will retry later" attempts=2 err="create SMTP client: 554 IP is rejected, smtp auth error limit exceed,163 zwqz-smtp-mta-g2-3,_____wDnz8fz9WZldxbuEA--.42126S0 1701246451"
"

Anything else we need to know?

No response

version

Official docker version

Cloud provider

localhost

OS version

macos:13.0.1

Install tools

@zisequkuai zisequkuai added the bug Categorizes issue or PR as related to a bug. label Nov 29, 2023
@cubxxw
Copy link
Contributor

cubxxw commented Nov 29, 2023

Based on the provided logs, it seems that the email notification feature of the application is failing. The error message suggests that there is an issue with the SMTP client and that the IP is being rejected due to an SMTP auth error limit being exceeded.

To resolve this issue, you can try the following steps:

  1. Check if the SMTP credentials are correct and up-to-date.
  2. Check if the SMTP server is running and reachable from the application.
  3. Check if there are any restrictions on the SMTP server that may be causing the issue.
  4. Try increasing the SMTP auth error limit if possible.

If you are unable to resolve the issue, could you please provide detailed information about yourself, such as the status of Docker, logs, and so on?

@zisequkuai
Copy link
Author

Thank you very much for your reply, is it possible to turn off email notifications, also my docker start alertmanager error, but my port 9093 does not have any services, but still says occupied, error messge ” Error invoking remote method 'docker-start-container': Error: (HTTP code 500) server error - driver failed programming external connectivity on endpoint alertmanager ( 5f295efe63d5d48a89e84ff2624d23b09cd3b0378a28c09e8c275ddf22b369e7): Bind 0.0.0.0:9093 failed: port assigned“

@zisequkuai
Copy link
Author

login docker message: "openim-admin | 172.28.0.1 - - [29/Nov/2023:11:09:01 +0000] "GET /login HTTP/1.1" 304 0 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36" "-"
prometheus | ts=2023-11-29T11:09:25.851Z caller=notifier.go:530 level=error component=notifier alertmanager=http://172.28.0.1:19093/api/v2/alerts count=14 msg="Error sending alert" err="Post "http://172.28.0.1:19093/api/v2/alerts\": dial tcp 172.28.0.1:19093: connect: connection refused"
grafana | logger=infra.usagestats t=2023-11-29T11:09:35.865328471Z level=info msg="Usage stats are ready to report"
prometheus | ts=2023-11-29T11:10:40.847Z caller=notifier.go:530 level=error component=notifier alertmanager=http://172.28.0.1:19093/api/v2/alerts count=14 msg="Error sending alert" err="Post "http://172.28.0.1:19093/api/v2/alerts\": dial tcp 172.28.0.1:19093: connect: connection refused"
"

@zisequkuai
Copy link
Author

Configuring smtp has been resolved. thanks a lot @cubxxw bro!

@cubxxw
Copy link
Contributor

cubxxw commented Nov 30, 2023

Congratulations on completing the task! It would be wonderful if you could kindly provide a description and record of the steps and process you undertook here. Your insights and experiences would be greatly appreciated. Thank you for your time and effort!

@kubbot
Copy link
Contributor

kubbot commented Jan 29, 2024

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 29, 2024
@kubbot
Copy link
Contributor

kubbot commented Feb 5, 2024

This issue was closed because it has been stalled for 7 days with no activity.

@kubbot kubbot closed this as completed Feb 5, 2024
@github-actions github-actions bot reopened this Aug 8, 2024
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 8, 2024
@skiffer-git
Copy link
Member

The latest version doesn't have this issue. Please go ahead and use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

4 participants