Page 2 of 5 FirstFirst 1234 ... LastLast
Results 11 to 20 of 47

Thread: apt-get has the problems to resolve address

  1. #11
    Join Date
    Jul 2009
    Location
    #ubuntu
    Beans
    139
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: apt-get has the problems to resolve address

    Actually, Medibuntu is down AGAIN, it's serverside on this one. It was down just a few weeks ago. I wonder what's going on over there?

    E: It's back up now.

  2. #12
    Join Date
    Jul 2009
    Location
    #ubuntu
    Beans
    139
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: apt-get has the problems to resolve address

    NEWS: I garbage picked a computer and put Xubuntu 10.04 on it. Xubuntu 10.04 does NOT seem to have this problem, all servers resolve after repeated attempts to reproduce. This means that whatever is happening with apt-get update is Ubuntu-specific.

  3. #13
    Join Date
    Aug 2008
    Beans
    4

    Re: apt-get has the problems to resolve address

    Thank you Gone fishing! This solved my problem.

    I think the problem occurs when 1. we are behind a proxy server, *and* 2. we specify the proxy information in the environment variable (http_proxy, ftp_proxy etc.). This is because, when we use sudo, it is not using the current user's environment (completely). So, the exported variables are not available in the "sudo" environment.

    The ways to solve this,
    1. use "sudo -E apt-get update". (preserves the current environment).
    (OR)
    2. export the variables in /root/.profile, then "sudo -i apt-get update".
    (OR)
    3. do a "sudo su -", then export the proxy information to the environment and do "apt-get update".

    Vignesh
    Last edited by r_vigneswaran; May 3rd, 2010 at 07:22 AM.

  4. #14
    Join Date
    Jul 2009
    Location
    #ubuntu
    Beans
    139
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: apt-get has the problems to resolve address

    I do not use a proxy here.

    Code:
    sudo -i apt-get update
    OR

    Code:
    sudo su
    AND
    apt-get update
    doesn't work for me.

    So this still applies.

    The only thing between me and the Internet is my 2wire router, which didn't cause any apt-get update related problems in any other Ubuntu release.

  5. #15
    Join Date
    Aug 2008
    Beans
    4

    Re: apt-get has the problems to resolve address

    Oh... Sorry, ThatBum. Actually, I intend to reply "ravi.xolve" and "GoneFishing". I have no clue about your problem .

  6. #16
    Join Date
    Jun 2007
    Location
    China
    Beans
    995
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: apt-get has the problems to resolve address

    The problem wasn't mediubuntu being down - that was another small problem and so I change to this mirror

    deb http://mirrors.ucr.ac.cr/medibuntu/ lucid free non-free
    deb-src http://mirrors.ucr.ac.cr/medibuntu/ lucid free non-free

    I note that UCT also has an RSA mirror

    deb ftp://ftp.leg.uct.ac.za/pub/linux/medibuntu/ lucid free non-free
    deb-src ftp://ftp.leg.uct.ac.za/pub/linux/medibuntu/ lucid free non-free

    r_vigneswaran I don't think the specifying variables is it as I just use 192.168.4.1:8024 for all protocols

    Thatbum I think your problem is quite different - did you specify a DNS in Network connections have you got the gateway IP right?
    Last edited by Gone fishing; May 3rd, 2010 at 12:22 PM.

  7. #17
    Join Date
    Jul 2009
    Location
    #ubuntu
    Beans
    139
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: apt-get has the problems to resolve address

    Yeah, I have a DNS, PPPoE set up, NAT working, gateway IP, and all that. It was all preconfigured by SBC when it came here...I knew that for awhile, I configured the wireless in there and came across it. Granted my line is a little noisy because of some bad phone line, or the cheapness of the router, or both, but it didn't cause any problems before.

    And I think Medibuntu did go down briefly. medibuntu.org was not found for awhile.

    This is the contents of my sources.list:

    Code:
    # deb cdrom:[Ubuntu 10.04 LTS _Lucid Lynx_ - Release i386 (20100429)]/ lucid main restricted
    deb-src http://archive.ubuntu.com/ubuntu lucid main restricted #Added by software-properties
    # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
    # newer versions of the distribution.
    
    
    ## Major bug fix updates produced after the final release of the
    ## distribution.
    
    ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
    ## team. Also, please note that software in universe WILL NOT receive any
    ## review or updates from the Ubuntu security team.
    
    ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu 
    ## team, and may not be under a free licence. Please satisfy yourself as to 
    ## your rights to use the software. Also, please note that software in 
    ## multiverse WILL NOT receive any review or updates from the Ubuntu
    ## security team.
    
    ## Uncomment the following two lines to add software from the 'backports'
    ## repository.
    ## N.B. software from this repository may not have been tested as
    ## extensively as that contained in the main release, although it includes
    ## newer versions of some applications which may provide useful features.
    ## Also, please note that software in backports WILL NOT receive any review
    ## or updates from the Ubuntu security team.
    # deb http://us.archive.ubuntu.com/ubuntu/ lucid-backports main restricted universe multiverse
    # deb-src http://us.archive.ubuntu.com/ubuntu/ lucid-backports main restricted universe multiverse
    
    ## Uncomment the following two lines to add software from Canonical's
    ## 'partner' repository.
    ## This software is not part of Ubuntu, but is offered by Canonical and the
    ## respective vendors as a service to Ubuntu users.
    deb http://archive.canonical.com/ubuntu lucid partner
    deb-src http://archive.canonical.com/ubuntu lucid partner
    deb http://mirrors.us.kernel.org/ubuntu/ lucid main universe restricted multiverse
    deb-src http://mirrors.us.kernel.org/ubuntu/ lucid main universe restricted multiverse #Added by software-properties
    deb http://security.ubuntu.com/ubuntu/ lucid-security universe main multiverse restricted
    deb-src http://security.ubuntu.com/ubuntu/ lucid-security universe main multiverse restricted #Added by software-properties
    deb http://mirrors.us.kernel.org/ubuntu/ lucid-updates universe main multiverse restricted
    deb-src http://mirrors.us.kernel.org/ubuntu/ lucid-updates universe main multiverse restricted #Added by software-properties
    deb http://mirrors.us.kernel.org/ubuntu/ lucid-proposed universe main multiverse restricted
    deb-src http://mirrors.us.kernel.org/ubuntu/ lucid-proposed universe main multiverse restricted #Added by software-properties
    deb http://mirrors.us.kernel.org/ubuntu/ lucid-backports universe main multiverse restricted
    deb-src http://mirrors.us.kernel.org/ubuntu/ lucid-backports universe main multiverse restricted #Added by software-properties
    deb http://downloads.sourceforge.net/project/ubuntuzilla/mozilla/apt all main
    I have noticed that it always happens with the servers near the end of the update, never the beginning.

    Example:

    Code:
    justyn@FrontRoomBoxLucid:~$ sudo apt-get update
    
    Hit http://security.ubuntu.com lucid-security Release.gpg                      
    Ign http://security.ubuntu.com/ubuntu/ lucid-security/universe Translation-en_US
    Ign http://security.ubuntu.com/ubuntu/ lucid-security/main Translation-en_US   
    Ign http://security.ubuntu.com/ubuntu/ lucid-security/multiverse Translation-en_US
    Ign http://security.ubuntu.com/ubuntu/ lucid-security/restricted Translation-en_US
    Ign http://downloads.sourceforge.net/project/ubuntuzilla/mozilla/apt/ all/main Translation-en_US
    Hit http://archive.ubuntu.com lucid Release.gpg                                
    Hit http://archive.ubuntu.com lucid Release                                    
    Hit http://archive.ubuntu.com lucid/main Sources                               
    Hit http://security.ubuntu.com lucid-security Release                          
    Hit http://security.ubuntu.com lucid-security/universe Packages                
    Hit http://security.ubuntu.com lucid-security/main Packages                    
    Hit http://security.ubuntu.com lucid-security/multiverse Packages              
    Hit http://archive.getdeb.net lucid-getdeb Release.gpg                         
    Hit http://archive.ubuntu.com lucid/restricted Sources                         
    Hit http://security.ubuntu.com lucid-security/restricted Packages              
    Hit http://security.ubuntu.com lucid-security/universe Sources                 
    Hit http://security.ubuntu.com lucid-security/main Sources                     
    Hit http://security.ubuntu.com lucid-security/multiverse Sources               
    Hit http://security.ubuntu.com lucid-security/restricted Sources               
    Ign http://archive.getdeb.net/ubuntu/ lucid-getdeb/apps Translation-en_US      
    Hit http://archive.getdeb.net lucid-getdeb Release                             
    Hit http://archive.getdeb.net lucid-getdeb/apps Packages                       
    Hit http://archive.canonical.com lucid Release.gpg                             
    Ign http://archive.canonical.com/ubuntu/ lucid/partner Translation-en_US       
    Hit http://archive.canonical.com lucid Release                                 
    Hit http://archive.canonical.com lucid/partner Packages                        
    Hit http://archive.canonical.com lucid/partner Sources                         
    Hit http://ppa.launchpad.net lucid Release.gpg                                 
    Ign http://ppa.launchpad.net/psyke83/ppa/ubuntu/ lucid/main Translation-en_US  
    Hit http://ppa.launchpad.net lucid Release                                     
    Hit http://ppa.launchpad.net lucid/main Packages                               
    Hit http://mirrors.us.kernel.org lucid Release.gpg                             
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid/main Translation-en_US          
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid/universe Translation-en_US      
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid/restricted Translation-en_US    
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid/multiverse Translation-en_US    
    Hit http://mirrors.us.kernel.org lucid-updates Release.gpg                     
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-updates/universe Translation-en_US
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-updates/main Translation-en_US  
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-updates/multiverse Translation-en_US
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-updates/restricted Translation-en_US
    Hit http://mirrors.us.kernel.org lucid-proposed Release.gpg                    
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-proposed/universe Translation-en_US
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-proposed/main Translation-en_US 
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-proposed/multiverse Translation-en_US
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-proposed/restricted Translation-en_US
    Hit http://mirrors.us.kernel.org lucid-backports Release.gpg                   
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-backports/universe Translation-en_US
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-backports/main Translation-en_US
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-backports/multiverse Translation-en_US
    Ign http://mirrors.us.kernel.org/ubuntu/ lucid-backports/restricted Translation-en_US
    Hit http://mirrors.us.kernel.org lucid Release                                 
    Hit http://mirrors.us.kernel.org lucid-updates Release                         
    Hit http://mirrors.us.kernel.org lucid-proposed Release                        
    Hit http://mirrors.us.kernel.org lucid-backports Release                       
    Get:1 http://downloads.sourceforge.net all Release.gpg [197B]                  
    Hit http://mirrors.us.kernel.org lucid/main Packages                           
    Hit http://mirrors.us.kernel.org lucid/universe Packages                       
    Hit http://mirrors.us.kernel.org lucid/restricted Packages                     
    Hit http://mirrors.us.kernel.org lucid/multiverse Packages                     
    Hit http://mirrors.us.kernel.org lucid/main Sources                            
    Hit http://mirrors.us.kernel.org lucid/universe Sources                        
    Hit http://mirrors.us.kernel.org lucid/restricted Sources                      
    Hit http://mirrors.us.kernel.org lucid/multiverse Sources                      
    Hit http://mirrors.us.kernel.org lucid-updates/universe Packages               
    Hit http://mirrors.us.kernel.org lucid-updates/main Packages                   
    Hit http://mirrors.us.kernel.org lucid-updates/multiverse Packages             
    Hit http://mirrors.us.kernel.org lucid-updates/restricted Packages             
    Hit http://mirrors.us.kernel.org lucid-updates/universe Sources                
    Hit http://mirrors.us.kernel.org lucid-updates/main Sources                    
    Hit http://mirrors.us.kernel.org lucid-updates/multiverse Sources              
    Hit http://mirrors.us.kernel.org lucid-updates/restricted Sources              
    Hit http://mirrors.us.kernel.org lucid-proposed/universe Packages              
    Hit http://mirrors.us.kernel.org lucid-proposed/main Packages                  
    Hit http://mirrors.us.kernel.org lucid-proposed/multiverse Packages            
    Hit http://mirrors.us.kernel.org lucid-proposed/restricted Packages            
    Hit http://mirrors.us.kernel.org lucid-proposed/universe Sources               
    Hit http://mirrors.us.kernel.org lucid-proposed/main Sources                   
    Hit http://mirrors.us.kernel.org lucid-proposed/multiverse Sources             
    Hit http://mirrors.us.kernel.org lucid-proposed/restricted Sources             
    Hit http://mirrors.us.kernel.org lucid-backports/universe Packages             
    Hit http://mirrors.us.kernel.org lucid-backports/main Packages                 
    Hit http://mirrors.us.kernel.org lucid-backports/multiverse Packages           
    Hit http://mirrors.us.kernel.org lucid-backports/restricted Packages           
    Hit http://mirrors.us.kernel.org lucid-backports/universe Sources              
    Hit http://mirrors.us.kernel.org lucid-backports/main Sources                  
    Hit http://mirrors.us.kernel.org lucid-backports/multiverse Sources            
    Hit http://mirrors.us.kernel.org lucid-backports/restricted Sources            
    Err http://linux.dropbox.com lucid Release.gpg                                 
      Something wicked happened resolving 'linux.dropbox.com:http' (-5 - No address associated with hostname)
    Err http://packages.medibuntu.org lucid Release.gpg                            
      Something wicked happened resolving 'packages.medibuntu.org:http' (-5 - No address associated with hostname)
    Ign http://packages.medibuntu.org/ lucid/free Translation-en_US                
    Ign http://linux.dropbox.com/ubuntu/ lucid/main Translation-en_US              
    Hit http://linux.dropbox.com lucid Release                                     
    Ign http://packages.medibuntu.org/ lucid/non-free Translation-en_US            
    Hit http://linux.dropbox.com lucid/main Packages                               
    Hit http://packages.medibuntu.org lucid Release                                
    Hit http://packages.medibuntu.org lucid/free Packages                          
    Hit http://packages.medibuntu.org lucid/non-free Packages
    Hit http://packages.medibuntu.org lucid/free Sources              
    Hit http://packages.medibuntu.org lucid/non-free Sources          
    Hit http://downloads.sourceforge.net all Release                               
    Ign http://downloads.sourceforge.net all/main Packages                         
    Ign http://downloads.sourceforge.net all/main Packages                         
    Hit http://downloads.sourceforge.net all/main Packages                         
    Fetched 197B in 18s (11B/s)                                                    
    W: Failed to fetch http://linux.dropbox.com/ubuntu/dists/lucid/Release.gpg  Something wicked happened resolving 'linux.dropbox.com:http' (-5 - No address associated with hostname)
    
    W: Failed to fetch http://packages.medibuntu.org/dists/lucid/Release.gpg  Something wicked happened resolving 'packages.medibuntu.org:http' (-5 - No address associated with hostname)
    
    E: Some index files failed to download, they have been ignored, or old ones used instead.
    It's always is like that, around 90%. Again, it's not only the dropbox and medibuntu entries that are giving me trouble. However, I've found that it's not completely random. It never happens to mirrors.us.kernel.org or security.ubuntu.com. Maybe it's a third party repo thing?

    I pinged security.ubuntu.com. I got 158, 156, 160, 160, and 156 ms. I then pinged packages.medibuntu.org, 166, 169, 165, 165, 164 ms. linux.dropbox.com, 60.3, 60.10, 60.3, 60.5, 61.9 ms. Fine. But another thing, is that both the graphical ping in Network Tools, and command ping took a REALLY long time to get a result of these pings, like a minute, but this time wasn't reported in the latency. The graphical ping in Network Tools just hung (greyed itself out) for that time and reported all the results at once instead of one by one most of the time, and command ping did one ping, sat there for a few seconds doing nothing, did another ping, sat there for a few seconds, etc.

    Also for both, it reported some packet loss, but the pings that made it through were at a fine latency. This is really getting my goat, I know I don't have packet loss. I tested it with pingtest.net, and ordinary Skype calls don't have any loss. Maybe my machine is too old? It's been 6 years since I got it, after all...I have upgraded the memory, graphics card, etc, but the processor is a Pentium D 820. That doesn't explain why it can't run ping, though! Ping worked fine in Karmic and Jaunty (command).

    Also, I have wireless (g), but that's been working fine for years, never less than 70% signal strength.

    I'm at a loss. Is my networking misconfigured?

    I hope this information can help. Thanks all. Ask me for more logs if it's required.
    Last edited by ThatBum; May 4th, 2010 at 03:17 AM.

  8. #18
    Join Date
    Oct 2006
    Location
    Brittany (as my username
    Beans
    28
    Distro
    Ubuntu 10.04 Lucid Lynx

    Re: apt-get has the problems to resolve address

    Quote Originally Posted by ThatBum View Post
    Yeah, I have a DNS, PPPoE set up, NAT working, gateway IP, and all that. It was all preconfigured by SBC when it came here...I knew that for awhile, I configured the wireless in there and came across it. Granted my line is a little noisy because of some bad phone line, or the cheapness of the router, or both, but it didn't cause any problems before.

    And I think Medibuntu did go down briefly. medibuntu.org was not found for awhile.

    [...]

    Example:

    Code:
    justyn@FrontRoomBoxLucid:~$ sudo apt-get update
    
    [...]
                                               
    W: Failed to fetch http://linux.dropbox.com/ubuntu/dists/lucid/Release.gpg  Something wicked happened resolving 'linux.dropbox.com:http' (-5 - No address associated with hostname)
    
    W: Failed to fetch http://packages.medibuntu.org/dists/lucid/Release.gpg  Something wicked happened resolving 'packages.medibuntu.org:http' (-5 - No address associated with hostname)
    
    E: Some index files failed to download, they have been ignored, or old ones used instead.
    It's always is like that, around 90%. Again, it's not only the dropbox and medibuntu entries that are giving me trouble. However, I've found that it's not completely random. It never happens to mirrors.us.kernel.org or security.ubuntu.com. Maybe it's a third party repo thing?

    I pinged security.ubuntu.com. I got 158, 156, 160, 160, and 156 ms. I then pinged packages.medibuntu.org, 166, 169, 165, 165, 164 ms. linux.dropbox.com, 60.3, 60.10, 60.3, 60.5, 61.9 ms. Fine. But another thing, is that both the graphical ping in Network Tools, and command ping took a REALLY long time to get a result of these pings, like a minute, but this time wasn't reported in the latency. The graphical ping in Network Tools just hung (greyed itself out) for that time and reported all the results at once instead of one by one most of the time, and command ping did one ping, sat there for a few seconds doing nothing, did another ping, sat there for a few seconds, etc.

    Also for both, it reported some packet loss, but the pings that made it through were at a fine latency. This is really getting my goat, I know I don't have packet loss. I tested it with pingtest.net, and ordinary Skype calls don't have any loss. Maybe my machine is too old? It's been 6 years since I got it, after all...I have upgraded the memory, graphics card, etc, but the processor is a Pentium D 820. That doesn't explain why it can't run ping, though! Ping worked fine in Karmic and Jaunty (command).

    Also, I have wireless (g), but that's been working fine for years, never less than 70% signal strength.

    I'm at a loss. Is my networking misconfigured?

    I hope this information can help. Thanks all. Ask me for more logs if it's required.
    I have often that problem, and the only way out I've found it's to force apt-get to clean its cache :

    sudo apt-get update -o Acquire::http::No-Cache=True

  9. #19
    Join Date
    Jun 2007
    Location
    China
    Beans
    995
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: apt-get has the problems to resolve address

    My sources.list

    #deb cdrom:[Ubuntu 10.04 LTS _Lucid Lynx_ - Release i386 (20100429)]/ lucid main restricted
    # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
    # newer versions of the distribution.

    deb http://ls.archive.ubuntu.com/ubuntu/ lucid main restricted
    deb-src http://ls.archive.ubuntu.com/ubuntu/ lucid main restricted

    ## Major bug fix updates produced after the final release of the
    ## distribution.
    deb http://ls.archive.ubuntu.com/ubuntu/ lucid-updates main restricted
    deb-src http://ls.archive.ubuntu.com/ubuntu/ lucid-updates main restricted

    ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
    ## team. Also, please note that software in universe WILL NOT receive any
    ## review or updates from the Ubuntu security team.
    deb http://ls.archive.ubuntu.com/ubuntu/ lucid universe
    deb-src http://ls.archive.ubuntu.com/ubuntu/ lucid universe
    deb http://ls.archive.ubuntu.com/ubuntu/ lucid-updates universe
    deb-src http://ls.archive.ubuntu.com/ubuntu/ lucid-updates universe

    ## N.B. software from this repository is ENTIRELY UNSUPPORTED by the Ubuntu
    ## team, and may not be under a free licence. Please satisfy yourself as to
    ## your rights to use the software. Also, please note that software in
    ## multiverse WILL NOT receive any review or updates from the Ubuntu
    ## security team.
    deb http://ls.archive.ubuntu.com/ubuntu/ lucid multiverse
    deb-src http://ls.archive.ubuntu.com/ubuntu/ lucid multiverse
    deb http://ls.archive.ubuntu.com/ubuntu/ lucid-updates multiverse
    deb-src http://ls.archive.ubuntu.com/ubuntu/ lucid-updates multiverse

    ## Uncomment the following two lines to add software from the 'backports'
    ## repository.
    ## N.B. software from this repository may not have been tested as
    ## extensively as that contained in the main release, although it includes
    ## newer versions of some applications which may provide useful features.
    ## Also, please note that software in backports WILL NOT receive any review
    ## or updates from the Ubuntu security team.
    # deb http://ls.archive.ubuntu.com/ubuntu/ lucid-backports main restricted universe multiverse
    # deb-src http://ls.archive.ubuntu.com/ubuntu/ lucid-backports main restricted universe multiverse

    ## Uncomment the following two lines to add software from Canonical's
    ## 'partner' repository.
    ## This software is not part of Ubuntu, but is offered by Canonical and the
    ## respective vendors as a service to Ubuntu users.
    # deb http://archive.canonical.com/ubuntu lucid partner
    # deb-src http://archive.canonical.com/ubuntu lucid partner

    deb http://security.ubuntu.com/ubuntu lucid-security main restricted
    deb-src http://security.ubuntu.com/ubuntu lucid-security main restricted
    deb http://security.ubuntu.com/ubuntu lucid-security universe
    deb-src http://security.ubuntu.com/ubuntu lucid-security universe
    deb http://security.ubuntu.com/ubuntu lucid-security multiverse
    deb-src http://security.ubuntu.com/ubuntu lucid-security multiverse
    and

    in the mediubuntu.list

    Obviously the dropping packets is bad and the taking seconds before being able to ping is bad.

    I think you need to find at what places the packets are being dropped. Between the PC and the router, router and ISPs gateway etc.

    On my system I get a little packet loss

    PC -> wirelessaccess pt-> wirelessaccess pt (150m through trees) -> proxyserver -> ADSL router (1 meg for 30+ PCs and Lesotho telephone lines) ->ISPs gateway but I never get more than 3-4% packet loss. If you get more than that you have a problem and it will be unstable on large downloads.

  10. #20
    Join Date
    Jul 2009
    Location
    #ubuntu
    Beans
    139
    Distro
    Xubuntu 14.04 Trusty Tahr

    Re: apt-get has the problems to resolve address

    Quote Originally Posted by Gone fishing View Post
    Obviously the dropping packets is bad and the taking seconds before being able to ping is bad.
    That's the thing, I think nothing is actually dropping. ping just seems to be hanging. The reported ping time is not actually seconds, but the usual millisecond values, for some reason.

    My router is a 2wire 2700HG-B. Through the advanced configuration (http://gateway.2wire.net/mdc on my router) shows this (partial):

    Code:
    DSL Line (Wire Pair):Line 1 (inner pair)
    Downstream Rate Cap: 3008 kbps
    Downstream Atten. at 300kHz: 40.8 dB
    Uncancelled Echo: 18.5 dB  Suspicious - check phone filters and alarm
    VCXO Frequency Offset: -1.8 ppm Ok
    Final Rx Gain: 16.9 dB Ok
    Impulse Noise Comp. Tones: 0 Ok
    Excessive Impulse Noise: 0 Ok
    Impulse noise protection: 0.00
    Delay of latency path: 0.25 ms
    I see the uncanceled echo. I am told this means I don't have phone filters on something. The check alarm bit is if you have some kind of paging or alarm system that uses the phone line, but that's moot because I don't have one. This has been there since I got the router, and, yes, I'm sure I have filters on everything. The house is from the 50's, and the wiring has never been replaced, so it might just be that. But anyway, this hasn't been a problem before.

    More importantly, through bumbling through the router's config, I found a BUILT-IN PING utility. The utility pings directly from the router and not through my computer. I pinged packages.medibuntu.org with it and got this:

    Code:
    Pinging [88.191.82.11] 30 times with: 64 bytes of data
    
    ping successful: icmp_seq=0 time=166 ms
    ping successful: icmp_seq=1 time=165 ms
    ping successful: icmp_seq=2 time=166 ms
    ping successful: icmp_seq=3 time=165 ms
    ping successful: icmp_seq=4 time=166 ms
    ping successful: icmp_seq=5 time=165 ms
    ping successful: icmp_seq=6 time=164 ms
    ping successful: icmp_seq=7 time=163 ms
    ping successful: icmp_seq=8 time=165 ms
    ping successful: icmp_seq=9 time=164 ms
    ping successful: icmp_seq=10 time=165 ms
    ping successful: icmp_seq=11 time=164 ms
    ping successful: icmp_seq=12 time=164 ms
    ping successful: icmp_seq=13 time=164 ms
    ping successful: icmp_seq=14 time=165 ms
    ping successful: icmp_seq=15 time=164 ms
    ping successful: icmp_seq=16 time=165 ms
    ping successful: icmp_seq=17 time=162 ms
    ping successful: icmp_seq=18 time=164 ms
    ping successful: icmp_seq=19 time=165 ms
    ping successful: icmp_seq=20 time=165 ms
    ping successful: icmp_seq=21 time=165 ms
    ping successful: icmp_seq=22 time=164 ms
    ping successful: icmp_seq=23 time=165 ms
    ping successful: icmp_seq=24 time=164 ms
    ping successful: icmp_seq=25 time=165 ms
    ping successful: icmp_seq=26 time=164 ms
    ping successful: icmp_seq=27 time=163 ms
    ping successful: icmp_seq=28 time=166 ms
    ping successful: icmp_seq=29 time=165 ms
    These were ALL INSTANT. Also, by testing with repeated trials, there was no lost packets. This reinforces that there is a problem with the client/router interface, or a bug somewhere. I'm tending to think the latter, because this never happened in Karmic, and I didn't change anything with the router upgrading from Karmic to Lucid. The only thing of significance was that the service was upgraded from 160kBps down/40kBps up to 315kBps down/50kBps up a awhile ago, but, again, this was before Lucid.

    Some more router stuff of interest:

    Code:
    Current Noise Margin: 20.0 dB/19.0 dB( down/up)
    Current Attenuation: 31.6 dB/27.0 dB (down/up)
    Current Output Power: 7.9 dBm/2.9 dBm (down/up)
    Code:
    Collected for 3 days
    
    (Since Reset/Current 24-Hour Interval/Current 15-Minute Interval/Time Since Last Event)
    
    Cell Header Errors:         2612         93         13         0:00:07
    Loss of Cell Delineation:         966         56         0         2:39:45
    Link Retrains:         13         1         0         2:39:44
    DSL Training Errors:         0         0         0         0:00:00
    Training Timeouts:         0         0         0         0:00:00
    Loss of Framing Failures:         22         1         0         2:39:45
    Loss of Signal Failures:         22         1         0         2:39:45
    Loss of Power Failures:         0         0         0         0:00:00
    Loss of Margin Failures:         22         1         0         2:39:45
    Cumulative Seconds w/Errors:         1365         88         26         0:00:07
    Cumulative Sec. w/Severe Errors:         39         1         0         2:39:45
    Corrected Blocks:         0         0         0         0:00:00
    Uncorrectable Blocks:         4031         159         35         0:00:07
    DSL Unavailable Seconds:         372         25         0         2:39:21
    ^ This worries me. This has increased since I last checked it. This might be the cause of all this, my bad line quality. I've been wanting to get cable for a long, LONG time, but the only cable provider near my location, Comcast, doesn't have service here. Damn AT&T, or SBC, or Yahoo. They've bought each other out so many times I don't know what they're even calling themselves anymore.

    Code:
    NAT Sessions
    
    current secs since boot: 270714
    session table 1004/1024 available, 0/512 used in inbound sessions:
    sess[24746]: bkt 2, flags: 0x000081a1, proto: 17, cnt: 86
      l: 192.168.1.66:123, f: 208.43.238.3:123, n: 71.134.233.218:123
      lnd: (60,0), fnd: (44,0)
      last used 270651, max_idle: 600
    sess[24747]: bkt 2, flags: 0x000081a1, proto: 17, cnt: 86
      l: 192.168.1.66:123, f: 207.171.7.152:123, n: 71.134.233.218:123
      lnd: (60,0), fnd: (44,0)
      last used 270666, max_idle: 600
    sess[24748]: bkt 2, flags: 0x000081a1, proto: 17, cnt: 84
      l: 192.168.1.66:123, f: 74.63.201.10:123, n: 71.134.233.218:123
      lnd: (60,0), fnd: (44,0)
      last used 270668, max_idle: 600
    sess[24749]: bkt 2, flags: 0x000081a1, proto: 17, cnt: 84
      l: 192.168.1.66:123, f: 207.7.148.214:123, n: 71.134.233.218:123
      lnd: (60,0), fnd: (44,0)
      last used 270703, max_idle: 600
    sess[24732]: bkt 4, flags: 0x00000190, proto: 17, cnt: 4638
      l: 71.134.233.218:49172, f: 68.94.156.1:53, n: 71.134.233.218:49172
      lnd: (0,0), fnd: (44,0)
      last used 270711, max_idle: 600
    sess[25509]: bkt 4, flags: 0x00008190, proto: 17, cnt: 297
      l: 71.134.233.218:49172, f: 68.94.157.1:53, n: 71.134.233.218:49172
      lnd: (0,0), fnd: (44,0)
      last used 270584, max_idle: 600
    sess[24799]: bkt 25, flags: 0x000001a1, proto: 6, cnt: 122
      l: 192.168.1.66:36925, f: 174.36.30.44:80, n: 71.134.233.218:36925
      lnd: (60,0), fnd: (44,0)
      last used 270662, max_idle: 86400
      TCP state ESTABLISHED
      TCP IN: is: 3462921545, sent: 7129, unack'd 0, mss 0, windows_scale 0 
      TCP OUT: is: 1890217321, sent: 6143, unack'd 0, mss 0, windows_scale 0 
    sess[25703]: bkt 65, flags: 0x00000190, proto: 17, cnt: 2
      l: 71.134.233.218:12222, f: 68.94.156.1:53, n: 71.134.233.218:12222
      lnd: (0,0), fnd: (44,0)
      last used 270710, max_idle: 600
    sess[25704]: bkt 200, flags: 0x000001a1, proto: 6, cnt: 15
      l: 192.168.1.66:57334, f: 75.126.110.108:443, n: 71.134.233.218:57334
      lnd: (60,0), fnd: (44,0)
      last used 270711, max_idle: 86400
      TCP state ESTABLISHED
      TCP IN: is: 2573245654, sent: 1664, unack'd 0, mss 0, windows_scale 0 
      TCP OUT: is: 1318338257, sent: 791, unack'd 0, mss 0, windows_scale 0 
    sess[25666]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 128.135.138.162:60491, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270427, max_idle: 600
    sess[25667]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 24.23.208.118:45679, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270427, max_idle: 600
    sess[25671]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 98.244.178.116:57172, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270473, max_idle: 600
    sess[25672]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 75.18.166.214:18577, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270473, max_idle: 600
    sess[25675]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 114.45.51.228:37544, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270550, max_idle: 600
    sess[25689]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 4
      l: 192.168.1.66:7094, f: 71.143.0.85:2791, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270630, max_idle: 600
    sess[25692]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 95.27.81.27:26465, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270651, max_idle: 600
    sess[25693]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 140.115.206.40:60384, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270651, max_idle: 600
    sess[25694]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 173.2.146.81:5732, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270651, max_idle: 600
    sess[25696]: bkt 212, flags: 0x000085a1, proto: 17, cnt: 2
      l: 192.168.1.66:7094, f: 94.192.245.199:5735, n: 71.134.233.218:7094
      lnd: (60,0), fnd: (44,0)
      last used 270681, max_idle: 600
    sess[24763]: bkt 230, flags: 0x000001a1, proto: 6, cnt: 211
      l: 192.168.1.66:46985, f: 71.237.226.138:63973, n: 71.134.233.218:46985
      lnd: (60,0), fnd: (44,0)
      last used 270705, max_idle: 86400
      TCP state ESTABLISHED
      TCP IN: is: 1041512636, sent: 1883, unack'd 0, mss 0, windows_scale 0 
      TCP OUT: is: 1833099151, sent: 4983, unack'd 0, mss 0, windows_scale 0
    ^The router has a hardware firewall, but I don't think that's doing anything here.

    Thanks for sticking with me on this problem.

    Oh, and clearing the apt-get cache didn't work. Thanks, though.

Page 2 of 5 FirstFirst 1234 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •