try remove replica and sort of locked up
by Will Kay
Hi,
I have two IPA replica in each locations. I had to move "ld4ipa1" to another network. I ran 'ipa-replica-manage del'. Built a new one with the same name, but ran into issues. I removed it again and the process looked fine (I thought).
When I try to remove another node ld4ipa2 with `ipa-replica-manage del`, it aborted with output below. I checked the topology graph. ld4ipa1 is still there, but there's no topology segment connecting to any other nodes. it is "standalone".
I think I'm in a pretty messy state. What should I do to remove ld4ipa1 and ld4ipa2?
Thanks and be safe
Will
=========
'ipa host-show ld4ipa1.xyz.com' - host hot found
'ipa-replica-manage list' still shows ld4ipa1 as a master
-----
# ipa-replica-manage del ld4ipa2.xyz.com
Server removal aborted:
Replication topology in suffix 'domain' is disconnected:
Topology does not allow server ldipa1.xyz.com to replicate with servers:
ny4ipa2.xyz
sg1ipa2.xyz.com
ny4ipa1.xyz.com
ld4ipa2.xyz.com
ny2ipa1.xyz.com
sg1ipa1.xyz.com
Topology does not allow server ld4ipa2.xyz.com to replicate with servers:
ld4ipa1.xyz.com
Topology does not allow server ny2ipa1.xyz.com to replicate with servers:
ld4ipa1.xyz.com
Topology does not allow server ny4ipa1.xyz.com to replicate with servers:
ld4ipa1.xyz.com
Topology does not allow server ny4ipa2.xyz.com to replicate with servers:
ld4ipa1.xyz.com
Topology does not allow server sg1ipa1.xyz.com to replicate with servers:
ld4ipa1.xyz.com
Topology does not allow server sg1ipa2.xyz.com to replicate with servers:
ld4ipa1.xyz.com.
-----------
# ipa-replica-manage list-ruv
Directory Manager password:
Replica Update Vectors:
ny4ipa1.xyz.com:389: 4
ld4ipa2.xyz.com:389: 15 <---??
sg1ipa1.xyz.com:389: 9
ny4ipa2.xyz.com:389: 7
ny2ipa1.xyz.com:389: 3
sg1ipa2.xyz.com:389: 11
ld4ipa2.xyz.com:389: 16 <-- ??
Certificate Server Replica Update Vectors:
ny4ipa1.xyz.com:389: 6
sg1ipa1.xyz.com:389: 10
ny4ipa2.xyz.com:389: 8
ny2ipa1.xyz.com:389: 5
sg1ipa2.xyz.com:389: 12
ld4ipa2.xyz.com:389: 17
3 years, 10 months
dnf now always crashes (segfault) [F30]
by Frédéric
Hi,
dnf always immediately crashes on my F30. I do not know what to do.
I just upgraded from F28 to F30. Everything seemed fine. I was able
then to run dnf upgrade, got a kernel update. I rebooted with success.
Then I started the system-upgrade process to F31:
$ sudo dnf system-upgrade download --refresh --releasever=31
I got some issue with py-bcrypt that was installed in python 3:
Erreur : Transaction test error:
le fichier /usr/lib64/python3.7/site-packages/bcrypt/__init__.py
entre en conflit avec les tentatives d'installation de
python3-py-bcrypt-0.4-21.fc31.x86_64 et
python3-bcrypt-3.1.6-3.fc31.x86_64
le fichier /usr/lib64/python3.7/site-packages/bcrypt/__pycache__/__init__.cpython-37.opt-1.pyc
entre en conflit avec les tentatives d'installation de
python3-py-bcrypt-0.4-21.fc31.x86_64 et
python3-bcrypt-3.1.6-3.fc31.x86_64
le fichier /usr/lib64/python3.7/site-packages/bcrypt/__pycache__/__init__.cpython-37.pyc
entre en conflit avec les tentatives d'installation de
python3-py-bcrypt-0.4-21.fc31.x86_64 et
python3-bcrypt-3.1.6-3.fc31.x86_64
I removed py-bcrypt with
$ sudo pip3 uninstall py-bcrypt
Then I re-run the system-upgrade. Still got the same transaction error
with bcrypt even if the directory did not exist anymore.
So I ran as root:
# rpm --rebuilddb
And from this point any call to dnf immediately crashes with:
Segmentation fault (core dumped):
# dnf check all
Segmentation fault (core dumped)
# dnf clean all
Segmentation fault (core dumped)
# dnf clean
Segmentation fault (core dumped)
# dnf search firefox
Segmentation fault (core dumped)
I rebooted but it is still the same. What should I do?
Thanks
3 years, 10 months
Upgrade f31->f32 Problems with ktp/telepathy
by Jonathan Ryshpan
Upgrading from f31 to f32 I get these errors:
$ sudo dnf system-upgrade download --refresh --skip-broken --
releasever=32Before you continue ensure that your system is fully
upgraded by running "dnf --refresh upgrade". Do you want to continue
[y/N]: yFedora Modular 32 - x86_64 ......Errors during downloading
metadata for repository 'virtualbox': - Status code: 404 for
http://download.virtualbox.org/virtualbox/rpm/fedora/32/x86_64/repodata/r...
(IP: 104.123.204.100)Error: Failed to download metadata for repo
'virtualbox': Cannot download repomd.xml: Cannot download
repodata/repomd.xml: All mirrors were triedIgnoring repositories:
virtualboxModular dependency problem:
Problem: conflicting requests - nothing provides module(platform:f31)
needed by module gimp:2.10:3120191106095052:f636be4b-
0.x86_64Error: Problem: package ktp-common-internals-19.12.2-
1.fc32.x86_64 requires libtelepathy-qt5-service.so.0()(64bit), but none
of the providers can be installed - problem with installed package
ktp-common-internals-19.12.1-1.fc31.x86_64 - telepathy-qt5-0.9.7-
9.fc31.x86_64 does not belong to a distupgrade repository - ktp-
common-internals-19.12.1-1.fc31.x86_64 does not belong to a distupgrade
repository
The problems with virtualbox and gimp look fairly simple; the apps can
simply be removed from my system and then reinstalled later. But
telepathy looks like a mess; there are a large number of rpms related
to it, namely the following list. I don't use telepathy and would be
happy to see it go, but I am nervous about removing so many rpms for
fear that there may be other dependencies, so that removing them might
damage my system. Can anyone advise me?Here is the list:ktp-desktop-
applets-19.12.1-1.fc31.x86_64ktp-auth-handler-19.12.1-1.fc31.x86_64ktp-
send-file-19.12.1-1.fc31.x86_64ktp-accounts-kcm-19.12.1-
1.fc31.x86_64ktp-approver-19.12.1-1.fc31.x86_64ktp-contact-runner-
19.12.1-1.fc31.x86_64ktp-contact-list-19.12.1-1.fc31.x86_64ktp-
filetransfer-handler-19.12.1-1.fc31.x86_64ktp-common-internals-19.12.1-
1.fc31.x86_64ktp-kded-integration-module-19.12.1-
1.fc31.x86_64telepathy-haze-0.8.0-3.fc22.x86_64telepathy-glib-0.24.1-
14.fc31.x86_64telepathy-accounts-signon-2.0-3.fc31.x86_64telepathy-
logger-0.8.2-9.fc31.x86_64telepathy-filesystem-0.0.2-
15.fc31.noarchtelepathy-logger-qt-17.08.0-7.fc31.x86_64telepathy-
gabble-0.18.4-7.fc29.x86_64telepathy-rakia-0.8.0-
13.fc31.x86_64telepathy-qt5-0.9.7-9.fc31.x86_64telepathy-mission-
control-5.16.4-9.fc31.x86_64telepathy-salut-0.8.1-15.fc29.x86_64
<Possibly more besides>
3 years, 10 months
F32 workstation seems a lot faster. Kernel ? KDE ? Firefox ?
by linux guy
Hello people.
Thanks to everyone who worked on F32. It looks and runs great.
F32 seems a lot faster on my workstation. (AMD 3600X 64 GB RAM @ 3600MHz,
NVMe SSD.) Is KDE faster ? Firefox ? Kernel ?
It is amazing how Fedora/Linux keeps improving release after release.
Keep up the great work.
3 years, 10 months
xargs + grep+grep
by bruce
Hi.
simple issue that I'm not quite seeing.
find /home -type f ! -path "*/csvn/*" ! -path "*/Android*/*" -name
"*.*" -print0 | xargs -0 grep 'repos' | xargs -0 grep 'github'
So, I start at the top of the dir, I skip a few of the child dirs, and
I want to find files containing "repos" and "github".
The above cmd returns the err
xargs: argument line too long
Any pointers on my mistake?
Thanks
3 years, 10 months
Need help with a weird kernel update panic.
by John Mellor
I have one completely stock workstation F32 machine where kernel updates
almost always cause a multiple-reboot panic problem. This problem also
occurred on F31, but not on releases before that. I'm stumped and need
some help in figuring it out.
The symptoms vary in the number of reboots and the type of tertiary
error, but are otherwise pretty similar. It does not matter whether I
use the Gnome update app or the CLI dnf method. After a number of
reboots, the upgrade succeeds and Fedora behaves nortmally again. I
think that this only happens whenever the kernel is upgraded.
What I observe is that the machine is rebooted and on reboot, grub (I
think) gets a halt for a 32-bit relocation error. This sequence may
happen twice. Its an i7 with plenty of memory and an SSD boot disk, so
the 32-bit thing is confusing. To get around this error, I powercycle
the box and get into the next stage of the problem. One the 2nd or 3rd
reboot, I usually see a halt with an access outside of the kernel space,
although with the update this morning, I had a kernel panic instead.
Cold-booting again, and the update is installed, and the last reboot and
I'm up on the new updates.
After that, the machine behaves normally until the next kernel updates.
I assume that there is some incorrectly-asynchronous operation in grub
related to the update entry, but I can find no grub logs to dig into
this problem. I have several other machines that do not see this
problem. I dug around in the fedora bugs, but not knowing what to look
for, I'm basically blind. Its a pretty serious bug, especially if the
machine is remote. Does anyone have a way out of this?
--
John Mellor
3 years, 10 months
Why do I have 4 kernels when the install limit is 3 ?
by Sreyan Chakravarty
Hi,
Running
cat /etc/dnf/dnf.conf | grep install
gives:
installonly_limit=3
So then why do I have 4 kernels ?
$ rpm -q kernel
kernel-5.3.7-301.fc31.x86_64
kernel-5.5.15-200.fc31.x86_64
kernel-5.6.8-200.fc31.x86_64
kernel-5.6.10-300.fc32.x86_64
Shouldn't the 5.3 kernel version be removed ?
Or is it treating the 2 5.6 versions as one ?
--
Regards,
Sreyan
3 years, 10 months
system upgrade from F28 to F31: problem with installed package NetworkManager-libnm
by Frédéric
Hi,
I would like to upgrade a system from F28 to F31. But I get the following error:
Problem: problem with installed package
NetworkManager-libnm-1:1.10.12-3.fc28.x86_64
- package NetworkManager-libnm-1:1.20.10-1.fc31.x86_64 conflicts
with NetworkManager-glib < 1:1.20.10-1.fc31 provided by
NetworkManager-glib-1:1.10.12-3.fc28.x86_64
- package NetworkManager-libnm-1:1.20.4-1.fc31.x86_64 conflicts with
NetworkManager-glib < 1:1.20.4-1.fc31 provided by
NetworkManager-glib-1:1.10.12-3.fc28.x86_64
- NetworkManager-libnm-1:1.10.12-3.fc28.x86_64 does not belong to a
distupgrade repository
- problem with installed package NetworkManager-glib-1:1.10.12-3.fc28.x86_64
(try to add '--allowerasing' to command line to replace conflicting
packages or '--skip-broken' to skip uninstallable packages)
--allowerasing does not seem to be a nice option. In particular, I do
not have a physical access to the computer so if I loose the network,
it will be difficult to recover.
Any idea what I can do?
Thanks,
F
3 years, 10 months
Simple-scan put print back!
by ToddAndMargo
I really do like FC32!
simple-scan-3.36.2-1.fc32.x86_64
Put print back in the hamburger!
Yippee!
3 years, 10 months
firewalld 100% CPU and unresponsive
by Richard Shaw
I don't know if this has been a problem the whole time after upgrade but I
noticed while checking system load for a different reason that
filrewalld is using 100% of one core.
It is not responsive to firewall-cmd nor is there anything useful in the
journal log:
# journalctl --no-hostname -b0 -u firewalld
-- Logs begin at Thu 2020-05-07 14:07:43 CDT, end at Tue 2020-05-12
07:15:25 CDT. --
May 12 06:47:20 systemd[1]: Starting firewalld - dynamic firewall daemon...
May 12 06:47:21 systemd[1]: Started firewalld - dynamic firewall daemon.
May 12 07:01:26 systemd[1]: Stopping firewalld - dynamic firewall daemon...
May 12 07:01:26 systemd[1]: firewalld.service: Succeeded.
May 12 07:01:26 systemd[1]: Stopped firewalld - dynamic firewall daemon.
May 12 07:01:26 systemd[1]: firewalld.service: Consumed 14min 1.157s CPU
time.
May 12 07:02:03 systemd[1]: Starting firewalld - dynamic firewall daemon...
May 12 07:02:03 systemd[1]: Started firewalld - dynamic firewall daemon.
I tried downgrading but it's still the version that ships with f32 so no
dice...
Anyone else seeing this?
Thanks,
Richard
3 years, 10 months