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

ENOENT: No such file or directory #2866

Closed
sergius02 opened this issue Dec 12, 2023 · 4 comments · Fixed by #2884
Closed

ENOENT: No such file or directory #2866

sergius02 opened this issue Dec 12, 2023 · 4 comments · Fixed by #2884

Comments

@sergius02
Copy link

sergius02 commented Dec 12, 2023

Hi!

Everytime i try to restart the container the web shows a 500 error page. When i go to see the production.log this error appears when an user open the web:

lib/gitlab/middleware/release_env.rb:13:in 'call'

ActionView::Template::Error (Could not load compiled manifest from /home/git/gitlab/public/assets/webpack/manifest.json.

Have you run 'rake gitlab:assets:compile'?

(original error Errno::ENOENT: No such file or directory @ rb_sysopen - /home/git/gitlab/public/assets/webpack/manifest.json)):
    52:
    53:   = webpack_bundle_tag 'super_sidebar' if show_super_sidebar?
    54:
    55:   = webpack_controller_bundle_tags
    56:
    57:   - unless omit_og
    58:     -# Open Graph - http://ogp.me/

lib/gitlab/webpack/manifest.rb:82:in 'rescue in load_manifest'

As the error says, i executed rake gitlab:assets:compile, but when it finish, nothing happend and the webpage still no load

@iDmple
Copy link

iDmple commented Jan 17, 2024

I have the same issue after updating to 16.x from 15.x. Anyone has an idea?

@kkimurak
Copy link
Contributor

If you are using relative url, #2884 may fix the issue I think.

@sergius02
Copy link
Author

If you are using relative url, #2884 may fix the issue I think.

Thats probably my problem. I'm using relative url, and when i delete manually the tmp folder, gitlab can launch succesfully.

@kkimurak
Copy link
Contributor

Glad to hear that, and sorry for the delay in providing a solution. I was aware of this problem in May, but I was working on a series of tasks to support postgresql-13 (and later versions) at the same time and forgot I was applying patch to my local instance until I saw this issue..

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

Successfully merging a pull request may close this issue.

3 participants