Hide Forgot
Description of problem: dansguardian does not start properly (with systemctl) After booting, dansguardian does not start Here are the error messages : [root@fedora ~]# sysctl start dansguardian.service/proc/sys/start: No such file or directory /proc/sys/dansguardian/service: No such file or directory But it starts using /etc/init.d [root@fedora ~]# /etc/init.d/dansguardian startStarting dansguardian (via systemctl): [ OK ] Notice how it then claims to be using systemctl ? odd. Version-Release number of selected component (if applicable): How reproducible: Reboot Steps to Reproduce: 1. 2. 3. Actual results: dansguardian fails to start as above dansguardian fails to start with systemctl Expected results: 1. dansguardian starts with boot. 2. dansguardian starts with systemctl Additional info: See above for error messages.
I've noticed similar behavior with other services, privoxy to be specific. I had an unrelated problem with privoxy https://bugzilla.redhat.com/show_bug.cgi?id=694597 privoxy would fail during the boot process When I tried to start it with systemctl, similar error message sysctl start privoxy.service /proc/sys/start: No such file or directory /proc/sys/privoxy/service: No such file or directory Once I added dansguardian to the start configuration systemctl enable dansguradian.service it all seems to be working as expected, so perhaps it is a problem with systemd.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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" (top right of this page) 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