[
https://issues.apache.org/jira/browse/SOLR-15936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Høydahl updated SOLR-15936:
-------------------------------
Description:
Jetty is logging these lines on every startup (SSL not enabled):
{code:java}
2022-01-19 11:43:18.053 WARN (main) [] o.e.j.u.s.S.config Trusting all
certificates configured for
Client@62dbe64e[provider=null,keyStore=null,trustStore=null]
2022-01-19 11:43:18.053 WARN (main) [] o.e.j.u.s.S.config No Client
EndPointIdentificationAlgorithm configured for
Client@62dbe64e[provider=null,keyStore=null,trustStore=null]
2022-01-19 11:43:18.194 WARN (main) [] o.e.j.u.s.S.config Trusting all
certificates configured for
Client@12fe1f28[provider=null,keyStore=null,trustStore=null]
2022-01-19 11:43:18.194 WARN (main) [] o.e.j.u.s.S.config No Client
EndPointIdentificationAlgorithm configured for
Client@12fe1f28[provider=null,keyStore=null,trustStore=null]
2 {code}
Why is this class is even triggered in a non-ssl config? Or do we have some
mis-configuration of Solr's default truststore or something that we should act
on?
Once this is fixed, PR [https://github.com/apache/solr/pull/543] can be
addressed, which moves LogWatcher earlier in the solr startup process to get as
much logs as possible in the UI.
was:
Jetty is logging these lines on every startup (SSL not enabled):
{code:java}
2022-01-19 11:43:18.053 WARN (main) [] o.e.j.u.s.S.config Trusting all
certificates configured for
Client@62dbe64e[provider=null,keyStore=null,trustStore=null]
2022-01-19 11:43:18.053 WARN (main) [] o.e.j.u.s.S.config No Client
EndPointIdentificationAlgorithm configured for
Client@62dbe64e[provider=null,keyStore=null,trustStore=null]
2022-01-19 11:43:18.194 WARN (main) [] o.e.j.u.s.S.config Trusting all
certificates configured for
Client@12fe1f28[provider=null,keyStore=null,trustStore=null]
2022-01-19 11:43:18.194 WARN (main) [] o.e.j.u.s.S.config No Client
EndPointIdentificationAlgorithm configured for
Client@12fe1f28[provider=null,keyStore=null,trustStore=null]
2 {code}
Why is this class is even triggered in a non-ssl config? Or do we have some
mis-configuration of Solr's default truststore or something that we should act
on?
> Fix confusing SSL related warn logs on sartup
> ---------------------------------------------
>
> Key: SOLR-15936
> URL: https://issues.apache.org/jira/browse/SOLR-15936
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Jan Høydahl
> Priority: Major
>
> Jetty is logging these lines on every startup (SSL not enabled):
> {code:java}
> 2022-01-19 11:43:18.053 WARN (main) [] o.e.j.u.s.S.config Trusting all
> certificates configured for
> Client@62dbe64e[provider=null,keyStore=null,trustStore=null]
> 2022-01-19 11:43:18.053 WARN (main) [] o.e.j.u.s.S.config No Client
> EndPointIdentificationAlgorithm configured for
> Client@62dbe64e[provider=null,keyStore=null,trustStore=null]
> 2022-01-19 11:43:18.194 WARN (main) [] o.e.j.u.s.S.config Trusting all
> certificates configured for
> Client@12fe1f28[provider=null,keyStore=null,trustStore=null]
> 2022-01-19 11:43:18.194 WARN (main) [] o.e.j.u.s.S.config No Client
> EndPointIdentificationAlgorithm configured for
> Client@12fe1f28[provider=null,keyStore=null,trustStore=null]
> 2 {code}
> Why is this class is even triggered in a non-ssl config? Or do we have some
> mis-configuration of Solr's default truststore or something that we should
> act on?
> Once this is fixed, PR [https://github.com/apache/solr/pull/543] can be
> addressed, which moves LogWatcher earlier in the solr startup process to get
> as much logs as possible in the UI.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
