I recently upgraded my PC from F26 to F27, and noticed that fail2ban was not
adding the configured chains to iptables. This worked fine at F26.
There are no error messages in the log files (dmesg, /var/log/messages,
/var/log/fail2ban.log). I have tried disabling SELinux, then restarting
fail2ban but the chains still do not appear. I do not use firewalld so removed
the fail2ban-firewalld package. I set the fail2ban log level to debug, and that
showed the relevant iptables commands that would add the chains, but otherwise
gave no indication of any error. (I used the logged iptables commands to
manually add the chains, and all the commands worked fine.)
If I log (using logger) appropriate log messages - such as an SSH failed
authentication attempt - then that particular chain does appear in iptables. If
I unban the logged IP address, then the chain remains in iptables. If I restart
fail2ban, then the chain is no longer in iptables.
I'm now a bit stumped as to what might be the problem. Anyone any ideas?
John Horne | Senior Operations Analyst | Technology and Information Services
University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK
This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, Plymouth University accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. Plymouth University does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
After a dnf update today, I was unable to bring up my normal wireless
connection on a Dell XPS 17 laptop. I was able to get a connection
via my cellphone, and did a "dnf downgrade iwl*-firmware
NetworkManager*", and after a reboot I am back online.
From info in /var/log/messages, it looks like the relevant firmware
packages are iwl7260-firmware-1:22.214.171.124-76.fc25.noarch which was
downgraded to iwl7260-firmware-1:126.96.36.199-68.fc25.noarch.
I'm happy to open a bugzilla if there isn't one on this issue, but it
seems to me I should have more info than what I posted above, and so
am looking for advice/guidance from the list.
Thanks in advance!
Within the next three weeks or so, barring any great surprises, I
hope to be putting Fedora 27 onto four PCs, a laptop, and a netbook. IIRC,
the netbook, which I haven't used recently, has F24 now; all the others
are running 26. I'll do all I can by upgrading, because every time I do a
fresh install, it costs me something more than a whole day per machine to
do the tweaking I need.
(I've been running Fedora since it was RedHat7; so my trifocal
fingers and arthritic eyeballs know their jobs IF I get all the tweaks
right -- a great boon and a bringer of cyber-survival, since I also keep
getting slower and more forgetful....)
A correspondent on another list says one used to be able to use
Mondo Rescue to grab all the settings on an existing install and clone
them onto a new one. That would save me vast tedium.
But the Mondo Rescue site lists only rpms for Fedora 23 and
before. And either I'm garbling my correspondent's directions, or they
don't work any more -- or both.
I tried a few variations on "dnf install Mondo-xyzq". I also
downloaded a few .rpms from Mondo's repository and ran "rpm -ivh" against
them. Both tries failed.
Is there a tutorial somewhere? Has Mondo Rescue forked into
something with another name? Have the Fedora Gurux and Alpha Plus
Technoids come up with a replacement while I wasn't looking??
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
After several days of fruitless effort I have to bring this to the
community. Since I upgraded to F27, I have never been able to sustain
any viable network connection to other computers on my network that run
Windows 10. Which means if I ever have to transfer files between or
among them, I have to use USB flash drives or even USB-connectable
Now I suppose I could buy a spare Western Digital Passport for this
application. But I would like to know what I'm missing.
For the record:
The computer I'm typing this on, that runs F27, presently has a wireless
connection to the network. I hope, within the next two months, to move
to an environment where I can connect this computer to the network using
a MoCA adapter, a switch in the room, and a coaxial connector in the
wall to connect this computer, a printer, and maybe a laptop if I bring
it into the same room. That never used to make any difference, but yes,
I'm going to try to "remedy" that "fault" (if anyone here chooses to
find fault with using a wireless connection).
The Samba workgroup is named Home. That's case-sensitive.
I have User authentication on the Samba server.
I created Samba user accounts for every Fedora user account on this
machine--all three of them.
With F26, I could always look up Home under Samba Shares and find it.
But now--nothing. And even specifying Home gets a not-found-here kind of
The Services application shows that both smb and nmb are running.
So what's wrong, where might the fault lie, and how do I correct it?
I lost the host Fedora25 when the Virtual machine(win7) was off.
I installed Fedora 25 on a new 1TB disk. Now I can mount the old root
and home on the new Fedora25. How to recover the win7 guest machine?
$ uname -a
Linux localhost.localdomain 4.13.15-100.fc25.x86_64 #1 SMP Tue Nov 21
22:45:32 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Please help me. Thanks.
I've been running Fedora since the Fedora Core days. About 11 days
ago, I upgraded my x86_64 system from 25 to 26. Prior to upgrading to
26, I was running 25 for over 6 months without any stability issues.
Since the upgrade to 26, something inspecting the process list is
wedging the OS. The problem isn't even obvious until I happen to run
'ps' and the command hangs indefinitely, and can't be killed.
However, at that point, the load avg takes off, and just keeps
climbing over time. The system is still mostly responsive, but
clearly its very unhappy about something. I'm able to check 'dmesg'
as well as /var/log/messages while its in the bad state, and there's
nothing new in either, and definitely nothing bad, unusual or
suspicious. Unfortunately, I can't even shutdown/reboot gracefully at
this point, as anything & everything that wants to inspect the process
list also hangs, and so the system never fully shuts down (I waited a
full hour the first time hoping that eventually it would proceed). I
have to hit RESET and then (thankfully) the system boots up just fine
The first hang happened about 28 hours after upgrading to 26. Things
were fine after that for just over 9 days of uptime when the same
thing happened all over again.
I've tried googling to see if there's any one else running into this,
and didn't find much. This was the closest thing, but its over a year
At this point, I'm wondering whether anyone:
0) recognizes this as a known bug
1) has any ideas how to debug it further
I try to compile gerbera in order to test this dlna server. There is an
option to have mysql as a database but, mysql no longer exists on
fedora, so if I activate this option, the compilation fails.
Is there a way to substitute mariadb?
Thank you for any help.
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
I recently noticed that spamassassin (running as the local "daemon"
account) will hang some of the time when processing messages, and
tracked it to the process attempting to access
~user/.spamassassin/user_prefs. I believe that should return an access
failure, but sometimes the process stalls instead.
In any case, I'd like to allow access, but my understanding is that
processes without a Kerberos ticket cannot access an NFS4 filesystem
with sec=krb5. Is that correct? If so, how would I allow a local
system account to access globally readable files? Should I create a
keytab, and set KRB5_KTNAME in the spamassassin environment?
Does anyone working with NFS and krb5 have any tips?
In my lab I installed a machine connected to a big screen on which we
This machine is supposed to be as much autonomous as possible. So I
chose impressive as PDF player but it seems that after few hours it
crashes because of a fatal error in XWayland.
Starting it from gnome + Xorg doesn't change anything.
I'm running Fedora 27+Gnome+Wayland.
So my question is, anyone knows others softwares I can start from bash
with options to put in full screen plus time between slides?...
Gnome-document looks good but it doesn't seems to be possible to do
that from bash.
I'm attempting to build a Fedora 26 ISO, but I'm having difficulties
with the instructions listed here:
Unfortunately, they fail when attempting to spawn a shell, with the
following error message:
/var/lib/mock/fedora-26-x86_64/root/dev is pre-mounted and
pre-populated. If a pre-mounted /dev is provided it needs to be an
unpopulated file system.
mknod(/var/lib/mock/fedora-26-x86_64/root/dev/null) failed: File exists
Is there a work around/another way to build an iso?