Public bug reported: When an error occurs from mod_python on Saucy (which uses Apache 2.4) there is nothing logged. I have tracked this issue down to the value of APLOG_NOERRNO being incorrect. This value is defined to be (APLOG_LEVELMASK + 1); on Apache 2.2, APLOG_LEVELMASK was 7, but on Apache 2.4 it is 15. The value in mod_python's Python code (which sadly can't use the C definition in a direct manner) is hardcoded as 8, but for Apache 2.4 it needs to be updated to 16. This variable is defined in lib/python/mod_python/apache.py, and should be an easy fix. (FWIW, I have not experienced other issues so far with the mod_python 3.3.1 patches for Apache 2.4.) (Also, I will note that the 3.4 and now 3.5 of mod_python from upstream no longer even have this variable: it still exists for backwards-compatibility with old code, but it is defined as 0.)
** Affects: libapache2-mod-python (Ubuntu) Importance: Undecided Status: New ** Patch added: "patch to fix this issue against 3.3.1" https://bugs.launchpad.net/bugs/1247013/+attachment/3897448/+files/aplog_noerrno.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libapache2-mod-python in Ubuntu. https://bugs.launchpad.net/bugs/1247013 Title: mod_python APLOG_NOERRNO unable to log on Apache 2.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1247013/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs