CPU/Memory
by Patrick Dupre
Hello,
I have 2 machines running fedora 20, one from 2007 with a dual processor
and 3 Go, and a recent one (2013) with a quad processor an 8 Go.
But it is a lot more convenient to use the old machine!!!
The recent one is always busy, 4 processors running
53.1 55.9 /usr/bin/python -Es /usr/sbin/setroublesootd -f
and the memory becomes full quickly requiring swapping!!
8 Go for the OS and firefox! Something is wrong.
Should I kill setroublesootd?
What is wrong? I cannot see.
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, 9 months
wlan0 not working - F20 arm
by Robert Moskowitz
I have this old Trendnet usb 802.11bg adapter plugged into my server.
It is not showing in Network manager (see prior message) so I am trying
via command lines:
# ifconfig wlan0 up
# iwlist wlan0 scan
wlan0 No scan results
Don't tell me that, my notebook is connected wirelessly and I can see
b/g support in the APs here.
and
# ifconfig wlan0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:14:d1:4c:0f:79 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
9 years, 9 months
NetworkManager not running? F20 arm xfce
by Robert Moskowitz
In my vnc connection to my server, the xfce system bar's network manager
tells me:
Networking disabled (when I place the mouse over the network icon)
Network Manager not running (when I click on the network icon, and this
text is grey)
Yet in my ssh session to the server:
# systemctl status NetworkManager.service
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Fri 2010-01-01 00:00:23 EST; 4 years 6
months ago
Main PID: 319 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─319 /usr/sbin/NetworkManager --no-daemon
Jan 01 00:01:15 cb2.htt-consult.com NetworkManager[319]: DHCPDISCOVER on
eth0 to 255.255.255.255 port 6...f2)
Jan 01 00:01:23 cb2.htt-consult.com dhclient[853]: DHCPDISCOVER on eth0
to 255.255.255.255 port 67 inte...f2)
Jan 01 00:01:23 cb2.htt-consult.com NetworkManager[319]: DHCPDISCOVER on
eth0 to 255.255.255.255 port 6...f2)
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: <warn> (eth0):
DHCPv4 request timed out.
Jan 01 00:01:24 cb2.htt-consult.com dhclient[853]: Received signal 15,
initiating shutdown.
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: Received signal
15, initiating shutdown.
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: <info> (eth0):
canceled DHCP transaction, DHCP...853
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: <info>
Activation (eth0) Stage 4 of 5 (IPv4 Co......
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: <info>
Activation (eth0) Stage 4 of 5 (IPv4 Co......
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: <info>
Activation (eth0) Stage 4 of 5 (IPv4 Co...te.
Hint: Some lines were ellipsized, use -l to show in full.
and
# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::c4:3ff:fe82:c153 prefixlen 64 scopeid 0x20<link>
ether 02:c4:03:82:c1:53 txqueuelen 1000 (Ethernet)
RX packets 3339 bytes 326670 (319.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3469 bytes 1641253 (1.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 87 base 0x6000
eth0:avahi: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 169.254.7.244 netmask 255.255.0.0 broadcast 169.254.255.255
ether 02:c4:03:82:c1:53 txqueuelen 1000 (Ethernet)
device interrupt 87 base 0x6000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 790 bytes 70412 (68.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 790 bytes 70412 (68.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:14:d1:4c:0f:79 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
And note wlan0 which is not showing up in network manager...
Note that the only network connection is direct cable to my notebook.
Separate message on wlan questions
9 years, 9 months
vncserver not starting today
by Robert Moskowitz
OK. New day, new testing. I can get IPv4 setup quickly and routing
right. Yeah me (with a little help from my friends I got by)!
So I go to start vncserver where I was up to yesterday where I got the
display wrong and get:
# systemctl start vncserver@:3.service
Job for vncserver@:3.service failed. See 'systemctl status
vncserver@:3.service' and 'journalctl -xn' for details.
# systemctl -l status vncserver@:3.service
vncserver@:3.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver@:3.service; enabled)
Active: failed (Result: exit-code) since Fri 2010-01-01 00:28:15
EST; 35s ago
Process: 952 ExecStart=/sbin/runuser -l rgm -c /usr/bin/vncserver %i
(code=exited, status=2)
Process: 949 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i >
/dev/null 2>&1 || : (code=exited, status=0/SUCCESS)
Jan 01 00:28:15 cb2.htt-consult.com systemd[1]: vncserver@:3.service:
control process exited, code=exited status=2
Jan 01 00:28:15 cb2.htt-consult.com systemd[1]: Failed to start Remote
desktop service (VNC).
Jan 01 00:28:15 cb2.htt-consult.com systemd[1]: Unit
vncserver@:3.service entered failed state.
So now what? It worked yesterday....
I can't find anything I did yesterday that I am not doing today.
9 years, 9 months
Problems with Fedora 20
by Roger
Couple of things seem to have gone awry.
I think Ubuntu update to 14.04 has messed around with Fedora 20 grub
boot because booting now takes for ever and defaults to Ctrl D to
Continue or root password for maintenance, then takes 30-50 seconds to boot.
2nd, With the latest updates and kernel-3.15.5-200.fc20.x86_64
something seems wrong. The machine used to be quite fast but now is very
slow.
Any processes like opening and deleting emails, screen refresh,
opening or closing files is very slow and the hard drive is working
overtime with every mouse click or key press.
CPUs are running at 20-50%, memory runs at 85%, temp directory is
running overtime.
Whereas performing the same in ubuntu 14.04, 386 memory runs around 35%,
cpu's 20-50%, no hard drive temp used at all, and emails open and delete
immediately.
I have cleaned repositories, removed unused files and software in both
setups, run sudo yum autoclean, sudo yum clean packages. top shows
nothing untoward.
I am running 3.15.4-200.fc20.x86_64 for this email and the system seems
to be better but the hard drive works overtime with each change.
kernel-3.14.8-200.fc20.x86_6 produces inode errors and boot fails.
There is a command to rebuild grub boot but I don't remember the
details, can someone please point me to how this should be done.
What should I look for as to why the system is not operating as before.
Help much appreciated
thanks
Roger
9 years, 9 months
Figuring out a headless server's zeroconf addr
by Robert Moskowitz
I have a headless system that I cannot connect to. So I was thinking to
put a direct connection to it and my notebook. Both ethernets would use
the zeroconf (169.254.0.0/16) addresses. I could then use fping
fping -g 169.254.0.0/16
And SHOULD be able to get its address, and then SSH into the box.
Any other thoughts? I can't get to the box to recable it and reboot it
(as that is the only way I can figure out for it to readdress eth0)
until this evening.
9 years, 9 months
Memory
by Patrick Dupre
Hello,
Is it normal that /usr/bin/python -Es /usr/sbin/setroublehootd -f (2 shells)
consumes 8 GO of RAM (i.e. 49% and 46% of the total)?
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, 9 months
NFS Performance Woes
by Ian Chapman
Hi,
I've been unable to track down an extremely annoying performance issue
with NFS. My home server has several exports shared over NFS4. The
exports are all secured using Kerberos except one, which can be mounted
using the traditional sys security model.
The problem is that write performance stalls at 48k/sec (or according to
nfsiostat 4k/sec) despite being on a 1Gbit network and once this occurs,
nothing I do seems to fix it. The only thing that does, is rebooting the
client machine. This has been occurring for a year or so now but is
happening so regularly now, it's driving me nuts! :-)
I'm fairly sure it's a client side issue, because rebooting the client
allows normal transfer speeds once again. If I only reboot the server it
makes no difference. My client is F19, the server is F20. After
rebooting the client, write transfers can be fine for a day or so and
then all of a sudden it hangs around 48k/sec again.
Restarting all the NFS daemons on the client makes no difference,
including the associated RPC daemons. The NFS exports are mounted via
autofs, but manually mounting makes no difference either.
When I'm experiencing slow writes to the server of 48k/sec, NFS reads
are still in the region of 100MB/sec. Using scp or even copying files to
the server via CIFS are well within the range of a 1Gbit network.
Nfsstat, wireshark and the system logs do not show anything which
screams there's a problem.
The network card in the client machine and the server shows no
collisions, dropped packets, frame overruns etc.
I've tested with the export that isn't using Kerberos and still have the
same issue. Messing with the rsize, wsize, async, sync parameters makes
no difference either.
The server has 32GB RAM, the client 16GB.
For all intents and purpose it looks like its working as it should, it's
just painfully slow.
Any NFS gurus out there, that can tell me what I'm doing wrong?
--
Ian Chapman.
9 years, 9 months
Re: NFS Performance Woes
by Peter Skensved
>
>
> On 07/21/14 19:59, Ian Chapman wrote:
> > Nfsstat, wireshark and the system logs do not show anything which screams there's a problem.
> >
> > The network card in the client machine and the server shows no collisions, dropped packets, frame overruns etc.
> >
> > I've tested with the export that isn't using Kerberos and still have the
> > same issue. Messing with the rsize, wsize, async, sync parameters makes no difference either.
> >
> > The server has 32GB RAM, the client 16GB.
> >
> > For all intents and purpose it looks like its working as it should, it's just painfully slow.
> >
> > Any NFS gurus out there, that can tell me what I'm doing wrong?
>
> I've been using NFSv4 extensively for several years and I've not had an issue that you
> describe where everything is fine and then suddenly performance goes to hell in a hand basket.
>
> It sounds as if you only have 2 systems to work with? No, tiebreaker so to speak?
>
> Have you considered running a VM on your client system to see if it is affected in the same way?
>
DNS problems can do it . Are your /etc/resolv.conf files correct ?
You could try running your own nameserver ( dnsmasq ) if the upstream
one is too slow or too busy.
peter
9 years, 9 months
