You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I zoom in quickly I get errors. For me these are 'acceptable' if the server would continue working after these, but it halts and becomes unresponsive (not after all errors, but it is common). Anything that can be done about that maybe? When I break with Ctrl+C and restart the server everything is working again.
Example of server output after which it frooze:
2017-06-29 05:57:57.946 INFO GET /customlayer/3/3/3.pbf
2017-06-29 05:57:57.949 INFO GET /customlayer/3/4/2.pbf
2017-06-29 05:57:58.446 WARN Get V4(92.110.243.159:48004) AbsolutePath("/customlayer/3/3/3.pbf") "Failed to send: Connection reset by peer (os error 104)" None
Error: Failed to send: Connection reset by peer (os error 104)
2017-06-29 05:57:58.657 INFO GET /customlayer/5/15/12.pbf
2017-06-29 05:57:58.960 INFO GET /customlayer/6/31/23.pbf
2017-06-29 05:57:58.961 INFO GET /customlayer/6/31/24.pbf
2017-06-29 06:13:53.458 WARN Get V4(92.110.243.159:46614) AbsolutePath("/customlayer/3/3/3.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:13:53.459 INFO GET /customlayer/7/62/48.pbf
2017-06-29 06:14:14.450 WARN Get V4(92.110.243.159:48040) AbsolutePath("/customlayer/5/15/12.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:14:14.450 INFO GET /customlayer/7/62/47.pbf
2017-06-29 06:14:14.451 INFO GET /customlayer/8/125/96.pbf
2017-06-29 06:14:43.122 WARN Get V4(92.110.243.159:48054) AbsolutePath("/customlayer/6/31/24.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:14:43.123 INFO GET /customlayer/8/125/97.pbf
2017-06-29 06:14:43.123 INFO GET /customlayer/9/250/192.pbf
2017-06-29 06:14:44.658 WARN Get V4(92.110.243.159:48002) AbsolutePath("/customlayer/3/4/2.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:14:44.659 INFO GET /customlayer/9/250/193.pbf
2017-06-29 06:30:21.116 WARN Get V4(92.110.243.159:48072) AbsolutePath("/customlayer/7/62/48.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:30:21.127 INFO GET /customlayer/9/251/192.pbf
2017-06-29 06:30:21.138 INFO GET /customlayer/9/251/193.pbf
2017-06-29 06:30:21.140 INFO GET /customlayer/10/501/385.pbf
2017-06-29 06:30:42.099 WARN Get V4(92.110.243.159:48088) AbsolutePath("/customlayer/8/125/96.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:30:42.103 INFO GET /customlayer/10/501/386.pbf
2017-06-29 06:31:10.770 WARN Get V4(92.110.243.159:48104) AbsolutePath("/customlayer/9/250/192.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:31:10.772 INFO GET /customlayer/11/1002/772.pbf
2017-06-29 06:31:12.306 WARN Get V4(92.110.243.159:48106) AbsolutePath("/customlayer/9/250/193.pbf") "Failed to send: Connection timed out (os error 110)" None
Error: Failed to send: Connection timed out (os error 110)
2017-06-29 06:31:12.306 INFO GET /customlayer/11/1003/772.pbf
The text was updated successfully, but these errors were encountered:
Looks like all threads are blocked because of the synchronous http server.This will be solved with hyper 0.11 (nickel-org/nickel.rs#402). In the meantime you can only increase the number of threads (command line or config). For production use it is strongly recomended to put a web server like Nginx or Apache in front of t-rex.
When I zoom in quickly I get errors. For me these are 'acceptable' if the server would continue working after these, but it halts and becomes unresponsive (not after all errors, but it is common). Anything that can be done about that maybe? When I break with Ctrl+C and restart the server everything is working again.
Example of server output after which it frooze:
The text was updated successfully, but these errors were encountered: