-
Notifications
You must be signed in to change notification settings - Fork 0
Playbooks troubleshooting guide
Kjetil Klepper edited this page Apr 15, 2024
·
7 revisions
- This is probably due to new variables having been added to the style file blue.scss. We have made our own modified version of this file that replaces the original to implement the NeLS style. Find out which variables are new and add them to the file in our playbook.
Problem: The Galaxy upgrade playbook fails in the "Build client" or "rebuild client" complaining that it Could not find yarn.
- Yarn is installed during the client build step, but only if the client actually needs to rebuilt. If you are re-running a playbook because it failed in a later step and have deleted the virtual environment that contains Yarn before the rerun, then the "install yarn" task may be skipped if the value of the file
/srv/galaxy/server/static/client_build_hash.txt(created when the client was built) matches the current Galaxy commit ID. To force installation, simply delete that file.
- If you are running the playbook on a small test server, it could be that you have run out of disk space. If that is the case, you can free up a lot of disk by deleting the yarn-cache in
/usr/local/share/.cache/yarn.