1. Home
  2. Raspberry Pi Group
  3. Connections drop out

Connections drop out

Running model B, Linux raspberrypi 3.10.25+ #622 PREEMPT Fri Jan 3

18:41:00 GMT 2014 armv6l GNU/Linux. Headless, Wifi connection, using wicd (due to reliability problems with network-manager). Rebuilt from scratch using NOOBS a week ago due to a MUNGed apt-get update on previous installation - long story.

Using package wview to collect and publish weather. Every minute, it does an ssh to my web hosting company to update files of changed weather conditions. I know that the connection is lost when I check my web site and the pages have not been updated for long periods. Early this morning, it had been an hour. I was unable to ssh into the Raspi. I had to power-cycle to get everything working again.

This has happened several times over the last week. I thought I had solved it by moving the powered USB Hub/Wifi dongle further from the Raspi. It ran for 2 days before failing again.

Following is what I collected from the logs. The "bad checksum" are all on my DNS entries. They seem suspicious, but they might just be a sympton rather than a cause. Any help would be greatly appreciated. JimR

debug Mar 15 01:17:27 raspberrypi kernel: [213216.734642] UDP: bad checksum. From 4.2.2.2:53 to 192.168.1.115:49383 ulen 120 Mar 15 01:17:36 raspberrypi kernel: [213225.950854] UDP: bad checksum. From 4.2.2.2:53 to 192.168.1.115:49383 ulen 120 Mar 15 01:17:50 raspberrypi kernel: [213239.775166] UDP: bad checksum. From 8.8.8.8:53 to 192.168.1.115:52826 ulen 51 Mar 15 01:17:55 raspberrypi kernel: [213245.100080] UDP: bad checksum. From 4.2.2.2:53 to 192.168.1.115:36986 ulen 103 Mar 15 01:26:03 raspberrypi kernel: [213733.048211] UDP: bad checksum. From 8.8.4.4:53 to 192.168.1.115:32881 ulen 118 Mar 15 01:27:57 raspberrypi kernel: [213847.124662] UDP: bad checksum. From 4.2.2.2:53 to 192.168.1.115:44899 ulen 120

syslog same

daemon.log Mar 15 01:17:18 raspberrypi ntpd[2070]: ntpd 4.2.6p5@1.2349-o Fri May 18

20:30:57 UTC 2012 (1) Mar 15 01:17:18 raspberrypi ntpd[2071]: proto: precision = 1.000 usec Mar 15 01:17:18 raspberrypi ntpd[2071]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Mar 15 01:17:18 raspberrypi ntpd[2071]: Listen normally on 1 lo 127.0.0.1 UDP 123 Mar 15 01:17:18 raspberrypi ntpd[2071]: peers refreshed Mar 15 01:17:18 raspberrypi ntpd[2071]: Listening on routing socket on fd #18 for interface updates Mar 15 01:17:18 raspberrypi ntpd[2071]: restrict: error in address '::' on line 38. Ignoring... Mar 15 01:17:18 raspberrypi ntpd[2071]: restrict: error in address '::1' on line 42. Ignoring... Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 0.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 1.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 2.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 3.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2078]: signal_no_reset: signal 17 had flags 4000000 Mar 15 01:17:24 raspberrypi dhclient: isc-dhclient-4.2.2 Mar 15 01:17:25 raspberrypi dhclient: isc-dhclient-4.2.2 Mar 15 01:17:36 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2 Mar 15 01:17:36 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium. Mar 15 01:17:36 raspberrypi dhclient: All rights reserved. Mar 15 01:17:36 raspberrypi dhclient: For info, please visit
formatting link
Mar 15 01:17:36 raspberrypi dhclient: Mar 15 01:17:36 raspberrypi dhclient: Listening on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:36 raspberrypi dhclient: Sending on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:36 raspberrypi dhclient: Sending on Socket/fallback Mar 15 01:17:37 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2 Mar 15 01:17:37 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium. Mar 15 01:17:37 raspberrypi dhclient: All rights reserved. Mar 15 01:17:37 raspberrypi dhclient: For info, please visit
formatting link
Mar 15 01:17:37 raspberrypi dhclient: Mar 15 01:17:37 raspberrypi dhclient: Listening on LPF/eth0/b8:27:eb:4d:de:f2 Mar 15 01:17:37 raspberrypi dhclient: Sending on LPF/eth0/b8:27:eb:4d:de:f2 Mar 15 01:17:37 raspberrypi dhclient: Sending on Socket/fallback Mar 15 01:17:38 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2 Mar 15 01:17:38 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium. Mar 15 01:17:38 raspberrypi dhclient: All rights reserved. Mar 15 01:17:38 raspberrypi dhclient: For info, please visit
formatting link
Mar 15 01:17:38 raspberrypi dhclient: Mar 15 01:17:38 raspberrypi dhclient: Listening on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:38 raspberrypi dhclient: Sending on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:38 raspberrypi dhclient: Sending on Socket/fallback Mar 15 01:17:57 raspberrypi ifplugd(wlan0)[1626]: Link beat detected. Mar 15 01:17:57 raspberrypi ifplugd(wlan0)[1626]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'. Mar 15 01:17:57 raspberrypi ifplugd(wlan0)[1626]: client: Ignoring unknown interface wlan0=wlan0. Mar 15 01:17:58 raspberrypi ifplugd(wlan0)[1626]: Program executed successfully. Mar 15 01:17:58 raspberrypi ntpd[2071]: Listen normally on 2 wlan0 192.168.1.115 UDP 123 Mar 15 01:17:58 raspberrypi ntpd[2071]: peers refreshed Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 0.debian.pool.ntp.org

