Mark is right, your path in the configuration file is relative to any current directory when the logging.config.fileConfig call is logging.config.fileConfig . It depends on the details of your deployment method.
You may need to specify the absolute path to your file, after specifying "test.log" to a directory that, as you know, will be writable by the process executing your code.
Another problem can only be the user rights issue that your Django process runs with: usually when you start the development server, it runs under your account and you usually do not encounter permission problems. When deployed (with Apache and mod_wsgi, say), the Apache process and / or the daemon mod_wsgi process run under different accounts, which may require permission to the corresponding folder.
If you need further help, please tell us more about your deployment with regard to the method, location of the log file directory, etc.
Vinay sajip
source share