Bokeh serve never ends

Community Support
1

Suddenly I started facing a problem with Bokeh server never ending a request.

My code is not started to get executed. Browser continues loading forever, while bokeh server process has 100% CPU.

I have the following Python code try.py:

print"hello"

``

And I call bokeh server with the following options:

bokeh serve try.py --address 0.0.0.0 --port 5006 --host ‘*’ --log-level=debug

``

  • No error occurs

  • Latest Bokeh (0.12.5) has the same result

  • If I try to access non existing page (i.e. /try2) - I do receive 404 properly

  • If I try to access the server without path, I am properly redirected (302) to /try and then it halts

  • I tried different command line options with the same result (including changing the filename to main.py)

The output is

2017-04-22 21:41:24,145 Starting Bokeh server version 0.12.4

2017-04-22 21:41:24,145 Host wildcard ‘*’ can expose the application to HTTP host header attacks. Host wildcard should only be used for testing purpose.

2017-04-22 21:41:24,145 Allowed Host headers: [’*’]

2017-04-22 21:41:24,145 These host origins can connect to the websocket: [‘localhost:5006’, ‘*’]

2017-04-22 21:41:24,146 Patterns are:

2017-04-22 21:41:24,146 [(’/try/?’,

2017-04-22 21:41:24,146 <class ‘bokeh.server.views.doc_handler.DocHandler’>,

2017-04-22 21:41:24,146 {‘application_context’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,

2017-04-22 21:41:24,147 ‘bokeh_websocket_path’: ‘/try/ws’}),

2017-04-22 21:41:24,147 (’/try/ws’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.ws.WSHandler’>,

2017-04-22 21:41:24,147 {‘application_context’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,

2017-04-22 21:41:24,147 ‘bokeh_websocket_path’: ‘/try/ws’}),

2017-04-22 21:41:24,147 (’/try/autoload.js’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.autoload_js_handler.AutoloadJsHandler’>,

2017-04-22 21:41:24,147 {‘application_context’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,

2017-04-22 21:41:24,147 ‘bokeh_websocket_path’: ‘/try/ws’}),

2017-04-22 21:41:24,147 (’/?’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.root_handler.RootHandler’>,

2017-04-22 21:41:24,147 {‘applications’: {’/try’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>},

2017-04-22 21:41:24,147 ‘prefix’: ‘’,

2017-04-22 21:41:24,147 ‘use_redirect’: True}),

2017-04-22 21:41:24,147 (’/static/(.*)’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.static_handler.StaticHandler’>)]

2017-04-22 21:41:24,149 Starting Bokeh server on port 5006 address 0.0.0.0 with applications at paths [’/try’]

2017-04-22 21:41:24,149 Starting Bokeh server with process id: 1969

2017-04-22 21:41:31,850 404 GET /main (10.10.10.53) 0.44ms

2017-04-22 21:41:39,150 [pid 1969] 0 clients connected

2017-04-22 21:41:39,150 [pid 1969] /try has 0 sessions with 0 unused

2017-04-22 21:41:54,150 [pid 1969] 0 clients connected

2017-04-22 21:41:54,150 [pid 1969] /try has 0 sessions with 0 unused

``

Any ideas on what should I try?

Thanks

2

I can't reproduce this with Bokeh 0.12.5 However there was a recent message about problems caused by the new Tornado 4.5 release. Tornado 4.5 is incompatible with previous releases of Bokeh. If you have it installed (that's my best guess, without more info) then you can either:

* dowgrade Tornado to <= 4.4.2
* install the latest Bokeh "dev" build

Bryan

···

On Apr 22, 2017, at 16:46, Meir Tseitlin <[email protected]> wrote:

Suddenly I started facing a problem with Bokeh server never ending a request.

My code is not started to get executed. Browser continues loading forever, while bokeh server process has 100% CPU.

I have the following Python code try.py:

print"hello"

And I call bokeh server with the following options:

bokeh serve try.py --address 0.0.0.0 --port 5006 --host '*' --log-level=debug

* No error occurs
* Latest Bokeh (0.12.5) has the same result
* If I try to access non existing page (i.e. /try2) - I do receive 404 properly
* If I try to access the server without path, I am properly redirected (302) to /try and then it halts
* I tried different command line options with the same result (including changing the filename to main.py)

The output is

2017-04-22 21:41:24,145 Starting Bokeh server version 0.12.4
2017-04-22 21:41:24,145 Host wildcard '*' can expose the application to HTTP host header attacks. Host wildcard should only be used for testing purpose.
2017-04-22 21:41:24,145 Allowed Host headers: ['*']
2017-04-22 21:41:24,145 These host origins can connect to the websocket: ['localhost:5006', '*']
2017-04-22 21:41:24,146 Patterns are:
2017-04-22 21:41:24,146 [('/try/?',
2017-04-22 21:41:24,146 <class 'bokeh.server.views.doc_handler.DocHandler'>,
2017-04-22 21:41:24,146 {'application_context': <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,
2017-04-22 21:41:24,147 'bokeh_websocket_path': '/try/ws'}),
2017-04-22 21:41:24,147 ('/try/ws',
2017-04-22 21:41:24,147 <class 'bokeh.server.views.ws.WSHandler'>,
2017-04-22 21:41:24,147 {'application_context': <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,
2017-04-22 21:41:24,147 'bokeh_websocket_path': '/try/ws'}),
2017-04-22 21:41:24,147 ('/try/autoload.js',
2017-04-22 21:41:24,147 <class 'bokeh.server.views.autoload_js_handler.AutoloadJsHandler'>,
2017-04-22 21:41:24,147 {'application_context': <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,
2017-04-22 21:41:24,147 'bokeh_websocket_path': '/try/ws'}),
2017-04-22 21:41:24,147 ('/?',
2017-04-22 21:41:24,147 <class 'bokeh.server.views.root_handler.RootHandler'>,
2017-04-22 21:41:24,147 {'applications': {'/try': <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>},
2017-04-22 21:41:24,147 'prefix': '',
2017-04-22 21:41:24,147 'use_redirect': True}),
2017-04-22 21:41:24,147 ('/static/(.*)',
2017-04-22 21:41:24,147 <class 'bokeh.server.views.static_handler.StaticHandler'>)]
2017-04-22 21:41:24,149 Starting Bokeh server on port 5006 address 0.0.0.0 with applications at paths ['/try']
2017-04-22 21:41:24,149 Starting Bokeh server with process id: 1969
2017-04-22 21:41:31,850 404 GET /main (10.10.10.53) 0.44ms
2017-04-22 21:41:39,150 [pid 1969] 0 clients connected
2017-04-22 21:41:39,150 [pid 1969] /try has 0 sessions with 0 unused
2017-04-22 21:41:54,150 [pid 1969] 0 clients connected
2017-04-22 21:41:54,150 [pid 1969] /try has 0 sessions with 0 unused