-> 199.102.46.73 Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 1.debian.pool.ntp.org

-> 199.7.177.206 Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 2.debian.pool.ntp.org

-> 198.199.100.18 Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 3.debian.pool.ntp.org

-> 199.102.46.72

messages Mar 15 01:17:18 raspberrypi ntpd[2070]: ntpd 4.2.6p5@1.2349-o Fri May 18

20:30:57 UTC 2012 (1) Mar 15 01:17:18 raspberrypi ntpd[2071]: proto: precision = 1.000 usec Mar 15 01:17:18 raspberrypi ntpd[2071]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123 Mar 15 01:17:18 raspberrypi ntpd[2071]: Listen normally on 1 lo 127.0.0.1 UDP 123 Mar 15 01:17:18 raspberrypi ntpd[2071]: peers refreshed Mar 15 01:17:18 raspberrypi ntpd[2071]: Listening on routing socket on fd #18 for interface updates Mar 15 01:17:18 raspberrypi ntpd[2071]: restrict: error in address '::' on line 38. Ignoring... Mar 15 01:17:18 raspberrypi ntpd[2071]: restrict: error in address '::1' on line 42. Ignoring... Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 0.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 1.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 2.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2071]: Deferring DNS for 3.debian.pool.ntp.org 1 Mar 15 01:17:19 raspberrypi ntpd[2078]: signal_no_reset: signal 17 had flags 4000000 Mar 15 01:17:24 raspberrypi dhclient: isc-dhclient-4.2.2 Mar 15 01:17:25 raspberrypi dhclient: isc-dhclient-4.2.2 Mar 15 01:17:36 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2 Mar 15 01:17:36 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium. Mar 15 01:17:36 raspberrypi dhclient: All rights reserved. Mar 15 01:17:36 raspberrypi dhclient: For info, please visit
formatting link
Mar 15 01:17:36 raspberrypi dhclient: Mar 15 01:17:36 raspberrypi dhclient: Listening on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:36 raspberrypi dhclient: Sending on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:36 raspberrypi dhclient: Sending on Socket/fallback Mar 15 01:17:37 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2 Mar 15 01:17:37 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium. Mar 15 01:17:37 raspberrypi dhclient: All rights reserved. Mar 15 01:17:37 raspberrypi dhclient: For info, please visit
formatting link
Mar 15 01:17:37 raspberrypi dhclient: Mar 15 01:17:37 raspberrypi dhclient: Listening on LPF/eth0/b8:27:eb:4d:de:f2 Mar 15 01:17:37 raspberrypi dhclient: Sending on LPF/eth0/b8:27:eb:4d:de:f2 Mar 15 01:17:37 raspberrypi dhclient: Sending on Socket/fallback Mar 15 01:17:38 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2 Mar 15 01:17:38 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium. Mar 15 01:17:38 raspberrypi dhclient: All rights reserved. Mar 15 01:17:38 raspberrypi dhclient: For info, please visit
formatting link
Mar 15 01:17:38 raspberrypi dhclient: Mar 15 01:17:38 raspberrypi dhclient: Listening on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:38 raspberrypi dhclient: Sending on LPF/wlan0/00:13:ef:d0:23:50 Mar 15 01:17:38 raspberrypi dhclient: Sending on Socket/fallback Mar 15 01:17:57 raspberrypi ifplugd(wlan0)[1626]: Link beat detected. Mar 15 01:17:57 raspberrypi ifplugd(wlan0)[1626]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'. Mar 15 01:17:57 raspberrypi ifplugd(wlan0)[1626]: client: Ignoring unknown interface wlan0=wlan0. Mar 15 01:17:58 raspberrypi ifplugd(wlan0)[1626]: Program executed successfully. Mar 15 01:17:58 raspberrypi ntpd[2071]: Listen normally on 2 wlan0 192.168.1.115 UDP 123 Mar 15 01:17:58 raspberrypi ntpd[2071]: peers refreshed Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 0.debian.pool.ntp.org

-> 199.102.46.73 Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 1.debian.pool.ntp.org

-> 199.7.177.206 Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 2.debian.pool.ntp.org

-> 198.199.100.18 Mar 15 01:18:01 raspberrypi ntpd_intres[2078]: DNS 3.debian.pool.ntp.org

-> 199.102.46.72

Reply to
JimR
Loading thread data ...

To elimnate the hub/cables what happens with the WiFi dongle plugged straight into the Pi?

Is the WiFi dongle on the "compatible" list?

PSU up to powering everything?

--
Cheers 
Dave.
Reply to
Dave Liquorice

Thanks for the suggestions Dave. I tried connecting the WiFi dongle directly to the Raspi, but no joy. I could not ssh to it at all, and there was no evidence that it was ssh-ing out to my web host.

I bought the whole thing as a kit from Prestige Milano (via Amazon), so I sort of assumed that they would sell compatible components.

I just received another Raspi from a different seller, CanaKit, so I decided to try the PSU from it on the original unit. Sure enough, I am now able to connect. The original PSU was rated at 1000 mA, and the new one at 1.0 A, so they "should" perform identically.

I can't tell if the WiFi dongle is on the compatible list -- there are no external manufacturer markings. In the syslog and dmesg, it only shows manufacturer as Realtek, but I think that is the chipset, not the actual manufacturer.

I'll have to let it run for a couple of days to see if the original error reappears.

Cheers,

JimR

Reply to
JimR

That sounds a bit odd. With it plugged into the Pi what does lsusb tell you? The two hex numbers after ID are the vendor and product indenties that the system uses to load the correct drivers etc. It is those rather than human friendly names that are important to the system.

Ah "should"... having followed the PSU related threads in here a 1A PSU is pushing it for a Model B Pi, WiFi etc. The steady state is probably OK but during boot it's anything but steady state and it only takes a tiny glitch to upset things. The quality/length of cable from the PSU to Pi can also have an effect, 0.5 ohm @ 0.5A is 0.25 V, doesn't sound much but the Pi only has a tolerance of +4.75 to +5.25 (0.5V). So if the PSU is outputing 5.0V that cable drop will push the voltage at the Pi right to lower tolerance.

--
Cheers 
Dave.
Reply to
Dave Liquorice

1.0 A is marginal for powering the system you're describing. I wouldn't attempt to run with such a low current rating.

I see Dave Liquorice has picked up on the same thing.

Dave

Reply to
Dave Higton

lsusb shows:

0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter

Looking at

formatting link
there are 4 or 5 different listings with those hex digits, but the last one actually says Realtek Semiconductor Corp., so perhaps it was actually manufactured by them.

Anyway, it has been running stably now for almost 3 days, so perhaps my problems have passed.

Thanks for your help

JimR

Reply to
JimR

An extra half AMP is massive, and glitches will be smoothed by the input capacitor. Mine work marvelously with a VodaNet USBdongle3G. Does WiFi use more?

Reply to
Unknown

so

1A PSU

probably

takes a

PSU

sound

if

the

Who said anything about an *extra* half amp? A model B with WiFi dongle is around the current. So with a poor quality and or long power lead the lower voltage limit is getting rather close.

How much energy do you think that tiny capcitor holds?

--
Cheers 
Dave.
Reply to
Dave Liquorice

0.5 x C x V^2 Joules!

;-)

Reply to
mm0fmf

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.