Bug 984426 - NM-dispatcher doesn't run on boot
NM-dispatcher doesn't run on boot
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: NetworkManager (Show other bugs)
19
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Dan Williams
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-15 04:25 EDT by Kamil Páral
Modified: 2013-07-15 08:12 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-15 08:12:02 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
journal after boot (150.29 KB, text/plain)
2013-07-15 04:27 EDT, Kamil Páral
no flags Details

  None (edit)
Description Kamil Páral 2013-07-15 04:25:36 EDT
Description of problem:
NetworkManager-dispatcher.service is enabled, but does not run after computer boots:

$ systemctl status NetworkManager-dispatcher.service 
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
   Active: inactive (dead) since Mon 2013-07-15 07:51:52 CEST; 9s ago
  Process: 787 ExecStart=/usr/libexec/nm-dispatcher.action (code=exited, status=0/SUCCESS)

The process seems to exit correctly, but I would expect it to be always running and executing scripts from /etc/NetworkManager/dispatcher.d/ on network changes.

I can start the service manually and then the process is running. But I reboot or suspend/resume the machine, the process will have exited again.

This worked correctly on Fedora 18, the dispatcher process was running all the time - after boot and after resume.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.8.2-8.git20130709.fc19.x86_64

How reproducible:
always

Steps to Reproduce:
1. enable NetworkManager-dispatcher.service
2. reboot
3. see its status, it's exited
Comment 1 Kamil Páral 2013-07-15 04:27:26 EDT
Created attachment 773588 [details]
journal after boot
Comment 2 Kamil Páral 2013-07-15 08:04:08 EDT
I tried in a freshly installed VM (I had to enable and start the service). After boot, the process seems to be running, for a while, then it exits:

[root@localhost ~]# systemctl status NetworkManager-dispatcher.service
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
   Active: active (running) since Mon 2013-07-15 08:00:38 EDT; 10s ago
 Main PID: 397 (nm-dispatcher.a)
   CGroup: name=systemd:/system/NetworkManager-dispatcher.service
           └─397 /usr/libexec/nm-dispatcher.action

[root@localhost ~]# systemctl status NetworkManager-dispatcher.service
NetworkManager-dispatcher.service - Network Manager Script Dispatcher Service
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager-dispatcher.service; enabled)
   Active: inactive (dead) since Mon 2013-07-15 08:00:52 EDT; 59s ago
  Process: 397 ExecStart=/usr/libexec/nm-dispatcher.action (code=exited, status=0/SUCCESS)
Comment 3 Kamil Páral 2013-07-15 08:12:02 EDT
I learned from jklimes that this is an expected behavior:

<jklimes> kparal: the dispatcher is not supposed to be running all the time. Rather it runs on an event (e.g. connection up) do the work and keeps running for 10s and exits.
<jklimes> kparal: it has a command line --persist to keep it running all the time
<jklimes> for debugging you can use: /usr/libexec/nm-dispatcher.action --persist --debug

I got confused because in F18 I believe the process was running all the time.

Never mind, sorry for the noise. Closing as NOTABUG.

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