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::Errors.capture_exception(:vault, e) #2412

Open
gau4828 opened this issue Sep 25, 2024 · 0 comments
Open

Canvas::Errors.capture_exception(:vault, e) #2412

gau4828 opened this issue Sep 25, 2024 · 0 comments

Comments

@gau4828
Copy link

gau4828 commented Sep 25, 2024

Summary:

I'm encountering an issue running the Canvas LMS production setup. The quick start works fine on both WSL and Docker, and I was able to run the production setup without issues until recently. Now, I'm facing an error related to

root@a8a048a20ab1:/var/canvas# sudo tail -f /var/log/apache2/error.log
App 7710 output:     /usr/share/passenger/helper-scripts/rack-loader.rb:27:in `<main>'
[ E 2024-09-25 15:36:37.2102 7463/T1t age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for application /var/canvas: The application encountered the following error: uninitialized constant Canvas::Errors

      Canvas::Errors.capture_exception(:vault, e)
            ^^^^^^^^
Did you mean?  Errno (NameError)
  Error ID: a1c7919c
  Error details saved to: /tmp/passenger-error-PNadEv.html

[ E 2024-09-25 15:36:37.2110 7463/Tb age/Cor/Con/CheckoutSession.cpp:282 ]: [Client 2-1] Cannot checkout session because a spawning error occurred. The identifier of the error is a1c7919c. Please see earlier logs for details about the error.

(I'll provide more details on the exact error message if needed).

Steps to reproduce:

  1. Set up Canvas LMS in production mode following the official documentation.
  2. Use Docker to run the production environment.
  3. Encounter the error when attempting to start the production environment.

Expected behavior:

The Canvas LMS production environment should start successfully, as it did before.

Additional notes:

Quick start works fine, no issues there.
This problem appeared recently, but no changes were made to the setup process from my side.
I'd appreciate guidance or any suggestions on how to debug and resolve this error in the production setup.

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