Need help. After update I am getting ” Sorry! We will be back soon.”

Hello,I ran a bench update, and it went smooth without errors, but then I can’t access my site and I get "Sorry! We will be back soon."Here is what i get when I run bench update:

frappe@work:~$ bench update
INFO:bench.utils:updating bench
INFO:bench.utils:git pull
Already up-to-date.
remote: Counting objects: 21, done.
remote: Compressing objects: 100% (10/10), done.
remote: Total 21 (delta 13), reused 19 (delta 11), pack-reused 0
Unpacking objects: 100% (21/21), done.
From https://github.com/frappe/frappe
   3f320db..1ba3d14  develop    -> upstream/develop
INFO:bench.utils:./env/bin/pip install Pillow
Requirement already satisfied: Pillow in ./env/lib/python2.7/site-packages
INFO:bench.app:pulling frappe
INFO:bench.utils:git pull  upstream master
From https://github.com/frappe/frappe
 * branch            master     -> FETCH_HEAD
Already up-to-date.
INFO:bench.utils:find . -name "*.pyc" -delete
INFO:bench.app:pulling erpnext
INFO:bench.utils:git pull  upstream master
From https://github.com/frappe/erpnext
 * branch            master     -> FETCH_HEAD
Already up-to-date.
INFO:bench.utils:find . -name "*.pyc" -delete
Updating Python libraries...
INFO:bench.utils:./env/bin/pip install --upgrade pip
/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pip/_vendor/requ                                                                                                             ests/packages/urllib3/util/ssl_.py:318: SNIMissingWarning: An HTTPS request has                                                                                                              been made, but the SNI (Subject Name Indication) extension to TLS is not availab                                                                                                             le on this platform. This may cause the server to present an incorrect TLS certi                                                                                                             ficate, which can cause validation failures. You can upgrade to a newer version                                                                                                              of Python to solve this. For more information, see https://urllib3.readthedocs.i                                                                                                             o/en/latest/security.html#snimissingwarning.
  SNIMissingWarning
/home/frappe/frappe-bench/env/local/lib/python2.7/site-packages/pip/_vendor/requ                                                                                                             ests/packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true SSLConte                                                                                                             xt object is not available. This prevents urllib3 from configuring SSL appropria                                                                                                             tely and may cause certain SSL connections to fail. You can upgrade to a newer v                                                                                                             ersion of Python to solve this. For more information, see https://urllib3.readth                                                                                                             edocs.io/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
Requirement already up-to-date: pip in ./env/lib/python2.7/site-packages
INFO:bench.utils:./env/bin/pip install -q -r /home/frappe/bench-repo/requirement                                                                                                             s.txt
INFO:bench.utils:./env/bin/pip install -q -r ./apps/ui_customization/requirement                                                                                                             s.txt
INFO:bench.utils:./env/bin/pip install -q -r ./apps/frappe/requirements.txt
INFO:bench.utils:./env/bin/pip install -q -r ./apps/erpnext/requirements.txt
Updating node libraries...
INFO:bench.utils:npm install
frappe@ /home/frappe/frappe-bench
├── babel-core@6.24.1
├── babel-preset-babili@0.0.12
├── babel-preset-es2015@6.24.1
├── babel-preset-es2016@6.24.1
├── babel-preset-es2017@6.24.1
├── chokidar@1.7.0
├── cookie@0.3.1
├── less@2.7.2
└── socket.io@2.0.1

npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.1.2
npm WARN frappe@ No description
Backing up sites...
Patching sites...
Migrating site1.local
Updating DocTypes for frappe        : [========================================]
Updating DocTypes for erpnext       : [========================================]
Syncing help database...
Migrating site2.local
Updating DocTypes for frappe        : [========================================]
Updating DocTypes for erpnext       : [========================================]
Syncing help database...
Migrating site3.local
Updating DocTypes for frappe        : [========================================]
Updating DocTypes for erpnext       : [========================================]
Syncing help database...
Migrating site4.local
Updating DocTypes for frappe        : [========================================]
Updating DocTypes for erpnext       : [========================================]
Syncing help database...
Migrating site5.local
Updating DocTypes for frappe        : [========================================]
Updating DocTypes for erpnext       : [========================================]
Syncing help database...
Wrote css/frappe-web.css - 64.95 KB
Wrote js/frappe-web.min.js - 138.62 KB
Wrote js/dialog.min.js - 94.68 KB
Wrote css/desk.min.css - 280.95 KB
Wrote css/frappe-rtl.css - 31.78 KB
Wrote js/libs.min.js - 814.29 KB
Wrote js/desk.min.js - 384.08 KB
Wrote js/d3.min.js - 380.17 KB
Wrote css/module.min.css - 2.08 KB
Wrote css/form.min.css - 4.47 KB
Wrote js/form.min.js - 185.93 KB
Wrote css/list.min.css - 15.72 KB
Wrote js/list.min.js - 145.52 KB
Wrote css/report.min.css - 7.77 KB
Wrote js/report.min.js - 255.37 KB
Wrote js/web_form.min.js - 247.45 KB
Wrote css/web_form.css - 24.42 KB
Wrote js/print_format_v3.min.js - 23.3 KB
Wrote css/erpnext.css - 7.87 KB
Wrote js/erpnext-web.min.js - 3.62 KB
Wrote js/erpnext.min.js - 115.87 KB
Wrote js/item-dashboard.min.js - 7.65 KB
INFO:bench.utils:sudo supervisorctl restart frappe-bench-workers: frappe-bench-web:
frappe-bench-frappe-schedule: stopped
frappe-bench-frappe-default-worker-0: stopped
frappe-bench-frappe-long-worker-0: stopped
frappe-bench-frappe-short-worker-0: stopped
frappe-bench-node-socketio: stopped
frappe-bench-frappe-web: stopped
frappe-bench-frappe-schedule: started
frappe-bench-frappe-default-worker-0: started
frappe-bench-frappe-long-worker-0: started
frappe-bench-frappe-short-worker-0: started
frappe-bench-frappe-web: started
frappe-bench-node-socketio: started
________________________________________________________________________________
Bench: Deployment tool for Frappe and ERPNext (https://erpnext.org).
Open source depends on your contributions, so please contribute bug reports, patches, fixes or cash and be a part of the community
()
frappe@work:~$

And after I ran the update and couldn’t access the site still, I ran sudo supervisorctl restart all and the result was:

frappe@work:~$ sudo supervisorctl restart all
frappe-bench-frappe-schedule: stopped
frappe-bench-frappe-default-worker-0: stopped
frappe-bench-frappe-long-worker-0: stopped
frappe-bench-frappe-short-worker-0: stopped
frappe-bench-frappe-web: stopped
frappe-bench-node-socketio: stopped
frappe-bench-redis-queue: stopped
frappe-bench-frappe-schedule: started
frappe-bench-frappe-default-worker-0: started
frappe-bench-frappe-long-worker-0: started
frappe-bench-frappe-short-worker-0: started
frappe-bench-frappe-web: started
frappe-bench-node-socketio: started
frappe-bench-redis-queue: started
frappe-bench-redis-cache: ERROR (abnormal termination)
frappe-bench-redis-socketio: ERROR (abnormal termination)
frappe@work:~$

I then ran sudo supervisorctl status, and the result is:

frappe@work:~$ sudo supervisorctl status
frappe-bench-redis:frappe-bench-redis-cache FATAL      Exited too quickly (process log may have details)
frappe-bench-redis:frappe-bench-redis-queue RUNNING    pid 20307, uptime 0:28:53
frappe-bench-redis:frappe-bench-redis-socketio FATAL      Exited too quickly (process log may have details)
frappe-bench-web:frappe-bench-frappe-web RUNNING    pid 23035, uptime 0:00:02
frappe-bench-web:frappe-bench-node-socketio RUNNING    pid 20285, uptime 0:28:53
frappe-bench-workers:frappe-bench-frappe-default-worker-0 RUNNING    pid 20283, uptime 0:28:54
frappe-bench-workers:frappe-bench-frappe-long-worker-0 RUNNING    pid 20306, uptime 0:28:53
frappe-bench-workers:frappe-bench-frappe-schedule RUNNING    pid 20241, uptime 0:28:56
frappe-bench-workers:frappe-bench-frappe-short-worker-0 RUNNING    pid 20270, uptime 0:28:54

I never faced this before. Can somebody help me in getting my system back?

Regards,
Ahmed

Hi see Supervisor doesnot start

You can try reloading supervisor:
sudo supervisorctl reload

Please check the /frappe-bench/logs directory for error logs

Dear @makarand_b Which log file exactly I should look into? For example there is one called redis-soketio.log and it reads"

[8795] 26 Jul 02:15:54.620 * Max number of open files set to 10032
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 8795
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[8795] 26 Jul 02:15:54.638 # Server started, Redis version 2.8.4
[8795] 26 Jul 02:15:54.639 # 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.
[8795] 26 Jul 02:15:54.639 * The server is now ready to accept connections on port 12311
[8795 | signal handler] (1469514703) Received SIGTERM, scheduling shutdown...
[8795] 26 Jul 02:31:43.944 # User requested shutdown...
[8795] 26 Jul 02:31:43.945 # Redis is now ready to exit, bye bye...
[9386] 26 Jul 02:31:48.204 * Max number of open files set to 10032
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 9386
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[9386] 26 Jul 02:31:48.217 # Server started, Redis version 2.8.4
[9386] 26 Jul 02:31:48.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.
[9386] 26 Jul 02:31:48.217 * The server is now ready to accept connections on port 12311
[9386 | signal handler] (1469514830) Received SIGTERM, scheduling shutdown...
[9386] 26 Jul 02:33:50.954 # User requested shutdown...
[9386] 26 Jul 02:33:50.954 # Redis is now ready to exit, bye bye...
[9558] 26 Jul 02:33:55.067 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 9558
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[9558] 26 Jul 02:33:55.085 # Server started, Redis version 2.8.4
[9558] 26 Jul 02:33:55.085 # 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.
[9558] 26 Jul 02:33:55.085 * The server is now ready to accept connections on port 12311
[2161] 14 Aug 01:22:02.930 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 2161
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[2161] 14 Aug 01:22:02.944 # Server started, Redis version 2.8.4
[2161] 14 Aug 01:22:02.944 # 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.
[2161] 14 Aug 01:22:02.944 * The server is now ready to accept connections on port 12311
[2161 | signal handler] (1471152430) Received SIGTERM, scheduling shutdown...
[2161] 14 Aug 01:27:10.674 # User requested shutdown...
[2161] 14 Aug 01:27:10.675 # Redis is now ready to exit, bye bye...
[2122] 14 Aug 01:28:01.826 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 2122
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[2122] 14 Aug 01:28:01.854 # Server started, Redis version 2.8.4
[2122] 14 Aug 01:28:01.854 # 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.
[2122] 14 Aug 01:28:01.857 * The server is now ready to accept connections on port 12311
[2122 | signal handler] (1472366378) Received SIGTERM, scheduling shutdown...
[2122] 28 Aug 02:39:38.903 # User requested shutdown...
[2122] 28 Aug 02:39:38.903 # Redis is now ready to exit, bye bye...
[8014] 28 Aug 02:39:40.640 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 8014
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[8014] 28 Aug 02:39:40.675 # Server started, Redis version 2.8.4
[8014] 28 Aug 02:39:40.675 # 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.
[8014] 28 Aug 02:39:40.676 * The server is now ready to accept connections on port 12311
[8014 | signal handler] (1472369149) Received SIGTERM, scheduling shutdown...
[8014] 28 Aug 03:25:49.655 # User requested shutdown...
[8014] 28 Aug 03:25:49.655 # Redis is now ready to exit, bye bye...
[9062] 28 Aug 03:25:51.444 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 9062
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[9062] 28 Aug 03:25:51.461 # Server started, Redis version 2.8.4
[9062] 28 Aug 03:25:51.461 # 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.
[9062] 28 Aug 03:25:51.461 * The server is now ready to accept connections on port 12311
[9062 | signal handler] (1478068807) Received SIGTERM, scheduling shutdown...
[9062] 02 Nov 02:40:07.653 # User requested shutdown...
[9062] 02 Nov 02:40:07.653 # Redis is now ready to exit, bye bye...
[2158] 02 Nov 02:49:54.127 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
                _._                                                  
           _.-``__ ''-._                                             
      _.-``    `.  `_.  ''-._           Redis 2.8.4 (00000000/0) 64 bit
  .-`` .-```.  ```\/    _.,_ ''-._                                   
 (    '      ,       .-`  | `,    )     Running in stand alone mode
 |`-._`-...-` __...-.``-._|'` _.-'|     Port: 12311
 |    `-._   `._    /     _.-'    |     PID: 2158
  `-._    `-._  `-./  _.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |           http://redis.io        
  `-._    `-._`-.__.-'_.-'    _.-'                                   
 |`-._`-._    `-.__.-'    _.-'_.-'|                                  
 |    `-._`-._        _.-'_.-'    |                                  
  `-._    `-._`-.__.-'_.-'    _.-'                                   
      `-._    `-.__.-'    _.-'                                       
          `-._        _.-'                                           
              `-.__.-'                                               

[2158] 02 Nov 02:49:54.142 # Server started, Redis version 2.8.4
[2158] 02 Nov 02:49:54.157 # 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.
[2158] 02 Nov 02:49:54.157 * The server is now ready to accept connections on port 12311
[18492] 15 Jun 06:22:46.406 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18492] 15 Jun 06:22:46.412 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18518] 15 Jun 06:22:47.466 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18518] 15 Jun 06:22:47.466 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18556] 15 Jun 06:22:49.924 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18556] 15 Jun 06:22:49.925 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18560] 15 Jun 06:22:53.131 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18560] 15 Jun 06:22:53.131 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18729] 15 Jun 06:23:48.229 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18729] 15 Jun 06:23:48.229 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18737] 15 Jun 06:23:49.558 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18737] 15 Jun 06:23:49.559 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18743] 15 Jun 06:23:52.580 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18743] 15 Jun 06:23:52.581 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18754] 15 Jun 06:23:56.201 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18754] 15 Jun 06:23:56.202 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18912] 15 Jun 06:24:53.755 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18912] 15 Jun 06:24:53.768 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18922] 15 Jun 06:24:55.134 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18922] 15 Jun 06:24:55.135 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18926] 15 Jun 06:24:58.139 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18926] 15 Jun 06:24:58.140 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[18959] 15 Jun 06:25:02.065 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[18959] 15 Jun 06:25:02.067 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19132] 15 Jun 06:26:02.978 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19132] 15 Jun 06:26:02.978 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19148] 15 Jun 06:26:04.780 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19148] 15 Jun 06:26:04.781 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19152] 15 Jun 06:26:06.815 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19152] 15 Jun 06:26:06.816 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19165] 15 Jun 06:26:10.587 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19165] 15 Jun 06:26:10.588 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19167] 15 Jun 06:26:12.596 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19167] 15 Jun 06:26:12.601 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19169] 15 Jun 06:26:14.608 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19169] 15 Jun 06:26:14.609 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19178] 15 Jun 06:26:17.213 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19178] 15 Jun 06:26:17.213 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[19182] 15 Jun 06:26:20.276 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[19182] 15 Jun 06:26:20.279 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[20315] 15 Jun 06:33:59.034 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[20315] 15 Jun 06:33:59.034 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[20333] 15 Jun 06:34:00.443 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[20333] 15 Jun 06:34:00.443 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[20339] 15 Jun 06:34:02.633 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[20339] 15 Jun 06:34:02.634 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[20352] 15 Jun 06:34:05.661 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[20352] 15 Jun 06:34:05.662 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[23263] 15 Jun 07:05:02.572 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[23263] 15 Jun 07:05:02.572 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[23280] 15 Jun 07:05:03.614 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[23280] 15 Jun 07:05:03.614 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[23289] 15 Jun 07:05:06.633 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[23289] 15 Jun 07:05:06.634 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use
[23300] 15 Jun 07:05:09.714 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[23300] 15 Jun 07:05:09.715 # Creating Server TCP listening socket 127.0.0.1:12311: bind: Address already in use

