What's going on with net.ipv4.conf.???.rp_filter ?
by Bob Marcan
Hi.
With previous kernel 3.18.5-101.fc20.x86_64
sysctl -w net.ipv4.conf.${interface}.rp_filter=0
was enough to run iptv.
With kernel 3.18.6-100.fc20.x86_64
sysctl -w net.ipv4.conf.all.rp_filter=0 is needed to get it run.
It is not the first time to observe this.
Does anyone have some clue about this?
BR, Bob
9 years, 3 months
swapping
by Patrick Dupre
Hello,
I guess that the permanent swapping is not due to setroubleshooter
but ma Go of RAM and teh swapping is just increasing permanently
reaching 5Go
(20 firefox processes are running requiring 5% of Mem each)
How can I trouble shoot this permanent issue on this computer?
Thank.
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
9 years, 3 months
(La)TeX suddenly can't find anything
by Andras Simon
I've been using LaTeX on a fully updated Fedora 21, but now suddenly
even TeXing the simplest plain TeX file produces this:
warning: kpathsea: /usr/share/texlive/texmf-config/ls-R: No usable
entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
warning: kpathsea: /usr/share/texlive/texmf-var/ls-R: No usable entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
warning: kpathsea: /usr/share/texlive/texmf-local/ls-R: No usable
entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
warning: kpathsea: /usr/share/texlive/texmf-dist/ls-R: No usable
entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
This is TeX, Version 3.14159265 (TeX Live 2014) (preloaded format=tex)
kpathsea: Running mktexfmt tex.fmt
warning: kpathsea: /usr/share/texlive/texmf-config/ls-R: No usable
entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
warning: kpathsea: /usr/share/texlive/texmf-var/ls-R: No usable entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
warning: kpathsea: /usr/share/texlive/texmf-local/ls-R: No usable
entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
warning: kpathsea: /usr/share/texlive/texmf-dist/ls-R: No usable
entries in ls-R.
warning: kpathsea: See the manual for how to generate ls-R.
tcfmgr: config file `tcfmgr.map' (usually in $TEXMFMAIN/texconfig) not
found (ls-R missing?).
fmtutil: config file `fmtutil.cnf' not found.
I can't find the format file `tex.fmt'!
There are a few ls-R files around, and all but one are binary files
(see below) which surprises me, but rpm -V on the package that
contains them doesn't complain. (The one that is a plain text file has
only this:
% ls-R -- filename database for kpathsea; do not change this line.
./:
.:
ls-R
in it.)
file says of the binary ls-R files that they're xz compressed; and
after uncompressing them, file reports this:
ELF 32-bit LSB relocatable, Intel 80386, version 1 (SYSV),
BuildID[sha1]=d1cc6893beed5454b21594f2dff8f27b6d9fad7d, not stripped
Can this be related to a recent filesystem problem on / ? I've
reinstalled all texlive packages after noticing and repairing it.
And, most importantly, what should I try?
Andras
9 years, 3 months
journalctl --follow
by Wolfgang S. Rupprecht
Is journalctl in the tail -f mode called "follow" supposed to be
realtime? I'm seeing it more or less output log lines in realtime for
many hours and then eventually it falls behind with half an hour or one
hour delay.
The (simplified) lines are from a perl sshd tracker are:
open( LOG, "journalctl -o short-precise -u sshd --follow |");
while (<LOG>) {
...
}
I suppose, it is possible that the delay is in perl, but journalctl
seems more likely to be the culprit, hence the subject line.
-wolfgang
9 years, 3 months
FC21 intermittently booting up to black/blank screen
by linuxnutster＠videotron.ca
Hello,
Subsequent to a fedup from FC20 to FC21, I've been having bootup issues
which I believe are VGA driver related. Every now and then I start my
computer and it boots up to a blank screen and hangs. When I move the
mouse, an X-shaped cursor appears. The latter does move with the mouse.
Once I hit reset, it boots up normally each time.
My vga card is an nvidia Geforce 210 ( Asus en210 ) 1GB. I started off
by manually installing the nvidia proprietary, with no change, and then
moved to akmod-nvidia-304xx. The issue remained. I am now using the
akmod-nvidia-340xx and still have the same problem. It seems to me I had
this problem for a little while under FC20 when it was released.
Please note, I am not an expert. I tend to be an "install it and use it"
type of user. I'm looking for input on how to troubleshoot this issue -
logs, etc... also...am I the only one experiencing this?
9 years, 3 months
nm-applet-WARNING: what am I missing
by Ranjan Maitra
Hi,
On a new F21 installation from scratch, I am getting the following message:
% nm-applet
GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.
(nm-applet:1436): nm-applet-WARNING **: Failed to initialize D-Bus: /bin/dbus-launch terminated abnormally without any error message
This makes me think that I am missing some package. What could it be? How do I trouble-shoot?
Many thanks for any pointers and best wishes,
Ranjan
--
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
____________________________________________________________
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!
9 years, 3 months
Unknown Metadata Type from Yumex
by Stephen Morris
WARNING: Unknown metadata type (group_gz) for <b>fedora</b>
I'm getting the above message on a number of repositories, where there
are a couple of different values between the brackets, when Yumex
downloaded the metadata this morning as part of it checking for
available updates. What does it mean and how do I rectify it?
Also, after downloading the metadata and applying the only update
available, which was an update I was expecting (it was the kmod-nvidia
update for the new kernel), yumex downloaded all the metadata again and
produced the same messages. Is the above messages the reason why Yumex
did the double metadata download?
9 years, 3 months
many journalctl processes at once on F20
by Fred Smith
Hi all!
I've got an old netbook sitting here, running F20, performing a dedicated
function, where nobody ever logs into it (except me, once in a long
while).
I've noticed lately that it seems AWFULLY slow (even for the slow
computer that it normally is). Last night I logged in to see if I could
see what's going on, and I fund a load average around 17-20, ten
instances of journalctl running, and over a gig of swap space in use.
Uptime, as of that moment was around six days.
In the output of top I didn't see anything particularly startling in
memory usage other than the gig of swap.
I did a "yum update", and rebooted this morning to pick up the new
kernel, libs, etc. and now it has no instances of journalctl running
and zero swap usage.
I'm puzzled as to why or how it got all those journalctl processes running,
as I thought it was a commandline app for viewing lots, and not something
the system would be running on its own.
This morning, "last" shows more or less normal-looking events, so unless
lastlog has been hacked it doesn't seem likely that there's been some
bad person in the system:
# last
fredex pts/1 192.168.2.12 Thu Feb 12 10:24 still logged in
fredex pts/0 192.168.2.12 Thu Feb 12 10:24 still logged in
reboot system boot 3.14.2-200.fc20. Thu Feb 12 10:12 still running
reboot system boot 3.14.2-200.fc20. Thu Feb 12 10:12 still running
fredex pts/0 :0.0 Thu Feb 12 10:06 - 10:09 (00:03)
fredex pts/1 192.168.2.12 Thu Feb 12 00:12 - 03:26 (03:13)
fredex pts/0 192.168.2.12 Thu Feb 12 00:02 - 03:26 (03:23)
fredex :0 Thu Feb 5 09:14 - down (7+00:57)
reboot system boot 3.14.2-200.fc20. Thu Feb 5 09:14 - 10:11 (7+00:57)
reboot system boot 3.14.2-200.fc20. Thu Feb 5 09:14 - 10:11 (7+00:57)
fredex pts/0 :0.0 Thu Jan 29 18:42 - 18:50 (00:07)
fredex :0 Thu Jan 29 18:33 - down (6+14:39)
reboot system boot 3.14.2-200.fc20. Thu Jan 29 18:32 - 09:13 (6+14:40)
reboot system boot 3.14.2-200.fc20. Thu Jan 29 18:32 - 09:13 (6+14:40)
fredex pts/1 192.168.2.12 Thu Jan 29 18:16 - 18:31 (00:14)
fredex pts/1 192.168.2.12 Mon Dec 22 09:40 - 09:41 (00:00)
fredex pts/1 192.168.2.12 Wed Dec 10 18:11 - 18:17 (00:06)
fredex pts/0 :0.0 Wed Dec 10 18:09 - 18:31 (50+00:22)
fredex :0 Wed Dec 10 18:08 - down (50+00:22)
reboot system boot 3.14.2-200.fc20. Thu Dec 4 20:54 - 18:31 (55+21:37)
reboot system boot 3.14.2-200.fc20. Thu Dec 4 20:54 - 18:31 (55+21:37)
reboot system boot 3.14.2-200.fc20. Wed Nov 19 04:54 - 18:31 (71+13:37)
reboot system boot 3.14.2-200.fc20. Wed Nov 19 04:54 - 18:31 (71+13:37)
fredex pts/1 192.168.2.12 Thu Nov 6 22:13 - 19:34 (21:20)
fredex pts/0 192.168.2.12 Wed Nov 5 23:44 - 19:34 (1+19:49)
reboot system boot 3.14.2-200.fc20. Wed Nov 5 23:44 - 18:31 (84+18:47)
reboot system boot 3.14.2-200.fc20. Wed Nov 5 23:44 - 18:31 (84+18:47)
fredex pts/0 192.168.2.12 Wed Nov 5 23:38 - 23:43 (00:05)
reboot system boot 3.14.2-200.fc20. Wed Nov 5 23:38 - 23:43 (00:05)
reboot system boot 3.14.2-200.fc20. Wed Nov 5 23:38 - 23:43 (00:05)
fredex pts/1 192.168.2.12 Wed Nov 5 23:09 - 23:37 (00:27)
fredex pts/0 192.168.2.12 Wed Nov 5 23:08 - 23:37 (00:28)
reboot system boot 3.14.2-200.fc20. Wed Nov 5 23:08 - 23:37 (00:29)
reboot system boot 3.14.2-200.fc20. Wed Nov 5 23:08 - 23:37 (00:29)
fredex pts/1 192.168.2.12 Wed Nov 5 22:54 - 23:07 (00:12)
fredex pts/0 192.168.2.12 Wed Nov 5 22:39 - 23:07 (00:27)
Anybody got any ideas?
thanks!
--
---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us -----------------------------
The eyes of the Lord are everywhere,
keeping watch on the wicked and the good.
----------------------------- Proverbs 15:3 (niv) -----------------------------
9 years, 3 months
Yum update Vbox -
by Bob Goodwin
This does not seem much of a problem but I am curious as to why I'm
having this? It seems waiting a while for the kernel to update will
eventually fix things but do I somehow have the wrong version of
virtualbox installed?
Bob
[root@box10 bobg]# yum update
............ snip ......
Resolving Dependencies
--> Running transaction check
---> Package kmod-VirtualBox.x86_64 0:4.3.20-4.fc21.2 will be updated
---> Package kmod-VirtualBox.x86_64 0:4.3.20-4.fc21.3 will be an update
--> Processing Dependency: kmod-VirtualBox-3.18.6-200.fc21.x86_64 >=
4.3.20-4.fc21.3 for package: kmod-VirtualBox-4.3.20-4.fc21.3.x86_64
--> Running transaction check
---> Package kmod-VirtualBox-3.18.6-200.fc21.x86_64.x86_64
0:4.3.20-4.fc21.3 will be installed
--> Processing Dependency: kernel-uname-r = 3.18.6-200.fc21.x86_64 for
package: kmod-VirtualBox-3.18.6-200.fc21.x86_64-4.3.20-4.fc21.3.x86_64
--> Finished Dependency Resolution
Error: Package:
kmod-VirtualBox-3.18.6-200.fc21.x86_64-4.3.20-4.fc21.3.x86_64
(rpmfusion-free-updates)
Requires: kernel-uname-r = 3.18.6-200.fc21.x86_64
Installed: kernel-core-3.17.8-300.fc21.x86_64 (@updates)
kernel-uname-r = 3.17.8-300.fc21.x86_64
......... snip .......
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
--
http://www.qrz.com/db/W2BOD
box10 Fedora-21/64bit Linux/XFCE
9 years, 3 months
Updates available?
by Temlakos
Everyone:
When is the last time anyone got any updates?
Since packagekit quit working for me (and yes, I have a bug on file),
I've been using "yum -y update" every day. For two days straight, it's
done nothing: "No packages marked for update." Now is that true? Or am I
getting yet another false negative?
Temlakos
9 years, 3 months
