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
``#### Prerequisites
Please check the FAQ, and search existing issues for similar questions before creating a new issue.YOU MAY DELETE THIS PREREQUISITES SECTION.
[ v ] I have checked the FAQ, and issues and found no answer.
I am using Pinpoint 3.0.1 and configured Redis to work on the same host as the Pinpoint Collector, without authentication. Despite confirming that Redis is up and running, I still get a RedisConnectionFailureException when starting the Collector. I am intentionally using Redis, unlike issue #11880, which discusses avoiding Redis.
I have not configured a Redis password, and verified the following:
Redis is running locally on port 6379.
No password is required (requirepass is not set).
Environment:
Pinpoint/collector version: 3.0.1
Please investigate why Redis authentication is being attempted even when no password is configured. Let me know if there is a workaround or patch needed for this version.
``#### Prerequisites
Please check the FAQ, and search existing issues for similar questions before creating a new issue.YOU MAY DELETE THIS PREREQUISITES SECTION.
I am using Pinpoint 3.0.1 and configured Redis to work on the same host as the Pinpoint Collector, without authentication. Despite confirming that Redis is up and running, I still get a RedisConnectionFailureException when starting the Collector. I am intentionally using Redis, unlike issue #11880, which discusses avoiding Redis.
application.yml
I have not configured a Redis password, and verified the following:
Redis is running locally on port 6379.
No password is required (requirepass is not set).
Environment:
Pinpoint/collector version: 3.0.1
Please investigate why Redis authentication is being attempted even when no password is configured. Let me know if there is a workaround or patch needed for this version.
error.txt
The text was updated successfully, but these errors were encountered: