Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • State Suggested Answer
  • Replies 18 replies
  • Answers 2 answers
  • Subscribers 676 subscribers
  • Views 1940 views
  • Users 0 members are here
Related

Raspberry Pi network dies

Former Member

Hi,

 

I have a raspberry Pi2 but at least once a day the network dies.

 

The last thing is normally a NTP run and I have uninstalled it and reinstalled but still the same thing happens.

 

The PI is set to get a IP address but on the router has a dedicated IP address.

Parents
  • 0

    Are you using wireless?  Have you checked out the syslog?

  • 0 in reply to screamingtiger

    Wired connection and this is what SYSLOG had

     

    Mar 23 10:17:09 raspberrypi kernel: [ 13.724325] Adding 102396k swap on /var/swap. Priority:-1 extents:2 across:2134012k SSFSMar 23 10:17:09 raspberrypi /usr/sbin/cron[1960]: (CRON) INFO (Running @reboot jobs)Mar 23 10:17:09 raspberrypi ntpd[1948]: ntpd 4.2.6p5@1.2349-o Mon Feb 9 03:34:42 UTC 2015 (1)Mar 23 10:17:09 raspberrypi ntpd[1979]: proto: precision = 1.250 usecMar 23 10:17:09 raspberrypi ntpd[1979]: Listen and drop on 0 v4wildcard 0.0.0.0 UDP 123Mar 23 10:17:09 raspberrypi ntpd[1979]: Listen normally on 1 lo 127.0.0.1 UDP 123Mar 23 10:17:09 raspberrypi ntpd[1979]: peers refreshedMar 23 10:17:09 raspberrypi ntpd[1979]: Listening on routing socket on fd #18 for interface updatesMar 23 10:17:09 raspberrypi ntpd[1979]: restrict: error in address '::' on line 38. Ignoring...Mar 23 10:17:09 raspberrypi ntpd[1979]: restrict: error in address '::1' on line 42. Ignoring...Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 0.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 1.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 2.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[1979]: Deferring DNS for 3.debian.pool.ntp.org 1Mar 23 10:17:09 raspberrypi ntpd[2001]: signal_no_reset: signal 17 had flags 4000000Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: Link beat detected.Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: Executing '/etc/ifplugd/ifplugd.action eth0 up'.Mar 23 10:17:09 raspberrypi dhclient: Internet Systems Consortium DHCP Client 4.2.2Mar 23 10:17:09 raspberrypi dhclient: Copyright 2004-2011 Internet Systems Consortium.Mar 23 10:17:09 raspberrypi dhclient: All rights reserved.Mar 23 10:17:09 raspberrypi dhclient: For info, please visithttps://www.isc.org/software/dhcp/Mar 23 10:17:09 raspberrypi dhclient: Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: Internet Systems Consortium DHCP Client 4.2.2Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: Copyright 2004-2011 Internet Systems Consortium.Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: All rights reserved.Mar 23 10:17:09 raspberrypi ifplugd(eth0)[1597]: client: For info, please visithttps://www.isc.org/software/dhcp/Mar 23 10:17:10 raspberrypi dhclient: Listening on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: Listening on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi dhclient: Sending on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: Sending on LPF/eth0/b8:27:eb:ca:f4:47Mar 23 10:17:10 raspberrypi dhclient: Sending on Socket/fallbackMar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: Sending on Socket/fallbackMar 23 10:17:10 raspberrypi dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:10 raspberrypi ifplugd(eth0)[1597]: client: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:17 raspberrypi dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:17 raspberrypi ifplugd(eth0)[1597]: client: DHCPREQUEST on eth0 to 255.255.255.255 port 67Mar 23 10:17:17 raspberrypi dhclient: DHCPACK from 192.168.0.1Mar 23 10:17:17 raspberrypi ifplugd(eth0)[1597]: client: DHCPACK from 192.168.0.1Mar 23 10:17:17 raspberrypi dhclient: bound to 192.168.0.15 -- renewal in 41528 seconds.Mar 23 10:17:17 raspberrypi ifplugd(eth0)[1597]: client: bound to 192.168.0.15 -- renewal in 41528 seconds.Mar 23 10:17:18 raspberrypi ifplugd(eth0)[1597]: Program executed successfully.Mar 23 10:17:19 raspberrypi ntpd[1979]: Listen normally on 2 eth0 192.168.0.15 UDP 123Mar 23 10:17:19 raspberrypi ntpd[1979]: peers refreshedMar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 0.debian.pool.ntp.org -> 129.70.132.36Mar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 1.debian.pool.ntp.org -> 144.76.117.245Mar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 2.debian.pool.ntp.org -> 193.140.100.41Mar 23 10:17:21 raspberrypi ntpd_intres[2001]: DNS 3.debian.pool.ntp.org -> 178.17.160.12

  • 0 in reply to Former Member

    oh post your auth.log too I am curious about something.

  • 0 in reply to Former Member

    SYSLOG seems all normal here and is from March 23 at 10:17... Have you tried "ifup eth0" after losing the network? This should work on an auto network

    Clem

Reply Children