-
Notifications
You must be signed in to change notification settings - Fork 107
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
Running compose status
fails on Get "http://localhost/api/v1/compose/queue": EOF
#3779
Comments
composer-cli compose status
fails on Get "http://localhost/api/v1/compose/queue": EOFcompose status
fails on Get "http://localhost/api/v1/compose/queue": EOF
I'm not sure how the system got into this state, but it looks like a job info json file in If you do not mind losing your saved blueprints, sources, previous composes, etc. you should be able to work around this by:
This deletes all the job files and the state file which holds all the details of the system. After rebooting it you will have to push any blueprints and re-add any sources you need. This is of course only a temporary fix and I'll look into making things fail more gracefully. |
Yes. I can confirm that this workaround helped:
Could the JSON file become corrupted during OS upgrades? |
I suppose if it was rebooted right in the middle of writing it it is possible, but I'd consider that very unlikely. |
Found myself in a similar situation this morning after removing the files in the jobs directory .. My solution was: find /var/lib/osbuild-composer/ -type f -delete
rm -rf /var/cache/osbuild-composer/rpmmd/*
systemctl | grep '^ osbuild.*' | cut -d" " -f 3 | xargs systemctl restart --no-block Rather than bring down the system, just another approach if you need to recover again. |
The next time someone hits this could you tar up the |
Describe the bug
With a fresh
osbuild
install, I cannot check the status of the current queue. Adding a new build to the queue works without any issues.Environment
rpm -qi osbuild-composer)
:To Reproduce
Run
composer-cli compose status
, e.g.:Expected behaviour
The status of the queue being printed out.
Additional context
I tried to follow up the instructions at https://access.redhat.com/solutions/7016594. I rebooted my system a couple of times as well. Nothing helped to resolve the issue. I am sure I was able to run the attached reproducer 6+ months ago.
The text was updated successfully, but these errors were encountered: