error on 01ifupdown script

[nelson]

When bring the interface up or down I see this message on the logs

May 18 10:03:36 count0 nm-dispatcher[8608]: req:1 'up' [enp2s0], "/etc/NetworkManager/dispatcher.d/01ifupdown": complete: failed with Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.
May 18 10:03:36 count0 NetworkManager[791]: <warn> [1463576616.8466] dispatcher: (29) 01ifupdown failed (failed): Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1.

Tracing the problem I see that the call to /usr/sbin/fanctl is done with incorrect parameters.

If I execute
/etc/NetworkManager/dispatcher.d/01ifupdown enp2s0 down

I get this error
run-parts: /etc/network/if-post-down.d/ubuntu-fan exited with return code 1

ubuntu-fan is doing the call in following way

/usr/sbin/fanctl net "$MODE" "$IFACE"

and the parameters passed by ubuntu-fan are

$MODE=stop
$IFACE=enp2s0

but fanctl expect other parameters as showed on the script's header

--------------
details

lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

$ apt-cache policy network-manager
network-manager:
  Installed: 1.1.93-0ubuntu4
  Candidate: 1.1.93-0ubuntu4
  Version table:
 *** 1.1.93-0ubuntu4 500
        500 http://ar.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.1.93-0ubuntu4
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed May 18 10:50:24 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-04-23 (24 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
IpRoute:
 default via 192.168.1.1 dev enp2s0 proto static metric 100
 169.254.0.0/16 dev enp2s0 scope link metric 1000
 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
 172.18.0.0/16 dev br-76f79dfb13e0 proto kernel scope link src 172.18.0.1 linkdown
 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.8 metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH
 br-76f79dfb13e0 bridge connected /org/freedesktop/NetworkManager/Devices/2 br-76f79dfb13e0 0a9f5c9b-cd67-4fb8-a72d-1811ca6fbb68 /org/freedesktop/NetworkManager/ActiveConnection/1
 docker0 bridge connected /org/freedesktop/NetworkManager/Devices/3 docker0 e5f99f7d-532f-4c52-8749-c78afa9271dd /org/freedesktop/NetworkManager/ActiveConnection/2
 enp2s0 ethernet connected /org/freedesktop/NetworkManager/Devices/0 Wired connection 1 ee3ec6ee-7242-4956-9d19-20ccb19c5fe5 /org/freedesktop/NetworkManager/ActiveConnection/8
 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- --
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Nico Schlömer (nschloe)]

The first error message I'm getting is
```
Sep 12 14:28:41 foobar nm-dispatcher[27267]: /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting primary: " (32-)/4 "

```
(Followed by the error messages in the original post.)

[cristian.tarsoaga (cristian-tarsoaga)]

Same problem. Recently upgraded to ubuntu server 17.10
Networking doesnt't start any interface due to this problem.
Wrong arguments while calling fanctl from ubuntu-fan

[Salamander (taav1-23)]

I had the problem of ubuntu-fan not being installed after the upgrade to 17.10/18.04, please mark ubuntu-fan as a dependency to NetworkManager or something to fix this. It was by pure chance I ended up here to find a way to debug this problem.