| View previous topic :: View next topic |
| Author |
Message |
setan
n00b
Joined: 21 Feb 2024
Posts: 65
|
 Posted: Sun Mar 24, 2024 9:51 am Post subject: Overnight emerge -e @world crashed my session |
 |
|
Hello,
yesterday I was performing the profile upgrade (17.1 to 23).
I have followed the steps all the way up to the last step.
Recompiling ~1400 packages takes a while. I have started it in the morning and it crashed by night.
I know that It stopped when compiling monero from the emerge log:
| Code: | 1711259073: ::: completed emerge (1370 of 1480) net-dns/unbound-1.19.1 to /
1711259073: >>> emerge (1371 of 1480) net-p2p/monero-0.18.3.3 to /
1711259073: === (1371 of 1480) Cleaning (net-p2p/monero-0.18.3.3::/var/db/repos/guru/net-p2p/monero/monero-0.18.3.3.ebuild)
1711259073: === (1371 of 1480) Compiling/Merging (net-p2p/monero-0.18.3.3::/var/db/repos/guru/net-p2p/monero/monero-0.18.3.3.ebuild)
# emerge -e logs end here
|
I have tried compiling it again and it compiled just fine.
At 07:12:51 kernel prints out taksks state (memrory values in pages and kills singal-desktop:
| Code: | Mar 24 07:12:51 buk10 kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=openrc.tor,mems_allowed=0,global_oom,task_memcg=/2,task=signal-desktop,pid=22743,uid=1000
Mar 24 07:12:51 buk10 kernel: Out of memory: Killed process 22743 (signal-desktop) total-vm:34512240kB, anon-rss:17208kB, file-rss:1684kB, shmem-rss:37408kB, UID:1000 pgtables:912kB oom_score_adj:200 |
and after that something goes wrong with wayland?
| Code: | Mar 24 07:12:56 buk10 foot: wayland: failed to read events from the Wayland socket: Broken pipe
Mar 24 07:12:56 buk10 foot: server: client FD=7: terminal still alive
Mar 24 07:12:56 buk10 foot: wayland: failed to roundtrip Wayland display: Broken pipe
Mar 24 07:12:56 buk10 last message buffered 2 times
Mar 24 07:12:56 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 07:12:56 buk10 foot: server: client FD=16: terminal still alive
Mar 24 07:12:56 buk10 foot: wayland: failed to roundtrip Wayland display: Broken pipe
Mar 24 07:12:56 buk10 last message buffered 2 times
Mar 24 07:12:56 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 07:12:56 buk10 foot: server: client FD=24: terminal still alive
Mar 24 07:12:56 buk10 foot: wayland: failed to roundtrip Wayland display: Broken pipe
Mar 24 07:12:56 buk10 last message buffered 2 times
Mar 24 07:12:56 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 07:12:56 buk10 foot: wayland: failed to flush wayland socket: Broken pipe
|
From there I only have dbus-daemon, Tor and NetworkManager logs, all the way up to this:
| Code: | Mar 24 10:11:04 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 kernel: Hyprland[2611]: segfault at 10 ip 00007f2d89e0a07b sp 00007fff073a50f0 error 4 in libc.so.6[7f2d89d96000+130000] likely on CPU 4 (core 0, socket 0)
Mar 24 10:11:07 buk10 kernel: Code: f8 10 76 7b 4c 3b b5 88 08 00 00 73 72 8b 35 38 81 11 00 85 f6 0f 85 b4 00 00 00 f6 43 08 01 75 22 48 8b 03 48 29 c3 49 01 c4 <48> 8b 53 08 48 83 e2 f8 48 39 c2 0f 85 ac 00 00 00 48 89 df e8 bc
Mar 24 10:11:07 buk10 foot: wayland: failed to read events from the Wayland socket: Connection reset by peer
Mar 24 10:11:07 buk10 foot: server: client FD=7: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: server: client FD=16: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: server: client FD=17: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: server: client FD=40: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: server: client FD=48: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: server: client FD=56: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: server: client FD=64: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: server: client FD=72: terminal still alive
Mar 24 10:11:07 buk10 foot: wayland: failed to roundtrip Wayland display: Connection reset by peer
Mar 24 10:11:07 buk10 last message buffered 2 times
Mar 24 10:11:07 buk10 foot: terminal: slave exited with signal 1 (Hangup)
Mar 24 10:11:07 buk10 foot: wayland: failed to flush wayland socket: Connection reset by peer
Mar 24 10:12:40 buk10 shutdown[3381]: shutting down for system reboot
|
At the end you can see me initiating reboot (from another TTY).
I want to ask:
1. How do I finish the emerge -e without recompiling >1200 packages again?
2. What happened with signal? Can that be connected to the "experimental" tray icon that I have run signal with? |
|
| Back to top |
|
 |
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1535
|
| Posted: Sun Mar 24, 2024 10:18 am Post subject: |
|
|
You can use emerge --resume in such situations. I don't know if the resume data is overwritten now, but you can try.
You can also try using the binhost to save time from compilation. It still takes several hours though. I had 1047 binary packages out of 1574 if I remember correctly but merging of binary packages doesn't happen in an instant and also some packages still need to be compiled. Even if I didn't have use incompatibilities, I wouldn't spare more than an additional 100 or even less packages from compilation.
Best Regards,
Georgi |
|
| Back to top |
|
|
setan
n00b
Joined: 21 Feb 2024
Posts: 65
|
| Posted: Sun Mar 24, 2024 10:43 am Post subject: |
|
|
Daaaamn, I forgot about that  .
I have tried all those:
| Code: | emerge --ask --emptytree --getbinpkg @world
emerge -a --emptytree --getbinpkg --binpkg-respect-use=y @world
emerge -a --emptytree --getbinpkg --binpkg-respect-use=n @world
|
but they all threw warnings at me, so I got scared.
Here is the first one:
| Code: | Would you like to merge these packages? [Yes/No] yes
>>> Verifying ebuild manifests
>>> Running pre-merge checks for acct-group/audio-0-r3
--2024-03-24 12:23:01-- https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64-v3/acct-group/audio/audio-0-r3-1.gpkg.tar
Resolving distfiles.gentoo.org... 156.146.33.137, 195.181.175.15, 195.181.170.18, ...
Connecting to distfiles.gentoo.org|156.146.33.137|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20480 (20K) [application/x-tar]
Saving to: ‘/var/cache/binpkgs/acct-group/audio/audio-0-r3-3.gpkg.tar.partial’
/var/cache/binpkgs/acct-group/audio/audio-0-r3-3.gpkg.tar.partial 100%[=============================================================================================================================================================================>] 20.00K --.-KB/s in 0.006s
2024-03-24 12:23:03 (3.44 MB/s) - ‘/var/cache/binpkgs/acct-group/audio/audio-0-r3-3.gpkg.tar.partial’ saved [20480/20480]
* audio-0-r3-3.gpkg.tar MD5 SHA1 size ;-) ... [ ok ]
!!!
gpg: keyblock resource '/etc/portage/gnupg/pubring.kbx': No such file or directory
[GNUPG:] ERROR add_keyblock_resource 33587281
[GNUPG:] PLAINTEXT 74 0
[GNUPG:] NEWSIG
gpg: Signature made Wed Mar 20 22:33:34 2024 CET
gpg: using RSA key 534E4209AB49EEE1C19D96162C44695DB9F6043D
[GNUPG:] ERROR keydb_search 33554445
[GNUPG:] ERROR keydb_search 33554445
[GNUPG:] ERRSIG 2C44695DB9F6043D 1 10 01 1710970414 9 534E4209AB49EEE1C19D96162C44695DB9F6043D
[GNUPG:] NO_PUBKEY 2C44695DB9F6043D
gpg: Can't check signature: No public key
gpg: can't create `/etc/portage/gnupg/random_seed': No such file or directory
!!! Invalid binary package: '/var/cache/binpkgs/acct-group/audio/audio-0-r3-3.gpkg.tar.partial', GPG verify failed
* Binary package is not usable
>>> Failed to emerge acct-group/audio-0-r3
>>> Running pre-merge checks for acct-group/kvm-0-r3
--2024-03-24 12:23:03-- https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64-v3/acct-group/kvm/kvm-0-r3-1.gpkg.tar
Resolving distfiles.gentoo.org... 195.181.175.41, 156.146.33.137, 156.146.33.140, ...
Connecting to distfiles.gentoo.org|195.181.175.41|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20480 (20K) [application/x-tar]
Saving to: ‘/var/cache/binpkgs/acct-group/kvm/kvm-0-r3-3.gpkg.tar.partial’
/var/cache/binpkgs/acct-group/kvm/kvm-0-r3-3.gpkg.tar.partial 100%[=============================================================================================================================================================================>] 20.00K --.-KB/s in 0.007s
2024-03-24 12:23:03 (2.67 MB/s) - ‘/var/cache/binpkgs/acct-group/kvm/kvm-0-r3-3.gpkg.tar.partial’ saved [20480/20480]
* kvm-0-r3-3.gpkg.tar MD5 SHA1 size ;-) ... [ ok ]
!!!
gpg: keyblock resource '/etc/portage/gnupg/pubring.kbx': No such file or directory
[GNUPG:] ERROR add_keyblock_resource 33587281
[GNUPG:] PLAINTEXT 74 0
[GNUPG:] NEWSIG
gpg: Signature made Wed Mar 20 22:33:54 2024 CET
gpg: using RSA key 534E4209AB49EEE1C19D96162C44695DB9F6043D
[GNUPG:] ERROR keydb_search 33554445
[GNUPG:] ERROR keydb_search 33554445
[GNUPG:] ERRSIG 2C44695DB9F6043D 1 10 01 1710970434 9 534E4209AB49EEE1C19D96162C44695DB9F6043D
[GNUPG:] NO_PUBKEY 2C44695DB9F6043D
gpg: Can't check signature: No public key
gpg: can't create `/etc/portage/gnupg/random_seed': No such file or directory
!!! Invalid binary package: '/var/cache/binpkgs/acct-group/kvm/kvm-0-r3-3.gpkg.tar.partial', GPG verify failed
* Binary package is not usable
|
and it goes on and on.
I know that --getbinpkg impiles -k, but I thougght that I'm better off without them then.
Also, how unstable would running with 1350/1500 upgraded packages would be?
They could update overtime and all would be fine. |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1535
|
| Posted: Sun Mar 24, 2024 12:39 pm Post subject: |
|
|
Problem is you can't just interrupt emerge -e and change the settings in-between. You should either --resume (I haven't checked if that's possible but it should be) or start over, that's the tricky part.
Regarding the error, I think you can disable package signature from make.conf by commenting the suggested line from the quickstart guide
| Code: | | #FEATURES="${FEATURES} binpkg-request-signature" |
Another option I think is to delete /etc/portage/gnupg. Try moving it away first.
Best Regards,
Georgi |
|
| Back to top |
|
|
sam_
Developer
Joined: 14 Aug 2020
Posts: 1678
|
| Posted: Sun Mar 24, 2024 12:45 pm Post subject: |
|
|
I wouldn't encourage turning off verification. Instead, try: mv /etc/portage/gnupg{,.bak} ; getuto.
If it still fails, share the output of getuto and from emerge failing. |
|
| Back to top |
|
|
logrusx
Veteran
Joined: 22 Feb 2018
Posts: 1535
|
| Posted: Sun Mar 24, 2024 12:56 pm Post subject: |
|
|
| sam_ wrote: | I wouldn't encourage turning off verification. Instead, try: mv /etc/portage/gnupg{,.bak} ; getuto.
If it still fails, share the output of getuto and from emerge failing. |
I was reluctant to suggest this as it was only from my memory and I couldn't recall from where I knew so I wasn't sure.
But I found it:
https://wiki.gentoo.org/wiki/Gentoo_Binary_Host_Quickstart#Troubleshooting
Best Regards,
Georgi |
|
| Back to top |
|
|
setan
n00b
Joined: 21 Feb 2024
Posts: 65
|
| Posted: Sun Mar 24, 2024 4:39 pm Post subject: |
|
|
Concerning the emerge --resume:
I forgot about all this. Now I need to reap what I sow.
For the binhost problems, it was my mistake again :ddd
https://forums.gentoo.org/viewtopic-p-8820885.html#8820885
However I am still curious what made my PC crash. |
|
| Back to top |
|
|
setan
n00b
Joined: 21 Feb 2024
Posts: 65
|
| Posted: Thu Mar 28, 2024 11:23 am Post subject: |
|
|
Running a system that has 4/5 of the packages migrated is stable so far.
I will come back here if something crashes |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
