freme-project / e-services

Apache License 2.0
1 stars 1 forks source link

Pipelines for labels are failing #26

Closed x-fran closed 8 years ago

x-fran commented 8 years ago

curl -X POST -H "Accept: application/json" -H "Content-Type: application/json" -H "Cache-Control: no-cache" -H "Postman-Token: 56b5c444-1f20-63f5-4a19-d41b0762df83" -d '[
    {
      "method": "POST",
      "endpoint": "http://api.freme-project.eu/current/e-entity/freme-ner/documents",
      "parameters": {
        "language": "en",
        "dataset": "dbpedia"
      },
      "headers": {
        "content-type": "text/plain",
        "accept": "text/turtle"
      },
      "body": "Dublin is great!"
    },
    {
      "method": "POST",
      "endpoint": "http://api.freme-project.eu/current/e-link/documents/",
      "parameters": {
        "templateid": "4496"
      },
      "headers": {
        "content-type": "text/turtle",
        "accept": "application/json+ld"
      }
    }
  ]' "http://api.freme-project.eu/current/pipelining/chain"

This command worked before and now I get this 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:7002 [rv2622.1blu.de/178.254.20.8] failed: Verbindungsaufbau abgelehnt",
  "error": "Bad Gateway",
  "status": 502,
  "timestamp": 1469725210805
}

Any idea why?

This is urgent!! We use it in production.

jnehring commented 8 years ago

I investigate on this

jnehring commented 8 years ago

It works now. @xFran please try again.

x-fran commented 8 years ago

It's working. Thank you @jnehring.

jnehring commented 8 years ago

What is the problem? When I execute the CURL then I get status code 200 and json ld data so it looks fine to me.

x-fran commented 8 years ago

I just reopen this issue because we have the same problem. The servers are failing.

You said you investigated on this. What is/was the problem?

jnehring commented 8 years ago

I opened this issue here: https://github.com/freme-project/FREMECommon/issues/22

x-fran commented 8 years ago

Ok. so I close this one and I follow https://github.com/freme-project/FREMECommon/issues/22

x-fran commented 8 years ago

The service is failing again.

"STATUS_CODE": 400, "CONTENT": { "exception": "eu.freme.common.exception.BadRequestException", "path": "\/pipelining\/chain", "message": "Request 0: java.net.UnknownHostException: api.freme-project.eu", "error": "Bad Request", "status": 400, "timestamp": 1470439348896 }

jnehring commented 8 years ago

The problem is again https://github.com/freme-project/FREMECommon/issues/22

I restarted FREME live. Is the problem solved? Can we close the issue?