Unable to connect with the server

After successful installation of erpnext this error shows.

frappe@priyangshusvm:~/frappe-bench$ bench start
07:24:28 system | redis_cache.1 started (pid=3560)
07:24:28 system | schedule.1 started (pid=3568)
07:24:28 system | worker_short.1 started (pid=3569)
07:24:28 system | redis_socketio.1 started (pid=3570)
07:24:28 system | worker_long.1 started (pid=3572)
07:24:28 system | web.1 started (pid=3571)
07:24:28 system | worker_default.1 started (pid=3573)
07:24:28 system | redis_queue.1 started (pid=3577)
07:24:28 system | socketio.1 started (pid=3574)
07:24:28 system | watch.1 started (pid=3567)
07:24:29 redis_cache.1 | 3560:C 01 Aug 2023 07:24:29.566 # oO0OoO0OoO0Oo Redi s is starting oO0OoO0OoO0Oo
07:24:29 redis_cache.1 | 3560:C 01 Aug 2023 07:24:29.566 # Redis version=6.0. 16, bits=64, commit=00000000, modified=0, pid=3560, just started
07:24:29 redis_cache.1 | 3560:C 01 Aug 2023 07:24:29.566 # Configuration load ed
07:24:29 redis_cache.1 | 3560:M 01 Aug 2023 07:24:29.567 * Increased maximum number of open files to 10032 (it was originally set to 1024).
07:24:29 redis_queue.1 | 3577:C 01 Aug 2023 07:24:29.567 # oO0OoO0OoO0Oo Redi s is starting oO0OoO0OoO0Oo
07:24:29 redis_queue.1 | 3577:C 01 Aug 2023 07:24:29.568 # Redis version=6.0. 16, bits=64, commit=00000000, modified=0, pid=3577, just started
07:24:29 redis_queue.1 | 3577:C 01 Aug 2023 07:24:29.568 # Configuration load ed
07:24:29 redis_socketio.1 | 3570:C 01 Aug 2023 07:24:29.567 # oO0OoO0OoO0Oo Redi s is starting oO0OoO0OoO0Oo
07:24:29 redis_socketio.1 | 3570:C 01 Aug 2023 07:24:29.569 # Redis version=6.0. 16, bits=64, commit=00000000, modified=0, pid=3570, just started
07:24:29 redis_socketio.1 | 3570:C 01 Aug 2023 07:24:29.569 # Configuration load ed
07:24:29 redis_queue.1 | 3577:M 01 Aug 2023 07:24:29.572 * Increased maximum number of open files to 10032 (it was originally set to 1024).
07:24:29 redis_socketio.1 | 3570:M 01 Aug 2023 07:24:29.570 * Increased maximum number of open files to 10032 (it was originally set to 1024).
07:24:29 redis_socketio.1 | 3570:M 01 Aug 2023 07:24:29.570 # Could not create s erver TCP listening socket 127.0.0.1:12000: bind: Address already in use
07:24:29 system | redis_socketio.1 stopped (rc=1)
07:24:29 system | sending SIGTERM to redis_cache.1 (pid 3560)
07:24:29 system | sending SIGTERM to redis_queue.1 (pid 3577)
07:24:29 system | sending SIGTERM to web.1 (pid 3571)
07:24:29 system | sending SIGTERM to socketio.1 (pid 3574)
07:24:29 system | sending SIGTERM to watch.1 (pid 3567)
07:24:29 system | sending SIGTERM to schedule.1 (pid 3568)
07:24:29 system | sending SIGTERM to worker_short.1 (pid 3569)
07:24:29 system | sending SIGTERM to worker_long.1 (pid 3572)
07:24:29 system | sending SIGTERM to worker_default.1 (pid 3573)
07:24:29 redis_queue.1 | 3577:M 01 Aug 2023 07:24:29.572 # Could not create s erver TCP listening socket 127.0.0.1:11000: bind: Address already in use
07:24:29 system | socketio.1 stopped (rc=-15)
07:24:29 system | worker_short.1 stopped (rc=-15)
07:24:29 redis_cache.1 | 3560:signal-handler (1690874669) Received SIGTERM sc heduling shutdown…
07:24:29 redis_cache.1 | 3560:M 01 Aug 2023 07:24:29.574 # Could not create s erver TCP listening socket 127.0.0.1:13000: bind: Address already in use
07:24:29 system | worker_long.1 stopped (rc=-15)
07:24:29 system | worker_default.1 stopped (rc=-15)
07:24:29 system | redis_cache.1 stopped (rc=1)
07:24:29 redis_queue.1 | 3577:signal-handler (1690874669) Received SIGTERM sc heduling shutdown…
07:24:29 system | redis_queue.1 stopped (rc=1)
07:24:29 system | web.1 stopped (rc=-15)
07:24:29 system | watch.1 stopped (rc=-15)
07:24:29 system | schedule.1 stopped (rc=-15)

https://discuss.frappe.io/search?q=bind%3A%20Address%20already%20in%20use%20order%3Alatest

You already have a running copy, so either stop that one, and then try again, or reboot the server so that it can start safely