Fedora 8: X/Nautilus eating CPU
by wwp
Hello all,
now that my Fedora 8 is fully set up, I notice periodical short
hangs of the Desktop, making its use quite uncomfortable. `top` tells me
that the X and Nautilus processes are eating up to 30% of CPU every
15-20sec approximately (I can hear some disk activity as well).
Sensors applets are configured to poll on a longer period basis so it's
probably not them. No cron activity has been set. Anyway, I was running
the same applets with my Fedora Core 5 and GNOME and never encountered
such behaviour before.
For the record, nautilus-action is installed and there are few mounts
(USB disks) visible onto the Desktop. I've tried closing all apps (but
GNOME Desktop) and this still happens.
Anybody has this too? Or any hint?
Regards,
--
wwp
15 years, 11 months
ssh and port 22 problem, cont.
by Gerhard Magnus
Greetings!
I've made some progress on troubleshooting this "ssh & port 22 problem".
Here was my original post:
When I try to connect from a remote machine to my one at home
using ssh I get the error message "ssh: connect to host 64.146.133.1 port
22: Connection refused" -- but using ssh in the outgoing direction (i.e.
from home to the remote location) works fine.
Here's what's happened since:
I have two machines (PuteA and PuteB) sharing an ActionTec DSL modem. The IP
I was using was that of my "Gateway" ISP (64.146.133.1) -- an error. But
when I used the correct, static IP address of the ActionTec
(64.146.133.52) I got this message:
ssh: connect to host 64.146.133.52 port22: Connection refused
I thought I had port forwarding (for port 22) set correctly on the modem. For
troubleshooting, my ISP advised me to run "tcpdump -n host 192.168.0.2" on
PuteA, where 192.168.0.2 is the "internal" IP of PuteA. Then I logged on
to the remote location from PuteB and tried to ssh from there to PuteA
using the static IP address. The ssh from the remote location timed out
with the same "port 22: connection refused" message. The tcpdump on Pute
A gave this message:
> tcpdump: listening on eth0
> 17:27:33.662753 arp who-has 192.168.0.2 tell 192.168.0.1
where 182.168.0.1 is the "internal" IP of the modem. (Sorry if I have
this terminology wrong.)
My ISP says the problem is the firewall on PuteA and that he doesn't do linux
firewalls.
Here are my replies to the people who responded to my first post:
(1) "Do you have the firewall configured to deny incoming packets to port
22?"
How do I check this?
(2) "You need to check that sshd is running on your system."
Yes. I comes up with each boot. Also "service sshd status" gives
"sshd (pid 787) is running".
(3) "sshd uses /etc/hosts.allow and /etc/hosts.deny. Check that they are
configured to allow your remote machine in."
Both files have only commented lines.
(4) "Also, if your /etc/ssh/sshd_config file has VerifyReverseMapping
turned on, you will get kicked out if your remote address does not work
with a reverse dns lookup."
There's a "VerifyReverseMapping no" line in the file but it's been commented
out.
(5) "Just to be sure: when you are at home machine, try 'ssh localhost'.
If this works, you probably need to check your firewall."
It seems to work -- I ssh to the machine itself.
(6) "This is common on every system I have ever loaded with FC2. Your
iptables are blocking the connection. You can do one of the following:
iptables -A INPUT -m tcp -p tcp --dport 22 - j ACCEPT"
I tried this. The ssh to PuteA from the remote location still times out.
(7) "Oh yes I also took out the REDHAT firewall entrie as I dont have a
clue as to how to work with it."
I've fiddled endlessly with this "system tool" at each of the three levels
of security as well as using the "customize" option to set eth0 as a
trusted device and to allow incoming ssh. It doesn't show the settings
that actually exist.
(8) "If your fedora box is connected directly to a DSL modem, you should
be able to find your IP address by running ifconfig from the command
line and looking for 'inet addr:' (probably under 'eth0')."
eth0 Link encap:Ethernet HWaddr 00:40:05:81:60:8E
inet addr:192.168.0.4 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2184 errors:0 dropped:0 overruns:0 frame:0
TX packets:2005 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1122075 (1.0 Mb) TX bytes:190214 (185.7 Kb)
Interrupt:5 Base address:0x3000
Could this be the problem -- the "inet addr" of 192.168.0.4? As far as I
can tell, the modem is 192.168.0.1, PuteA is 192.168.0.2, and PuteB is
192.168.0.3. I haven't set anything as 192.168.0.4.
(9) "nmap 64.146.133.52"
(The 1598 ports scanned but not shown below are in state: closed)
Port State Service
23/tcp open telnet
53/tcp open domain
80/tcp open http
Shouldn't ssh be here? And what's telnet doing open? The books have me
scared to death of this... hackers, crackers, script kiddies, etc.
Thanks for the help!
Jerry Magnus
15 years, 12 months
Yum repair
by Timothy Murphy
I upgraded FC-6 to F-7 on an Athlon64 machine,
and the process hung several (3 I think) times during installation.
Each time I re-started the machine,
the number of packages was greatly reduced: 950 ... 400 ... 50.
The system works fine,
but it is pretty clear all the packages were not properly installed.
Eg when I ran "yum update" after the installation
only 30 or so packages were downloaded,
while on other systems the number was 300-400.
Is there any way of checking that everything has been downloaded?
Or is there even a command like "yum --force install"
to force a re-installation of a particular package?
--
Timothy Murphy
e-mail (<80k only): tim /at/ birdsnest.maths.tcd.ie
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland
16 years
keyspan usb serial and fc6 help
by matt pieklik
I had my keyspan USB serial adapter 19HS working with FC5, but now
that I have upgraded to FC6 it is no longer fully functional. It is
detected, and I get one way communication through it when I use
minicom. I am able to send but not receive, I determined this by
connecting two machine via serial.
Is this a problem with the USB serial adapter, or do I not have the
associated serial port configured correctly?
Here is the output from the startup:
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
usbcore: registered new interface driver libusual
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usb usb1: configuration #1 chosen from 1 choice
usb usb2: configuration #1 chosen from 1 choice
usb usb3: configuration #1 chosen from 1 choice
usb usb4: configuration #1 chosen from 1 choice
usb 2-2: new full speed USB device using uhci_hcd and address 3
usb 2-2: configuration #1 chosen from 2 choices
SELinux: initialized (dev usbfs, type usbfs), uses genfs_contexts
usbcore: registered new interface driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new interface driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan - (without firmware)
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan 1 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan 2 port adapter
drivers/usb/serial/usb-serial.c: USB Serial support registered for
Keyspan 4 port adapter
usb 2-2: Keyspan 1 port adapter converter now attached to ttyUSB0
usbcore: registered new interface driver keyspan
drivers/usb/serial/keyspan.c: v1.1.4:Keyspan USB to Serial Converter Driver
Thanks for any help.
Matt
16 years
/tmp running out of space
by Anne Wilson
/tmp is filling up rapidly. I'm guessing that it would be safe enough to
delete everything dated previous to the last bootup. Am I right?
Anne
16 years, 1 month
iptables
by Strong
I try to make possible for my guest (qemu) OS to get Internet access
but I get on it:
$ ping some_Internet_ip
>From 192.168.0.1 Destination host prohibited
Guest has ip 192.168.0.3, host - 192.168.0.1 and ppp0.
My host iptables file:
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Firewall-1-INPUT - [0:0]
-A INPUT -j RH-Firewall-1-INPUT
-A RH-Firewall-1-INPUT -i lo -j ACCEPT
-A RH-Firewall-1-INPUT -p icmp --icmp-type any -j ACCEPT
-A RH-Firewall-1-INPUT -p 50 -j ACCEPT
-A RH-Firewall-1-INPUT -p 51 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp --dport 5353 -d 224.0.0.251 -j ACCEPT
-A RH-Firewall-1-INPUT -p udp -m udp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -p tcp -m tcp --dport 631 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
-A RH-Firewall-1-INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 192.168.0.3 -i ppp0 -j ACCEPT
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
What is wrong?
16 years, 1 month