[15306] 11 May 23:19:06.864 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
[15306] 11 May 23:19:06.864 # Creating Server TCP listening socket 127.0.0.1:6379: bind: Address already in use
frappe-bench-redis:frappe-bench-redis-cache RUNNING pid 1358, uptime 0:13:50 frappe-bench-redis:frappe-bench-redis-queue RUNNING pid 1355, uptime 0:13:50 frappe-bench-redis:frappe-bench-redis-socketio RUNNING pid 1359, uptime 0:13:50 frappe-bench-web:frappe-bench-frappe-web RUNNING pid 1353, uptime 0:13:50 frappe-bench-web:frappe-bench-node-socketio RUNNING pid 1354, uptime 0:13:50 frappe-bench-workers:frappe-bench-frappe-default-worker-0 FATAL Exited too quickly (process log may have details) frappe-bench-workers:frappe-bench-frappe-long-worker-0 FATAL Exited too quickly (process log may have details) frappe-bench-workers:frappe-bench-frappe-schedule RUNNING pid 1349, uptime 0:13:50 frappe-bench-workers:frappe-bench-frappe-short-worker-0 FATAL Exited too quickly (process log may have details)
Which logs would indicate the problem with the workers? I changed the port for redis to avoid it conflicting with something else in the redis conf file. Do I need to update then elsewhere?
I have this warning Redis cache server not running. Please contact Administrator / Tech support
and this in bench start
08:46:55 redis_socketio.1 | [5287] 25 Jul 08:46:55.490 # Unable to set the max number of files limit to 10032 (Operation not permitted), setting the max clients configuration to 3984.
Upon inspection of the logs and supervisorctl status, my node node-socketio keeps on starting after every 4 05 5 seconds. Looks like its terminating and supervisord is restarting it. Is anyone fcing the same issue?
Use sudo killall -9 node from the commandline to kill any zombie processes that might be lingering and bound to your port. this sometimes happens with socket.io when it fails to shutdown properly.
Check if web socket connections disabled in the firewall of the server?
In my case It turned out to be SELinux permission issue and solved by running this command: sudo semanage port --add --type httpportt --proto tcp 9000 (Port number should match to as that of socketio)
make sure that your domain points to your server.
make sure that an nginx server block is running for your domain with ssl or w/o ssl enabled as per your setup.
Check by any chance your are using CDN / CloudFlare (proxy mode on for domain), if so disabling it will solve the problem.
Thanks @yashodhan for the response. I have my firewall and selinux disabled, running nginx and not using CDN/CloudFare. It is also not leaving any zombie processes behind when it terminates.
If it helps, I am using CentOS release 7.2.1511 and node v6.3.1
Have you even checked your socket.io is installed or not / nodejs installed/running?
You need to check both node-socketio.error.log and node-socketio.log
As well as You need to check both redis-socketio.error.log & redis-socketio.log under /home/frappe/frappe-bench/logs
I did everything you mentioned and my system has 60GB free memory. While checking the node-socketio.error.log log file, the following exception is causing the node to terminate. I tried to start node from commandline too, and it exits after encountering the exception below. When I comment out the responsible code block, node runs without issue.
TypeError: Cannot read property 'user' of undefined
at /home/frappe/emines/apps/frappe/socketio.js:48:54
at Request.callback (/home/frappe/node_modules/superagent/lib/node/index.js:591:12)
at IncomingMessage.<anonymous> (/home/frappe/node_modules/superagent/lib/node/index.js:766:18)
at emitNone (events.js:91:20)
at IncomingMessage.emit (events.js:185:7)
at endReadableNT (_stream_readable.js:975:12)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)