[Bug 783839] New: systemd does not start service
https://bugzilla.novell.com/show_bug.cgi?id=783839 https://bugzilla.novell.com/show_bug.cgi?id=783839#c0 Summary: systemd does not start service Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bzb.dev001@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20100101 Firefox/15.0.1 I'm running on opensuse 12.2 32bit with lxde and using systemd to startup a manually compiled version of apache httpd. After performing the steps below, httpd is not running. I've read http://doc.opensuse.org/documentation/html/openSUSE/opensuse-reference/cha.s... but not helpful. My manually compiled httpd is located in /usr/local/bin/apache-2.2.23 and I have verified that httpd is properly configured and can be invoked manually. I created /etc/systemd/system/myhttpd.target. This file is shown below. [Unit] Description=my apache httpd After=syslog.target network.target Before=getty@tty1.service [Service] Type=forking PIDFile=/usr/local/bin/httpd-2.2.23/logs/httpd.pid ExecStart=/usr/local/bin/httpd-2.2.23/bin/apachectl -k start ExecReload=/usr/local/bin/httpd-2.2.23/bin/apachectl -k restart ExecStop=/usr/local/bin/httpd-2.2.23/bin/apachectl -k stop [Install] WantedBy=multi-user.target I then executed the following command at the console. # systemctl start myhttpd.target # systemctl status myhttpd.target Loaded: loaded (/etc/systemd/system/my-httpd.target; enabled) Active: active since Fri, 05 Oct 2012 21:37:55 -0400; 32s ago # systemctl --failed UNIT LOAD ACTIVE SUB JOB DESCRIPTION NetworkManager.service loaded failed failed Network Manager xinetd.service loaded failed failed LSB: Starts the xinet daemon. Be aware that xinetd doesn't start if no service is configured to run under it. To enable xinetd services go to YaST Network Services (xinetd) section. LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. JOB = Pending job for the unit. 2 units listed. Pass --all to see inactive units, too. # ps -ley|grep -i http NOTE:no httpd entries are shown. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783839 https://bugzilla.novell.com/show_bug.cgi?id=783839#c1 --- Comment #1 from Y T <bzb.dev001@gmail.com> 2012-10-06 06:00:44 EDT --- Rebooting the system does not start the service either -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783839 https://bugzilla.novell.com/show_bug.cgi?id=783839#c2 Michal Vyskocil <mvyskocil@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mvyskocil@suse.com InfoProvider| |fcrozat@suse.com AssignedTo|bnc-team-screening@forge.pr |fcrozat@suse.com |ovo.novell.com | --- Comment #2 from Michal Vyskocil <mvyskocil@suse.com> 2012-10-09 07:25:27 UTC --- If you want to start service, file have to end with a suffix **.service**. The .target type cannot be used it. See documentation for details http://0pointer.de/public/systemd-man/systemd.target.html http://0pointer.de/public/systemd-man/systemd.service.html @frederic: I would say systemd have to be strict here and report the error - what do you think? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783839 https://bugzilla.novell.com/show_bug.cgi?id=783839#c3 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #3 from Frederic Crozat <fcrozat@suse.com> 2012-10-09 13:00:59 UTC --- The error is reported in the system logs (dmesg or systemd-journalctl), when the file is being parsed (either at startup or when running systemctl daemon-reload, which is needed for systemd to read new or modified unit files). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783839 https://bugzilla.novell.com/show_bug.cgi?id=783839#c4 --- Comment #4 from Michal Vyskocil <mvyskocil@suse.com> 2012-10-10 07:48:50 UTC --- Well, that's true - in this case I would close it as INVALID, beacuse systemd behaves properly. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783839 https://bugzilla.novell.com/show_bug.cgi?id=783839#c5 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #5 from Frederic Crozat <fcrozat@suse.com> 2012-10-10 07:56:59 UTC --- closing as INVALID then -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com