Redis-server Failed to start Topic is solved

[Rilic]

I had just managed to get Gitea set up when I decided to uninstall the proftp fileserver. On reboot, the redis-server fails to start and that in turn has stopped other services from working properly (nextcloud, gitea and cuberite).

Here's the output of systemctl status redis-server.service:

Code: Select all

● redis-server.service - Advanced key-value store
   Loaded: loaded (/lib/systemd/system/redis-server.service; disabled; vendor preset: enabled)
   Active: failed (Result: resources) since Fri 2020-05-08 18:35:25 BST; 1min 24s ago
     Docs: http://redis.io/documentation,
           man:redis-server(1)

May 08 18:35:25 Condor systemd[1]: redis-server.service: Service RestartSec=100ms expired, sched
uling restart.
May 08 18:35:25 Condor systemd[1]: redis-server.service: Scheduled restart job, restart counter 
is at 5.
May 08 18:35:25 Condor systemd[1]: Stopped Advanced key-value store.
May 08 18:35:25 Condor systemd[1]: redis-server.service: Start request r
epeated too quickly.
May 08 18:35:25 Condor systemd[1]: redis-server.service: Failed with res
ult 'resources'.
May 08 18:35:25 Condor systemd[1]: Failed to start Advanced key-value st
ore.

Any ideas?

[Rilic]

Here is an interesting line from journalctl:

Code: Select all

May 08 18:35:24 Condor systemd[1]: redis-server.service: Failed to run 'start' task: Read-only file system

Might this have something to do with it?

[Joulinar]

Hi,

I guess this hit you as well viewtopic.php?f=11&t=7595

If yes, pls follow the workaround I described

[Rilic]

That did it! Thank you, I thought my installation was a goner.

You might recall my post earlier about changing the drive. Would this affect the steps needed to make the switch? I'm still very new to Linux, so sorry if it seems obvious.

[Joulinar]

yes, pls don't use driver manager for next days until DietPi v6.30 was released. This should fix the issues with r/o file systems.