[jira] [Created] (SOLR-3006) Schema related problems are not logged

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (SOLR-3006) Schema related problems are not logged

JIRA jira@apache.org
Schema related problems are not logged
--------------------------------------

                 Key: SOLR-3006
                 URL: https://issues.apache.org/jira/browse/SOLR-3006
             Project: Solr
          Issue Type: Improvement
    Affects Versions: 4.0
         Environment: example run like: java -jar start.jar
            Reporter: Sami Siren
            Priority: Minor


If there's a problem in analyzer config or for example some mandatory attribute is missing from fieldType definition the resulting exception is not currently shown on log (console).

The only thing visible, logged two times, is this:

{code}
SEVERE: Could not start Solr. Check solr/home property and the logs
org.apache.solr.common.SolrException: No cores were created, please check the logs for errors
{code}

If I load the solr web page it shows the actual error(s). It would be nice if the problem was also logged on console/log.

There's some suspicious looking lines in AbstractPluginLoader at around line 169:

{code}
          SolrException e = new SolrException
            (ErrorCode.SERVER_ERROR,
             "Plugin init failure for " + type + ":" + ex.getMessage(), ex);
{code}
where the SolrException is created with a constructor that sets the logged flag to true. Still there is a line
{code}
          SolrException.logOnce(log,null,e);
{code}

a little later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (SOLR-3006) Schema related problems are not logged

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sami Siren updated SOLR-3006:
-----------------------------

    Attachment: SOLR-3006.patch

This trivial patch seems to do what I wanted.
               

> Schema related problems are not logged
> --------------------------------------
>
>                 Key: SOLR-3006
>                 URL: https://issues.apache.org/jira/browse/SOLR-3006
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0
>         Environment: example run like: java -jar start.jar
>            Reporter: Sami Siren
>            Priority: Minor
>         Attachments: SOLR-3006.patch
>
>
> If there's a problem in analyzer config or for example some mandatory attribute is missing from fieldType definition the resulting exception is not currently shown on log (console).
> The only thing visible, logged two times, is this:
> {code}
> SEVERE: Could not start Solr. Check solr/home property and the logs
> org.apache.solr.common.SolrException: No cores were created, please check the logs for errors
> {code}
> If I load the solr web page it shows the actual error(s). It would be nice if the problem was also logged on console/log.
> There's some suspicious looking lines in AbstractPluginLoader at around line 169:
> {code}
>           SolrException e = new SolrException
>             (ErrorCode.SERVER_ERROR,
>              "Plugin init failure for " + type + ":" + ex.getMessage(), ex);
> {code}
> where the SolrException is created with a constructor that sets the logged flag to true. Still there is a line
> {code}
>           SolrException.logOnce(log,null,e);
> {code}
> a little later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-3006) Schema related problems are not logged

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180833#comment-13180833 ]

Mark Miller commented on SOLR-3006:
-----------------------------------

I think this may be part of an issue I ran into before: https://issues.apache.org/jira/browse/SOLR-2191

Unfortunately, I never got that one in.
               

> Schema related problems are not logged
> --------------------------------------
>
>                 Key: SOLR-3006
>                 URL: https://issues.apache.org/jira/browse/SOLR-3006
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0
>         Environment: example run like: java -jar start.jar
>            Reporter: Sami Siren
>            Priority: Minor
>         Attachments: SOLR-3006.patch
>
>
> If there's a problem in analyzer config or for example some mandatory attribute is missing from fieldType definition the resulting exception is not currently shown on log (console).
> The only thing visible, logged two times, is this:
> {code}
> SEVERE: Could not start Solr. Check solr/home property and the logs
> org.apache.solr.common.SolrException: No cores were created, please check the logs for errors
> {code}
> If I load the solr web page it shows the actual error(s). It would be nice if the problem was also logged on console/log.
> There's some suspicious looking lines in AbstractPluginLoader at around line 169:
> {code}
>           SolrException e = new SolrException
>             (ErrorCode.SERVER_ERROR,
>              "Plugin init failure for " + type + ":" + ex.getMessage(), ex);
> {code}
> where the SolrException is created with a constructor that sets the logged flag to true. Still there is a line
> {code}
>           SolrException.logOnce(log,null,e);
> {code}
> a little later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (SOLR-3006) Schema related problems are not logged

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/jira/browse/SOLR-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181186#comment-13181186 ]

Sami Siren commented on SOLR-3006:
----------------------------------

I see, that indeed is related. I think I'll just close this one and see If I can push the other one further.
               

> Schema related problems are not logged
> --------------------------------------
>
>                 Key: SOLR-3006
>                 URL: https://issues.apache.org/jira/browse/SOLR-3006
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0
>         Environment: example run like: java -jar start.jar
>            Reporter: Sami Siren
>            Priority: Minor
>         Attachments: SOLR-3006.patch
>
>
> If there's a problem in analyzer config or for example some mandatory attribute is missing from fieldType definition the resulting exception is not currently shown on log (console).
> The only thing visible, logged two times, is this:
> {code}
> SEVERE: Could not start Solr. Check solr/home property and the logs
> org.apache.solr.common.SolrException: No cores were created, please check the logs for errors
> {code}
> If I load the solr web page it shows the actual error(s). It would be nice if the problem was also logged on console/log.
> There's some suspicious looking lines in AbstractPluginLoader at around line 169:
> {code}
>           SolrException e = new SolrException
>             (ErrorCode.SERVER_ERROR,
>              "Plugin init failure for " + type + ":" + ex.getMessage(), ex);
> {code}
> where the SolrException is created with a constructor that sets the logged flag to true. Still there is a line
> {code}
>           SolrException.logOnce(log,null,e);
> {code}
> a little later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

[jira] [Resolved] (SOLR-3006) Schema related problems are not logged

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/SOLR-3006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sami Siren resolved SOLR-3006.
------------------------------

    Resolution: Duplicate

SOLR-2191 would probably fix this too
               

> Schema related problems are not logged
> --------------------------------------
>
>                 Key: SOLR-3006
>                 URL: https://issues.apache.org/jira/browse/SOLR-3006
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 4.0
>         Environment: example run like: java -jar start.jar
>            Reporter: Sami Siren
>            Priority: Minor
>         Attachments: SOLR-3006.patch
>
>
> If there's a problem in analyzer config or for example some mandatory attribute is missing from fieldType definition the resulting exception is not currently shown on log (console).
> The only thing visible, logged two times, is this:
> {code}
> SEVERE: Could not start Solr. Check solr/home property and the logs
> org.apache.solr.common.SolrException: No cores were created, please check the logs for errors
> {code}
> If I load the solr web page it shows the actual error(s). It would be nice if the problem was also logged on console/log.
> There's some suspicious looking lines in AbstractPluginLoader at around line 169:
> {code}
>           SolrException e = new SolrException
>             (ErrorCode.SERVER_ERROR,
>              "Plugin init failure for " + type + ":" + ex.getMessage(), ex);
> {code}
> where the SolrException is created with a constructor that sets the logged flag to true. Still there is a line
> {code}
>           SolrException.logOnce(log,null,e);
> {code}
> a little later.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]