Redis_queue.1 stopped (rc=-15)

Hi,
Redis is stopped how to solve this problem.

~/frappe-bench$ bench start
15:21:57 system           | redis_cache.1 started (pid=13767)
15:21:57 system           | web.1 started (pid=13777)
15:21:57 redis_cache.1    | 13770:C 09 Feb 2023 15:21:57.616 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
15:21:57 redis_cache.1    | 13770:C 09 Feb 2023 15:21:57.616 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13770, just started
15:21:57 redis_cache.1    | 13770:C 09 Feb 2023 15:21:57.616 # Configuration loaded
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.617 * Increased maximum number of open files to 10032 (it was originally set to 1024).
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.618 * Running mode=standalone, port=13000.
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.618 # Server initialized
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.618 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.618 * Ready to accept connections
15:21:57 system           | redis_queue.1 started (pid=13780)
15:21:57 system           | redis_socketio.1 started (pid=13771)
15:21:57 redis_socketio.1 | 13773:C 09 Feb 2023 15:21:57.617 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
15:21:57 redis_socketio.1 | 13773:C 09 Feb 2023 15:21:57.617 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13773, just started
15:21:57 redis_socketio.1 | 13773:C 09 Feb 2023 15:21:57.617 # Configuration loaded
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.618 * Increased maximum number of open files to 10032 (it was originally set to 1024).
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.619 * Running mode=standalone, port=12000.
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.619 # Server initialized
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.619 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.620 * Ready to accept connections
15:21:57 system           | schedule.1 started (pid=13793)
15:21:57 redis_queue.1    | 13783:C 09 Feb 2023 15:21:57.629 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
15:21:57 redis_queue.1    | 13783:C 09 Feb 2023 15:21:57.629 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13783, just started
15:21:57 redis_queue.1    | 13783:C 09 Feb 2023 15:21:57.629 # Configuration loaded
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.630 * Increased maximum number of open files to 10032 (it was originally set to 1024).
15:21:57 system           | socketio.1 started (pid=13797)
15:21:57 system           | watch.1 started (pid=13794)
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.642 * Running mode=standalone, port=11000.
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.642 # Server initialized
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.642 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.643 * Ready to accept connections
15:21:57 system           | worker.1 started (pid=13795)
15:21:57 worker.1         | /bin/sh: 1: cannot create logs/worker.log: Permission denied
15:21:57 system           | worker.1 stopped (rc=2)
15:21:57 system           | sending SIGTERM to redis_cache.1 (pid 13767)
15:21:57 system           | sending SIGTERM to redis_socketio.1 (pid 13771)
15:21:57 system           | sending SIGTERM to redis_queue.1 (pid 13780)
15:21:57 system           | sending SIGTERM to web.1 (pid 13777)
15:21:57 system           | sending SIGTERM to socketio.1 (pid 13797)
15:21:57 system           | sending SIGTERM to watch.1 (pid 13794)
15:21:57 system           | sending SIGTERM to schedule.1 (pid 13793)
15:21:57 redis_cache.1    | 13770:signal-handler (1675936317) Received SIGTERM scheduling shutdown...
15:21:57 redis_queue.1    | 13783:signal-handler (1675936317) Received SIGTERM scheduling shutdown...
15:21:57 redis_socketio.1 | 13773:signal-handler (1675936317) Received SIGTERM scheduling shutdown...
15:21:57 system           | web.1 stopped (rc=-15)
15:21:57 system           | socketio.1 stopped (rc=-15)
15:21:57 system           | schedule.1 stopped (rc=-15)
15:21:57 system           | watch.1 stopped (rc=-15)
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.718 # User requested shutdown...
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.718 * Removing the pid file.
15:21:57 redis_cache.1    | 13770:M 09 Feb 2023 15:21:57.719 # Redis is now ready to exit, bye bye...
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.720 # User requested shutdown...
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.720 * Removing the pid file.
15:21:57 redis_socketio.1 | 13773:M 09 Feb 2023 15:21:57.721 # Redis is now ready to exit, bye bye...
15:21:57 system           | redis_cache.1 stopped (rc=-15)
15:21:57 system           | redis_socketio.1 stopped (rc=-15)
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.743 # User requested shutdown...
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.743 * Removing the pid file.
15:21:57 redis_queue.1    | 13783:M 09 Feb 2023 15:21:57.744 # Redis is now ready to exit, bye bye...
15:21:57 system           | redis_queue.1 stopped (rc=-15)

Thank you.

This is the relevant error. Set appropriate permissions for the log folder/user.

1 Like

@gavindsouza Can, you explain me how to do that๐Ÿ˜•.

Hi, @gavindsouza.

I have solve it using this lines

cd ~/frappe-bench/logs
sudo chown -R frappe:frappe *

Thank a lot.