Redis does not start.cenos7php7vagrant virtualbox environment

Asked 2 years ago, Updated 2 years ago, 115 views

Hello, please lend me your wisdom m(__)m
I'm trying to install and boot Redis 2.8 with yum, but it seems to have stopped booting in the middle.

The installation uses Vagrant and VirtualBox to include apache 2.4 in CentOS 7.1.15.
Adjust the console settings in the virtual box
Vagrant has 2GB of VirtualBox← memory.

server console:

[vagrant@localhost~]$sudo systemctl start redis
[vagrant@localhost~]$sudo systemctl status redis
● redis.service-Redis persistent key-value database
   Loaded: loaded (/usr/lib/systemd/system/redis.service; disabled; vendor preset: disabled)
  Drop-In: /etc/systemd/system/redis.service.d
           --limit.conf
   Active: failed (Result: exit-code) since month 2016-04-25 20:26:43 JST; 2sago
  Process: 3685 ExecStop=/usr/bin/redis-shutdown (code=exited, status=1/FAILURE)
  Process: 3684 ExecStart=/usr/bin/redis-server/etc/redis.conf --daemonize no (code=exited, status=1/FAILURE)
 Main PID: 3684 (code=exited, status=1/FAILURE)

 April 25 20:26:43 localhost.localdomain systemd[1]—Started Redis persistent key-value database.
 April 25 20:26:43 localhost.localdomain systemd[1]—Starting Redis persistent key-value database...
 April 25 20:26:43 localhost.localdomain systemd[1]:redis.service:main process expired, code=exited, status=1/FAILURE
 April 25 20:26:43 localhost.localdomain redis-shutdown [3685]: Could not connect to Redis at 127.0.0.1:6379: Connection refused
 April 25 20:26:43 localhost.localdomain systemd[1]:redis.service:control process expired, code=exited status=1
 April 25 20:26:43 localhost.localdomain systemd[1]: Unit redis.service entered failed state.
 April 25 20:26:43 localhost.localdomain systemd[1]:redis.service failed.
[vagrant@localhost~]$ 

The output is like this.
How should I adjust it to make it move?
Please let me know again.

php centos vagrant virtualbox redis

2022-09-30 19:29

1 Answers

Report Results
Console

>redis-server

Type to run.This is the screen where the redis service is running.
Leave it as it is, boot up another console, and

>redis-clipping
PONG

I was able to confirm that it will boot now.So it didn't seem to have failed the installation.
Run Ctrl+c on the service side to stop the service.

/var/log/redis/redis.log
Review this and the commands in it
'sysctlvm.overcommit_memory=1' Do this

> sudo sysctl vm.overcommit_memory=1
> sudo servicel start redis.service
>servicectl status redis

It worked.
And it's written there,
'/etc/sysctl.conf'

vm.overcommit_memory=1


Get out of virtualBox (Vagrant) and

>vi Vagrantfile

Now comment out the increased memory settings

>vagrant reload

Verify that the default memory space remains at 2048MB (once you increase it, it stays the same)I happened to know)
In vagrantssh

>servicectl status redis

It worked.

I think I'll put it all together in Quita.


2022-09-30 19:29

If you have any answers or tips


© 2024 OneMinuteCode. All rights reserved.