Any ideas on what should I try?

Thanks

--
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/561eaa47-d9cc-42c5-bf1c-4a214e260ca5%40continuum.io\.
For more options, visit https://groups.google.com/a/continuum.io/d/optout\.

3

Yep, this is exactly the case! Need to add tornado==4.4.2 to requirements…

Thanks - you saved my life!

···

On Sunday, April 23, 2017 at 12:52:37 AM UTC+3, Bryan Van de ven wrote:

I can’t reproduce this with Bokeh 0.12.5 However there was a recent message about problems caused by the new Tornado 4.5 release. Tornado 4.5 is incompatible with previous releases of Bokeh. If you have it installed (that’s my best guess, without more info) then you can either:

  • dowgrade Tornado to <= 4.4.2

  • install the latest Bokeh “dev” build

Bryan

On Apr 22, 2017, at 16:46, Meir Tseitlin [email protected] wrote:

Suddenly I started facing a problem with Bokeh server never ending a request.

My code is not started to get executed. Browser continues loading forever, while bokeh server process has 100% CPU.

I have the following Python code try.py:

print"hello"

And I call bokeh server with the following options:

bokeh serve try.py --address 0.0.0.0 --port 5006 --host ‘*’ --log-level=debug

  • No error occurs
  • Latest Bokeh (0.12.5) has the same result
  • If I try to access non existing page (i.e. /try2) - I do receive 404 properly
  • If I try to access the server without path, I am properly redirected (302) to /try and then it halts
  • I tried different command line options with the same result (including changing the filename to main.py)

The output is

2017-04-22 21:41:24,145 Starting Bokeh server version 0.12.4

2017-04-22 21:41:24,145 Host wildcard ‘*’ can expose the application to HTTP host header attacks. Host wildcard should only be used for testing purpose.

2017-04-22 21:41:24,145 Allowed Host headers: [‘*’]

2017-04-22 21:41:24,145 These host origins can connect to the websocket: [‘localhost:5006’, ‘*’]

2017-04-22 21:41:24,146 Patterns are:

2017-04-22 21:41:24,146 [(‘/try/?’,

2017-04-22 21:41:24,146 <class ‘bokeh.server.views.doc_handler.DocHandler’>,

2017-04-22 21:41:24,146 {‘application_context’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,

2017-04-22 21:41:24,147 ‘bokeh_websocket_path’: ‘/try/ws’}),

2017-04-22 21:41:24,147 (‘/try/ws’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.ws.WSHandler’>,

2017-04-22 21:41:24,147 {‘application_context’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,

2017-04-22 21:41:24,147 ‘bokeh_websocket_path’: ‘/try/ws’}),

2017-04-22 21:41:24,147 (‘/try/autoload.js’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.autoload_js_handler.AutoloadJsHandler’>,

2017-04-22 21:41:24,147 {‘application_context’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>,

2017-04-22 21:41:24,147 ‘bokeh_websocket_path’: ‘/try/ws’}),

2017-04-22 21:41:24,147 (‘/?’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.root_handler.RootHandler’>,

2017-04-22 21:41:24,147 {‘applications’: {‘/try’: <bokeh.server.application_context.ApplicationContext object at 0x7fe2abce8b90>},

2017-04-22 21:41:24,147 ‘prefix’: ‘’,

2017-04-22 21:41:24,147 ‘use_redirect’: True}),

2017-04-22 21:41:24,147 (‘/static/(.*)’,

2017-04-22 21:41:24,147 <class ‘bokeh.server.views.static_handler.StaticHandler’>)]

2017-04-22 21:41:24,149 Starting Bokeh server on port 5006 address 0.0.0.0 with applications at paths [‘/try’]

2017-04-22 21:41:24,149 Starting Bokeh server with process id: 1969

2017-04-22 21:41:31,850 404 GET /main (10.10.10.53) 0.44ms

2017-04-22 21:41:39,150 [pid 1969] 0 clients connected

2017-04-22 21:41:39,150 [pid 1969] /try has 0 sessions with 0 unused

2017-04-22 21:41:54,150 [pid 1969] 0 clients connected

2017-04-22 21:41:54,150 [pid 1969] /try has 0 sessions with 0 unused

Any ideas on what should I try?

Thanks

–
You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

To post to this group, send email to [email protected].

To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/561eaa47-d9cc-42c5-bf1c-4a214e260ca5%40continuum.io.

For more options, visit https://groups.google.com/a/continuum.io/d/optout.