-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Complete failure of the event system after an attempt to add a hook event #18866
Comments
Before adding events on hooks, I tried to add PSQL events:
I tried to add ES events, but it just said that the endpoint did not respond (that is, ES does not exist on the endpoint) |
lib/pq#414 - seems to be intentional. Since you don't share the actual settings you use, I can't really help you more. |
GitHub does not allow attaching |
Just do |
After the command: minio-server-config-01-25-2024-20-51-32.txt
After trying to add a new event of as hook: minio-server-config-01-25-2024-20-55-56.txt The error remains, events still refuse to be added. |
Expected Behavior
Working events after adding a web hook and restarting the server
Current Behavior
An error is displayed at the standard startup via the command line:
Full console output:
After that, the server turns on normally, only the events do not work. If I try to add a new event, but there will be no error, just please restart so that the changes take effect. After the reboot, the same error occurs, and a new event is not added.
Possible Solution
Most likely, I messed up something while try to adding events
Steps to Reproduce (for bugs)
Context
Before adding the hook event, I tried adding ElasticSearch hooks. But maybe I was doing something wrong, they stubbornly did not want to see the endpoint on the local address. Then, after another reboot, I decided to add just a point of hooks.
Regression
Not
Your Environment
The text was updated successfully, but these errors were encountered: