sometimes the OrangePi PC freezes and I see the following error in kern.log

May  6 11:17:14 orangepipc NetworkManager[554]: <error> [1494058633.9922] platform-linux: do-add-ip4-address[2: 10.45.168.13/24]: failure 17 (File exists)

 

I use static! ip in my OPi and there is no other device using the same ip

 

eth0      Link encap:Ethernet  HWaddr 66:9b:7a:fd:fb:59
          inet addr:10.45.168.13  Bcast:10.45.168.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2731 errors:0 dropped:24 overruns:0 frame:0
          TX packets:3476 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:226456 (226.4 KB)  TX bytes:636217 (636.2 KB)
          Interrupt:114

 

and the following warnings....

May  6 11:17:13 orangepipc NetworkManager[554]: <warn>  [1494058632.7573] SettingsPlugin-Ofono: file doesn't exist: /var/lib/ofono
May  6 11:17:14 orangepipc NetworkManager[554]: <warn>  [1494058633.9910] failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
May  6 11:17:14 orangepipc NetworkManager[554]: <warn>  [1494058633.9930] arping[0x384a18,2]: arping could not be found; no ARPs will be sent
May  6 11:17:16 orangepipc NetworkManager[554]: <warn>  [1494058635.9889] arping[0x384a18,2]: arping could not be found; no ARPs will be sent

 

I googled them but found nothing helpfull,

any ideas?

sometimes the OrangePi PC freezes and I see the following error in kern.log
May  6 11:17:14 orangepipc NetworkManager[554]: [1494058633.9922] platform-linux: do-add-ip4-address[2: 10.45.168.13/24]: failure 17 (File exists)
 
[...]
any ideas?

Are you sure that the kernel log message and the freeze are related? For me this looks like a red herring. Did you ever see this message and everything was working?

Also please define "freezing": network dead incl. ping? ssh stopped? Mouse stoppen (if using a UI)?

Also check the CPU temperature. And the power supply. They cause most freezes and reboots from my little experience.

Harald

I have the same problem with Orange Pi Plus 2:

Sep  5 18:09:40 localhost NetworkManager[553]: <error> [1504624180.7920] platform-linux: do-add-ip4-address[2: 192.168.1.34/24]: failure 17 (File exists)   
Sep  5 18:09:40 localhost NetworkManager[553]: <error> [1504624180.8153] platform-linux: do-add-ip4-route[2: 0.0.0.0/0 100]: failure 3 (No such process)   

Sep  5 18:09:40 localhost NetworkManager[553]: <warn>  [1504624180.8155] default-route: failed to add default route 0.0.0.0/0 via 192.168.1.1 dev 2 metric 100 mss 0 src user with effective metric 100     

I miss connection with orangePi (can't connect via ssh/vnc, can't ping), but internet still works on device. After rebooting everything is fine. This problem repeats every evening.

 

Is it possible to solve this without removing network-manager?

On 9/5/2017 at 10:52 PM, federko said:

I have the same problem with Orange Pi Plus 2:

Is it possible to solve this without removing network-manager?

 

I removed network-manager and configured network via armbian-config - everything is fine more than week.

Using NanoPi Neo with Linux Lap 3.4.113-sun8i #4 SMP PREEMPT Wed Nov 22 13:45:28 CET 2017 armv7l armv7l armv7l GNU/Linux  with current Armbian updated.  Headless server.

 

 I've had the same problem.  The wireless stops working (I think only partially) so I can't ping or ssh the unit.  Interestingly, when I try and ping the wifi dongle LED flashes as I would expect for a ping and the AP wifi light also flashes at the same time.

 

I'm using wifi to connect to the LAN and internet with dhcp (192.168.1.x) and have the ethernet unplugged but with a static IP set to a different network (10.0.0.x).

 

If I turn off the AP wireless, the LED on the wifi dongle goes out and when I start the AP wireless it comes back on.  The AP logs don't show the NanoPi asking for an IP though.

 

Gord_W

 

 

Dec 15 07:06:25 Lap dhclient[819]: DHCPREQUEST of 192.168.1.17 on wlan0 to 192.168.1.1 port 67 (xid=0x49d4e22)
Dec 15 07:06:25 Lap dhclient[819]: DHCPACK of 192.168.1.17 from 192.168.1.1
Dec 15 07:06:25 Lap NetworkManager[434]: <info>  [1513339585.7334]   address 192.168.1.17
Dec 15 07:06:25 Lap NetworkManager[434]: <info>  [1513339585.7336]   plen 24 (255.255.255.0)
Dec 15 07:06:25 Lap NetworkManager[434]: <info>  [1513339585.7338]   gateway 192.168.1.1
Dec 15 07:06:25 Lap NetworkManager[434]: <info>  [1513339585.7339]   server identifier 192.168.1.1
Dec 15 07:06:25 Lap NetworkManager[434]: <info>  [1513339585.7339]   lease time 86400
Dec 15 07:06:25 Lap NetworkManager[434]: <info>  [1513339585.7341]   nameserver '192.168.1.1'
Dec 15 07:06:25 Lap NetworkManager[434]: <info>  [1513339585.7342] dhcp4 (wlan0): state changed bound -> bound
Dec 15 07:06:25 Lap NetworkManager[434]: <error> [1513339585.7368] platform-linux: do-add-ip4-address[4: 192.168.1.17/24]: failure 17 (File exists)                           <<<<<<<<<<<<<<<<<<<   Problem lines
Dec 15 07:06:25 Lap NetworkManager[434]: <error> [1513339585.7385] platform-linux: do-add-ip4-route[4: 0.0.0.0/0 600]: failure 3 (No such process)                            <<<<<<<<<<<<<<<<<<<   Problem lines
Dec 15 07:06:25 Lap dbus[401]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Dec 15 07:06:25 Lap NetworkManager[434]: <warn>  [1513339585.7387] default-route: failed to add default route 0.0.0.0/0 via 192.168.1.1 dev 4 metric 600 mss 0 src user with effective metric 600
Dec 15 07:06:25 Lap dhclient[819]: bound to 192.168.1.17 -- renewal in 33647 seconds.
Dec 15 07:06:25 Lap systemd[1]: Starting Network Manager Script Dispatcher Service...
Dec 15 07:06:26 Lap dbus[401]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Dec 15 07:06:26 Lap systemd[1]: Started Network Manager Script Dispatcher Service.
Dec 15 07:06:26 Lap nm-dispatcher[9137]: req:1 'dhcp4-change' [wlan0]: new request (1 scripts)
Dec 15 07:06:26 Lap nm-dispatcher[9137]: req:1 'dhcp4-change' [wlan0]: start running ordered scripts...

Follow up.

 

After purging NetworkManager (that takes a huge amount of other stuff too) and entering wlan0 and eth0 in /etc/network/interface, it has been up for a few days without the wifi failing.

 

Gord_W

 

Thank you.

But in order to fix and learn something from this problem, we need to see

armbianmonitor -u

... since its probably related to the NetworkManager versions, which can come in three different packages: Jessie, Xenial or Stretch.

Sorry for the slow reply, I just saw it.

I don't know if this is any use to you still, but here it is.

 

root@Lap:~# armbianmonitor -u
System diagnosis information will now be uploaded to http://sprunge.us/SMFU
Please post the URL in the forum where you've been asked for.

 

Since I have removed NetworkManager and added ethernet and wifi details in /etc/network/interface, I've had no problems with wifi.

 

Gord_W