You are not logged in.
What does the following error message in the journal mean?
I first noticed it after zram-generator was updated today.
(sd-exec-[419]: /usr/lib/systemd/system-generators/zram-generator terminated by signal ABRT.
Last edited by athan (2024-12-09 17:38:26)
Offline
https://wiki.archlinux.org/title/Zram
If you want to know *why* it aborted w/o providing any context: because you did something wrong
Offline
because you did something wrong
Yes, I did something very wrong, I answered "Yes" when pacman -Syu showed today's update of the zram-generator...
Thanks for the helpful answer.
Offline
What do you expect? Magic knowlege about the issue?
https://bbs.archlinux.org/viewtopic.php?id=57855
Edit, to maybe get this anywhere: an ABRT is a controlled exit.
There's probably some message in the system journal or the service status explaining it and perhaps some https://wiki.archlinux.org/title/Core_d … _core_dump to tell what's going on.
Last edited by seth (2024-12-09 13:58:28)
Offline
It's a minimal archinstall installation without any manual intervention or configuration of zram or swapping in general.
It worked fine with the zram created defaults until today. After zram-generator package was updated earlier it stopped working returning this error message.
I'm sorry I can't give more details but that's all it happened.
PS: If it helps, trying to manually start the zram service (sudo systemctl start systemd-zram-setup@zram0.service) I got the following error
Dec 09 16:12:22 arch zram-generator[4895]: thread 'main' panicked at /build/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_builder-4.5.23/src/parser/error.rs:32:9:
Dec 09 16:12:22 arch zram-generator[4895]: Mismatch between definition and access of `setup-device`. Could not downcast to TypeId(0xb98b1b7157a6417863eb502cd6cb5d6d), need to downcast to TypeId(0xcc946482a73f732ee0d1ba88c4926b66)
Dec 09 16:12:22 arch zram-generator[4895]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Dec 09 16:12:22 arch systemd[1]: systemd-zram-setup@zram0.service: Main process exited, code=dumped, status=6/ABRT
Last edited by athan (2024-12-09 14:30:57)
Offline
Yes you can, start w/ your /etc/systemd/zram-generator.conf and the "systemctl status systemd-zram-setup@zram0.service".
Then check for coredumps.
And again: there's gonna be context to this in the system journal where you found that line tbw.
Offline
/etc/systemd/zram-generator.conf as created by archinstall contains just the device name apparently using zram defaults for the rest
[zram0]
Also tried with some values with exactly the same results
[zram0]
zram-size = min(ram / 2, 4096)
compression-algorithm = zstd
systemctl status systemd-zram-setup@zram0.service
× systemd-zram-setup@zram0.service - Create swap on /dev/zram0
Loaded: loaded (/usr/lib/systemd/system/systemd-zram-setup@.service; static)
Active: failed (Result: core-dump) since Mon 2024-12-09 16:12:22 EET; 20min ago
Invocation: 874ee4ac605f4a47bbc96681186b36fc
Docs: man:zram-generator(8)
man:zram-generator.conf(5)
Process: 4895 ExecStart=/usr/lib/systemd/system-generators/zram-generator --setup-device zram0 (code=dumped, signal=ABRT)
Main PID: 4895 (code=dumped, signal=ABRT)
Mem peak: 1.5M
CPU: 13ms
Dec 09 16:12:22 arch systemd[1]: Starting Create swap on /dev/zram0...
Dec 09 16:12:22 arch zram-generator[4895]: thread 'main' panicked at /build/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_builder-4.5.23/src/parser/error.rs:32:9:
Dec 09 16:12:22 arch zram-generator[4895]: Mismatch between definition and access of `setup-device`. Could not downcast to TypeId(0xb98b1b7157a6417863eb502cd6cb5d6d), need to downcast to TypeId(0xcc946482a73f732ee0d1ba88c4926b66)
Dec 09 16:12:22 arch zram-generator[4895]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Dec 09 16:12:22 arch systemd[1]: systemd-zram-setup@zram0.service: Main process exited, code=dumped, status=6/ABRT
Dec 09 16:12:22 arch systemd[1]: systemd-zram-setup@zram0.service: Failed with result 'core-dump'.
Dec 09 16:12:22 arch systemd[1]: Failed to start Create swap on /dev/zram0.
Last edited by athan (2024-12-09 14:38:49)
Offline
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Dec 09 16:12:22 arch systemd[1]: systemd-zram-setup@zram0.service: Failed with result 'core-dump'.
https://wiki.archlinux.org/title/Core_d … _core_dump
Mismatch between definition and access of `setup-device`. Could not downcast to TypeId(0xb98b1b7157a6417863eb502cd6cb5d6d), need to downcast to Ty>
Please don't copy-paste out of the pager but that looks like some code bug (miscast access, interpreting a string as something else or whatever) you should report at https://github.com/systemd/zram-generator/issues
Offline
In the end, the solution to the issue seems to have been simpler than it first appeared.
After a pacman -Rs zram-generator and reinstalling it from scratch everything works normally. I guess the latest update somehow messed things up.
Offline
That's kinda odd, did you re-install rust along?
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Offline
That's kinda odd, did you re-install rust along?
Nope, just the zram-generator.
Rust is make dependency, so it was not installed with the zram-generator binary package.
Thanks!
Last edited by athan (2024-12-09 17:48:25)
Offline