Supported Operating Systems

KevinBrown · July 19, 2023, 8:36am

Hi Everyone,

I’ve previously had Frappe installed on many machines, and even our own website is using it but, I remember a while back on the official install guide it used to give instructions for more linux distributions than just Ubuntu & Debian.

What is officially the recommended OS and version to use to make sure it installs correctly because I’m having all manner of issues with Ubuntu 22.04 and 23.04 and Debian 12.

I’m really keen to start building another app on Frappe but cant get it to install without errors

mangroliya · July 19, 2023, 9:03am

Hi,

Frappe Version-14 works perfectly with Ubuntu 22.04 and Python 3.10.

Thanks,

Divyesh Mangroliya

pmjd · July 19, 2023, 11:52am

What issues are you facing? I’ve just done a reinstall on Ubuntu 22.04 and it all went well.

I followed this guide but there was a couple of steps which I needed to workaround but can’t remember of the top of my head…

KevinBrown · July 19, 2023, 1:44pm

I’ll try using that guide, that you.

I’m facing all sorts of issues, and not all at the same time, i’ve had perfectly working installations and as soon as I attempt to make a custom app it fails. other times the installation of Frappe fails because its asking for a different version of yarn, and then sometimes its not recognising some bench commands, its all very odd and because i’m trying to build a development laptop i just reinstall the OS.

pmjd · July 19, 2023, 2:11pm

Actually I think it was the nodejs step I had an issue with. It was on Ubuntu, so I ended up installing it from the Ubuntu app store instead of via terminal

KevinBrown · July 19, 2023, 3:38pm

OK, just did a full reinstall of Ubuntu 22.04 on my laptop.

I’m following the guide here:

I’ve install Frappe Framework and can confirm that bench version is 5.16.4

But when i run bench init it gives the following error:

