Created attachment 596905 [details] 01-statuschecker Description of problem: Scripts put into /etc/NetworkManager/dispatcher.d/ don't function properly when 10-sendmail is present. Status vpn-down is not detected when a VPN is disconnected from NetworkManager, but does for vpn-up (I've not tested for other statuses). The same script behaves as expected when 10-sendmail is removed. I've attached a simple script for testing along with my copy of 10-sendmail which has the problem. Version-Release number of selected component (if applicable): sendmail-8.14.5-11.fc16.x86_64 How reproducible: always Steps to Reproduce: 1. Copy 01-statuschecker to /etc/NetworkManager/dispatcher.d/ 2. Make executable 3. Make sure 10-sendmail is also present 4. Connect to a VPN with NetworkManager 5. Disconnect from a VPN with NetworkManager Actual results: StatusChecker - VPN up triggered Expected results: StatusChecker - VPN up triggered StatusChecker - VPN down trigger ed Additional info:
Created attachment 596906 [details] 10-sendmail Buggy 10-sendmail included in my version of sendmail.
I am unable to reproduce (tried with openvpn): # grep statuschecker /var/log/messages Jul 9 13:39:37 localhost dbus-daemon[1071]: statuschecker: StatusChecker - VPN up triggered Jul 9 13:39:37 localhost statuschecker: StatusChecker - VPN up triggered Jul 9 13:40:05 localhost dbus-daemon[1071]: statuschecker: StatusChecker - VPN down triggered Jul 9 13:40:05 localhost statuschecker: StatusChecker - VPN down triggered # ls /etc/NetworkManager/dispatcher.d 00-netreport 01-statuschecker 05-netfs 10-sendmail 11-dhclient 20-chrony # cat /etc/system-release Fedora release 16 (Verne) I also tried on F17, and it also worked as expected. But maybe I got where the problem could be. I guess your hostname is not resolvable after the VPN disconnectiob (e.g. there is no network connectivity or misconfigured DNS). Sendmail needs your hostname to be resolvable and to match with your IP, i.e.: # nslookup `hostname` should return your FQDN and your IP address. You can simply hack this by including your hostname into /etc/hosts to resolve to your loopback interface, e.g.: 127.0.0.1 YOURHOSTNAME localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6 Without this it still works, but there is a slight timeout in sendmail restart, so I think in case you would wait, the vpn-down should show in the log. Please try to add the --no-block to 10-sendmail: /bin/systemctl --no-block try-restart sendmail.service || : And let me know whether it fixes your problem.
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.