On 2020-04-21 23:21, Ed Greshko wrote:
On 2020-04-22 14:11, ToddAndMargo via users wrote:
On 2020-04-21 23:05, Ed Greshko wrote:
On 2020-04-22 14:00, ToddAndMargo via users wrote:
On 2020-04-21 22:55, Ed Greshko wrote:
rpm --rebuilddb
Hi Ed,
I happened after doing a # dnf upgrade and the upgrade froze for an hour on selinux policies
What did you do when it "froze"?
I did a ps and kill -9 on three dnf process
I did a reboot later trying to troubleshoot this. No joy.
Well, hard to say what kind of problems may be caused by killing dnf in the middle of what it may have been doing.
You first, could try
setenforce 0 dnf upgrade....
No change.
More info:
# dnf upgrade --refresh --disablerepo=* --enablerepo=fedora Fedora 30 - x86_64 17 kB/s | 16 kB 00:00 Bus error (core dumped)
# tail -f /var/log/messages Apr 21 23:25:30 server audit[2710]: ANOM_ABEND auid=1001 uid=0 gid=0 ses=4 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=2710 comm="dnf" exe="/usr/bin/python3.7" sig=7 res=1
Apr 21 23:25:30 server kernel: traps: dnf[2710] trap stack segment ip:7fe2296e78ed sp:7ffd432ffd20 error:0 in libdnf.so.2[7fe229652000+103000]
Apr 21 23:25:30 server systemd-coredump[2712]: Failed to connect to coredump service: Connection refused Apr 21 23:25:30 server abrt-dump-journal-core[1109]: Failed to obtain all required information from journald