[
https://issues.apache.org/jira/browse/SOLR-9548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15566924#comment-15566924
]
Shawn Heisey commented on SOLR-9548:
------------------------------------
I think this probably needs to be in another issue, but I can't locate an open
one, and I don't want to open a new one until I know that there's not an
existing one we can do the work in:
The startup logging, when in cloud mode, should log the precise information
that will be used when registering with zookeeper -- host, port, context path,
http/https, etc. Have a user on IRC that has run into a problem starting a
second node because it sees an existing ephemeral live node that matches the
info it's trying to use to register. Setting the "-h hostname" option on
bin/solr fixes the issue. If the logging had included the precise registration
info, it would have been easier to track down. Ultimately we figured out that
both hosts were trying to register as 127.0.1.1 -- because /etc/hosts was
incorrect.
> solr.log should start with informative welcome message
> ------------------------------------------------------
>
> Key: SOLR-9548
> URL: https://issues.apache.org/jira/browse/SOLR-9548
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Server
> Reporter: Jan Høydahl
> Assignee: Jan Høydahl
> Labels: logging
> Fix For: 6.3, master (7.0)
>
> Attachments: SOLR-9548-detailversion.patch, SOLR-9548.patch
>
>
> When starting Solr, the first log line should be more informative, such as
> {code}
> Welcome to Apache Solr™ version 7.0.0, running in standalone mode on port
> 8983 from folder /Users/janhoy/git/lucene-solr/solr
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
