Skip to content
This repository has been archived by the owner on Jul 30, 2022. It is now read-only.

Timed out with heroku server #2

Open
anil614sagar opened this issue Nov 21, 2015 · 2 comments
Open

Timed out with heroku server #2

anil614sagar opened this issue Nov 21, 2015 · 2 comments

Comments

@anil614sagar
Copy link

2015-11-21T06:45:10.129425+00:00 app[web.1]: Nov-21-2015 06:45:10 [http_server] Websocket connection for peer "IoT-Demo" established.
2015-11-21T06:45:10.565198+00:00 app[web.1]: Nov-21-2015 06:45:10 [http_server] Peer connection established "IoT-Demo".
2015-11-21T06:45:24.603897+00:00 heroku[router]: at=info method=GET path="/" host=anil-zetta.herokuapp.com request_id=ebba0bdd-d787-4424-b522-edbe2eddb7d2 fwd="111.93.155.244" dyno=web.1 connect=0ms service=16ms status=200 bytes=803
2015-11-21T06:45:24.814755+00:00 heroku[router]: at=info method=GET path="/" host=anil-zetta.herokuapp.com request_id=1d33af83-2f4f-48ab-9958-dac28b7326ad fwd="111.93.155.244" dyno=web.1 connect=1ms service=3ms status=200 bytes=803
2015-11-21T06:45:24.977987+00:00 heroku[router]: at=info method=GET path="/servers/cloud" host=anil-zetta.herokuapp.com request_id=9dee8bf2-112e-411b-b9c2-874610fa479c fwd="111.93.155.244" dyno=web.1 connect=1ms service=4ms status=200 bytes=844
2015-11-21T06:45:55.118148+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/servers/IoT-Demo" host=anil-zetta.herokuapp.com request_id=a4852a04-e79e-443d-a7ed-6315c2a0f6be fwd="111.93.155.244" dyno=web.1 connect=0ms service=30001ms status=503 bytes=0
2015-11-21T06:46:00.496044+00:00 heroku[router]: at=info method=GET path="/" host=anil-zetta.herokuapp.com request_id=1e51caec-ec81-46e1-bfd6-f42a5a1973be fwd="111.93.155.244" dyno=web.1 connect=1ms service=4ms status=200 bytes=803
2015-11-21T06:46:20.270896+00:00 heroku[router]: at=error code=H15 desc="Idle connection" method=GET path="/servers/cloud/events?topic=logs" host=anil-zetta.herokuapp.com request_id=ba36328d-3996-4ab3-a045-b7ea7c5d2e31 fwd="111.93.155.244" dyno=web.1 connect=1ms service=55002ms status=503 bytes=129
2015-11-21T06:46:33.871178+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/servers/IoT-Demo" host=anil-zetta.herokuapp.com request_id=e1906eed-c9f8-4e7f-98da-a3fef87f036f fwd="111.93.155.244" dyno=web.1 connect=1ms service=30001ms status=503 bytes=0
2015-11-21T06:47:03.265978+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/servers/IoT-Demo" host=anil-zetta.herokuapp.com request_id=bafad133-cf77-49d2-a464-e8c64fdb58d5 fwd="111.93.155.244" dyno=web.1 connect=0ms service=30000ms status=503 bytes=0
2015-11-21T06:50:33.177938+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=GET path="/servers/IoT-Demo" host=anil-zetta.herokuapp.com request_id=f0741056-2dac-4533-884c-4f7de669f8f0 fwd="111.93.155.244" dyno=web.1 connect=0ms service=30000ms status=503 bytes=0
2015-11-21T07:00:43.681411+00:00 heroku[router]: at=info method=GET path="/peers/IoT-Demo?connectionId=f4b76c41-e3ed-40fa-8ef6-07ec154d09f6" host=anil-zetta.herokuapp.com request_id=76b799ca-31c4-42d5-bd2b-9a75e9f1bdf8 fwd="111.93.155.244" dyno=web.1 connect=0ms service=933566ms status=101 bytes=4881

@mdobson
Copy link
Contributor

mdobson commented Nov 21, 2015

Anil,

What version of Zetta are you using to peer to the cloud sample?

If it is v1.0.0-beta then you will be encountering a breaking change within the peering API. This is the issue that you are seeing.

-Matt

@anil614sagar
Copy link
Author

@mdobson , Thank you for quick reply, As you said, Most probably it's recent version that causes the issue. I will confirm same once i verify.

But, It works with AWS , issue is with heroku servers only.

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

No branches or pull requests

2 participants