Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Canvas Build scripts are broken / missing during Installation #2430

Open
OZORDI opened this issue Nov 28, 2024 · 0 comments
Open

Canvas Build scripts are broken / missing during Installation #2430

OZORDI opened this issue Nov 28, 2024 · 0 comments

Comments

@OZORDI
Copy link

OZORDI commented Nov 28, 2024

Server Specs:

Ubuntu 22.04 LTS
4 vCPUs
6gb RAM but 10gb of swap memory
400gb SSD.
(Its a base tier Contabo VPS)

Heres my terminal logs:

https://pastebin.com/eUwYyse3

Steps to reproduce:

  1. I followed the below often cited tutorial because the offical Production start guide is missing quite a bit: https://elearningevolve.com/blog/install-canvas-lms/
  2. This error occurs at Step 5 specifically when I ran RAILS_ENV=production bundle exec rake canvas:compile_assets;
  3. You can still follow through with the guide till the end but upon visiting https://canvas.example.com youll be met with a blank page on Safari and HTTP response code 500 on Chrome.
  4. When you run the entire bundle of terminal commands in Step 5, all goes well until warnings and slight errors start popping up. The first notable and likely issue is 'https://registry.yarnpkg.com/cosmiconfig/-/cosmiconfig-6.0.0.tgz - unable to unzip file. Tar might be corrupted'.
  5. It happens around Step 5, specifically 'RAILS_ENV=production bundle exec rake canvas:compile_assets;' but it might be an issue thats cascading from previous failed commands.

Summary:

The Canvas installation / compile from source process is broken in some way and has been for a while and is affecting a portion of users. Its consistently failing to retrieve the scripts it needs to build core Canvas modules

Observed behavior:

During the following process

Applying patches...
[email protected] ✔
yarn run v1.19.1
$ yarn workspace-run build:canvas
$ r() { wsrun --fast-exit --exclude-missing --report -c $@; exit $?; } && r build:canvas

Canvas runs into an issue where is states it cant find the scripts needed to install core parts of Canvas like '@instructure/date-js' and '@instructure/grading-utils'. This has been an longstanding issue as the earliest occurence i could find of it is from 2022.

At the end it states 248 packages are missing script 'build:canvas'

Additional notes:

  • I should also note that the directories for the Canvas API are fully up and running. For instance if i go to https://canvas.example.com/doc/api/all_resources.html it returns the actual webpage. It seems to be the API documentation is the only part of Canvas thats functioning properly. Navigating to the main webpage at https://canvas.example.com returns a blank page with no exposed HTTP request or response headers.

  • I should also add that if you were to follow the article i linked to guide you through the installation process at no point are you prompted to create the default canvas user / admin user. Adjacent to this, I recall seeing another person having this issue and stating that production.log kept mentioning '.ID is Null' meaning the default user wasnt created yet.

  • At first i thought Prod branch was broken as of the time i first attempted the Canvas Install so on my second attempt i used git checkout stable/2024-12-18 instead (since it was marked as 'stable') but i still ran into the same issue

  • I will try replicating the installation process on a beefy Vultr Instance (4 vCPUs 16 GB
    384 GB NVMe) to eliminate variables like Contabo having networking issues or me not having enough native memory.

Current work around
I believe if you were to follow the article down to the Tee but use a Canvas Stable build from around the time the article was first published 'August 2023' it should be possible to have a smooth installation process. I am yet to try this myself though

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant