Closed jnehring closed 7 years ago
Hi @jnehring ,
The bug was in our NIFParser . I fixed it, so could you please update our FREME-DEV/Live?
Btw, it solves our #164 issue
Thanks,
I now get with this requets
curl -X POST --header 'Content-Type: text/plain' --header 'Accept: text/turtle' -d 'Berlin' ' https://api-dev.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&mode=all '
the following error
{ "exception": "eu.freme.bservices.filter.proxy.exception.BadGatewayException", "path": "/e-entity/freme-ner/documents", "message": "Proxy failed: org.apache.http.conn.HttpHostConnectException: Connect to rv2622.1blu.de:7001 [rv2622.1blu.de/178.254.20.8] failed: Connection refused", "error": "Bad Gateway", "status": 502, "timestamp": 1480054601569 }
the same error occurs with mode=link
@jnehring, is this related to this bug?
2016-11-25 6:19 GMT+01:00 Sandro notifications@github.com:
Hi @jnehring https://github.com/jnehring ,
The bug was in our NIFParser https://github.com/NLP2RDF/NIF-lib/blob/0.3/src/main/java/org/nlp2rdf/parser/NIFParser.java#L29 . I fixed it, so could you please update our FREME-DEV/Live?
Btw, it solves our #164 https://github.com/freme-project/freme-ner/issues/164 issue
Thanks,
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/freme-project/freme-ner/issues/165#issuecomment-262882614, or mute the thread https://github.com/notifications/unsubscribe-auth/ABH5Ajg7NHlge86BWG6Bm7BwaAx3PUWCks5rBm_4gaJpZM4K7Yh0 .
I'm getting the same error on both dev and live versions. Any news on this?
@m1ci and @sandroacoelho , do you see a way to solve this without Jan? It seems the bug influences other demos as well, also without the use of the link mode. See
https://github.com/freme-project/freme-ner/issues/163#issuecomment-262924453
Actually all demos using FREME-NER seem to fail now, see e.g. also https://freme-project.github.io/freme-showcase/ease-of-adaption.html
@borriellom @fsasaki The FREME-NER was not running on the server. I have started it right now and will check why the process has stopped . Could please check if it is ok now?
works, thanks!
2016-11-25 13:29 GMT+01:00 Sandro notifications@github.com:
@borriellom https://github.com/borriellom @fsasaki https://github.com/fsasaki The FREME-NER was not running on the server. I have started it right now and will check why the process has stopped . Could please check if it is ok now?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/freme-project/freme-ner/issues/165#issuecomment-262947897, or mute the thread https://github.com/notifications/unsubscribe-auth/ABH5AvCOlhfMnV-0XML97ONvBk4XQsLLks5rBtSogaJpZM4K7Yh0 .
Yes, it works now. Thanks!!!
Thanks for the fix! This bug is fixed on freme-dev but not on freme-live. I will leave the issue open to check if is fixed after the next release.
The problem still exists on freme-live and it is fixed on freme-dev. Meanwhile I have released all parts of freme.
http://api.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&informat=text&mode=link&input=Wild+Atlantic+Way&outformat=turtle works and the issue is fixed on freme live
http://api.freme-project.eu/current/e-entity/freme-ner/documents?language=en&dataset=dbpedia&informat=text&mode=link&input=Wild+Atlantic+Way&outformat=turtle
It loads for a long time but never finishes and produces no result.
It used to work before, see #129
Probably this is the same error as #164