Bug 848892 - Cherokee systemd service never starts due to a timeout
Summary: Cherokee systemd service never starts due to a timeout
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: cherokee
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Lisý
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-16 17:50 UTC by Jean-François Fortin Tam
Modified: 2012-12-06 02:48 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-06 02:48:30 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jean-François Fortin Tam 2012-08-16 17:50:37 UTC
SELinux is disabled.


[root@krom jeff]# service cherokee enable
Redirecting to /bin/systemctl enable  cherokee.service

[root@krom jeff]# service cherokee start
Redirecting to /bin/systemctl start  cherokee.service

(wait a minute or so)

Job failed. See system journal and 'systemctl status' for details.



[root@krom jeff]# service cherokee status
Redirecting to /bin/systemctl status  cherokee.service
cherokee.service - Cherokee Lightweight Web Server
	  Loaded: loaded (/usr/lib/systemd/system/cherokee.service; enabled)
	  Active: failed (Result: timeout) since Fri, 10 Aug 2012 16:12:10 -0400
	  CGroup: name=systemd:/system/cherokee.service



And yet, *during the minute where service cherokee start is running* (ie: before it supposedly spits a timeout error), cherokee is actually running fine (you can access the web server's pages and all that). It is only when systemd "gives up" that it kills the cherokee server and everything becomes inaccessible.

Comment 1 Paweł 2012-10-05 18:47:22 UTC
Solution https://bugzilla.redhat.com/show_bug.cgi?id=786748#c3

Comment 2 Jean-François Fortin Tam 2012-12-06 02:48:30 UTC
Works for me now in Fedora 18.


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