Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FREME NER does not start #174

Closed
jnehring opened this issue Jan 24, 2017 · 1 comment
Closed

FREME NER does not start #174

jnehring opened this issue Jan 24, 2017 · 1 comment
Assignees
Labels

Comments

@jnehring
Copy link
Member

jnehring commented Jan 24, 2017

Error message in /opt/freme-ner-dev/logs/broker.log on rv2622.1blu.de

ERROR   2017-01-23 17:05:07,221 [main] org.springframework.boot.SpringApplication  - Application startup failed
eu.freme.common.exception.InternalServerErrorException: It was not possible to read the spotter dictionary. Please check if the path is correct (/opt/freme-ner-dev/dictionary)
        at org.elinker.core.spotter.FremeSpotter.buildDictionary(FremeSpotter.java:42)
        at org.elinker.core.spotter.FremeSpotter.onApplicationEvent(FremeSpotter.java:65)
        at org.elinker.core.spotter.FremeSpotter.onApplicationEvent(FremeSpotter.java:21)

Can you please

  1. Add a fall back behaviour that it can start even when it is not configured correctly
  2. Put the resource somewhere else. The folder /opt/freme-ner-dev gets deleted whenever Jenkins reinstalls freme-ner. A good place is this folder](https://github.com/freme-project/freme-packages/tree/master/freme-ner-dev/src/main/resources), if it not too large. This gets deployed to /opt/freme-ner-dev/config .
@sandroacoelho
Copy link
Contributor

Fixed. Thanks @jnehring .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants