-
Notifications
You must be signed in to change notification settings - Fork 108
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] redis-server refuses to start on Fedora 38 #3403
Labels
Comments
ndokos
added
bug
Agent
Tool Meister
Of and relating to the Tool Meister sub-system
labels
Apr 26, 2023
However we choose to address this, the fix needs to apply to the Fedora-38-based containerized Agent as well. (We might want to contemplate whether fixing the container should be the fix for this issue...although, perhaps it's too soon to suggest that we ship only a containerized Agent instead of a native installation.) |
Ditto on Fedora 37. |
ndokos
added a commit
to ndokos/pbench
that referenced
this issue
May 24, 2023
Fixes distributed-system-analysis#3403. Fedora 37 and Fedora 38 run it in protected mode by default. We probably should be doing that everywhere but for the time being, we turn it off everywhere instead.
ndokos
added a commit
to ndokos/pbench
that referenced
this issue
May 24, 2023
Fixes distributed-system-analysis#3403. Fedora 37 and Fedora 38 run it in protected mode by default. We probably should be doing that everywhere but for the time being, we turn it off everywhere instead. PBENCH-1163
ndokos
added a commit
that referenced
this issue
May 25, 2023
* Disable redis protected-mode Fixes #3403. Fedora 37 and Fedora 38 run it in protected mode by default. We probably should be doing that everywhere but for the time being, we turn it off everywhere instead. PBENCH-1163 * Fix the util-scripts tool-meister tests
ndokos
added a commit
to ndokos/pbench
that referenced
this issue
Jun 7, 2023
Fixes distributed-system-analysis#3403. Fedora 37 and Fedora 38 run it in protected mode by default. We probably should be doing that everywhere but for the time being, we turn it off everywhere instead. Fix the util-scripts tool-meister tests PBENCH-1163
ndokos
added a commit
that referenced
this issue
Jun 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Description
On Fedora 38,
redis-server
does not start:[warn][2023-04-26T17:26:44.476406] Unable to connect to redis server,
Redis server
Redis is running in protected mode because protected mode is enabled
and no password is set for the default user. In this mode connections
are only accepted from the loopback interface. If you want to connect
from external computers to Redis you may adopt one of the following
solutions:
Just disable protected mode sending the command 'CONFIG
SET protected-mode no' from the loopback interface by connecting to
Redis from the same host the server is running, however MAKE SURE
Redis is not publicly accessible from internet if you do so. Use
CONFIG REWRITE to make this change permanent.
Alternatively you can just disable the protected mode by editing
the Redis configuration file, and setting the protected mode option to
'no', and then restarting the server.
If you started the server manually just for testing, restart it
with the '--protected-mode no' option.
Setup a an authentication password for the default user. NOTE: You
only need to do one of the above things in order for the server to
start accepting connections from the outside.
Version info:
[root@dhcp31-112 ~]# uname -a
Linux dhcp31-112.perf.lab.eng.bos.redhat.com 6.2.9-300.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Mar 30 22:32:58 UTC 2023 x86_64 GNU/Linux
[root@dhcp31-112 ~]# redis-server --version
Redis server v=7.0.10 sha=00000000:0 malloc=jemalloc-5.2.1 bits=64 build=3ac3e681393b08b3
To Reproduce
Run
pbench-user-benchmark -- sleep 20
on a Fedora 38 system with a v0.72 agent.Actual Results
redis-server
issues a warning and does not start.Expected Results
redis-server
should start.Additional information
No response
The text was updated successfully, but these errors were encountered: