Bug 767859 - nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' exited with error status 3.
Summary: nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' e...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chrony
Version: 16
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Miroslav Lichvar
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-15 01:46 UTC by David Kovalsky
Modified: 2014-03-31 23:46 UTC (History)
3 users (show)

Fixed In Version: chrony-1.26-5.20110831gitb088b7.fc16
Clone Of:
Environment:
Last Closed: 2012-02-22 02:01:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description David Kovalsky 2011-12-15 01:46:38 UTC
My syslog is full of these messages:
nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/11-dhclient' exited with error status 3. It's always the last line printed after I successfully connect to the network, get IP address and everything. 

The script should ideally terminate with zero return code to rid the syslog of the nothing saying message. Or in the other case, fix the underlying issue why it bails out every time with return code 3 :)


dhclient-4.2.3-4.P1.fc16.x86_64

Comment 1 Jiri Popelka 2011-12-15 10:24:27 UTC
/etc/NetworkManager/dispatcher.d/11-dhclient
actually just calls scripts from /etc/dhcp/dhclient.d/

I guess the source of the non-zero return code could be
the /etc/dhcp/dhclient.d/chrony.sh because F16 uses
Chrony as the default NTP client.

CCing Chrony maintainer as Mirek is also author of the 11-dhclient script.

Comment 2 Miroslav Lichvar 2011-12-15 10:49:57 UTC
I don't see where the chrony dhclient script or the chrony-helper script could return 3. I suspect it actually comes from the "service ntpd condrestart" call in the ntp dhclient script.

What scripts do you see in /etc/dhcp/dhclient.d ? Do you have enabled chronyd or ntpd service?

Comment 3 David Kovalsky 2011-12-15 11:17:42 UTC
kovinek:/etc/dhcp/dhclient.d
(0) # ll
total 4
-rwxr-xr-x 1 root root 547 Sep  6 17:27 chrony.sh


# service chronyd status
Redirecting to /bin/systemctl  status chronyd.service
chronyd.service - NTP client/server
          Loaded: loaded (/lib/systemd/system/chronyd.service; disabled)
          Active: inactive (dead)
          CGroup: name=systemd:/system/chronyd.service

kovinek:/etc/dhcp/dhclient.d
# echo $?
3


 # yum -q list installed \*chrony\* \*ntp\*
Installed Packages
chrony.x86_64                                1.26-3.20110831gitb088b7.fc16               @fedora   
fontpackages-filesystem.noarch               1.44-2.fc15                                 @fedora/15



Let me know if you need anything else.

Comment 4 Miroslav Lichvar 2011-12-15 11:31:08 UTC
Ok, thanks. Let's reassign it to chrony.

As a workaround, you can uninstall the chrony package :).

Comment 5 Fedora Update System 2012-02-10 16:56:22 UTC
chrony-1.26-4.20110831gitb088b7.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/chrony-1.26-4.20110831gitb088b7.fc16

Comment 6 Fedora Update System 2012-02-10 21:58:26 UTC
Package chrony-1.26-4.20110831gitb088b7.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing chrony-1.26-4.20110831gitb088b7.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-1531/chrony-1.26-4.20110831gitb088b7.fc16
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2012-02-15 14:08:31 UTC
chrony-1.26-5.20110831gitb088b7.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/chrony-1.26-5.20110831gitb088b7.fc16

Comment 8 Fedora Update System 2012-02-22 02:01:07 UTC
chrony-1.26-5.20110831gitb088b7.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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