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

qubes-dom0-update --clean exits unexpectedly #3893

Closed
lunarthegrey opened this Issue May 11, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@lunarthegrey

lunarthegrey commented May 11, 2018

Qubes OS version:

Qubes Release 4.0

Affected component(s):

qubes-dom0-update


Steps to reproduce the behavior:

Run this in a dom0 terminal: sudo qubes-dom0-update --clean

Expected behavior:

Yum cache is removed successfully.

Actual behavior:

Says that files were removed, then looks to be syncing repo-data. After a short (sometimes long) period of time you get an error and the process will be killed like:
/usr/bin/fakeroot: line 181: 9686 Killed FAKEROOTKEY=$FAKEROOTKEY LD_LIBRARY_PATH="$PATHS" LD_PRELOAD="$LIB" "$@"

General notes:

Seems to only happen when running sudo qubes-dom0-update --clean


Related issues:

None that I know of.

@lunarthegrey lunarthegrey changed the title from qubes-dom0-update --clean exits unexpectidly to qubes-dom0-update --clean exits unexpectedly May 11, 2018

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek May 11, 2018

Member

What VM you use for UpdateVM, default sys-firewall? What template it has, default fedora-26?
Do you see anything related in journalctl -e in that VM?

Member

marmarek commented May 11, 2018

What VM you use for UpdateVM, default sys-firewall? What template it has, default fedora-26?
Do you see anything related in journalctl -e in that VM?

@andrewdavidwong andrewdavidwong added the bug label May 12, 2018

@andrewdavidwong andrewdavidwong added this to the Release 4.0 updates milestone May 12, 2018

@lunarthegrey

This comment has been minimized.

Show comment
Hide comment
@lunarthegrey

lunarthegrey May 13, 2018

@marmarek I currently use sys-firewall and it's running off the default fedora-26 template. Thanks for the suggestion about checking journalctl. I actually found that it was OOMing and that's what caused the process to die. Once I gave more memory to sys-firewall the issue doesn't occur.

I kind of forgot how update VMs worked...

@marmarek I currently use sys-firewall and it's running off the default fedora-26 template. Thanks for the suggestion about checking journalctl. I actually found that it was OOMing and that's what caused the process to die. Once I gave more memory to sys-firewall the issue doesn't occur.

I kind of forgot how update VMs worked...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment