mod_wsgi: Unable to change working directory to '/home/maas'

Bug #1380682 reported by Gavin Panella
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
maas (Ubuntu)
New
Undecided
Unassigned

Bug Description

The following are the first three lines in error.log after starting apache2 on Trusty, with packages built from trunk r3243, freshly installed:

[Mon Oct 13 16:17:42.112043 2014] [:alert] [pid 29378:tid 140674480793472] (2)No such file or directory: mod_wsgi (pid=29378): Unable to change working directory to '/home/maas'.
[Mon Oct 13 16:17:42.112181 2014] [:alert] [pid 29379:tid 140674480793472] (2)No such file or directory: mod_wsgi (pid=29379): Unable to change working directory to '/home/maas'.
[Mon Oct 13 16:17:42.112729 2014] [mpm_event:notice] [pid 29375:tid 140674480793472] AH00489: Apache/2.4.7 (Ubuntu) mod_wsgi/3.4 Python/2.7.6 configured -- resuming normal operations

There is no /home/maas directory (i.e. it's not a permissions issue).

I think the "working directory" message appears twice because Apache is configured to run mod_wsgi in 2 processes.

It doesn't appear to affect operation.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

Isn't this really a packaging bug?

Gavin Panella (allenap)
no longer affects: maas
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.