Hi, Joakim,
Just wanted to follow up on this. I'm using the jetty.sh script and was
thinking perhaps it's using the full path to the logs directory when it
should be using a relative path? I'm not seeing this behavior with 9.1.3
and am consistently afterwards so curious what changed.
Thanks,
Rob
On Mon, Apr 7, 2014 at 4:21 PM, Rob Moore <rob.mo...@gmail.com> wrote:
> Thanks again, Joakim.
>
> BTW, the issue I was seeing had to do with the new requestlog.filename
> configuration. I was using requestlog.filename=request.log and saw this
> error:
>
> 2014-04-07 20:57:03.258:INFO:oejs.Server:main: jetty-9.1.4.v20140401
> 2014-04-07 20:57:03.353:WARN:oejuc.AbstractLifeCycle:main: FAILED
> org.eclipse.jetty.server.AsyncNCSARequestLog@60e07ad7:
> java.io.IOException: Cannot write log directory /opt
> java.io.IOException: Cannot write log directory /opt
> at
> org.eclipse.jetty.util.RolloverFileOutputStream.setFile(RolloverFileOutputStream.java:219)
>
> I'm puzzled as to why it is trying to write to /opt as that's not the
> jetty base dir.
>
> I tried changing the value to logs/requestlog.conf assuming that it would
> a relative path and that didn't work (it results in
> /opt/jettylogs/request.log) so I added the forward slash to the beginning
> of it and voila it worked.
>
>
>
>
> On Mon, Apr 7, 2014 at 2:02 PM, Joakim Erdfelt <joa...@intalio.com> wrote:
>
>> Current design for start.log is that it is always relative to
>> ${jetty.base}/${JETTY_LOGS}/start.log
>>
>> The origin for that decision has been lost in the sands of time.
>> (In other words, I can't justify that decision).
>>
>> So I filed a bug for it:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=432192
>>
>> --
>> Joakim Erdfelt <joa...@intalio.com>
>> webtide.com <http://www.webtide.com/> - intalio.com/jetty
>> Expert advice, services and support from from the Jetty & CometD experts
>> eclipse.org/jetty - cometd.org
>>
>>
>> On Mon, Apr 7, 2014 at 11:44 AM, Rob Moore <rob.mo...@gmail.com> wrote:
>>
>>> Indeed, it is complaining about being able to write to the log directory
>>> in the start.log.
>>>
>>> I've added the start-log-file=logs/start.log as you suggested and I find
>>> this in the logs:
>>>
>>> java.io.IOException: Cannot write start.log to directory
>>> /opt/jetty-distribution-9.1.4.v20140401/opt/jetty-distribution-9.1.4.v20140401/logs
>>> [directory doesn't exist or is read-only]
>>>
>>> Note the duplicate jetty home defined in the path.
>>>
>>> I ran jetty.sh check and see the following for JETTY_LOGS
>>>
>>> JETTY_LOGS = /opt/jetty-distribution-9.1.4.v20140401/logs
>>>
>>> What's odd is that the start.log is created in the logs directory even
>>> though jetty complains it can't write it there.
>>>
>>> Rob
>>>
>>>
>>>
>> _______________________________________________
>> jetty-users mailing list
>> jetty-users@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/jetty-users
>>
>>
>
_______________________________________________
jetty-users mailing list
jetty-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/jetty-users
