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

Apache fails to start, cannot find public folder #52

Closed
apolopena opened this issue Mar 6, 2021 · 1 comment
Closed

Apache fails to start, cannot find public folder #52

apolopena opened this issue Mar 6, 2021 · 1 comment
Assignees
Labels
bug Something isn't working passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main

Comments

@apolopena
Copy link
Owner

apolopena commented Mar 6, 2021

Describe the bug

Sometimes this error pops up

DocumentRoot '/workspace/gitpod-laravel8-starter/public' is not a directory, or is not readable
Action 'start' failed.
The Apache error log may have more information

However after the system is ready Apache will start manually via start_apache

Screenshots

image

Steps to reproduce

Happens every time right now in https://github.com/apolopena/gitpod-laravel8-starter
Doesn't seem tot happen at all in https://github.com/apolopena/laravel8-starter-b892185

Update:
Does not happen everytime in https://github.com/apolopena/gitpod-laravel8-starter either

Expected behavior

Apache should start at any time during the init command.

Additional information

This could be related to gitpod-io/workspace-images#354
I will dive deeper on this and provide an update
It is odd that the issue is replicable in one repo but not in another when the code in the two repos is virtually the same.

Update:
This did not have to do with gitpod-io/workspace-images/pull/354. Rather it seems like osmetime the cpu in the cloud just lags and the public folder was not available at the time the server was told to start.

@apolopena apolopena added the bug Something isn't working label Mar 6, 2021
@apolopena apolopena self-assigned this Mar 6, 2021
@apolopena apolopena added the internal-gitpod-bug Bug in the Gitpod platform itself label Mar 6, 2021
apolopena added a commit that referenced this issue Mar 7, 2021
@apolopena
Copy link
Owner Author

The fix was to prompt the user with a spinner and then use gp sync-await gitpod-inited to ensure the server is opened after the public folder is available.

@apolopena apolopena added in-dev-qa passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main and removed internal-gitpod-bug Bug in the Gitpod platform itself in-dev-qa labels Mar 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working passed-dev-qa Optional state. Use this when QAing other peoples fixes in another branch.ready to be merged to main
Projects
None yet
Development

No branches or pull requests

1 participant