Tailing lines of node-socketio.log
method: 'POST',
path: '/api/method/frappe.async.get_user_info' },
accepted: false,
noContent: false,
badRequest: true,
unauthorized: false,
notAcceptable: false,
forbidden: false,
notFound: false,
type: 'text/html',
setEncoding: [Function],
redirects: [] },
status: 400 }
Tailing lines of node-socketio.error.log
Error: Redis connection to 127.0.0.1:12311 failed - connect ECONNREFUSED
at RedisClient.on_error (/home/erpnext/frappe-bench/node_modules/redis/index.js:199:24)
at Socket.<anonymous> (/home/erpnext/frappe-bench/node_modules/redis/index.js:109:14)
at Socket.emit (events.js:107:17)
at net.js:459:14
at process._tickCallback (node.js:355:11)
events.js:85
throw er; // Unhandled 'error' event
^
Error: Redis connection to 127.0.0.1:12311 failed - connect ECONNREFUSED
at RedisClient.on_error (/home/erpnext/frappe-bench/node_modules/redis/index.js:199:24)
at Socket.<anonymous> (/home/erpnext/frappe-bench/node_modules/redis/index.js:109:14)
at Socket.emit (events.js:107:17)
at net.js:459:14
at process._tickCallback (node.js:355:11)
Fri, 18 Sep 2015 22:56:04 GMT express deprecated res.sendfile: Use res.sendFile instead at ../apps/frappe/socketio.js:21:7
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Tue, 22 Sep 2015 07:46:04 GMT express deprecated res.sendfile: Use res.sendFile instead at ../apps/frappe/socketio.js:21:7
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Error: ENOENT, stat '/home/erpnext/frappe-bench/sites/index.html'
at Error (native)
Edit: sudo supervisorctl status all
showed everything was running fine, I rebooted the server and I am not getting the error anymore! Solved for now I guess. The message poped up after bench update (master). Rebooted and the message vanished.