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

Chatbot took long to respond and in the end "Oops! Unfortunately, I'm unable to answer right now." #157

Open
spencerwongfeilong opened this issue Feb 21, 2024 · 1 comment

Comments

@spencerwongfeilong
Copy link

I crawl an entire website. And i an running webwhiz on a ubuntu machine.

In the logs of front end, it shows the following.

frontend_1 | 2024/02/21 02:08:50 [error] 31#31: *7 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 10.200.230.2, server: , request: "POST /api/chatbot/answer/?debug=true HTTP/1.1", upstream: "http://172.19.0.4:3000/chatbot/answer/", host: "192.168.0.124:3030", referrer: "http://192.168.0.124:3030/app/edit-chatbot/65d466ea2177ff2312d365a7/"
frontend_1 | 10.200.230.2 - - [21/Feb/2024:02:08:50 +0000] "POST /api/chatbot/answer/?debug=true HTTP/1.1" 504 569 "http://192.168.0.124:3030/app/edit-chatbot/65d466ea2177ff2312d365a7/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36" "-"

@spencerwongfeilong
Copy link
Author

spencerwongfeilong commented Feb 21, 2024

It seems that the python worker took a long time to respond. While it did respond eventually, after 270 seconds, i guess it was too late. What can i do to help resolve this?

I would like to add that there are 1000 over pages crawled. This could be the underlying root cause.

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

No branches or pull requests

1 participant