-
-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Hugo stuck on "Start building sites …" #8166
Comments
|
Interestingly enough, after a few minutes I couldn't reproduce it in my lab, but it was still failing in Gitlab. So I downgraded my image to 0.70.0 and it has been working without issues since then.
That's the currently failing site : |
I've found this has started happening to me too. Normally I invoke hugo from a webserver, but in this case I manually tested it and have found this happens occasionally when I run the command normally. It too gets caught on
I find I am able to reproduce this with 100% consistency on my production server after deleting the I am unable to reproduce this on my dev machine. Update: In my manual testing, if I Update: Now that I am manually creating |
Using the site.zip from @ybizeul, I'm able to reproduce the issue. My tests show that removing all images and CSS from the root of the content folder resolves the issue. Running with the Go race detector doesn't trigger a race for me. Here's what I'm seeing:
@DarrienG, thanks for the additional info. The link to your site source doesn't work for me: 404. Can you confirm that your site is similar to what I describe above? |
Ah sorry, I forgot I left it private. I'll check after work, but my site is here if you'd like to test in the meantime: I'm guessing it will be the same for me though. |
I'm back. I cannot confirm this is the same. There are no If this is the case, I believe this bug is also on 0.74 and possibly the releases in between as well, which is why I originally upgraded, thinking the upgrade would fix it. |
Confirming this bug goes back at least as far as 0.74.0
My site uses a theme that is not compatible with Hugo <0.74.0 so I can't test any further. |
I am facing the same issue in Hugo 0.82.0 |
@SMUsamaShah It looks like you can work around this by:
Then update the image link in content/about_me.md to |
@jmooring |
@SMUsamaShah From what I can see, the image in content dir is causing the problem. Try it yourself:
The build hangs. Now move the image and try again.
The build completes. |
I get it now. It's only visible in the loop the way you did it.
Isn't it a bug? |
Yes, that is why this issue has a "Bug" label. |
I hit this issue with a txt file and some json files in the content folder. Moving them out enable the build to happen again. This was for a Azure static web site as I was adding routes. This is related to Azure/static-web-apps#412 linked above. |
Hitting this issue as well. |
This bug still exists. On Windows machines, the hidden PS: Run in the website's root directory |
When Desktop.ini is in the "<root>/data/" folder
It would be ideal if Hugo server would simply ignore Desktop.ini files. Desktop.ini normally has the "System" and "Hidden" file attributes. Could either or both of those on a given file indicate the file should be ignored by Hugo? |
This is an unrelated issue. See: |
Hitting this issue as well. |
@bep If you do this, no problem: while true; do rm -rf public && mkdir public && GOMAXPROCS=1 hugo --debug; done |
@jmooring I have found the stupid culprits (2) ... Will create a PR soon. |
As in, not in parallel. Closes gohugoio#8166
This is related to gohugoio#8166 – if the /public folder did not exist, you had no /static files and had static files in /content root, then you would get a "no such file or directory" error.
This is related to gohugoio#8166 – if the /public folder did not exist, you had no /static files and had static files in /content root, then you would get a "no such file or directory" error.
* Before this commit, when you had static files in the root of /content and no /public folder, that folder would not be created unless the /static syncer had already run. * So, with a common pattern doing `rm -rf public && hugo` would the fail now and then because /static and /content are processed in parallel (unless you have cleanDestinationDir=true) * This was even worse before commit 0b918e1 – a frozen build. Closes gohugoio#8166
Note that a workaround for the above would be to always make sure that |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes
Context
Hugo running as a container in Gitlab pages, container base is
klakegg/hugo:debian
but it doesn't seem to matter.Description
Every once in a while (actually, every single time when run in Gitlab) hugo will be stuck on
Start building sites …
message.I was able to run in
--debug
and got the following :Then I wanted to reproduce the issue home and it was a little bit trickier, it happens less often, but running site generation in a
while
loop does the trick. So here is what I was able to catch withstrace
, it's stuck with repeatingFUTEX_WAIT_PRIVATE
I'm running
hugo
with the following flags to test :Also, the site is bound to the container from a local directory
I'm not sure what other parts of strace would be relevant.
The text was updated successfully, but these errors were encountered: