Networking Service Status Active(Exited) after boot

[paulweakley]

Raspberry Pi 3, JessieLite with the latest raspbian updates. Started with the version that was released May 10th.

Every time I reboot the Pi I can connect via SSH for a few seconds and then the connection is lost. When connected to the HDMI I can see that the networking service exits right after the boot. Status is active (exited). I try restarting the service and using dhclient to get an IP address but no luck. I've tried a flush, setting the IP to 0.0.0.0 and nothing works. I'd post the output here but that would require me to type everything so I'm hoping that someone has had this issue before and knows exactly what to fix.

For reference, isc-dhcp-service and hostapd have been installed but they are disabled on boot so they should not affect anything.

Other notables is that when the service is running I have an interface that shows as "wwan0" with a local ip address starting with 169.254

Any advice would be greatly appreciated. I'm rather stuck here. It happens a lot for me and some times I can recover but this time I've had no luck. I've created new SD card images and they all eventually get here so I'm not sure what the problem could be. I've installed all the same tools and packages with a Wheezy image and they worked perfectly but since I'm using a Pi 3 now I'm stuck with Jessie.

EDIT:
I was able to force an IP address to it finally and here is the outputs that I pulled.

After boot: sudo service networking status
● networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
/lib/systemd/system/networking.service.d
└─network-pre.conf
Active: active (exited) since Sun 2016-05-29 16:16:12 UTC; 7min ago
Process: 282 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS)

May 29 16:16:11 raspberrypi systemd[1]: Starting LSB: Raise network interfaces....
May 29 16:16:12 raspberrypi wpa_supplicant[439]: Successfully initialized wpa_supplicant
May 29 16:16:12 raspberrypi networking[282]: Configuring network interfaces...done.
May 29 16:16:12 raspberrypi systemd[1]: Started LSB: Raise network interfaces..

Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.

Run: sudo service networking restart
● networking.service - LSB: Raise network interfaces.
Loaded: loaded (/etc/init.d/networking)
Drop-In: /run/systemd/generator/networking.service.d
└─50-insserv.conf-$network.conf
/lib/systemd/system/networking.service.d
└─network-pre.conf
Active: active (running) since Sun 2016-05-29 16:23:26 UTC; 6s ago
Process: 1649 ExecStop=/etc/init.d/networking stop (code=exited, status=0/SUCCESS)
Process: 1768 ExecStart=/etc/init.d/networking start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/networking.service
└─1852 /sbin/wpa_supplicant -s -B -P /run/wpa_supplicant.wlan0.pid -i wlan0 -D nl80211,wext -c /etc/wpa_supplicant/wpa_supplicant.conf

May 29 16:23:25 raspberrypi wpa_supplicant[1851]: Successfully initialized wpa_supplicant
May 29 16:23:26 raspberrypi networking[1768]: Configuring network interfaces...ifup: interface eth0 already configured
May 29 16:23:26 raspberrypi networking[1768]: done.
May 29 16:23:26 raspberrypi systemd[1]: Started LSB: Raise network interfaces..

Warning: Unit file changed on disk, 'systemctl daemon-reload' recommended.

Output from ifconfig
eth0 Link encap:Ethernet HWaddr b8:27:eb:c7:83:90
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:783 errors:0 dropped:47 overruns:0 frame:0
TX packets:114 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42276 (41.2 KiB) TX bytes:19130 (18.6 KiB)

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:65536 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:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

wlan0 Link encap:Ethernet HWaddr b8:27:eb:92:d6:c5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:43 errors:0 dropped:43 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21188 (20.6 KiB) TX bytes:0 (0.0 B)

wwan0 Link encap:Ethernet HWaddr 02:aa:df:a8:2a:73
inet addr:169.254.221.242 Bcast:169.254.255.255 Mask:255.255.0.0
inet6 addr: fe80::b989:39dc:c33f:6896/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:9129 (8.9 KiB)

[epoch1970]

Hmm. "wwan0" with a "fake" MAC address sounds like a typo in a config file somewhere.
Have you checked /etc/network/interfaces and other config files to see where this wwan0 thing is defined?

My guess is that a typo makes networking fail for wifi, and it takes down ethernet config at the same time.

[paulweakley]

Yes, I checked that and nothing defined in the network interfaces but I had left a fona device plugged in to the usb port so once I removed that I haven't seen the wwan in the interfaces list but the initial problem still persists. Also installed is ppp but I've had these issues even without that installed so I don't believe it's the cause.

[paulweakley]

So I figured out the issue, after much exploring I found that the contents of /etc/network/interfaces had only the one line for the ethernet:

iface eth0 inet manual

so I added these two lines above it after comparing the file to wheezy versions:

auto eth0
allow-hotplug eth0


and now I haven't seen the issue after several reboots


Edit:
As a side note, the exit status of the networking service doesn't seem to be involved in the inability to retain the IP address. After this fix is applied it still has the same exit code but the ethernet port keeps it the ip address just fine

[epoch1970]

As a side note, the exit status of the networking service doesn't seem to be involved in the inability to retain the IP address. After this fix is applied it still has the same exit code but the ethernet port keeps it the ip address just fine

Yeah, well. Systemd exit codes... Have you tried looking at the systemd event journal?
I'm being sarcastic. I am definitely not a fan of systemd.

Glad you solved your issue!