Bench start error on VPS System

I received the following error while starting bench

10:36:41 redis_cache.1 | [15861] 07 Oct 10:36:41.923 # 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.
10:36:41 redis_cache.1 | [15861] 07 Oct 10:36:41.923 * The server is now ready to accept connections on port 13000
10:36:42 socketio.1 | events.js:160
10:36:42 socketio.1 | throw er; // Unhandled ‘error’ event
10:36:42 socketio.1 | ^
10:36:42 socketio.1 |
10:36:42 socketio.1 | Error: listen EADDRINUSE :::9000
10:36:42 socketio.1 | at Object.exports._errnoException (util.js:1036:11)
10:36:42 socketio.1 | at exports._exceptionWithHostPort (util.js:1059:20)
10:36:42 socketio.1 | at Server._listen2 (net.js:1252:14)
10:36:42 socketio.1 | at listen (net.js:1288:10)
10:36:42 socketio.1 | at Server.listen (net.js:1384:5)
10:36:42 socketio.1 | at Object. (/home/ujjawal/frappe-bench/apps/frappe/socketio.js:13:6)
10:36:42 socketio.1 | at Module._compile (module.js:556:32)
10:36:42 socketio.1 | at Object.Module._extensions…js (module.js:565:10)
10:36:42 socketio.1 | at Module.load (module.js:473:32)
10:36:42 socketio.1 | at tryModuleLoad (module.js:432:12)
10:36:42 system | socketio.1 stopped (rc=1)
10:36:42 system | sending SIGTERM to redis_socketio.1 (pid 15817)
10:36:42 system | sending SIGTERM to worker_long.1 (pid 15819)
10:36:42 system | sending SIGTERM to watch.1 (pid 15821)
10:36:42 system | sending SIGTERM to redis_queue.1 (pid 15823)
10:36:42 system | sending SIGTERM to web.1 (pid 15826)
10:36:42 system | sending SIGTERM to schedule.1 (pid 15828)
10:36:42 system | sending SIGTERM to worker_default.1 (pid 15830)
10:36:42 system | sending SIGTERM to redis_cache.1 (pid 15831)
10:36:42 system | sending SIGTERM to worker_short.1 (pid 15832)
10:36:42 redis_socketio.1 | [15834 | signal handler] (1475836602) Received SIGTERM, scheduling shutdown…
10:36:42 redis_queue.1 | [15838 | signal handler] (1475836602) Received SIGTERM, scheduling shutdown…
10:36:42 redis_cache.1 | [15861 | signal handler] (1475836602) Received SIGTERM, scheduling shutdown…
10:36:42 system | worker_long.1 stopped (rc=-15)
10:36:42 system | schedule.1 stopped (rc=-15)
10:36:42 system | watch.1 stopped (rc=-15)
10:36:42 system | worker_default.1 stopped (rc=-15)
10:36:42 system | worker_short.1 stopped (rc=-15)
10:36:42 system | web.1 stopped (rc=-15)
10:36:42 redis_socketio.1 | [15834] 07 Oct 10:36:42.417 # User requested shutdown…
10:36:42 redis_socketio.1 | [15834] 07 Oct 10:36:42.417 # Redis is now ready to exit, bye bye…
10:36:42 system | redis_socketio.1 stopped (rc=-15)
10:36:42 redis_queue.1 | [15838] 07 Oct 10:36:42.419 # User requested shutdown…
10:36:42 redis_queue.1 | [15838] 07 Oct 10:36:42.419 # Redis is now ready to exit, bye bye…
10:36:42 system | redis_queue.1 stopped (rc=-15)
10:36:42 redis_cache.1 | [15861] 07 Oct 10:36:42.425 # User requested shutdown…
10:36:42 redis_cache.1 | [15861] 07 Oct 10:36:42.425 # Redis is now ready to exit, bye bye…
10:36:42 system | redis_cache.1 stopped (rc=-15)

@Ujjawal
However, I don’t have any idea about it, but I noticed one thing regarding some memory on the top of the error.

Try these things:

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.

Regards
Ruchin Sharma