• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: apt-get fails  (Read 2677 times)
Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« on: December 20, 2010, 06:29:11 AM »

When trying to install NTP, I didn't succeed and the system recommended running apt-get update. So that's what I did:

sheevaplug-debian:~# apt-get update
Err http://10.82.108.51 binary/ Release.gpg
  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed out)
Err http://http.us.debian.org stable Release.gpg
  Temporary failure resolving 'http.us.debian.org'
Err http://www.backports.org lenny-backports Release.gpg
  Temporary failure resolving 'www.backports.org'

.......... and so on.......

W: Failed to fetch http://10.82.108.51/kedars/sheevaplug_wifi/builds/packages/binary/Packages  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed out)
W: Some index files failed to download, they have been ignored, or old ones used instead.
W: You may want to run apt-get update to correct these problems
sheevaplug-debian:~#


OK, if apt-get update fails, the systen advises to run apt-get update.....

I thought that may be the system has no internet access, so I checked /etc/network/interfaces:

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
     address 192.168.1.87
     netmask 255.255.255.0
     gateway 192.168.1.254
     dns-nameservers 195.121.1.34 195.121.1.66


These addresses are correct, I double checked that.

Any help would be most welcome...
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

two9er
Jr. Member
**

Karma: 10
Posts: 51


View Profile
« Reply #1 on: December 20, 2010, 08:05:21 AM »

You've got networking issues.
Please post the copied output from the following commands:

# ifconfig

# cat /etc/resolv.conf

# route

# ping 192.168.1.254

# dig yahoo.com

HTH, Jim
« Last Edit: December 20, 2010, 08:07:07 AM by two9er » Logged

Just plugging away! GuruPlug Server Plus, 1TB esata hd, 8GB microSD (rfs)

Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« Reply #2 on: December 20, 2010, 09:12:48 AM »

Thanks Jim, this is the result:

sheevaplug-debian:~# ifconfig
eth0      Link encap:Ethernet  HWaddr f0:ad:4e:ff:12:04
          inet addr:192.168.1.87  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::f2ad:4eff:feff:1204/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:76945 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12743 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5360480 (5.1 MiB)  TX bytes:1154890 (1.1 MiB)
          Interrupt:11

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:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:280 (280.0 B)  TX bytes:280 (280.0 B)

uap0      Link encap:Ethernet  HWaddr 00:24:23:21:94:af
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

sheevaplug-debian:~# cat /etc/resolv.conf
nameserver 192.168.0.1

sheevaplug-debian:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 eth0
192.168.1.0     *               255.255.255.0   U     0      0        0 uap0

sheevaplug-debian:~# ping 192.168.1.254
PING 192.168.1.254 (192.168.1.254) 56(84) bytes of data.
64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=1.37 ms
64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.653 ms
64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.792 ms
64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=0.704 ms
...etc...

sheevaplug-debian:~# dig yahoo.com
-bash: dig: command not found
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

two9er
Jr. Member
**

Karma: 10
Posts: 51


View Profile
« Reply #3 on: December 20, 2010, 10:06:07 AM »

The nameserver in /etc/resolv.conf is incorrect, and according to man interfaces, dns-nameservers is not an allowed entry.

Quote
The static Method
       This  method  may be used to define ethernet interfaces with statically
       allocated IPv4 addresses.

       Options

              address address
                     Address (dotted quad) required

              netmask netmask
                     Netmask (dotted quad) required

              broadcast broadcast_address
                     Broadcast address (dotted quad)

              network network_address
                     Network address (dotted quad) required for 2.0.x kernels

              metric metric
                     Routing metric for default gateway (integer)

              gateway address
                     Default gateway (dotted quad)

              pointopoint address
                     Address of  other  end  point  (dotted  quad).  Note  the
                     spelling of "point-to".

              media type
                     Medium type, driver dependent

              hwaddress class address
                     Hardware  Address. class is one of ether, ax25, ARCnet or
                     netrom. address is dependent on the above choice.

              mtu size
                     MTU size

Instead of talking you through the joys of the vi editor, it may be just as easy overwrite /etc/resolv.conf with the proper entry:

# echo "nameserver 195.121.1.34" > /etc/resolv.conf && echo "nameserver 195.121.1.66" >> /etc/resolv.conf

Sorry about the dig command, it is not installed.

HTH, Jim
Logged

Just plugging away! GuruPlug Server Plus, 1TB esata hd, 8GB microSD (rfs)

Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« Reply #4 on: December 20, 2010, 11:53:19 AM »

Hi Jim,

Don't worry, VI is acceptable as an editor but my Debian package also provides NANO.

Then, I found out I had made a stupid mistake; the nameservers are not on 192 but 195

So, it looks like this now:

sheevaplug-debian:~# cat /etc/resolv.conf
nameserver 195.121.1.34
nameserver 195.121.1.66


sheevaplug-debian:~# ping 195.121.1.34
PING 195.121.1.34 (195.121.1.34) 56(84) bytes of data.
64 bytes from 195.121.1.34: icmp_seq=1 ttl=123 time=19.3 ms
64 bytes from 195.121.1.34: icmp_seq=2 ttl=123 time=19.6 ms
64 bytes from 195.121.1.34: icmp_seq=3 ttl=123 time=19.2 ms
^C

sheevaplug-debian:~# ping 195.121.1.66
PING 195.121.1.66 (195.121.1.66) 56(84) bytes of data.
64 bytes from 195.121.1.66: icmp_seq=1 ttl=123 time=20.7 ms
64 bytes from 195.121.1.66: icmp_seq=2 ttl=123 time=19.3 ms
^C

but the results for apt-get update are still the same:
sheevaplug-debian:~# apt-get update
Ign http://10.82.108.51 binary/ Release.gpg
Ign http://10.82.108.51 binary/ Translation-en_US
Ign http://10.82.108.51 binary/ Release
Ign http://10.82.108.51 binary/ Packages/DiffIndex
Ign http://10.82.108.51 binary/ Packages
Err http://10.82.108.51 binary/ Packages
  302 Found
11% [Connecting to ftp.us.debian.org] [Connecting to http.us.debian.org] [Connecting to seErr http://security.debian.org lenny/updates Release.gpg
  Temporary failure resolving 'security.debian.org'

....etc....

W: Failed to fetch http://10.82.108.51/kedars/sheevaplug_wifi/builds/packages/binary/Packages  302 Found
W: Some index files failed to download, they have been ignored, or old ones used instead.
W: You may want to run apt-get update to correct these problems

Thanks, Peter
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« Reply #5 on: December 20, 2010, 12:09:28 PM »

Hold your horses, the third attempt is producing results now.
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

Manaslu
Newbie
*

Karma: 0
Posts: 13


View Profile
« Reply #6 on: December 20, 2010, 12:24:27 PM »

It works, although the download doesn't go flawlessly. These are the error messages I get:
Err http://10.82.108.51 binary/ Release.gpg
  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed out)
Err http://10.82.108.51 binary/ Translation-en_US
  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed out)
Ign http://10.82.108.51 binary/ Release
Ign http://10.82.108.51 binary/ Packages/DiffIndex
Ign http://10.82.108.51 binary/ Packages
Err http://10.82.108.51 binary/ Packages
  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed out)
W: Failed to fetch http://10.82.108.51/kedars/sheevaplug_wifi/builds/packages/binary/Relea se.gpg  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed out)

W: Failed to fetch http://10.82.108.51/kedars/sheevaplug_wifi/builds/packages/binary/en_US .gz  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed out)

W: Failed to fetch http://10.82.108.51/kedars/sheevaplug_wifi/builds/packages/binary/Packages  Could not connect to 10.82.108.51:80 (10.82.108.51). - connect (110 Connection timed  out)

E: Some index files failed to download, they have been ignored, or old ones used instead.
Logged

2 x NSLU2 + Slimserver + rsync. 2 x USB 500GB. Guruplug Standard

two9er
Jr. Member
**

Karma: 10
Posts: 51


View Profile
« Reply #7 on: December 20, 2010, 05:06:27 PM »

I can't connect to 10.82.108.51 either. The server may be down or the ip address is not correct.

HTH, Jim
Logged

Just plugging away! GuruPlug Server Plus, 1TB esata hd, 8GB microSD (rfs)

Pages: [1]
Print
Jump to: