We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After changing configuration in the "globals" section to enable Redis Sentinel, the changes do not get used by the Dashboard
Old configuration
addrs: - redis-1.multipass:6379
New configuration
addrs: - redis-1.multipass:26379 - redis-2.multipass:26379 - redis-3.multipass:26379 enableSentinel: true sentinelPass: "abcd" masterName: "mymaster"
After deploying the Helm chart, Dashboard shows the following errors in the log.
time="Dec 17 10:30:55" level=info msg="Creating new KV connection pool" time="Dec 17 10:30:55" level=info msg="Attempting to reach KV store" time="Dec 17 10:30:55" level=info msg="--> Using SSL (https) for dashboard and API" time="Dec 17 10:30:55" level=info msg="Creating new KV connection pool" time="Dec 17 10:30:55" level=info msg="Attempting to reach KV store" time="Dec 17 10:30:55" level=info msg="Starting zeroconf heartbeat" time="Dec 17 10:30:55" level=info msg="Starting notification handler for gateway cluster" time="Dec 17 10:30:55" level=info msg="Loading routes..." time="Dec 17 10:30:55" level=info msg="Initializing Internal TIB v1.5.1" time="Dec 17 10:30:55" level=info msg="Creating new KV connection pool" time="Dec 17 10:30:55" level=info msg="Attempting to reach KV store" time="Dec 17 10:30:55" level=debug msg="Error trying to set value:ERR Only HELLO messages are accepted by Sentinel instances." time="Dec 17 10:30:55" level=error msg="Could not send notification" time="Dec 17 10:30:55" level=error msg="ERR Only HELLO messages are accepted by Sentinel instances." time="Dec 17 10:30:55" level=info msg="Subscription started: dashboard.ui.messages" time="Dec 17 10:30:55" level=info msg="Subscription started: tyk.cluster.notifications" time="Dec 17 10:30:55" level=info msg="Initializing Identity Cache" prefix="TIB INITIALIZER" time="Dec 17 10:30:55" level=info msg="Set KV store" prefix="TIB REDIS STORE" time="Dec 17 10:30:55" level=info msg="Initializing Identity Cache" prefix="TIB INITIALIZER" time="Dec 17 10:30:55" level=info msg="Set KV store" prefix="TIB REDIS STORE" time="Dec 17 10:30:55" level=info msg="Using internal Identity Broker v1.5.1. Routes are loaded and available." time="Dec 17 10:30:55" level=info msg="Generating portal on the custom domain: tyk-portal.local" 2024/12/17 10:30:55 github.com/TykTechnologies/tyk-analytics/dashboard/sql_storage.go:307 [0.777ms] [rows:1] SELECT * FROM "tyk_organisations" time="Dec 17 10:30:57" level=debug msg="Error trying to set value:ERR Only HELLO messages are accepted by Sentinel instances." time="Dec 17 10:30:57" level=error msg="Could not send notification" time="Dec 17 10:30:57" level=error msg="ERR Only HELLO messages are accepted by Sentinel instances." time="Dec 17 10:30:59" level=debug msg="Error trying to set value:ERR Only HELLO messages are accepted by Sentinel instances." time="Dec 17 10:30:59" level=error msg="Could not send notification" time="Dec 17 10:30:59" level=error msg="ERR Only HELLO messages are accepted by Sentinel instances." time="Dec 17 10:31:01" level=debug msg="Error trying to set value:ERR Only HELLO messages are accepted by Sentinel instances." time="Dec 17 10:31:01" level=error msg="Could not send notification"
After the following is added into the "tyk-dashboard" section, Dashboard no longer shows the errors:
extraEnvs: - name: TYK_DB_REDISMASTERNAME value: mymaster - name: TYK_DB_REDISSENTINELPASSWORD value: abcd
The text was updated successfully, but these errors were encountered:
No branches or pull requests
After changing configuration in the "globals" section to enable Redis Sentinel, the changes do not get used by the Dashboard
Old configuration
New configuration
After deploying the Helm chart, Dashboard shows the following errors in the log.
After the following is added into the "tyk-dashboard" section, Dashboard no longer shows the errors:
The text was updated successfully, but these errors were encountered: