Hi, After cloning a bench through Bit Bucket in my local machine, Bench Start is not working .

ERPNext
1 
WARN: Command not being executed in bench directory
11:24:58 system           | redis_cache.1 started (pid=4413)
11:24:58 system           | redis_socketio.1 started (pid=4416)
11:24:58 system           | redis_queue.1 started (pid=4421)
11:24:58 system           | socketio.1 started (pid=4429)
11:24:58 system           | web.1 started (pid=4425)
11:24:58 system           | watch.1 started (pid=4431)
11:24:58 system           | schedule.1 started (pid=4435)
11:24:58 redis_queue.1    | 4422:C 16 May 2023 11:24:58.506 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11:24:58 redis_queue.1    | 4422:C 16 May 2023 11:24:58.506 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=4422, just started
11:24:58 redis_queue.1    | 4422:C 16 May 2023 11:24:58.506 # Configuration loaded
11:24:58 redis_socketio.1 | 4419:C 16 May 2023 11:24:58.506 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11:24:58 redis_socketio.1 | 4419:C 16 May 2023 11:24:58.506 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=4419, just started
11:24:58 redis_socketio.1 | 4419:C 16 May 2023 11:24:58.506 # Configuration loaded
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.507 * Increased maximum number of open files to 10032 (it was originally set to 1024).
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.507 * Increased maximum number of open files to 10032 (it was originally set to 1024).
11:24:58 redis_cache.1    | 4417:C 16 May 2023 11:24:58.506 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
11:24:58 redis_cache.1    | 4417:C 16 May 2023 11:24:58.506 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=4417, just started
11:24:58 redis_cache.1    | 4417:C 16 May 2023 11:24:58.506 # Configuration loaded
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.507 * Increased maximum number of open files to 10032 (it was originally set to 1024).
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.508 * Running mode=standalone, port=11003.
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.508 # Server initialized
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.508 * Running mode=standalone, port=13003.
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.508 # Server initialized
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.508 # 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.
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.508 # 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.
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.508 * Running mode=standalone, port=12003.
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.508 # Server initialized
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.508 # 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.
11:24:58 system           | worker.1 started (pid=4439)
11:24:58 worker.1         | /bin/sh: 1: cannot create logs/worker.log: Directory nonexistent
11:24:58 system           | worker.1 stopped (rc=2)
11:24:58 system           | sending SIGTERM to redis_cache.1 (pid 4413)
11:24:58 system           | sending SIGTERM to redis_socketio.1 (pid 4416)
11:24:58 system           | sending SIGTERM to redis_queue.1 (pid 4421)
11:24:58 system           | sending SIGTERM to web.1 (pid 4425)
11:24:58 system           | sending SIGTERM to socketio.1 (pid 4429)
11:24:58 system           | sending SIGTERM to watch.1 (pid 4431)
11:24:58 system           | sending SIGTERM to schedule.1 (pid 4435)
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.509 * Ready to accept connections
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.509 * Ready to accept connections
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.510 * Ready to accept connections
11:24:58 redis_cache.1    | 4417:signal-handler (1684216498) Received SIGTERM scheduling shutdown...
11:24:58 redis_socketio.1 | 4419:signal-handler (1684216498) Received SIGTERM scheduling shutdown...
11:24:58 redis_queue.1    | 4422:signal-handler (1684216498) Received SIGTERM scheduling shutdown...
11:24:58 system           | socketio.1 stopped (rc=-15)
11:24:58 system           | web.1 stopped (rc=-15)
11:24:58 system           | schedule.1 stopped (rc=-15)
11:24:58 system           | watch.1 stopped (rc=-15)
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.609 # User requested shutdown...
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.609 * Removing the pid file.
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.609 # User requested shutdown...
11:24:58 redis_socketio.1 | 4419:M 16 May 2023 11:24:58.609 # Redis is now ready to exit, bye bye...
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.609 * Removing the pid file.
11:24:58 redis_queue.1    | 4422:M 16 May 2023 11:24:58.609 # Redis is now ready to exit, bye bye...
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.610 # User requested shutdown...
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.610 * Removing the pid file.
11:24:58 redis_cache.1    | 4417:M 16 May 2023 11:24:58.610 # Redis is now ready to exit, bye bye...
11:24:58 system           | redis_queue.1 stopped (rc=-15)
11:24:58 system           | redis_socketio.1 stopped (rc=-15)
11:24:58 system           | redis_cache.1 stopped (rc=-15)
2

Did you run bench start in the /home/user/frappe-bench/ folder?

3

Yes I did .

4

11:24:58 worker.1 | /bin/sh: 1: cannot create /home/user/frappe-bench/logs/worker.log: Directory nonexistent

Have you checked permissions on /home/user/frappe-bench/ and subfolders especially the logs folder?

5

Yes, I have checked but still, the problem exists.

6

i would now say reset your system. try installing everything from zero. because without more information nobody can help you. the error is unclear.

i believe there will be some important system files missing that are being installed when you go through the normal installation procedure that are not on your machine when you copy from bit bucket.

7

Sure, I will look into that now.