Rasa [2019-05-28 07:10:56] "OPTIONS /webhooks/rest/webhook HTTP/1.1" 404 341 0.000560
I'm trying to run rasa server but I'm getting this 404 error, anyone, no response from dialogue_management.py
was using python 3.6.7, I have resolved the issue, using this command python3 -m rasa_core.run -d models/dialogue -u models/nlu/default/customer_service_chatbot --port 5005 --credentials credentials.yml --endpoints endpoints.yml --enable_api and python -m rasa_core_sdk.endpoint --actions actions
Related
when I go to my appharbor site I get a 502 Bad Gateway
in the logs I see
appharbor nginx xx.xx.xxx.xxx - "POST / HTTP/1.1" 502 150 "-" "Logplex/unknown" "source=nginx measure#http.response_time=0.000s measure#http.bytes.sent=300"
it was a problem on appharbors side
Trying to run a mock apns service on AWS EC2.
Connection works well with curl and simple go program using apns2 library.
However when using pushy the query gets stopped at the loadbalancer with a HTTP 1/1 400 Bad Request. So is not getting through to the mock apsn service.
It looks like pushy is trying to negotiate to use http2, but it is also resolving the CNAME of the hostname to make that request. The hostname of the EC2 instance does not have an SSL certificate, and AWS do not allow EC2 instances to have their own certificate. SSL is done via the load balancer. Which is why I guess it gets the Bad Request error.
Is there some way to get pushy.apns to go straight to h2, without the negotiation. The apple APNS service works simply by replacing the hostname in the curl and go examples I'm using.
The log output of a pushy request looks like
https 2018-10-12T08:19:30.301789Z app/pushproxy/7ba468ea0d0278b2 86.172.XX.230:61136 - -1 -1 -1 400 - 0 288 "- https://pushproxy-XXXXXXX.eu-west-2.elb.amazonaws.com:443- -" "-" ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 - "-" "-" "arn:aws:acm:eu-west-2:914858662894:certificate/XXXXXX-d957-4e9d-bda6-00c2f42a6e3a" - 2018-10-12T08:19:30.286000Z "-" "-"
And a curl request looks like
h2 2018-10-12T08:13:43.142341Z app/pushproxy/7ba468ea0d0278b2 86.172.XX.230:60860 172.31.27.35:443 0.000 0.002 0.000 200 200 239 78 "POST https://pushproxy.mycompany.com:443/3/device/a9001c6cbf953a9b2820f4da9c7f8d37e84338460304a2ce0a04a32e85ca2532 HTTP/2.0" "curl/7.61.1" ECDHE-RSA-AES128-GCM-SHA256 TLSv1.2 arn:aws:elasticloadbalancing:eu-west-2:914858662894:targetgroup/pushProxy/252675c1a61756ea "Root=1-5bc057b7-a61a4ca4d5880b40f00d17c0" "pushproxy.mycompany.com" "arn:aws:acm:eu-west-2:914858662894:certificate/XXXXXXX-a34f-415b-b687-8789cf21197f" 0 2018-10-12T08:13:43.140000Z "forward" "-"
curl command
curl -v -d '{"aps":{"alert":"<message>","badge":42}}' \
-H "apns-id: 45454554646445454433433334332344" \
-H "apns-topic: com.2mee.Bridge2Mee" \
-H "apns-priority: 10" --http2 \
--cert pushcert.pem https://pushproxy.mycompany.com/3/device/a9001c6cbf953a9b2820f4da9c7f8d37e84338460304a2ce0a04a32e85ca2532
I've followed this tutorial: https://www.digitalocean.com/community/tutorials/how-to-migrate-a-parse-app-to-parse-server-on-ubuntu-14-04
All fine, except that when it comes to sending a POST request to the Parse-server, I get an error 502. Here are both POST and GET requests which return a 502 when using https and a 301 when using HTTP:
curl -X POST \
-H "X-Parse-Application-Id: AppId" \
-H "Content-Type: application/json" \
-d '{"score":1337,"playerName":"Sammy","cheatMode":false}' \
https://domain.name/parse/classes/GameScore
curl -H "X-Parse-Application-Id: APPID" http://domain.name/parse/classes/GameScore
I specially wanted to check if
mongod.conf
is fine (mine is the same as the one on the tutorial) and if
/etc/nginx/sites-enabled/default
is also fine.
Here is the log:
2016/03/07 22:11:30 [error] 7288#0: *7 connect() failed (111: Connection refused) while connecting to upstream, client: myComputerIP, server: domain.name, request: "GET /parse/classes/GameScore HTTP/1.1", upstream: "http://127.0.0.1:1337/classes/GameScore", host: "domain.name"
Any ideas? Thanks
I was running into the same problem, in my case was an error due to the change of the path of an internal dependency during the migration.
I was able to troubleshoot it using:
pm2 logs 0
Hope it helps.
There was a syntax error in my cloud code.
Looks like your node.js server isn't running (or not listening on port 1337) - make sure it's up by running and if not, start the parse-server.
I have an annoying problem in Apache Karaf 3.0.2. I want to add a feature repository. It is located in my private Nexus Snapshot Repository and protected by username and password. Everything is correctly stated in my settings.xml
~/.m2/repository/settings.xml:
<servers>
<server>
<id>test</id>
<username>karaf</username>
<password>karafpass</password>
</server>
</servers>
org.ops4j.pax.url.mvn.cfg:
org.ops4j.pax.url.mvn.repositories= \
http://repo1.maven.org/maven2#id=central, \
http://repository.springsource.com/maven/bundles/release#id=spring.ebr.release, \
http://repository.springsource.com/maven/bundles/external#id=spring.ebr.external, \
http://zodiac.springsource.com/maven/bundles/release#id=gemini, \
http://repository.apache.org/content/groups/snapshots-group#id=apache#snapshots#noreleases, \
https://oss.sonatype.org/content/repositories/snapshots#id=sonatype.snapshots.deploy#snapshots#norelease, \
https://oss.sonatype.org/content/repositories/ops4j-snapshots#id=ops4j.sonatype.snapshots.deploy#snapshots#noreleases, \
http://192.168.178.25:8081/nexus/content/repositories/snapshots#id=test#snapshots#noreleases
The command to add the feature repository:
feature:repo-add mvn:com.test/com.test.feature/1.0.0-SNAPSHOT/xml/features
In the first try I get:
Error executing command: Error resolving artifact com.test:com.test.feature:xml:features:1.0.0-SNAPSHOT:
Could not find artifact com.test:com.test.feature:xml:features:1.0.0-SNAPSHOT in apache (http://repository.apache.org/content/groups/snapshots-group/)
Why does it fail? The error statement is right, but why is the artifact not found in my Snapshot-Repository? Here is what I can see in my Nexus request.log:
192.168.178.25 - - [25/Dez/2014:15:44:40 +0100] "GET /nexus/content/repositories/snapshots/com/test/com.test.feature/1.0.0-SNAPSHOT/maven-metadata.xml HTTP/1.1" 401 0
192.168.178.25 - - [25/Dez/2014:15:44:43 +0100] "GET /nexus/content/repositories/snapshots/com/test/com.test.feature/1.0.0-SNAPSHOT/com.test.feature-1.0.0-SNAPSHOT-features.xml HTTP/1.1" 401 0
192.168.178.25 - - [25/Dez/2014:15:44:43 +0100] "GET /nexus/content/repositories/snapshots/com/test/com.test.feature/1.0.0-SNAPSHOT/com.test.feature-1.0.0-SNAPSHOT-features.xml HTTP/1.1" 404 1289
The problem is the 401 in the first line which hinders karaf from getting maven-metadata.xml to form the subsequent commands right. Why? All credentials are part of my M2 settings.xml, just use them!
The next try with the same command succeeds and the request.log says:
192.168.178.25 - - [25/Dez/2014:15:59:02 +0100] "GET /nexus/content/repositories/snapshots/com/test/com.test.feature/1.0.0-SNAPSHOT/maven-metadata.xml HTTP/1.1" 200 1029
192.168.178.25 - - [25/Dez/2014:15:59:02 +0100] "GET /nexus/content/repositories/snapshots/com/test/com.test.feature/1.0.0-SNAPSHOT/maven-metadata.xml.sha1 HTTP/1.1" 200 40
192.168.178.25 - - [25/Dez/2014:15:59:03 +0100] "GET /nexus/content/repositories/snapshots/com/test/com.test.feature/1.0.0-SNAPSHOT/com.test.feature-1.0.0-20141224.100146-1-features.xml HTTP/1.1" 200 1086
192.168.178.25 - - [25/Dez/2014:15:59:04 +0100] "GET /nexus/content/repositories/snapshots/com/test/com.test.feature/1.0.0-SNAPSHOT/com.test.feature-1.0.0-20141224.100146-1-features.xml.sha1 HTTP/1.1" 200 40
Please, I require your help? How can I get rid of that problem?
I am trying to manage a EC2 cloud instance with deltacloud API through curl. With the mock driver everything works fine: deltacloudd -i mock -r 10.0.0.3
curl --user "mockuser:mockpassword" "http://10.0.0.3:3001/api/instances?format=xml"
curl -X POST --user "mockuser:mockpassword" "http://10.0.0.3:3001/api/instances/inst1/stop?format=xml"
But with EC2 I am unable to start a stopped instance: deltacloudd -i ec2 -P eu-west-1 -r 10.0.0.3 -V
curl --user "accesskey:secretaccesskey" "http://10.0.0.3:3001/api/instances?format=xml"
curl -X POST --user "accesskey:secretaccesskey" "http://10.0.0.3:3001/api/instances/i-NNNNNNNN/start?format=xml"
Returns: The required capability to execute this operation is missing
Deltacloud log output:
Listening on 10.0.0.3:3001, CTRL+C to stop
D, [2014-06-25T10:47:34.149001 #3575] DEBUG -- : New Aws::Ec2 using per_thread-connection mode
D, [2014-06-25T10:47:34.150897 #3575] DEBUG -- : Opening new HTTPS connection to ec2.eu-west-1.amazonaws.com:443
10.0.0.5 - - [25/Jun/2014 10:47:34] "GET /api/instances?format=xml HTTP/1.1" ec2 eu-west-1 200 1628 0.6204
10.0.0.5 - - [25/Jun/2014 10:48:14] "POST /api/instances/i-NNNNNNNN/start?format=xml {} HTTP/1.1" ec2 eu-west-1 412 60 0.0077
Its therefore obvious that deltacloud process GET, but not forward the POST request to AWS.
The Problem also happens even by clicking the start button at the webinterface (10.0.0.3:3001). The accesskey and secretaccesskey are working fine with python-boto.
Can anyone suggest me whats wrong?
The short answer is, that you can not start a stopped Amazon EC2 instance with deltacloud in the current version 1.1.3 (2013-04-17). Perhaps there will be soon a newer version, but since Red Hat reduced their support the development of deltacloud slowed down.