[rt-users] RT boilerplate error: Log file '/local/rt3/var/log/rt.log' couldn't be written or created
Mauricio Tavares
raubvogel at gmail.com
Fri Feb 24 14:29:34 EST 2012
On Fri, Feb 24, 2012 at 1:26 PM, Richard McMahon <rgm at ast.cam.ac.uk> wrote:
>
>>>
>>> This produces the error.
>>>
>>> Log file '/local/rt3/var/log/rt.log' couldn't be written or created.
>>> RT can't run. at /local/rt3/lib/RT.pm line 318.
>>>
>>> Is there a way to change the location of the of rt.log from within a perl
>>> script. I do not have root priveledges and only want read access for
>>> queries using the API.
>>>
>> I do not know if this helps, but in RT_SiteConfig.pm you could
>> set, for instance,
>>
>> Set($LogDir,'/tmp/');
>> Set($LogToFileNamed, 'rt.log');
>>
>> or wherever it needs to go. About /local/rt3/var/log/rt.log, I wonder
>> who owns /local/rt3/var/log.
>>
>>
>
> thanks
>
> on our system:
>
> /local/rt3/var/log/rt.log is owned by apache
>
> /local/rt3/etc/RT_Config.pm and
> /local/rt3/etc/RT_SiteConfig.pm are owned by root
>
> r.
Sounds like my setup. If this was an ubuntu install, I would see
(or ask someone to do the deed) if apparmor is not allowing the apache
user to create /local/rt3/var/log/rt.log.
More information about the rt-users
mailing list