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:126.96.36.199-76.fc25.noarch which was
downgraded to iwl7260-firmware-1:188.8.131.52-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!
in order to backing up of the data , I wrote a script that uses the rsync
This script have to be launched manually, and the data are saved on a USB
Hard Disk, which (obviously) must be mounted.
The mounting of the partitions for the back up on the USB HD is made
permantly at boot of the computer (the name of the backup-partitions is
wrote in the file / etc / fstab) :
UUID=376214F24CC07CE0 /media/BKx_data-personal ntfs defaults 0 0
UUID=479F99A324FF4D1D /media/BKx_programming ntfs defaults 0 0
UUID=EA8266EA8266BB29 /media/BKx_data-common ntfs defaults 0 0
This script works fine.
However, this solution for backing up the data is problematic, because *I
always receive messages with the request of access to the partitions ** of
the “backup-partitions”** by "nautilus"* - every time that I use the "find"
I can consider that this problem is connected with the *permanent *
*mounting* of the partitions on the HD-USB (on the file /etc/fstab).
To avoid these problems I actually removed the permanent mounting of the
partitions by registering them on the file fstab and now I'm looking for an
alternative solution for the back up the data.
I think this solution can go in the following directions:
mounting the partitions (commanded by the script) before executing the
rsync command and unmounting them immediately afterwards.
alternatively, giving appropriate orders to the “udev feature” about the
backup partitions (I think this is possible to do, but I do not know how to
I would like to have some suggestions and advice about it.
Funny, the things one learns after making the first clean install in ten
or more iterations of Fedora.
For instance, that Adobe long ago abandoned the Adobe ("Acrobat") Reader
for Linux, and the nspluginwrapper project.
So that now, if you still want to use Adobe for Linux, you have to save
an old rpm and install it directly. And do it every time you reinstall
Fedora--or at least reinstall it cleanly.
I need advice on whether I can abandon Adobe Reader completely, and what
to use instead.
I use it all the time for certain PDF's that come with form fields that
you fill out. Not all PDF viewers--and not the PDF viewer native to
Firefox--support form filling. Without form filling, I have to fill in
forms by hand--and my fist is a bit of a strain on anyone's eyes,
especially those of a bureaucrat or his confidential secretary. So I
need form filling.
That aside, I'd love to have something that opens seemlessly in any
For the record, I use KDE. But I'll still use any GNOME products that
still open in KDE.
Just had another boot that utterly failed because services that were
supposed to start only after the network interfaces came up, didn't. They
started too soon. Privoxy's logfile has the smoking gun:
2017-12-16 09:42:39.875 7f4acdaa6740 Fatal error: can't bind to 192.168.0.1:8000: Cannot assign requested address
This is despite that NetworkManager-wait-online was enabled and active. This
is what everyone kept telling me was the only thing that needed to be done.
Well, it was enabled:
[root@shorty system]# systemctl status NetworkManager-wait-online
● NetworkManager-wait-online.service - Network Manager Wait Online
Loaded: loaded (/usr/lib/systemd/system/NetworkManager-wait-
Active: active (exited) since Sat 2017-12-16 09:42:39 EST; 12min ago
Process: 977 ExecStart=/usr/bin/nm-online -s -q --timeout=30 (code=exited,
Main PID: 977 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 4915)
Dec 16 09:42:32 shorty.email-scan.com systemd: Starting Network Manager Wait
Dec 16 09:42:39 shorty.email-scan.com systemd: Started Network Manager Wait O
It came up at 09:42:39. And, at 09:42:39 privoxy also came up. And privoxy
still blew chunks because the primary network interface wasn't up yet.
Why is it so friggin difficult to get something this simple, this basic
concept of starting things only after the network interfaces are up, working
correctly, and reliably?
Oh yeah, I know. systemd.
OK, I just updated my system and got the same
ridiculous delays I saw someone else complain about
recently. Not once, but twice. First when
it installed the new rpcbind, then second
when it ran the rpcbind scriptlet.
Worse than that, when I rebooted to make sure
everything was loaded from scratch and up to
date, the reboot hung for about 3 minutes
saying a start job was running for man-db-cache-update
(or something like that).
What kind of moronic decision is it to postpone
a reboot while updating the man db? If there is
anything less critical I have a hard time thinking
what it is.
For gosh sakes, keep a flag somewhere that says if
the man db is up to date and update it on a timer
when the system is back up again if required.
is it just me ?
in an terminal running "man man" constantly scrolling the pages up or down: it scrolls some line/a page (~2 seconds), stops, scrolls some lines, stops ...
Also if I play video's or card games I notice micro dropout's.
Video plays 2 seconds fluidly, then pauses/stucks for a ~1/4 second, plays 2 seconds fluidly, pauses/stucks for a ~1/4 second, and so on.
it seems like a video-buffer isn't constantly filled to play videos smooth.
I exclude hardware error cause:
- the box is just an half year old and I tested a card game under windows 7 without dropouts.
- I tested with another monitor.
I tested an elder kernel ~4.13.x without an solution.
I tested under wayland and Xorg-Gnome.
F27 is up date.
Any hints to debug/troubleshoot this ?
Or is it just me ?
currently running fedora 27 on my asus laptop, and i've previously
whined about how cripplingly slow the firefox browser is, to the point
where i had to kill it and restart it several times a day (memory
more recently, it simply locks up my entire system, typically within
only minutes of my starting it, to the point where i've bailed on it
and switched to chrome. at this point, since i'm not wedded to any
particular browser, i'm open to suggestions for a simple, fast,
reliable and secure browser for fedora.
of course there is always opera (which i haven't used in quite some
time so i have no idea how well that fits the bill). and if i choose
to stick with chrome, i just ran across what looks like a hardened
version of it, iridium:
i'm sure there are other possibilities, so i'm open to suggestions. i
really wish i knew why firefox was treating me so badly, but i've
given up trying to figure it out and just want to move on.
Robert P. J. Day Ottawa, Ontario, CANADA
I am experiencing random logouts on my system. No apparent
links to any one program or sequence of events. In fact the last time
it happened there were no windows open yet. I went up for the
Activities button and next thing I saw was the login window.
Processor: AMD FX-8300 eight-core processor x 8
OS type: 64 bit
Graphics: AMD Oland
GNOME: Version 3.24.2
Has anyone else experienced this? Also my system is
experiencing some choppiness when running 0AD.