New user's registration have been closed due to high spamming and low trafic on this forum. Please contact forum admins directly if you need an account. Thanks !

Problems updating BubbaTwo

Got problems with your B2 or B3? Share and get helped!
mountaindude
Posts: 57
Joined: 25 Aug 2007, 11:56

Problems updating BubbaTwo

Post by mountaindude »

Becoming root by doing an su, then apt-get update just to get things up to date. Problem is that nothing is downloaded, the output stops at
"0% [Waiting for headers] [Waiting for headers]" for a long time, before failing.

The bubba does have internet connectivity and correct DNS setup, pinging known Internet hosts work as expected.

When trying to update from the web UI, this also fails.

Is the Excito repositories not online yet, or something else?
dan13l
Posts: 50
Joined: 20 Apr 2007, 20:30

Post by dan13l »

apt-get update worked OK for me yesterday. Which doesn't solve your problem, I know, but it might be useful information.
Cheeseboy
Posts: 789
Joined: 08 Apr 2007, 12:16

Post by Cheeseboy »

It worked fine for me too. But then I'm pretty close to the servers geographically...

Perhaps you could check if you can reach the URLs listed in /etc/apt/sources.list from your network at all?

Cheers,

Cheeseboy
mountaindude
Posts: 57
Joined: 25 Aug 2007, 11:56

Post by mountaindude »

Cheeseboy wrote:It worked fine for me too. But then I'm pretty close to the servers geographically...
So am I..
Perhaps you could check if you can reach the URLs listed in /etc/apt/sources.list from your network at all?

Cheers,

Cheeseboy
That's the funny part, I can ping those servers just fine. Still apt-get fails.

Hmmm... just realized I had put the bubba2 behind my existing router/wlan/firewall box... This shouldn't affect outgoing connections when doing an apt-get update, but I guess I could move the bubba to become connected directly to the Internet.. A bit of work doing that, but I'll test.
carl
Posts: 474
Joined: 07 May 2008, 04:41

Re: Problems updating BubbaTwo

Post by carl »

mountaindude wrote:Becoming root by doing an su, then apt-get update just to get things up to date. Problem is that nothing is downloaded, the output stops at
"0% [Waiting for headers] [Waiting for headers]" for a long time, before failing.

The bubba does have internet connectivity and correct DNS setup, pinging known Internet hosts work as expected.

When trying to update from the web UI, this also fails.

Is the Excito repositories not online yet, or something else?
This looks like it can be related to a silicon bug in the Freescale CPU, causing the packet checksum generation fail under some conditions. The bug itself has been known for a while, though we have been unable to confirm the exact source, and haven't realized the impact of it until recently. The issue will be resolved in the next software release, where we will add an workaround for the silicon bug, but until then, can you please try the following?

1. Install the package ethtool, if you can't apt-get install it, download following file to an other computer, and scp it over to the bubbatwo: http://ftp.se.debian.org/debian/pool/ma ... owerpc.deb

2. execute following as root: ethtool --offload eth0 tx off rx off

Now, if the issue at hand was related to above silicon bug, then you should be able to use apt-get update/dist-upgrade etc...

/Carl Fürstenberg
/Carl Fürstenberg, Excito Software Developer
http://www.excito.com
support@excito.com
mountaindude
Posts: 57
Joined: 25 Aug 2007, 11:56

Re: Problems updating BubbaTwo

Post by mountaindude »

1. Install the package ethtool, if you can't apt-get install it, download following file to an other computer, and scp it over to the bubbatwo: http://ftp.se.debian.org/debian/pool/ma ... owerpc.deb

Where on the bubba should the .deb file be stored?
carl
Posts: 474
Joined: 07 May 2008, 04:41

Re: Problems updating BubbaTwo

Post by carl »

mountaindude wrote:
1. Install the package ethtool, if you can't apt-get install it, download following file to an other computer, and scp it over to the bubbatwo: http://ftp.se.debian.org/debian/pool/ma ... owerpc.deb

Where on the bubba should the .deb file be stored?
When you have transferred it over to the bubba, ssh into the bubba and change to root, issue following command: dpkg -i ethtool_5-1_powerpc.deb (assuming that the deb-file is in that current directory)

/Carl
/Carl Fürstenberg, Excito Software Developer
http://www.excito.com
support@excito.com
mountaindude
Posts: 57
Joined: 25 Aug 2007, 11:56

Re: Problems updating BubbaTwo

Post by mountaindude »

carl wrote: 2. execute following as root: ethtool --offload eth0 tx off rx off

Now, if the issue at hand was related to above silicon bug, then you should be able to use apt-get update/dist-upgrade etc...
Comfirmed, that fixed the problem and I can now do a successful "apt-get update".

Next question is then: Is this a one-time operation or is the same thing needed after each reboot?
carl
Posts: 474
Joined: 07 May 2008, 04:41

Re: Problems updating BubbaTwo

Post by carl »

mountaindude wrote:
carl wrote: 2. execute following as root: ethtool --offload eth0 tx off rx off

Now, if the issue at hand was related to above silicon bug, then you should be able to use apt-get update/dist-upgrade etc...
Comfirmed, that fixed the problem and I can now do a successful "apt-get update".

Next question is then: Is this a one-time operation or is the same thing needed after each reboot?
Is is something that needs to be done at each boot (you can add it to /etc/rc.local if you want). We are working on solving this exact issue, first by the above workaround, but also digging into the root of the problem.

/Carl
/Carl Fürstenberg, Excito Software Developer
http://www.excito.com
support@excito.com
jonj1
Posts: 51
Joined: 24 Oct 2008, 15:33

Post by jonj1 »

Hi,

I have the exact same problem on a brand-new bubba 2; atp-get says 'waiting for headers' indefinitely but ping works and wget resolves the ip address and says 'connected' but doesn't download. I tried installing the ethtool deb package as suggested above, but with no luck. My bubba is connected to a router via eth1, so I ran the ethtool... command on eth1 also for good measure.

Any ideas?
thanks,
Jon
darione75
Posts: 76
Joined: 06 Aug 2008, 12:28

Post by darione75 »

I've the same problem of jony1
I've try to follow this post for resolve mailmail problem, for install mailx, but nothing, my bubba don't work properly. I start to benot satisfy about this product..
jonj1
Posts: 51
Joined: 24 Oct 2008, 15:33

Post by jonj1 »

Hi,

In case it's related to the network config instead the silicon bug, here's some info about my bubba. I set it up though the web interface to acquire an IP address automatically on both WAN and LAN. The LAN port is connected to my router as per network setup 6 in the manual.
cheers.
Jon

Code: Select all

# ethtool --offload eth1 tx off rx off 

Code: Select all

# 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 eth1
239.0.0.0       *               255.0.0.0       U     0      0        0 eth1
default         dsldevice.confi 0.0.0.0         UG    0      0        0 eth1
bubba:/home/jjackson# cat /etc/resolv.conf 
search config
nameserver 192.168.1.254

Code: Select all

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:22:02:00:01:D6  
          UP BROADCAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:670 (670.0 b)
          Base address:0xe000 

eth1      Link encap:Ethernet  HWaddr 00:22:02:00:01:D7  
          inet addr:192.168.1.66  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::222:2ff:fe00:1d7/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:22591964 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1971747 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2968030928 (2.7 GiB)  TX bytes:132134431 (126.0 MiB)

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:386 errors:0 dropped:0 overruns:0 frame:0
          TX packets:386 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:32706 (31.9 KiB)  TX bytes:32706 (31.9 KiB)

Code: Select all

# ping www.google.com
PING www.l.google.com (66.102.9.99) 56(84) bytes of data.
64 bytes from 66.102.9.99: icmp_seq=1 ttl=243 time=41.3 ms
64 bytes from 66.102.9.99: icmp_seq=2 ttl=243 time=40.6 ms
64 bytes from 66.102.9.99: icmp_seq=3 ttl=243 time=40.8 ms
^C
--- www.l.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2009ms
rtt min/avg/max/mdev = 40.687/40.979/41.388/0.340 ms
ping works...

Code: Select all

# wget http://www.excito.com/
--09:42:13--  http://www.excito.com/
           => `index.html'
Resolving www.excito.com... 194.236.32.217
Connecting to www.excito.com|194.236.32.217|:80... connected.
HTTP request sent, awaiting response... ^C
wget times out...

Code: Select all

# apt-get update
0% [Waiting for headers] [Waiting for headers]
changes eventually to

Code: Select all

Err http://update.excito.org marielle Release.gpg
  Connection failed
Err http://ftp.se.debian.org etch Release.gpg                              
  Connection failed [IP: 130.239.18.173 80]
Hit http://ftp.se.debian.org etch Release                                  
14% [Waiting for headers] [Waiting for headers]   
Eek
Posts: 372
Joined: 23 Dec 2007, 03:03
Location: the Netherlands

Post by Eek »

what does

Code: Select all

wget http://www.google.com
give?
jonj1
Posts: 51
Joined: 24 Oct 2008, 15:33

Post by jonj1 »

About the same unfortunately... This is after about a minute.

Code: Select all

# wget http://www.google.com
--10:17:55--  http://www.google.com/
           => `index.html'
Resolving www.google.com... 66.102.9.104, 66.102.9.99, 66.102.9.147
Connecting to www.google.com|66.102.9.104|:80... connected.
HTTP request sent, awaiting response... 
Eek
Posts: 372
Joined: 23 Dec 2007, 03:03
Location: the Netherlands

Post by Eek »

hmm looks like DNS resolves,
but TCP connection fails
or NAT doesn't work
what is your setup?
internet connection direct into B2?
or internet -> router -> B2 ?
Post Reply