12.04 no Web and very slow

**dgermann** · July 18th, 2014

Friends--

About 3 days ago, one of my computers became excruciatingly slow, and lost contact with the Web. Can you help me trouble shoot this?

Symptoms:

Production environment, one of 3 active desktops; there is also a server and a machine dedicated to running backups. All are Ubuntu 12.04, except one desktop is WinXP.

Network connections are cifs running Samba.

Cannot ping yahoo.com nor google.com, nor apt-get: it does not connect to any repository.

Cannot connect using rdesktop to 192.168.0.111, the Win XP box.

Can connect to this computer via ssh.

No other machine on this network is experiencing similar problems. This network has been running with no problems since 12.04.1 came out, about 2 years.

(I have noticed other times when an Ubuntu machine is disconnected from the network, it often runs slow.)

What I have tried so far:

top: nothing unusual found.

/var/log: large files in syslog (1.9 M), kern.log (1.9 M).

plugged another computer into the cable this machine used and it had no problems with Web connection, speed was good.

ran clamscan, report:

----------- SCAN SUMMARY -----------
Known viruses: 3499748
Engine version: 0.98.1
Scanned directories: 52103
Scanned files: 214349
Infected files: 0
Data scanned: 8434.30 MB
Data read: 8988.95 MB (ratio 0.94:1)
Time: 2408.951 sec (40 m 8 s)
doug@doug2:~$

Code:

doug@doug2:~$ ping yahoo.com
ping: unknown host yahoo.com
doug@doug2:~$ sudo ifdown -a
doug@doug2:~$ sudo ifup -a
doug@doug2:~$ ping yahoo.com
ping: unknown host yahoo.com
doug@doug2:~$ sudo ufw status
Status: active

To                         Action      From
--                         ------      ----
22/tcp                     ALLOW       192.168.0.0/24
3551/tcp                   ALLOW       192.168.0.0/24
1194/tcp                   ALLOW       192.168.0.0/24

So what would you try next?

Thanks!

**TheFu** · July 18th, 2014

Reset/fix the DNS settings after you verify that you can ping internet IP addresses like 8.8.8.8. IF you can ping that means the network is up and just DNS is not working. IF you cannot ping the internet by IP address, try to ping the router by IP - if that doesn't work, look for a HW or driver failure on the network card. But since other machines can connect to the problem machine, it is probably just the DNS issue.

**dgermann** · July 18th, 2014

TheFu--

Many thanks for helping me!

Here's what happened:

Code:

doug@doug2:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
324 packets transmitted, 0 received, 100% packet loss, time 324764ms

doug@doug2:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
24 packets transmitted, 0 received, 100% packet loss, time 22999ms

So that brings us to the hardware/driver step. I am out of my league here. What to test and how? I can take the box to my computer guru, a half hour away, but would like to test the driver first. Not even sure how to figure which driver to replace or test?

Suggestions?

Thanks!

**TheFu** · July 19th, 2014

Ouch - that sucks.
Please post the output from

sudo lshw -C network
ifconfig
route

**dgermann** · July 19th, 2014

@ TheFu--

Thanks for your sympathy! <grin>

Code:

doug@doug2:~$  sudo lshw -C network
[sudo] password for doug: 
  *-network               
       description: Ethernet interface
       product: 82566DC-2 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: eth0
       version: 02
       serial: 00:19:d1:ec:0e:27
       size: 100Mbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=1.5.1-k duplex=full firmware=1.3-0 ip=192.168.0.7 latency=0 link=yes multicast=yes port=twisted pair speed=100Mbit/s
       resources: irq:46 memory:e2200000-e221ffff memory:e2224000-e2224fff ioport:20e0(size=32)
doug@doug2:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr [BLANKED]  
          inet addr:192.168.0.7  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::219:d1ff:feec:e27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:39804 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30325 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:29609618 (29.6 MB)  TX bytes:3427007 (3.4 MB)
          Interrupt:20 Memory:e2200000-e2220000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:3262 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3262 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:213298 (213.2 KB)  TX bytes:213298 (213.2 KB)

doug@doug2:~$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
192.168.0.0     *               255.255.255.0   U     1      0        0 eth0
doug@doug2:~$

OK, so what's that tell us?

Thanks, TheFu!

**TheFu** · July 19th, 2014

So here's what all this stuff says.
* PC IP is 192.168.0.7
* PC NIC is using the e1000 driver - that's the most standard GigE NIC there is
* Router is 10/100 base-tx, not GigE.
* Router IP is 192.168.0.1, but the machine can't ping it? But there aren't any errors on the line either.

Are you sure this is the correct PC with the problem?

Disable the firewall - sudo iptables -F and try everything again.

**dgermann** · July 19th, 2014

@TheFu--

Thanks!

Twice I ran sudo iptables -F and twice it locked up the computer. My ssh session stalled, I tried another and it timed out. Rebooted machine each time.

At the console of the machine, I watched: it sat for probably a minute before it came up with the intel screen, then it booted up Ubuntu 12.04 at what seemed normal speed. After login, it was slow coming up, but not intolerably so.

Then I tried ctrl-alt-t and nothing happened. I noticed the network icon in the top bar (it is running gnome) had a red x on it. But nothing seemed to be working. I did notice a lot of disk activity going on. ssh to this machine and did sudo ufw disable, and then tried ping again. Still no go for either address:

Code:

doug@doug2:~$ sudo ufw disable
Firewall stopped and disabled on system startup
doug@doug2:~$ ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
^C
--- 192.168.0.1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3022ms

doug@doug2:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3022ms

Yes this is the correct machine.

I may not be seeing what you are seeing but the unaccounted disk activity and the long wait at bootup before the intel splash screen came up are suggesting to me a hardware issue, perhaps a hard disk issue, or maybe as you suggested a network card issue.

What do you see, TheFu?

Thanks ever so much.

**TheFu** · July 19th, 2014

If you can't ping the router the issue is between the machine and the router. Tried a diff cable, diff router port? The card and driver seems to be working. Are you certain the network settings are correct? What are the settings on the other machines
* ip
* netmask
* gateway

Can you swap in another NIC?

**dgermann** · July 19th, 2014

TheFu--

Thanks for continuing to help me.

1. Different cable: I tried another machine on this cable, it worked fine. That seems to narrow it to the machine, yes?

2. Network settings: should be correct; this machine was working fine until a couple days ago, and the person who uses it would not have any idea that there were even network settings to change.

3. Another machine networking settings:

Code:

doug@fire:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr [BLANKED]
          inet addr:192.168.0.3  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::ea40:f2ff:feed:2c25/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1823476 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2795152 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:533328750 (533.3 MB)  TX bytes:3371167795 (3.3 GB)
          Interrupt:20 Memory:f7200000-f7220000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:7579 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7579 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:805175 (805.1 KB)  TX bytes:805175 (805.1 KB)

doug@fire:~$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
192.168.0.0     *               255.255.255.0   U     1      0        0 eth0
doug@fire:~$

4. Reassign ipaddress:

Code:

doug@doug2:~$ sudo ifconfig eth0 192.168.0.155 netmask 255.255.255.0
[sudo] password for doug: 

[had to ssh login again]

doug@doug2:~$ ping 192.168.0.201
PING 192.168.0.201 (192.168.0.201) 56(84) bytes of data.
64 bytes from 192.168.0.201: icmp_req=1 ttl=64 time=0.530 ms
64 bytes from 192.168.0.201: icmp_req=2 ttl=64 time=0.250 ms
64 bytes from 192.168.0.201: icmp_req=3 ttl=64 time=0.290 ms
^C
--- 192.168.0.201 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.250/0.356/0.530/0.125 ms
doug@doug2:~$ ping 8.8.8.8
connect: Network is unreachable
doug@doug2:~$ ifconfig eth0
eth0      Link encap:Ethernet  HWaddr [BLANKED]
          inet addr:192.168.0.155  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::219:d1ff:feec:e27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:11670 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12840 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2503845 (2.5 MB)  TX bytes:1486474 (1.4 MB)
          Interrupt:20 Memory:e2200000-e2220000

5. Have tried to login to my router from another machine, but the connection timed out. I will now try to reboot the router and report back, if I am able after that.

Thanks!

**dgermann** · July 19th, 2014

OK, rebooted the router, and was now able to access that.

Was able to ping the router from the problem machine, but not 8.8.8.8, and a sudo apt-get update was not able to connect to any repository.

Machine did seem to respond faster. After rebooting, back to slowness. And these results:

Code:

doug@doug2:~$ ping 192.168.0.201
PING 192.168.0.201 (192.168.0.201) 56(84) bytes of data.
^C
--- 192.168.0.201 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 5999ms

doug@doug2:~$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2016ms

doug@doug2:~$ route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.0.1     0.0.0.0         UG    0      0        0 eth0
link-local      *               255.255.0.0     U     1000   0        0 eth0
192.168.0.0     *               255.255.255.0   U     1      0        0 eth0
doug@doug2:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr [BLANKED]
          inet addr:192.168.0.7  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::219:d1ff:feec:e27/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:230 errors:0 dropped:0 overruns:0 frame:0
          TX packets:396 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:39631 (39.6 KB)  TX bytes:43711 (43.7 KB)
          Interrupt:20 Memory:e2200000-e2220000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:53 errors:0 dropped:0 overruns:0 frame:0
          TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:3341 (3.3 KB)  TX bytes:3341 (3.3 KB)

Router is a tplink TL-WR1043ND. All connections referred to so far are wired. Don't think anything is connecting wireless at the moment.

What's next, guru? <grin>

Thread: 12.04 no Web and very slow

Thread Tools

Display

12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Re: 12.04 no Web and very slow

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions