Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 401845 - www-apps/bugzilla-4.0.4 webapp-config upgrade from 4.0.2 - start-stop-daemon: failed to exec `/var/www/myhost/htdocs/jobqueue.pl': Bad file descriptor
Summary: www-apps/bugzilla-4.0.4 webapp-config upgrade from 4.0.2 - start-stop-daemon:...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Server (show other bugs)
Hardware: All All
: Normal normal (vote)
Assignee: Gentoo Web Application Packages Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-01 19:47 UTC by Jaak Ristioja
Modified: 2012-03-10 14:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jaak Ristioja 2012-02-01 19:47:58 UTC 
I had bugzilla 4.0.2 installed and I also installed 4.0.4 (new slot?). After running webapp-config --upgrade to upgrade my bugzilla installation, the bugzilla-queue initscript stopped working:

# /etc/init.d/bugzilla-queue restart
 * Stopping bugzilla-queue ...                                                                                                           [ ok ]
 * Starting bugzilla-queue ...
 * start-stop-daemon: failed to exec `/var/www/myhost/htdocs/jobqueue.pl': Bad file descriptor
 * start-stop-daemon: failed to start `/var/www/myhost/htdocs/jobqueue.pl'                                                  [ !! ]
 * ERROR: bugzilla-queue failed to start

The issue appears to be that after running webapp-config to upgrade the host, the jobqueue.pl file lacks execute permissions (has 644). A workaround for the issue appears to be to chmod a+x /var/www/myhost/htdocs/jobqueue.pl
Comment 1 Christian Ruppert (idl0r) gentoo-dev 2012-02-28 14:54:46 UTC 
Please try 4.2.
Comment 2 Jaak Ristioja 2012-02-28 15:07:15 UTC 
(In reply to comment #1)
> Please try 4.2.

Uhmmn...no. I don't have the hardware resources for that. The current installation is running on a production site and I may not upgrade to 4.2 right now. If you bump to 4.0.5 to also fix a CSRF, I'll consider it during the next maintenance downtime.
Comment 3 Jaak Ristioja 2012-03-10 14:37:15 UTC 
Upgrade from 4.0.4 to 4.0.5 doesn't have this problem. Thanks!