Open Stack

Michael,


Thanks for your response and help with steps to debug the issue.. The issue is resolved now by increasing the MTU size of GRE tunnel.


Regards

Ashish

________________________________
From: Michael Krotscheck <krotscheck at gmail.com>
Sent: Tuesday, May 12, 2015 8:44 PM
To: Ashish Jain (WT01 - BAS); openstack at lists.openstack.org
Subject: Re: [Openstack] ["Potential Spoofed"] Re: ["Potential Spoofed"] Issue with receiving response with large payload from a node js application running on openstack

Hey there, Ashish-

I'm afraid I have never encountered this issue before myself, but I can assist with debugging. The first step would be to isolate whether the problem is with OpenStack's Nova, LBaaS, NodeJS, your application code, or the browser itself. This could be as easy as trying it from a different browser - firefox vs. chrome for instance - and if the response in one is correct and the other is not, then you have your culprit. If that doesn't work, you'll need to capture the entire HTTP request (I recommend Chrome's Network Debugging tools), and replay the request in a tool like curl or Postman. With this method, you may be able to recreate the issue by selectively adding/removing HTTP request headers.

At this point, you've got some clues. If there is a specific header that causes the request to behave oddly, then it's likely that the problem is on the server side rather than the client side. If the issue persists only in the browser, and not curl/postman, then your issue is with your client runtime and/or application code.

>From that point forward, continue isolating components to see if they contribute to the issue. Armed with the knowledge of which component is causing your issue, you can solicit specific answers from the appropriate community :). Good luck!

Michael

On Tue, May 12, 2015 at 2:23 AM <ashish.jain14 at wipro.com<mailto:ashish.jain14 at wipro.com>> wrote:
Another point to add If I use curl I can see the total response size I could receive is 906 bytes which means 227 bytes for header and  payload size of 679 bytes. Any clues anyone?

________________________________________
From: ashish.jain14 at wipro.com<mailto:ashish.jain14 at wipro.com> <ashish.jain14 at wipro.com<mailto:ashish.jain14 at wipro.com>>
Sent: Tuesday, May 12, 2015 2:05 PM
To: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: ["Potential Spoofed"] Re: [Openstack] ["Potential Spoofed"] Issue with receiving response with large payload from a node js application running on openstack

I just figured out that if the payload size is greater than 623 , I do not get any response back. The size of the header is 227 bytes. So the total response size sent all the way to my browser is 850 bytes. Anything above this is not received  by browser.

________________________________________
From: ashish.jain14 at wipro.com<mailto:ashish.jain14 at wipro.com> <ashish.jain14 at wipro.com<mailto:ashish.jain14 at wipro.com>>
Sent: Tuesday, May 12, 2015 11:29 AM
To: openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Subject: ["Potential Spoofed"] [Openstack] Issue with receiving response with large payload from a node js application running on openstack

Hello,


I have got a nodejs application which is deployed on openstack provisioned resources. Somehow whenever my response has a large payload I am unable to receive the response to my web browser however I am able to print the response at the nodejs server end which is running in openstack. I am using LBAAS from neutron and use the IP of LBAAS to hit nodejs.


Scenario1: I send a request for an id which exist in DB. DB returns json data which is delivered to nodejs. However unable to send it to browser running on my host. I get a 504 error


Scenario2: I send a request for an id which DOES NOT exist in DB. This time I get back the json response all the way till browser.


To summarize all the communications are working fine, only difference between the 2 scenarios is payload size. I have been playing around with MTU on network as well as the compute node for br-tun and eth1 but till now have not succeeded . I am also trying out few things with tcpdump but nothing substantial I have found till now.


Need some help on how to debug this out.


Regards
Ashish

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com<http://www.wipro.com>

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150512/30c96eda/attachment.html>