kevin@EliteBook:~$ bench init bench
Setting Up Environment
$ python3 -m venv env
$ /home/kevin/bench/env/bin/python -m pip install --quiet --upgrade pip
$ /home/kevin/bench/env/bin/python -m pip install --quiet wheel
Getting frappe
$ git clone GitHub - frappe/frappe: Low code web framework for real world applications, in Python and Javascript --depth 1 --origin upstream
Cloning into ‘frappe’…
remote: Enumerating objects: 3213, done.
remote: Counting objects: 100% (3213/3213), done.
remote: Compressing objects: 100% (2851/2851), done.
remote: Total 3213 (delta 409), reused 2016 (delta 261), pack-reused 0
Receiving objects: 100% (3213/3213), 17.14 MiB | 5.37 MiB/s, done.
Resolving deltas: 100% (409/409), done.
Installing frappe
$ /home/kevin/bench/env/bin/python -m pip install --quiet --upgrade -e /home/kevin/bench/apps/frappe
$ yarn install
yarn install v1.22.19
[1/5] Validating package.json…
error frappe-framework@: The engine “node” is incompatible with this module. Expected version “>=18”. Got “14.15.0”
error Found incompatible module.
info Visit yarn install | Yarn for documentation about this command.
subprocess.CalledProcessError: Command ‘yarn install’ returned non-zero exit status 1.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File “/usr/local/lib/python3.10/dist-packages/bench/commands/make.py”, line 68, in init
init(
File “/usr/local/lib/python3.10/dist-packages/bench/utils/render.py”, line 105, in wrapper_fn
return fn(*args, **kwargs)
File “/usr/local/lib/python3.10/dist-packages/bench/utils/system.py”, line 79, in init
get_app(
File “/usr/local/lib/python3.10/dist-packages/bench/app.py”, line 444, in get_app
app.install(verbose=verbose, skip_assets=skip_assets, restart_bench=restart_bench)
File “/usr/local/lib/python3.10/dist-packages/bench/utils/render.py”, line 126, in wrapper_fn
return fn(*args, **kwargs)
File “/usr/local/lib/python3.10/dist-packages/bench/app.py”, line 242, in install
install_app(
File “/usr/local/lib/python3.10/dist-packages/bench/app.py”, line 581, in install_app
bench.run(“yarn install”, cwd=app_path)
File “/usr/local/lib/python3.10/dist-packages/bench/bench.py”, line 48, in run
return exec_cmd(cmd, cwd=cwd or self.cwd, _raise=_raise)
File “/usr/local/lib/python3.10/dist-packages/bench/utils/init.py”, line 158, in exec_cmd
raise CommandFailedError(cmd) from subprocess.CalledProcessError(return_code, cmd)
bench.exceptions.CommandFailedError: yarn install

ERROR: There was a problem while creating bench
Do you want to rollback these changes? [y/N]: y

KevinBrown · July 19, 2023, 3:44pm

I’ve got passed that issue using:

nvm install 18
nvm use 18

KevinBrown · July 19, 2023, 3:50pm

OK, I’ve got it installed and a new bench initiated, but when i run bench start, it just stops immediately

kevin@EliteBook:~/bench$ bench start
16:48:09 system | redis_cache.1 started (pid=13796)
16:48:09 system | redis_queue.1 started (pid=13802)
16:48:09 system | redis_socketio.1 started (pid=13801)
16:48:09 system | socketio.1 started (pid=13811)
16:48:09 system | worker.1 started (pid=13820)
16:48:09 system | web.1 started (pid=13808)
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13799, just started
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # Configuration loaded
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.277 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=13000.
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 # Server initialized
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 # 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.
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13805, just started
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # Configuration loaded
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.278 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13804, just started
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # Configuration loaded
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=11000.
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 # Server initialized
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 # 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.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=12000.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 # Server initialized
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 # 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.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 system | schedule.1 started (pid=13816)
16:48:09 system | watch.1 started (pid=13815)
16:48:09 socketio.1 | Realtime service listening on: 9000
16:48:09 watch.1 | Please update your node version to 18
16:48:09 watch.1 |
16:48:10 watch.1 | yarn run v1.22.19
16:48:10 watch.1 | error frappe-framework@: The engine “node” is incompatible with this module. Expected version “>=18”. Got “14.15.0”
16:48:10 watch.1 | error Commands cannot run with an incompatible environment.
16:48:10 watch.1 | info Visit yarn run | Yarn for documentation about this command.
16:48:10 system | watch.1 stopped (rc=0)
16:48:10 system | sending SIGTERM to redis_cache.1 (pid 13796)
16:48:10 system | sending SIGTERM to redis_socketio.1 (pid 13801)
16:48:10 system | sending SIGTERM to redis_queue.1 (pid 13802)
16:48:10 system | sending SIGTERM to web.1 (pid 13808)
16:48:10 system | sending SIGTERM to socketio.1 (pid 13811)
16:48:10 system | sending SIGTERM to schedule.1 (pid 13816)
16:48:10 system | sending SIGTERM to worker.1 (pid 13820)
16:48:10 redis_socketio.1 | 13805:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 redis_cache.1 | 13799:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 redis_queue.1 | 13804:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 system | worker.1 stopped (rc=-15)
16:48:10 system | schedule.1 stopped (rc=-15)
16:48:10 system | web.1 stopped (rc=-15)
16:48:10 system | socketio.1 stopped (rc=-15)
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 # Redis is now ready to exit, bye bye…
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 # Redis is now ready to exit, bye bye…
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.182 # Redis is now ready to exit, bye bye…
16:48:10 system | redis_socketio.1 stopped (rc=-15)
16:48:10 system | redis_cache.1 stopped (rc=-15)
16:48:10 system | redis_queue.1 stopped (rc=-15)
kevin@EliteBook:~/bench$ bench start
16:48:09 system | redis_cache.1 started (pid=13796)
16:48:09 system | redis_queue.1 started (pid=13802)
16:48:09 system | redis_socketio.1 started (pid=13801)
16:48:09 system | socketio.1 started (pid=13811)
16:48:09 system | worker.1 started (pid=13820)
16:48:09 system | web.1 started (pid=13808)
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13799, just started
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # Configuration loaded
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.277 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=13000.
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 # Server initialized
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 # 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.
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13805, just started
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # Configuration loaded
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.278 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13804, just started
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # Configuration loaded
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=11000.
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 # Server initialized
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 # 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.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=12000.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 # Server initialized
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 # 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.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 system | schedule.1 started (pid=13816)
16:48:09 system | watch.1 started (pid=13815)
16:48:09 socketio.1 | Realtime service listening on: 9000
16:48:09 watch.1 | Please update your node version to 18
16:48:09 watch.1 |
16:48:10 watch.1 | yarn run v1.22.19
16:48:10 watch.1 | error frappe-framework@: The engine “node” is incompatible with this module. Expected version “>=18”. Got “14.15.0”
16:48:10 watch.1 | error Commands cannot run with an incompatible environment.
16:48:10 watch.1 | info Visit yarn run | Yarn for documentation about this command.
16:48:10 system | watch.1 stopped (rc=0)
16:48:10 system | sending SIGTERM to redis_cache.1 (pid 13796)
16:48:10 system | sending SIGTERM to redis_socketio.1 (pid 13801)
16:48:10 system | sending SIGTERM to redis_queue.1 (pid 13802)
16:48:10 system | sending SIGTERM to web.1 (pid 13808)
16:48:10 system | sending SIGTERM to socketio.1 (pid 13811)
16:48:10 system | sending SIGTERM to schedule.1 (pid 13816)
16:48:10 system | sending SIGTERM to worker.1 (pid 13820)
16:48:10 redis_socketio.1 | 13805:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 redis_cache.1 | 13799:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 redis_queue.1 | 13804:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 system | worker.1 stopped (rc=-15)
16:48:10 system | schedule.1 stopped (rc=-15)
16:48:10 system | web.1 stopped (rc=-15)
16:48:10 system | socketio.1 stopped (rc=-15)
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 # Redis is now ready to exit, bye bye…
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 # Redis is now ready to exit, bye bye…
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.182 # Redis is now ready to exit, bye bye…
16:48:10 system | redis_socketio.1 stopped (rc=-15)
16:48:10 system | redis_cache.1 stopped (rc=-15)
16:48:10 system | redis_queue.1 stopped (rc=-15)
kevin@EliteBook:~/bench$ bench start
16:48:09 system | redis_cache.1 started (pid=13796)
16:48:09 system | redis_queue.1 started (pid=13802)
16:48:09 system | redis_socketio.1 started (pid=13801)
16:48:09 system | socketio.1 started (pid=13811)
16:48:09 system | worker.1 started (pid=13820)
16:48:09 system | web.1 started (pid=13808)
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13799, just started
16:48:09 redis_cache.1 | 13799:C 19 Jul 2023 16:48:09.276 # Configuration loaded
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.277 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=13000.
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 # Server initialized
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.278 # 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.
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13805, just started
16:48:09 redis_socketio.1 | 13805:C 19 Jul 2023 16:48:09.277 # Configuration loaded
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.278 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=13804, just started
16:48:09 redis_queue.1 | 13804:C 19 Jul 2023 16:48:09.277 # Configuration loaded
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 * Increased maximum number of open files to 10032 (it was originally set to 1024).
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=11000.
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 # Server initialized
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.278 # 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.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.278 * Running mode=standalone, port=12000.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 # Server initialized
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 # 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.
16:48:09 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 redis_queue.1 | 13804:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 redis_cache.1 | 13799:M 19 Jul 2023 16:48:09.279 * Ready to accept connections
16:48:09 system | schedule.1 started (pid=13816)
16:48:09 system | watch.1 started (pid=13815)
16:48:09 socketio.1 | Realtime service listening on: 9000
16:48:09 watch.1 | Please update your node version to 18
16:48:09 watch.1 |
16:48:10 watch.1 | yarn run v1.22.19
16:48:10 watch.1 | error frappe-framework@: The engine “node” is incompatible with this module. Expected version “>=18”. Got “14.15.0”
16:48:10 watch.1 | error Commands cannot run with an incompatible environment.
16:48:10 watch.1 | info Visit yarn run | Yarn for documentation about this command.
16:48:10 system | watch.1 stopped (rc=0)
16:48:10 system | sending SIGTERM to redis_cache.1 (pid 13796)
16:48:10 system | sending SIGTERM to redis_socketio.1 (pid 13801)
16:48:10 system | sending SIGTERM to redis_queue.1 (pid 13802)
16:48:10 system | sending SIGTERM to web.1 (pid 13808)
16:48:10 system | sending SIGTERM to socketio.1 (pid 13811)
16:48:10 system | sending SIGTERM to schedule.1 (pid 13816)
16:48:10 system | sending SIGTERM to worker.1 (pid 13820)
16:48:10 redis_socketio.1 | 13805:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 redis_cache.1 | 13799:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 redis_queue.1 | 13804:signal-handler (1689781690) Received SIGTERM scheduling shutdown…
16:48:10 system | worker.1 stopped (rc=-15)
16:48:10 system | schedule.1 stopped (rc=-15)
16:48:10 system | web.1 stopped (rc=-15)
16:48:10 system | socketio.1 stopped (rc=-15)
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_socketio.1 | 13805:M 19 Jul 2023 16:48:10.181 # Redis is now ready to exit, bye bye…
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_cache.1 | 13799:M 19 Jul 2023 16:48:10.181 # Redis is now ready to exit, bye bye…
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.181 # User requested shutdown…
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.181 * Removing the pid file.
16:48:10 redis_queue.1 | 13804:M 19 Jul 2023 16:48:10.182 # Redis is now ready to exit, bye bye…
16:48:10 system | redis_socketio.1 stopped (rc=-15)
16:48:10 system | redis_cache.1 stopped (rc=-15)
16:48:10 system | redis_queue.1 stopped (rc=-15)
kevin@EliteBook:~/bench$

KevinBrown · July 19, 2023, 3:59pm

Anyone any idea on how to get this running?

pmjd · July 19, 2023, 4:20pm

Looks like the node version is still out of date, maybe the version you installed has been overwritten?

KevinBrown · July 19, 2023, 4:21pm

I’ve installed version 18 and it is in use but frappe doesnt seem to see it, i’ve used a bit of a hack to get it running for now

yarn config set ignore-engines true

mangroliya · July 19, 2023, 7:33pm

Hi,

Install Node with following commands and it should work flawlessly:

Install CURL

sudo apt install curl

Install Node

curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash

source ~/.profile

nvm install 16.15.0

Install NPM

sudo apt-get install npm

Install Yarn

sudo npm install -g yarn

Thanks,

Divyesh Mangroliya

trentmu · July 23, 2023, 9:38am

You have a redis error as well, so most likely that your supervisor subsystem is not set up correctly

VinodKumarkolli · September 5, 2023, 1:41pm

when you are initialising bench, user version argument
By default, bench init will get ‘develop’ branch of frappe-bench which has dependency on “node 18”

$ bench init --version version-14 custom_bench_name

this has no dependency on node 18