[
https://issues.apache.org/jira/browse/HDDS-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17558244#comment-17558244
]
Ritesh H Shukla commented on HDDS-6559:
---------------------------------------
Access control failures are logged in s3g logs. Filling it here as a reminder.
{code:java}
javax.servlet.ServletException: javax.servlet.ServletException:
java.lang.RuntimeException: PERMISSION_DENIED
org.apache.hadoop.ozone.om.exceptions.OMException: User
testuser2/[email protected] doesn't have LIST permission to access volume
Volume:s3v s3g_1 | at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:162)
s3g_1 | at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
s3g_1 | at org.eclipse.jetty.server.Server.handle(Server.java:516) s3g_1
| at
org.eclipse.jetty.server.HttpChannel.lambda$handle$1(HttpChannel.java:388)
s3g_1 | at
org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:633) s3g_1
| at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:380) s3g_1
| at
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:277)
s3g_1 | at
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311)
s3g_1 | at
org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:105) s3g_1 |
at org.eclipse.jetty.io.ChannelEndPoint$1.run(ChannelEndPoint.java:104) s3g_1
| at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:338)
s3g_1 | at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:315)
s3g_1 | at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:173)
s3g_1 | at
org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:131)
s3g_1 | at
org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:386)
s3g_1 | at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:883)
s3g_1 | at
org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1034)
s3g_1 | at java.base/java.lang.Thread.run(Thread.java:829){code}
> S3G client logging review
> -------------------------
>
> Key: HDDS-6559
> URL: https://issues.apache.org/jira/browse/HDDS-6559
> Project: Apache Ozone
> Issue Type: Improvement
> Components: S3
> Reporter: Ritesh H Shukla
> Assignee: Duong
> Priority: Major
>
> Currently a broad range of errors get logged to S3G's log which include
> errors that can be induced by a client. Ideally these should not be logged
> (Example invalid header), there can be an access log which only captures HTTP
> requests and responses but the S3G log should be for the internal state of
> S3G.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
