Frappe installation error || Bench start

After bench start:
i am getting this

bench start
04:15:47 system | redis_queue.1 started (pid=6126)
04:15:47 system | web.1 started (pid=6127)
04:15:47 system | redis_cache.1 started (pid=6120)
04:15:47 system | watch.1 started (pid=6132)
04:15:47 redis_cache.1 | 6123:C 30 Apr 2024 04:15:47.212 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
04:15:47 redis_cache.1 | 6123:C 30 Apr 2024 04:15:47.212 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=6123, just started
04:15:47 redis_cache.1 | 6123:C 30 Apr 2024 04:15:47.212 # Configuration loaded
04:15:47 redis_cache.1 | 6123:M 30 Apr 2024 04:15:47.215 * Increased maximum number of open files to 10032 (it was originally set to 1024).
04:15:47 redis_cache.1 | 6123:M 30 Apr 2024 04:15:47.217 * Running mode=standalone, port=13000.
04:15:47 redis_cache.1 | 6123:M 30 Apr 2024 04:15:47.217 # Server initialized
04:15:47 redis_cache.1 | 6123:M 30 Apr 2024 04:15:47.217 # 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.
04:15:47 redis_cache.1 | 6123:M 30 Apr 2024 04:15:47.218 * Ready to accept connections
04:15:47 system | socketio.1 started (pid=6133)
04:15:47 system | worker.1 started (pid=6144)
04:15:47 system | schedule.1 started (pid=6145)
04:15:47 redis_queue.1 | 6129:C 30 Apr 2024 04:15:47.236 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
04:15:47 redis_queue.1 | 6129:C 30 Apr 2024 04:15:47.237 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=6129, just started
04:15:47 redis_queue.1 | 6129:C 30 Apr 2024 04:15:47.237 # Configuration loaded
04:15:47 redis_queue.1 | 6129:M 30 Apr 2024 04:15:47.238 * Increased maximum number of open files to 10032 (it was originally set to 1024).
04:15:47 redis_queue.1 | 6129:M 30 Apr 2024 04:15:47.244 * Running mode=standalone, port=11000.
04:15:47 redis_queue.1 | 6129:M 30 Apr 2024 04:15:47.251 # Server initialized
04:15:47 redis_queue.1 | 6129:M 30 Apr 2024 04:15:47.252 # 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.
04:15:47 redis_queue.1 | 6129:M 30 Apr 2024 04:15:47.253 * Ready to accept connections
04:15:48 socketio.1 | Realtime service listening on: 9000
04:15:48 watch.1 |
04:15:49 web.1 | /home/ubuntu/frappe-bench/env/lib/python3.11/site-packages/passlib/utils/init.py:854: DeprecationWarning: ‘crypt’ is deprecated and slated for removal in Python 3.13
04:15:49 web.1 | from crypt import crypt as _crypt
04:15:49 watch.1 | yarn run v1.22.22
04:15:49 watch.1 | $ node esbuild --watch --live-reload
04:15:49 web.1 | WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead.
04:15:49 web.1 | * Running on all addresses (0.0.0.0)
04:15:49 web.1 | * Running on http://127.0.0.1:8000
04:15:49 web.1 | * Running on http://172.31.41.170:8000
04:15:49 web.1 | Press CTRL+C to quit
04:15:49 web.1 | * Restarting with stat
04:15:50 web.1 | /home/ubuntu/frappe-bench/env/lib/python3.11/site-packages/passlib/utils/init.py:854: DeprecationWarning: ‘crypt’ is deprecated and slated for removal in Python 3.13
04:15:50 web.1 | from crypt import crypt as _crypt
04:15:50 web.1 | * Debugger is active!
04:15:50 web.1 | * Debugger PIN: 434-737-278
04:16:29 watch.1 | Watching for changes…
04:16:29 watch.1 | Error deleting form_builder.bundle.6W7UPKV5.css
04:16:29 watch.1 | Error deleting form_builder.bundle.6W7UPKV5.css
04:16:29 watch.1 | Error deleting print_format_builder.bundle.PS5PYIYU.css
04:16:29 watch.1 | Error deleting print_format_builder.bundle.PS5PYIYU.css
04:16:29 watch.1 | Error deleting workflow_builder.bundle.TSSLVGY7.css
04:16:29 watch.1 | Error deleting build_events.bundle.UQITVRO5.css
04:16:29 watch.1 | Error deleting build_events.bundle.UQITVRO5.css
04:16:29 watch.1 | Error deleting workflow_builder.bundle.TSSLVGY7.css
04:16:29 watch.1 | Error deleting file_uploader.bundle.P35V7PZC.css

In browser i didnt seen any page how to solve

@Ramki_Marichamy server is running just fine , are you sure you entered the right url ?

Running i am getting this error
05:10:07 watch.1 | Watching for changes…
05:10:07 watch.1 | Error deleting form_builder.bundle.6W7UPKV5.css
05:10:07 watch.1 | Error deleting form_builder.bundle.6W7UPKV5.css
05:10:07 watch.1 | Error deleting print_format_builder.bundle.PS5PYIYU.css
05:10:07 watch.1 | Error deleting print_format_builder.bundle.PS5PYIYU.css
05:10:07 watch.1 | Error deleting workflow_builder.bundle.TSSLVGY7.css
05:10:07 watch.1 | Error deleting workflow_builder.bundle.TSSLVGY7.css
05:10:07 watch.1 | Error deleting build_events.bundle.UQITVRO5.css
05:10:07 watch.1 | Error deleting file_uploader.bundle.P35V7PZC.css
05:10:07 watch.1 | Error deleting file_uploader.bundle.P35V7PZC.css
05:10:07 watch.1 | Error deleting build_events.bundle.PF7SQEJJ.js

In website page not found i am getting

@Ramki_Marichamy keep the server running and open another terminal and run curl localhost:8000

:~/frappe-bench$ curl localhost:8000
<!doctype html>

404 Not Found

Not Found

localhost does not exist.

@Ramki_Marichamy you probably did something wrong in the installation. have you created a site and set it as default ? and also try bench build

I created new-site
i run command bench use-site
then i run bench start

bench build i am getting this warn messgae:
DONE Total Build Time: 38.727s

WARN Cannot connect to redis_cache to update assets_json
WARN Cannot connect to redis_cache to update assets_json
WARN Cannot connect to redis_cache to update assets_json
Done in 40.45s.

right now bench restart will work??
if i did bench restart means i am getting this
ubuntu@ip-172-31-41-170:~/frappe-bench$ bench restart
$ supervisorctl restart frappe:
frappe: ERROR (no such group)
frappe: ERROR (no such group)
ERROR: supervisorctl restart frappe:
subprocess.CalledProcessError: Command ‘supervisorctl restart frappe:’ returned non-zero exit status 2.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/local/bin/bench”, line 8, in
sys.exit(cli())
^^^^^
File “/usr/local/lib/python3.11/dist-packages/bench/cli.py”, line 132, in cli
bench_command()
File “/usr/local/lib/python3.11/dist-packages/bench/commands/utils.py”, line 41, in restart
Bench(“.”).reload(web, supervisor, systemd)
File “/usr/local/lib/python3.11/dist-packages/bench/utils/render.py”, line 126, in wrapper_fn
return fn(*args, **kwargs)
^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/dist-packages/bench/bench.py”, line 152, in reload
restart_supervisor_processes(bench_path=self.name, web_workers=web, _raise=_raise)
File “/usr/local/lib/python3.11/dist-packages/bench/utils/bench.py”, line 342, in restart_supervisor_processes
failure = bench.run(f"{sudo}supervisorctl restart {group}", _raise=_raise)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/dist-packages/bench/bench.py”, line 48, in run
return exec_cmd(cmd, cwd=cwd or self.cwd, _raise=_raise)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.11/dist-packages/bench/utils/init.py”, line 169, in exec_cmd
raise CommandFailedError(cmd) from subprocess.CalledProcessError(return_code, cmd)
bench.exceptions.CommandFailedError: supervisorctl restart frappe:

@Ramki_Marichamy bench restart works for production modes but it seems you are running developer mode ,

Thankyou for your reply. Now i again created new frappe-bench
bench new-site
bench use site
bench --site site enable-scheduler
bench --start

Redis error:
I changed port into
cd /etc/redis/redis.conf file
i comment port 6379
and added port 11000 there

while bench start i am getting this now
/frappe-bench$ bench start
06:17:46 system | redis_cache.1 started (pid=12597)
06:17:46 system | web.1 started (pid=12607)
06:17:46 system | redis_queue.1 started (pid=12603)
06:17:46 system | schedule.1 started (pid=12608)
06:17:46 system | watch.1 started (pid=12610)
06:17:46 system | socketio.1 started (pid=12609)
06:17:46 redis_cache.1 | 12600:C 30 Apr 2024 06:17:46.339 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
06:17:46 redis_queue.1 | 12606:C 30 Apr 2024 06:17:46.335 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
06:17:46 redis_queue.1 | 12606:C 30 Apr 2024 06:17:46.340 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=12606, just started
06:17:46 redis_queue.1 | 12606:C 30 Apr 2024 06:17:46.342 # Configuration loaded
06:17:46 redis_queue.1 | 12606:M 30 Apr 2024 06:17:46.343 * Increased maximum number of open files to 10032 (it was originally set to 1024).
06:17:46 redis_cache.1 | 12600:C 30 Apr 2024 06:17:46.343 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=12600, just started
06:17:46 redis_cache.1 | 12600:C 30 Apr 2024 06:17:46.343 # Configuration loaded
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.344 * Increased maximum number of open files to 10032 (it was originally set to 1024).
06:17:46 redis_queue.1 | 12606:M 30 Apr 2024 06:17:46.345 # Could not create server TCP listening socket 127.0.0.1:11000: bind: Address already in use
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.348 * Running mode=standalone, port=13000.
06:17:46 system | redis_queue.1 stopped (rc=1)
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.351 # Server initialized
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.351 # 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.
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.352 * Ready to accept connections
06:17:46 system | worker.1 started (pid=12620)
06:17:46 system | sending SIGTERM to redis_cache.1 (pid 12597)
06:17:46 system | sending SIGTERM to web.1 (pid 12607)
06:17:46 system | sending SIGTERM to socketio.1 (pid 12609)
06:17:46 system | sending SIGTERM to watch.1 (pid 12610)
06:17:46 system | sending SIGTERM to schedule.1 (pid 12608)
06:17:46 system | sending SIGTERM to worker.1 (pid 12620)
06:17:46 redis_cache.1 | 12600:signal-handler (1714457866) Received SIGTERM scheduling shutdown…
06:17:46 system | worker.1 stopped (rc=-15)
06:17:46 system | web.1 stopped (rc=-15)
06:17:46 system | watch.1 stopped (rc=-15)
06:17:46 system | schedule.1 stopped (rc=-15)
06:17:46 system | socketio.1 stopped (rc=-15)
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.457 # User requested shutdown…
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.457 * Removing the pid file.
06:17:46 redis_cache.1 | 12600:M 30 Apr 2024 06:17:46.457 # Redis is now ready to exit, bye bye…
06:17:46 system | redis_cache.1 stopped (rc=-15)

