Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#32131 - [fcgiwrap] systemd service file hangs

Attached to Project: Community Packages
Opened by skydrome (skydrome) - Sunday, 21 October 2012, 03:23 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 17 November 2012, 11:55 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
systemd hangs when trying to start fcgiwrap

from journal:
systemd[1]: Starting Simple server for running CGI applications over FastCGI...
spawn-fcgi[1308]: spawn-fcgi: child spawned successfully: PID: 1309
systemd[1]: PID file /var/run/fcgiwrap.pid not readable (yet?) after start.
systemd[1]: fcgiwrap.service operation timed out. Terminating.
systemd[1]: Failed to start Simple server for running CGI applications over FastCGI.
systemd[1]: Unit fcgiwrap.service entered failed state.


followed https://wiki.archlinux.org/index.php/Nginx#fcgiwrap
same results using socket method
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Saturday, 17 November 2012, 11:55 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 1.0.3-4.
Comment by Daniel Wallace (gtmanfred) - Sunday, 21 October 2012, 03:46 GMT
in my opinion this package should be rebuilt from a git archive of this package, as socket activation was only recently added
https://github.com/gnosek/fcgiwrap/commit/9836d6d22ac22fe7be584da2006ae8d9479096cc

this actually worked perfectly for me after building from git and enabling the default .socket file
Comment by skydrome (skydrome) - Sunday, 21 October 2012, 16:46 GMT
the rc init script worked as expected, the only thing i can think of is that when fcgiwrap starts it outputs a line saying it started, maybe systemd doesnt like that?
Comment by Lukas Fleischer (lfleischer) - Saturday, 03 November 2012, 21:24 GMT
1.0.3-4 was built from Git and includes proper systemd support (including socket activation). Does that fix everything you mentioned in the bug report?
Comment by skydrome (skydrome) - Sunday, 04 November 2012, 02:46 GMT
systemctl start fcgiwrap:
systemd[1]: Started Simple CGI Server.
fcgiwrap[6594]: Cannot get script name, are DOCUMENT_ROOT and SCRIPT_NAME (or SCRIPT_FILENAME) set and is the script executable?
fcgiwrap[6594]: Status: 403 Forbidden
fcgiwrap[6594]: Content-type: text/plain
fcgiwrap[6594]: 403Status: 502 Bad Gateway
fcgiwrap[6594]: Content-type: text/plain
fcgiwrap[6594]: An error occurred while reading CGI reply (no response received)

ls /run:
srwxr-xr-x 1 root root 0 fcgiwrap.sock

pgrep fcgi:
nothing
Comment by Dave Reisner (falconindy) - Sunday, 04 November 2012, 02:56 GMT
You're supposed to start the socket, not the service.
Comment by skydrome (skydrome) - Sunday, 04 November 2012, 04:20 GMT
argh yes, i removed the old service file that i forgot about and started fcgiwrap.socket:
Loaded: loaded (/usr/lib/systemd/system/fcgiwrap.socket; enabled)
Active: active (listening) since Sun, 2012-11-04 00:17:18 EDT; 9s ago
CGroup: name=systemd:/system/fcgiwrap.socket
systemd[1]: Stopping fcgiwrap Socket.
systemd[1]: Starting fcgiwrap Socket.
systemd[1]: Listening on fcgiwrap Socket.
Comment by Dave Reisner (falconindy) - Sunday, 04 November 2012, 04:22 GMT
Right, that part is easy... Does fcgiwrap startup on the first request?
Comment by Cedric Girard (Xdark) - Monday, 05 November 2012, 10:20 GMT
Yes for me.

Loading...