Error start erpnext

frappe@ip-172-31-19-134:~/frappe-bench$ bench start
06:06:39 system | redis_queue.1 started (pid=30645)
06:06:38 redis_queue.1 | 30649:C 12 Jun 06:06:38.912 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
06:06:38 redis_queue.1 | 30649:C 12 Jun 06:06:38.912 # Redis version=4.0.9, b its=64, commit=00000000, modified=0, pid=30649, just started
06:06:38 redis_queue.1 | 30649:C 12 Jun 06:06:38.912 # Configuration loaded
06:06:39 system | socketio.1 started (pid=30647)
06:06:39 system | schedule.1 started (pid=30650)
06:06:39 system | web.1 started (pid=30646)
06:06:39 redis_queue.1 | 30649:M 12 Jun 06:06:39.402 * Increased maximum numb er of open files to 10032 (it was originally set to 1024).
06:06:39 redis_queue.1 | 30649:M 12 Jun 06:06:39.402 # Creating Server TCP li stening socket 127.0.0.1:11000: bind: Address already in use
06:06:39 system | redis_queue.1 stopped (rc=1)
06:06:40 system | worker_default.1 started (pid=30669)
06:06:40 system | worker_long.1 started (pid=30670)
06:06:40 system | redis_socketio.1 started (pid=30648)
06:06:40 redis_socketio.1 | 30660:C 12 Jun 06:06:39.320 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
06:06:40 redis_socketio.1 | 30660:C 12 Jun 06:06:39.400 # Redis version=4.0.9, b its=64, commit=00000000, modified=0, pid=30660, just started
06:06:40 redis_socketio.1 | 30660:C 12 Jun 06:06:39.400 # Configuration loaded
06:06:40 redis_socketio.1 | 30660:M 12 Jun 06:06:39.401 * Increased maximum numb er of open files to 10032 (it was originally set to 1024).
06:06:40 redis_socketio.1 | 30660:M 12 Jun 06:06:39.401 # Creating Server TCP li stening socket 127.0.0.1:12000: bind: Address already in use
06:06:40 system | redis_socketio.1 stopped (rc=1)
06:06:40 system | redis_cache.1 started (pid=30657)
06:06:40 system | watch.1 started (pid=30661)
06:06:40 system | worker_short.1 started (pid=30681)
06:06:40 system | sending SIGTERM to redis_cache.1 (pid 30657)
06:06:40 system | sending SIGTERM to web.1 (pid 30646)
06:06:40 system | sending SIGTERM to socketio.1 (pid 30647)
06:06:40 system | sending SIGTERM to watch.1 (pid 30661)
06:06:40 system | sending SIGTERM to schedule.1 (pid 30650)
06:06:40 system | sending SIGTERM to worker_short.1 (pid 30681)
06:06:40 system | sending SIGTERM to worker_long.1 (pid 30670)
06:06:40 system | sending SIGTERM to worker_default.1 (pid 30669)
06:06:40 redis_cache.1 | 30676:C 12 Jun 06:06:40.755 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
06:06:40 redis_cache.1 | 30676:C 12 Jun 06:06:40.756 # Redis version=4.0.9, b its=64, commit=00000000, modified=0, pid=30676, just started
06:06:40 redis_cache.1 | 30676:C 12 Jun 06:06:40.756 # Configuration loaded
06:06:40 redis_cache.1 | 30676:M 12 Jun 06:06:40.756 * Increased maximum numb er of open files to 10032 (it was originally set to 1024).
06:06:40 redis_cache.1 | 30676:M 12 Jun 06:06:40.757 # Creating Server TCP li stening socket 127.0.0.1:13000: bind: Address already in use
06:06:40 system | redis_cache.1 stopped (rc=1)
06:06:40 system | worker_short.1 stopped (rc=-15)
06:06:41 system | watch.1 stopped (rc=-15)
06:06:41 system | web.1 stopped (rc=-15)
06:06:41 system | worker_default.1 stopped (rc=-15)
06:06:41 system | worker_long.1 stopped (rc=-15)
06:06:41 system | socketio.1 stopped (rc=-15)
06:06:41 system | schedule.1 stopped (rc=-15)

I cant bench start after i restart EC3 AWS

This means another instance of redis_cache is already running.

It is possible that an orphan redis_cache process is running. You can kill it with

pkill redis

Note: It is also possible that bench start is already running on the server or that the server is running in production mode.

frappe@ip-172-31-19-134:~/frappe-bench$ pkill redis
pkill: killing pid 1162 failed: Operation not permitted

can you help me?