Dear @snv, thanks. I tried reload but it didn’t help. Here is the result:

frappe@work:~$ sudo supervisorctl reload
Restarted supervisord
frappe@work:~$ sudo supervisorctl status
frappe-bench-redis:frappe-bench-redis-cache FATAL      Exited too quickly (process log may have details)
frappe-bench-redis:frappe-bench-redis-queue RUNNING    pid 26745, uptime 0:00:14
frappe-bench-redis:frappe-bench-redis-socketio FATAL      Exited too quickly (process log may have details)
frappe-bench-web:frappe-bench-frappe-web STARTING
frappe-bench-web:frappe-bench-node-socketio RUNNING    pid 26744, uptime 0:00:14
frappe-bench-workers:frappe-bench-frappe-default-worker-0 RUNNING    pid 26739, uptime 0:00:14
frappe-bench-workers:frappe-bench-frappe-long-worker-0 RUNNING    pid 26741, uptime 0:00:14
frappe-bench-workers:frappe-bench-frappe-schedule RUNNING    pid 26740, uptime 0:00:14
frappe-bench-workers:frappe-bench-frappe-short-worker-0 RUNNING    pid 26742, uptime 0:00:14

@ahmed,

Can you try to restart the redis server?

@ahmed_personal,

Please check the /frappe-bench/logs directory for error logs

Hello @makarand_b, restarted redis service but it didn’t help I guess. Still getting the same Sorry! message.

root@work:/home/frappe# sudo service redis-server restart
Stopping redis-server: redis-server.
Starting redis-server: redis-server.
root@work:/home/frappe#

I still need help please.

Can someone help me to recover from the below 2 errors?

frappe-bench-redis:frappe-bench-redis-cache FATAL Exited too quickly (process log may have details)
frappe-bench-redis:frappe-bench-redis-socketio FATAL Exited too quickly (process log may have details)

and these:

05:22:34 redis_queue.1 | [30320] 16 Jun 05:22:34.792 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.

05:22:34 redis_queue.1 | [30320] 16 Jun 05:22:34.792 # Creating Server TCP listening socket 127.0.0.1:6379: bind: Address already in use

05:22:34 redis_cache.1 | [30327] 16 Jun 05:22:34.822 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.

05:22:34 redis_cache.1 | [30327] 16 Jun 05:22:34.822 # Creating Server TCP listening socket 127.0.0.1:11311: bind: Address already in use

fuser -k 11311/tcp
fuser -k 10032/tcp
fuser -k 6379/tcp