I’ve setup a new bench, alongside an existing bench that uses the develop branch, with the version-14 stable branch.
I cannot start the new version-14 bench.
The develop branch has not been started.
I get the following error
Error: connect ECONNREFUSED 127.0.0.1:12001
I also notice that I don’t have either redis_socketio.conf or redis_socketio.acl files in the /bench/site/config folder, only the redis_cache.conf and redis_queue.conf (plus .acl files).
Is this missing file the issue, how do I create it if it is?
Have tried to replicate the missing files, did not work.
I have dropped this bench and created a new bench.
Trying to install Frappe 14.46 and cannot start the bench, get the following:
02:21:33 system | redis_queue.1 started (pid=19620)
02:21:33 redis_queue.1 | 19624:C 29 Aug 2023 02:21:33.496 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
02:21:33 redis_queue.1 | 19624:C 29 Aug 2023 02:21:33.496 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=19624, just started
02:21:33 redis_queue.1 | 19624:C 29 Aug 2023 02:21:33.496 # Configuration loaded
02:21:33 redis_queue.1 | 19624:M 29 Aug 2023 02:21:33.497 * Increased maximum number of open files to 10032 (it was originally set to 1024).
02:21:33 system | web.1 started (pid=19622)
02:21:33 redis_queue.1 | 19624:M 29 Aug 2023 02:21:33.498 * Running mode=standalone, port=11001.
02:21:33 redis_queue.1 | 19624:M 29 Aug 2023 02:21:33.498 # Server initialized
02:21:33 redis_queue.1 | 19624:M 29 Aug 2023 02:21:33.498 # 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.
02:21:33 redis_queue.1 | 19624:M 29 Aug 2023 02:21:33.499 * Ready to accept connections
02:21:33 system | schedule.1 started (pid=19644)
02:21:33 system | redis_cache.1 started (pid=19615)
02:21:33 redis_cache.1 | 19617:C 29 Aug 2023 02:21:33.493 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
02:21:33 redis_cache.1 | 19617:C 29 Aug 2023 02:21:33.493 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=19617, just started
02:21:33 redis_cache.1 | 19617:C 29 Aug 2023 02:21:33.493 # Configuration loaded
02:21:33 redis_cache.1 | 19617:M 29 Aug 2023 02:21:33.494 * Increased maximum number of open files to 10032 (it was originally set to 1024).
02:21:33 redis_cache.1 | 19617:M 29 Aug 2023 02:21:33.495 * Running mode=standalone, port=13001.
02:21:33 redis_cache.1 | 19617:M 29 Aug 2023 02:21:33.495 # Server initialized
02:21:33 redis_cache.1 | 19617:M 29 Aug 2023 02:21:33.495 # 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.
02:21:33 redis_cache.1 | 19617:M 29 Aug 2023 02:21:33.495 * Ready to accept connections
02:21:33 system | worker.1 started (pid=19641)
02:21:33 system | watch.1 started (pid=19665)
02:21:34 socketio.1 | node:events:492
02:21:34 socketio.1 | throw er; // Unhandled 'error' event
02:21:34 socketio.1 | ^
02:21:34 socketio.1 |
02:21:34 socketio.1 | Error: connect ECONNREFUSED 127.0.0.1:12001
02:21:34 socketio.1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1495:16)
02:21:34 socketio.1 | Emitted 'error' event on RedisClient instance at:
02:21:34 socketio.1 | at RedisClient.on_error (/home/bench/alphasite/apps/frappe/node_modules/redis/index.js:342:14)
02:21:34 socketio.1 | at Socket.<anonymous> (/home/bench/alphasite/apps/frappe/node_modules/redis/index.js:223:14)
02:21:34 socketio.1 | at Socket.emit (node:events:514:28)
02:21:34 socketio.1 | at emitErrorNT (node:internal/streams/destroy:151:8)
02:21:34 socketio.1 | at emitErrorCloseNT (node:internal/streams/destroy:116:3)
02:21:34 socketio.1 | at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
02:21:34 socketio.1 | errno: -111,
02:21:34 socketio.1 | code: 'ECONNREFUSED',
02:21:34 socketio.1 | syscall: 'connect',
02:21:34 socketio.1 | address: '127.0.0.1',
02:21:34 socketio.1 | port: 12001
02:21:34 socketio.1 | }
02:21:34 socketio.1 |
02:21:34 socketio.1 | Node.js v18.17.1
02:21:34 system | socketio.1 stopped (rc=1)
02:21:34 system | sending SIGTERM to redis_cache.1 (pid 19615)
02:21:34 system | sending SIGTERM to redis_queue.1 (pid 19620)
02:21:34 system | sending SIGTERM to web.1 (pid 19622)
02:21:34 system | sending SIGTERM to watch.1 (pid 19665)
02:21:34 system | sending SIGTERM to schedule.1 (pid 19644)
02:21:34 system | sending SIGTERM to worker.1 (pid 19641)
02:21:34 system | schedule.1 stopped (rc=-15)
02:21:34 redis_queue.1 | 19624:signal-handler (1693272094) Received SIGTERM scheduling shutdown...
02:21:34 redis_cache.1 | 19617:signal-handler (1693272094) Received SIGTERM scheduling shutdown...
02:21:34 system | worker.1 stopped (rc=-15)
02:21:34 system | watch.1 stopped (rc=-15)
02:21:34 system | web.1 stopped (rc=-15)
02:21:34 redis_queue.1 | 19624:M 29 Aug 2023 02:21:34.501 # User requested shutdown...
02:21:34 redis_queue.1 | 19624:M 29 Aug 2023 02:21:34.501 * Removing the pid file.
02:21:34 redis_queue.1 | 19624:M 29 Aug 2023 02:21:34.501 # Redis is now ready to exit, bye bye...
02:21:34 redis_cache.1 | 19617:M 29 Aug 2023 02:21:34.501 # User requested shutdown...
02:21:34 redis_cache.1 | 19617:M 29 Aug 2023 02:21:34.501 * Removing the pid file.
02:21:34 redis_cache.1 | 19617:M 29 Aug 2023 02:21:34.501 # Redis is now ready to exit, bye bye...
02:21:34 system | redis_queue.1 stopped (rc=-15)
02:21:34 system | redis_cache.1 stopped (rc=-15)
If I switch the new bench to the develop branch it will start without issue. If I change the working develop branch back to version-14 branch, the bench will no longer start.
Does anyone know why?
Is it impossible to now run two separate benches for stable and develop on the same machine?
