You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
failed {"error": "Error 1419: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)"}
#66
Open
mbauer599 opened this issue
Feb 16, 2024
· 1 comment
I'm attempting to integrate icinga into Amazon RDS (mysql) and am running into this issue. It's not possible to grant SUPER or set log_bin_trust_function_creators in this environment, so I need an alternative workaround.
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | 2024-02-16T16:27:16.199Z DEBUG entrypoint/main.go:42 translating env vars to YAML config
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | 2024-02-16T16:27:16.200Z DEBUG entrypoint/main.go:108 checking SQL database
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | 2024-02-16T16:27:20.205Z DEBUG entrypoint/main.go:137 importing schema into SQL database
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | 2024-02-16T16:27:20.214Z FATAL entrypoint/main.go:38 failed {"error": "Error 1419: You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)"}
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | main.main
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | /entrypoint/main.go:38
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | runtime.main
docker-compose-icinga_icingadb.1.luk77f7knb39@hdicingam01 | /usr/local/go/src/runtime/proc.go:267
And ideas or help is appreciated.
The text was updated successfully, but these errors were encountered:
Exactly as the error states.
I'm attempting to integrate icinga into Amazon RDS (mysql) and am running into this issue. It's not possible to grant SUPER or set
log_bin_trust_function_creators
in this environment, so I need an alternative workaround.And ideas or help is appreciated.
The text was updated successfully, but these errors were encountered: