I can’t tell what was happening, but it seems like Nginx would request the page from bokeh, and bokeh would just hang and not do anything, it seemed pretty clear that it was nothing wrong with the nginx setup because if I typed in something like ipaddress:80/nonexistent then I’d get a 404 message in the bokeh serve output.
I finally lucked out and randomly was able to fix the problem with an earlier version of bokeh. 0.12.2 works, 0.12.5 didnt work.
Tornado 4.5 came out after the last bokeh release, and introduced a breaking incompatibility. First suggestion is to make sure you do not have tornado 4.5 installed. If that’s not the issue then more information is needed to help diagnose.
I can’t tell what was happening, but it seems like Nginx would request the page from bokeh, and bokeh would just hang and not do anything, it seemed pretty clear that it was nothing wrong with the nginx setup because if I typed in something like ipaddress:80/nonexistent then I’d get a 404 message in the bokeh serve output.
I finally lucked out and randomly was able to fix the problem with an earlier version of bokeh. 0.12.2 works, 0.12.5 didnt work.
–
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].
It works now. I currently have Tornado 4.4.1 installed.
···
On Friday, May 5, 2017 at 12:33:23 PM UTC-4, Bryan Van de ven wrote:
Tornado 4.5 came out after the last bokeh release, and introduced a breaking incompatibility. First suggestion is to make sure you do not have tornado 4.5 installed. If that’s not the issue then more information is needed to help diagnose.
I can’t tell what was happening, but it seems like Nginx would request the page from bokeh, and bokeh would just hang and not do anything, it seemed pretty clear that it was nothing wrong with the nginx setup because if I typed in something like ipaddress:80/nonexistent then I’d get a 404 message in the bokeh serve output.
I finally lucked out and randomly was able to fix the problem with an earlier version of bokeh. 0.12.2 works, 0.12.5 didnt work.
–
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].
I’m just leaving this information here in the google discussion in case it helps someone else who wastes a full day like me on this problem, because it was not mentioned in the documentation.
···
On Friday, May 5, 2017 at 12:41:00 PM UTC-4, Rachel Melamed wrote:
It works now. I currently have Tornado 4.4.1 installed.
On Friday, May 5, 2017 at 12:33:23 PM UTC-4, Bryan Van de ven wrote:
Tornado 4.5 came out after the last bokeh release, and introduced a breaking incompatibility. First suggestion is to make sure you do not have tornado 4.5 installed. If that’s not the issue then more information is needed to help diagnose.
I can’t tell what was happening, but it seems like Nginx would request the page from bokeh, and bokeh would just hang and not do anything, it seemed pretty clear that it was nothing wrong with the nginx setup because if I typed in something like ipaddress:80/nonexistent then I’d get a 404 message in the bokeh serve output.
I finally lucked out and randomly was able to fix the problem with an earlier version of bokeh. 0.12.2 works, 0.12.5 didnt work.
–
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].
What was not mentioned? The tornado 4.5 incompat? As I said, the tornado release came after the last Bokeh release, and was entirely outside our control. The incompatibility has been fixed in master and latest dev builds, and conda packages on both defaults and conda forge have been patched. This has been discussed in GH the mailing list and stack overflow numerous times now. We are working as hard as humanly possible to get a new release out but it will be a few weeks at least due to other considerations. Trust me I am as frustrated by this turn of events as you.
I’m just leaving this information here in the google discussion in case it helps someone else who wastes a full day like me on this problem, because it was not mentioned in the documentation.
On Friday, May 5, 2017 at 12:41:00 PM UTC-4, Rachel Melamed wrote:
It works now. I currently have Tornado 4.4.1 installed.
On Friday, May 5, 2017 at 12:33:23 PM UTC-4, Bryan Van de ven wrote:
Tornado 4.5 came out after the last bokeh release, and introduced a breaking incompatibility. First suggestion is to make sure you do not have tornado 4.5 installed. If that’s not the issue then more information is needed to help diagnose.
I can’t tell what was happening, but it seems like Nginx would request the page from bokeh, and bokeh would just hang and not do anything, it seemed pretty clear that it was nothing wrong with the nginx setup because if I typed in something like ipaddress:80/nonexistent then I’d get a 404 message in the bokeh serve output.
I finally lucked out and randomly was able to fix the problem with an earlier version of bokeh. 0.12.2 works, 0.12.5 didnt work.
–
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].
I did not see it on stack overflow, despite reading basically every post on bokeh/nginx that I could find, and I did not see it in this discussion group, despite the same. Maybe it was discussed there, but in such a a way that it would not be obvious to me that it was related to the problem I was having.
I was just going by the docs that I linked to earlier, which did not mention anything about the appropriate version of tornado/bokeh that needed to be used. I followed exactly what was in those docs, and it did not work until I luckily tried it on a computer that happened to have a different version of bokeh installed.
I’m not trying to vent at you. I’m just, like I said, trying to help a casual/one-time user who is in my situation, and who has no way of knowing what the problem was.
···
On Friday, May 5, 2017 at 1:00:13 PM UTC-4, Bryan Van de ven wrote:
What was not mentioned? The tornado 4.5 incompat? As I said, the tornado release came after the last Bokeh release, and was entirely outside our control. The incompatibility has been fixed in master and latest dev builds, and conda packages on both defaults and conda forge have been patched. This has been discussed in GH the mailing list and stack overflow numerous times now. We are working as hard as humanly possible to get a new release out but it will be a few weeks at least due to other considerations. Trust me I am as frustrated by this turn of events as you.
I’m just leaving this information here in the google discussion in case it helps someone else who wastes a full day like me on this problem, because it was not mentioned in the documentation.
On Friday, May 5, 2017 at 12:41:00 PM UTC-4, Rachel Melamed wrote:
It works now. I currently have Tornado 4.4.1 installed.
On Friday, May 5, 2017 at 12:33:23 PM UTC-4, Bryan Van de ven wrote:
Tornado 4.5 came out after the last bokeh release, and introduced a breaking incompatibility. First suggestion is to make sure you do not have tornado 4.5 installed. If that’s not the issue then more information is needed to help diagnose.
I can’t tell what was happening, but it seems like Nginx would request the page from bokeh, and bokeh would just hang and not do anything, it seemed pretty clear that it was nothing wrong with the nginx setup because if I typed in something like ipaddress:80/nonexistent then I’d get a 404 message in the bokeh serve output.
I finally lucked out and randomly was able to fix the problem with an earlier version of bokeh. 0.12.2 works, 0.12.5 didnt work.
–
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].