@Ramki_Marichamy Could not create server TCP listening socket 127.0.0.1:11000 . port 11000 is busy. did you close the first one ? with ctrl+c (dont just close the terminal).

How to solve this @bahaou

@Ramki_Marichamy reboot your virtual machine . if you ever set production mode , delete it

@bahaou I reboot that instance
till same error it shows redis 11000

bench --site turiyatree.new enable-scheduler
Enabled for turiyatree.new

frappe-bench$ bench doctor
-----Checking scheduler status-----
Maintenance mode on for turiyatree.new
Scheduler paused for turiyatree.new
turiyatree.new: Maintenance mode is ON
Scheduler inactive for turiyatree.new
Workers online: 0
-----turiyatree.new Jobs-----

For Bench Start Command:
bench start
06:54:20 system | redis_cache.1 started (pid=1616)
06:54:20 system | web.1 started (pid=1624)
06:54:20 system | schedule.1 started (pid=1625)
06:54:20 system | redis_queue.1 started (pid=1622)
06:54:20 system | socketio.1 started (pid=1628)
06:54:20 system | watch.1 started (pid=1632)
06:54:20 redis_cache.1 | 1619:C 30 Apr 2024 06:54:20.541 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
06:54:20 system | worker.1 started (pid=1637)
06:54:20 redis_queue.1 | 1634:C 30 Apr 2024 06:54:20.552 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
06:54:20 redis_cache.1 | 1619:C 30 Apr 2024 06:54:20.552 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=1619, just started
06:54:20 redis_cache.1 | 1619:C 30 Apr 2024 06:54:20.552 # Configuration loaded
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.554 * Increased maximum number of open files to 10032 (it was originally set to 1024).
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.556 * Running mode=standalone, port=13000.
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.557 # Server initialized
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.557 # 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.
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.558 * Ready to accept connections
06:54:20 redis_queue.1 | 1634:C 30 Apr 2024 06:54:20.563 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=1634, just started
06:54:20 redis_queue.1 | 1634:C 30 Apr 2024 06:54:20.563 # Configuration loaded
06:54:20 redis_queue.1 | 1634:M 30 Apr 2024 06:54:20.564 * Increased maximum number of open files to 10032 (it was originally set to 1024).
06:54:20 redis_queue.1 | 1634:M 30 Apr 2024 06:54:20.565 # Could not create server TCP listening socket 127.0.0.1:11000: bind: Address already in use
06:54:20 system | redis_queue.1 stopped (rc=1)
06:54:20 system | sending SIGTERM to redis_cache.1 (pid 1616)
06:54:20 system | sending SIGTERM to web.1 (pid 1624)
06:54:20 system | sending SIGTERM to socketio.1 (pid 1628)
06:54:20 system | sending SIGTERM to watch.1 (pid 1632)
06:54:20 system | sending SIGTERM to schedule.1 (pid 1625)
06:54:20 system | sending SIGTERM to worker.1 (pid 1637)
06:54:20 redis_cache.1 | 1619:signal-handler (1714460060) Received SIGTERM scheduling shutdown…
06:54:20 system | worker.1 stopped (rc=-15)
06:54:20 system | watch.1 stopped (rc=-15)
06:54:20 system | socketio.1 stopped (rc=-15)
06:54:20 system | schedule.1 stopped (rc=-15)
06:54:20 system | web.1 stopped (rc=-15)
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.659 # User requested shutdown…
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.659 * Removing the pid file.
06:54:20 redis_cache.1 | 1619:M 30 Apr 2024 06:54:20.659 # Redis is now ready to exit, bye bye…
06:54:20 system | redis_cache.1 stopped (rc=-15)

bench --version
5.22.3

I added 11000port in redis.confd file
But in bench

its try to connect with 6379
redis-cli
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected> ping
Could not connect to Redis at 127.0.0.1:6379: Connection refused
not connected>