ghostbsd upgrade failed [pid was killed failed to reclaim memory]

janove75

hello !
ghostbsd upgrade failed in gui mode
now the multi-user mode doesn't work
the system is running in single mode
so I tried to relauch the upgrade process
#pkg update -f #pkg upgrade -f
the result is
The process will require x MiB more space.
if I try to launch, the process begin and abort
the reason is "pid was killed failed to reclaim memory"

Do you have any idea to solve this situation ?

grahamperrin

janove75 … failed in gui mode …

Similarly, failures may occur in vt(4).

In this case I was at ttyv1:

[576/718] Extracting openjdk17-17.0.14+7.1: 100%
Child process pid=1395 terminated abnormally: Killed
root@mowa219-gjp4-ghostbsd-14-vm:~ # pkg upgrade -y
…

@janove75 if you have a GitHub account, please subscribe to:

pkg upgrade finding nothing after an incomplete upgrade · Issue #2441 · freebsd/pkg

@ericbsd I wonder whether the rewritten scheduler is as well-prepared, as the previous scheduler, to cope with untimely interruption.

https://www.freebsd.org/status/report-2024-10-2024-12/#_pkgbase_motivated_improvements_to_pkg

janove75

I have found a way
I did a partial upgrade using the command
pkg upgrade -f -x '^partial.*'
pkg query '%n' | grep '^partial'
I used every letter of the alphabet to replace "partial"
It's not very elegant, but it finally worked and I can now boot in multi-user mode.
But the x graphical interface is less friendly than before the upgrade.
The screen resolution is 1366x768 instead of 1920x1080. I will try to fix this in a few days. If you have any idea, you are welcome.
And I will also make more space for a future upgrade. If you have a shortcut, I will take it.

vimanuelt

janove75 The screen resolution of 1366x768 covers more situations than your hardware alone. To set 1920x1080 as default might upset many users.

grahamperrin

janove75 I have found a way …

For anyone who encounters a missing package as a result of untimely interruption to an upgrade, a hint.

Either:

activate the boot environment that preceded the upgrade; or
take relevant information from the environment.

In the screenshot below, I mounted the environment at /tmp/down then ran:

pkg -r /tmp/down prime-origins | sort -u > ~/pkg\ prime-origins.txt

The list in the pkg prime-origins.txt file will help to identify which missing packages, if any, should be installed.

After installations:

pkg check -d

grahamperrin

grahamperrin @ericbsd I wonder whether the rewritten scheduler is as well-prepared, as the previous scheduler, to cope with untimely interruption.

Found:

put back pkg … · ghostbsd/ghostbsd-ports@6408ab0 (2025-04-09)