[ 
https://issues.apache.org/jira/browse/AXIS2C-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549853
 ] 

Senaka Fernando commented on AXIS2C-711:
----------------------------------------

Hi Stefano,
      Did u try using /tmp/axis2c.log instead of /etc/httpd/logs/axis2c.log? I 
guess this is because it doesn't have write access. As you see, it is not your 
user account that needs write access but the account in which the process which 
accesses the file runs. Therefore, if you really want to keep this location, 
you may try a chmod 766 or chmod 777 on your file(s).

I have successfully got the messages logged to the file that I specify instead 
of the apache log, and I used /tmp/axis2.log. This is because the folder /tmp 
has write access.

Regards,
Senaka

> Log messages when deployed to apache written to wrong file
> ----------------------------------------------------------
>
>                 Key: AXIS2C-711
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-711
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/deployment
>    Affects Versions: 1.0.0, 1.1.0
>         Environment: RedHat Enterprise Linux 4 running Apache 2.0.52
>            Reporter: Stefano Pettini
>            Assignee: Damitha Kumarage
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> According to user manual:
> PATH_TO_LOG_FILE has to be replaced with the full path to where you wish to 
> have the Axis2/C log file, for example, /tmp/axis2.log. Note that the log 
> file path should have write access to the daemon user account under which the 
> Apache2 HTTPD process is run.
> It doesn't seem to work: Axis log messages are written to apache's error_log 
> file, not the file specified with PATH_TO_LOG_FILE.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to