Bench update --build challenge

I’m currently running version-12 but we I try to apply latest update, I get and error as bellow

$ bench update --build
Backing up sites…
INFO:bench.utils:bench build
yarn run v1.17.3
$ FRAPPE_ENV=production node rollup/build.js
Production mode
:heavy_check_mark: Built js/moment-bundle.min.js
:heavy_check_mark: Built js/libs.min.js

Building frappe assets…

:heavy_check_mark: Built js/dialog.min.js
:heavy_check_mark: Built js/social.min.js
:heavy_check_mark: Built js/modules.min.js
:heavy_check_mark: Built js/web_form.min.js
:heavy_check_mark: Built js/chat.js
:heavy_check_mark: Built js/list.min.js
:heavy_check_mark: Built css/printview.css
:heavy_check_mark: Built css/frappe-rtl.css
:heavy_check_mark: Built css/module.min.css
:heavy_check_mark: Built css/form.min.css
:heavy_check_mark: Built css/list.min.css
:heavy_check_mark: Built frappe/css/email.css
:heavy_check_mark: Built css/report.min.css
:heavy_check_mark: Built css/frappe-web.css
:heavy_check_mark: Built css/web_form.css
:heavy_check_mark: Built css/desk.min.css
error Command failed with signal “SIGKILL”.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
INFO:bench.utils:sudo supervisorctl restart frappe-bench-workers: frappe-bench-web:
frappe-bench-workers:frappe-bench-frappe-schedule: stopped
frappe-bench-workers:frappe-bench-frappe-default-worker-0: stopped
frappe-bench-workers:frappe-bench-frappe-long-worker-0: stopped
frappe-bench-workers:frappe-bench-frappe-short-worker-0: stopped
frappe-bench-web:frappe-bench-frappe-web: stopped
frappe-bench-web:frappe-bench-node-socketio: stopped
frappe-bench-workers:frappe-bench-frappe-schedule: started
frappe-bench-workers:frappe-bench-frappe-default-worker-0: started
frappe-bench-workers:frappe-bench-frappe-long-worker-0: started
frappe-bench-workers:frappe-bench-frappe-short-worker-0: started
frappe-bench-web:frappe-bench-frappe-web: started
frappe-bench-web:frappe-bench-node-socketio: started

Seems I have issues building desk assets but I’ve checked for clues in logs and cannot find anything to point me in the right direction. Any pointers will be greatly appreciated

P.S Hope to see you at the conference

1 Like

reboot your vm then run command again before running other command

Did you run ERPNext anyway with AWS? How did you resolve this issue?