Created attachment 521577 [details]
An fpaste-server failure traceback from /var/log/httpd/error_log
Description of problem:
After clean installation of fpaste-server, using default sample configuration
fails a traceback in /var/log/httpd/error_log (attached)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install fpaste-server
2. Use sample config:
cp /etc/httpd/conf.d/fpaste_server.conf.sample /etc/httpd/conf.d/fpaste_server.conf
3. service httpd restart
4. Access the server URL with a browser.
Accessing with a browser the service URL result in "Internal Server Error"
and the server logs contain the attached traceback.
Working fpaste server
I also tried to follow the guidelines in:
* Got the same failure after going through all the steps, so this
problem does not seem to relate to some configuration error.
* Some tasks could have been done by the package itself. As a minimum
creating the 'fpaste' user should be the package responsibility
(including a reserved UID etc.)
* If an sqlite3 configuration can be made to work out of the box (without
editing files etc.) maybe it should be the default configuration (including
the required dependencies), so a minimal fpaste-server (e.g: on some local
network) can be made to work "out-of-the-box" without any manual intervention.
* I know this is not specific to fpaste-server, but configuration files should
be somewhere under /etc and not /usr.
I've just run through the install again on F15 without this issue. I will build out a fresh F15 install in the morning and double-check, however I don't think there is any problems on this end.
I did note a couple typos in the INSTALL.rst, but I'm supposing since you are past them, it didn't affect much.
As for the comments you have made above not related to the error. I do understand your desire to have the configuration be simple. Standing up an fpaste-server instance with sqlite3 is actually quite simple, I agree. But since we want this to be a robust server application, it's probably better that we use something like postgresql or mysql at a minimum.
Not sure about the reference to /etc vs /usr other than to say that I normally agree. The settings.py is just how Django does things and thus part of their normal configuration setup.
In the meantime, if you could figure out what package is giving that weird ctypes error, I'd be most appreciative.
Oh, I missed one comment. You mentioned the creation of the fpaste user. Well, that user is only for the web interface, not to run a service and thus why it was not created during package install. If the fpaste user actually were the one running the process (in this case, it's apache) I would have done so.
OK, the culprit is selinux (setenforce 0 "solved" it)
After consulting /var/log/audit/audit.log and using audit2why, the minimal
setting that solved the problem (with setenforce 1) was:
setsebool -P httpd_tmp_exec 1
With this, the fpaste-server work as advertised.
I think that you can add this to your howto, but maybe the selinux fedora
team would have better idea. They should probably add specific rules
for this service to fedora targeted policy (re-assign the bug?)
Interesting to say the least. Thanks for that tidbit. I've added a mention of it in the updated INSTALL.rst.
Also, I misspoke previously, the fpaste user is actually created to managed the postgresql database.
Thanks for your help on this.
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: