Bug 1087883 - dispatcher scripts are not being run
Summary: dispatcher scripts are not being run
Keywords:
Status: CLOSED DUPLICATE of bug 974811
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-15 13:59 UTC by Charles R. Anderson
Modified: 2014-04-16 02:01 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-04-16 02:01:09 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Charles R. Anderson 2014-04-15 13:59:55 UTC
Description of problem:

NetworkManager dispatcher scripts aren't running.  This is causing dnssec-trigger to fail to work properly.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.0-34.git20131003.fc20.x86_64

How reproducible:
always

Steps to Reproduce:
1. install dnssec-trigger and reboot
2. change from one wireless connection to another that uses different dns servers
3. "dnssec-trigger-control status" should show new forwarders as "cache"

Actual results:

First wireless network has 172.30.42.65 handed back by DHCP for DNS servers:

>dnssec-trigger-control status
at 2014-04-14 22:37:42
http fedoraproject.org (66.35.62.166): OK 
cache 172.30.42.65: OK 
state: cache secure

Second wireless network has 192.168.1.1 handed back by DHCP for DNS servers, but the dispatcher scripts didn't run to update unbound:

>dnssec-trigger-control status
at 2014-04-14 22:37:42
http fedoraproject.org (66.35.62.166): OK 
cache 172.30.42.65: OK 
state: cache secure

Expected results:

On connection to second wireless network:

>dnssec-trigger-control status
at 2014-04-14 22:37:42
http fedoraproject.org (66.35.62.166): OK 
cache 192.168.1.1: OK 
state: cache secure

Additional info:

Apr 15 09:33:15 a dbus-daemon[704]: dbus[704]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr 15 09:33:15 a dbus[704]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Apr 15 09:33:15 a dbus-daemon[704]: dbus[704]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.
Apr 15 09:33:15 a dbus[704]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.
Apr 15 09:33:15 a NetworkManager[833]: <warn> Dispatcher failed: (32) Unit dbus-org.freedesktop.nm-dispatcher.service failed to load: No such file or directory.

NetworkManager-openvpn-0.9.9.0-0.1.git20140128.fc20.x86_64
NetworkManager-glib-0.9.9.0-34.git20131003.fc20.x86_64
NetworkManager-vpnc-gnome-0.9.8.2-2.fc20.x86_64
NetworkManager-0.9.9.0-34.git20131003.fc20.x86_64
NetworkManager-vpnc-0.9.8.2-2.fc20.x86_64
NetworkManager-openvpn-gnome-0.9.9.0-0.1.git20140128.fc20.x86_64
NetworkManager-pptp-0.9.8.2-3.fc20.x86_64
NetworkManager-openconnect-0.9.8.0-2.fc20.x86_64
NetworkManager-pptp-gnome-0.9.8.2-3.fc20.x86_64

# locate dispatch | grep nm
/etc/dbus-1/system.d/nm-dispatcher.conf
/usr/libexec/nm-dispatcher.action
/usr/share/dbus-1/system-services/org.freedesktop.nm_dispatcher.service

-rw-r--r--. 1 root root 159 Apr  8 14:34 /usr/share/dbus-1/system-services/org.freedesktop.nm_dispatcher.service

>cat /usr/share/dbus-1/system-services/org.freedesktop.nm_dispatcher.service
[D-BUS Service]
Name=org.freedesktop.nm_dispatcher
Exec=/usr/libexec/nm-dispatcher.action
User=root
SystemdService=dbus-org.freedesktop.nm-dispatcher.service

Comment 1 Charles R. Anderson 2014-04-15 14:51:49 UTC
Same problem with the latest from koji:

NetworkManager-0.9.9.0-37.git20131003.fc20.x86_64
NetworkManager-glib-0.9.9.0-37.git20131003.fc20.x86_64

Comment 2 Charles R. Anderson 2014-04-15 15:24:56 UTC
>ls -l /usr/libexec/nm-dispatcher.action 
-rwxr-xr-x. 1 root root 36048 Apr 15 07:43 /usr/libexec/nm-dispatcher.action*

Comment 3 Charles R. Anderson 2014-04-15 15:26:25 UTC
>ls -l /etc/dbus-1/system.d/nm-dispatcher.conf
-rw-r--r--. 1 root root 465 Apr 15 07:43 /etc/dbus-1/system.d/nm-dispatcher.conf

>cat /etc/dbus-1/system.d/nm-dispatcher.conf
<!DOCTYPE busconfig PUBLIC
 "-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
 "http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>
	<policy user="root">
		<allow own="org.freedesktop.nm_dispatcher"/>
		<allow send_destination="org.freedesktop.nm_dispatcher"/>
    </policy>
    <policy context="default">
		<deny own="org.freedesktop.nm_dispatcher"/>
		<deny send_destination="org.freedesktop.nm_dispatcher"/>
    </policy>
</busconfig>

Comment 4 Charles R. Anderson 2014-04-16 02:01:09 UTC

*** This bug has been marked as a duplicate of bug 974811 ***


Note You need to log in before you can comment on or make changes to this bug.