From: Greg B. <gre...@gm...> - 2011-06-14 12:22:49
|
Hi, I upgrade Yaws from 1.88 to 1.90 today, I've got a rails website with a reverse proxy access via Yaws. After the upgrade, Yaws hangs when I try to access the rails website and after that no virtual host are available at all, all Yaws is frozen. All worked fine with Yaws 1.88. >From a browser view, when I access to the rails website the page is indefinitely loaded and nothing is displayed. Here is my configuration for the virtual host "dev.d-lan.net": <server dev.d-lan.net> port = 8081 listen = 0.0.0.0 revproxy = / http://localhost:8083 partial_post_size = nolimit </server> The rails website is working fine, I opened the port to access it: http://dev.d-lan.net:8083 Anyone has an idea? |
From: Manuel D. A. <ma...@ag...> - 2011-06-14 12:50:19
|
Hello I've opened the same issue in github, but I'm using yaws embedded im my app. https://github.com/klacke/yaws/issues/60 Regards. 2011/6/14 Greg Burri <gre...@gm...> > Hi, > > I upgrade Yaws from 1.88 to 1.90 today, I've got a rails website with a > reverse proxy access via Yaws. > > After the upgrade, Yaws hangs when I try to access the rails website and > after that no virtual host are available at all, all Yaws is frozen. All > worked fine with Yaws 1.88. > > From a browser view, when I access to the rails website the page is > indefinitely loaded and nothing is displayed. > > Here is my configuration for the virtual host "dev.d-lan.net": > > <server dev.d-lan.net> > port = 8081 > listen = 0.0.0.0 > revproxy = / http://localhost:8083 > partial_post_size = nolimit > </server> > > The rails website is working fine, I opened the port to access it: > http://dev.d-lan.net:8083 > > Anyone has an idea? > > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > > |
From: Steve V. <vi...@ie...> - 2011-06-14 18:40:54
|
Hi all, I'm aware of the problem, but was traveling and speaking at Erlang Factory London last week, and this week I'm leaving my current job to join Basho, so I haven't been able to take a look at this issue just yet. Klacke is off on holiday at present as well. I'll do my best to look at the problem as soon as I can. --steve On Tue, Jun 14, 2011 at 8:25 AM, Manuel Durán Aguete <ma...@ag...> wrote: > Hello > > > I've opened the same issue in github, but I'm using yaws embedded im my > app. > https://github.com/klacke/yaws/issues/60 > Regards. > 2011/6/14 Greg Burri <gre...@gm...> >> >> Hi, >> >> I upgrade Yaws from 1.88 to 1.90 today, I've got a rails website with a >> reverse proxy access via Yaws. >> >> After the upgrade, Yaws hangs when I try to access the rails website and >> after that no virtual host are available at all, all Yaws is frozen. All >> worked fine with Yaws 1.88. >> >> From a browser view, when I access to the rails website the page is >> indefinitely loaded and nothing is displayed. >> >> Here is my configuration for the virtual host "dev.d-lan.net": >> >> <server dev.d-lan.net> >> port = 8081 >> listen = 0.0.0.0 >> revproxy = / http://localhost:8083 >> partial_post_size = nolimit >> </server> >> >> The rails website is working fine, I opened the port to access it: >> http://dev.d-lan.net:8083 >> >> Anyone has an idea? >> >> >> ------------------------------------------------------------------------------ >> EditLive Enterprise is the world's most technically advanced content >> authoring tool. Experience the power of Track Changes, Inline Image >> Editing and ensure content is compliant with Accessibility Checking. >> http://p.sf.net/sfu/ephox-dev2dev >> _______________________________________________ >> Erlyaws-list mailing list >> Erl...@li... >> https://lists.sourceforge.net/lists/listinfo/erlyaws-list >> > > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > > |
From: Steve V. <vi...@ie...> - 2011-06-17 16:30:35
|
OK, thanks to Manuel's example I've been able to duplicate the problem, and will try to work on it over the weekend. Thanks for your patience. --steve On Tue, Jun 14, 2011 at 2:40 PM, Steve Vinoski <vi...@ie...> wrote: > Hi all, I'm aware of the problem, but was traveling and speaking at > Erlang Factory London last week, and this week I'm leaving my current > job to join Basho, so I haven't been able to take a look at this issue > just yet. Klacke is off on holiday at present as well. I'll do my best > to look at the problem as soon as I can. > > --steve > > On Tue, Jun 14, 2011 at 8:25 AM, Manuel Durán Aguete <ma...@ag...> wrote: >> Hello >> >> >> I've opened the same issue in github, but I'm using yaws embedded im my >> app. >> https://github.com/klacke/yaws/issues/60 >> Regards. >> 2011/6/14 Greg Burri <gre...@gm...> >>> >>> Hi, >>> >>> I upgrade Yaws from 1.88 to 1.90 today, I've got a rails website with a >>> reverse proxy access via Yaws. >>> >>> After the upgrade, Yaws hangs when I try to access the rails website and >>> after that no virtual host are available at all, all Yaws is frozen. All >>> worked fine with Yaws 1.88. >>> >>> From a browser view, when I access to the rails website the page is >>> indefinitely loaded and nothing is displayed. >>> >>> Here is my configuration for the virtual host "dev.d-lan.net": >>> >>> <server dev.d-lan.net> >>> port = 8081 >>> listen = 0.0.0.0 >>> revproxy = / http://localhost:8083 >>> partial_post_size = nolimit >>> </server> >>> >>> The rails website is working fine, I opened the port to access it: >>> http://dev.d-lan.net:8083 >>> >>> Anyone has an idea? >>> >>> >>> ------------------------------------------------------------------------------ >>> EditLive Enterprise is the world's most technically advanced content >>> authoring tool. Experience the power of Track Changes, Inline Image >>> Editing and ensure content is compliant with Accessibility Checking. >>> http://p.sf.net/sfu/ephox-dev2dev >>> _______________________________________________ >>> Erlyaws-list mailing list >>> Erl...@li... >>> https://lists.sourceforge.net/lists/listinfo/erlyaws-list >>> >> >> >> ------------------------------------------------------------------------------ >> EditLive Enterprise is the world's most technically advanced content >> authoring tool. Experience the power of Track Changes, Inline Image >> Editing and ensure content is compliant with Accessibility Checking. >> http://p.sf.net/sfu/ephox-dev2dev >> _______________________________________________ >> Erlyaws-list mailing list >> Erl...@li... >> https://lists.sourceforge.net/lists/listinfo/erlyaws-list >> >> > |
From: Steve V. <vi...@ie...> - 2011-06-21 02:39:52
|
I just pushed a fix for this to github. Please give it a try and let me know if it fixes the issues you've been seeing. --steve On Fri, Jun 17, 2011 at 12:30 PM, Steve Vinoski <vi...@ie...> wrote: > OK, thanks to Manuel's example I've been able to duplicate the > problem, and will try to work on it over the weekend. Thanks for your > patience. > > --steve > > On Tue, Jun 14, 2011 at 2:40 PM, Steve Vinoski <vi...@ie...> wrote: >> Hi all, I'm aware of the problem, but was traveling and speaking at >> Erlang Factory London last week, and this week I'm leaving my current >> job to join Basho, so I haven't been able to take a look at this issue >> just yet. Klacke is off on holiday at present as well. I'll do my best >> to look at the problem as soon as I can. >> >> --steve >> >> On Tue, Jun 14, 2011 at 8:25 AM, Manuel Durán Aguete <ma...@ag...> wrote: >>> Hello >>> >>> >>> I've opened the same issue in github, but I'm using yaws embedded im my >>> app. >>> https://github.com/klacke/yaws/issues/60 >>> Regards. >>> 2011/6/14 Greg Burri <gre...@gm...> >>>> >>>> Hi, >>>> >>>> I upgrade Yaws from 1.88 to 1.90 today, I've got a rails website with a >>>> reverse proxy access via Yaws. >>>> >>>> After the upgrade, Yaws hangs when I try to access the rails website and >>>> after that no virtual host are available at all, all Yaws is frozen. All >>>> worked fine with Yaws 1.88. >>>> >>>> From a browser view, when I access to the rails website the page is >>>> indefinitely loaded and nothing is displayed. >>>> >>>> Here is my configuration for the virtual host "dev.d-lan.net": >>>> >>>> <server dev.d-lan.net> >>>> port = 8081 >>>> listen = 0.0.0.0 >>>> revproxy = / http://localhost:8083 >>>> partial_post_size = nolimit >>>> </server> >>>> >>>> The rails website is working fine, I opened the port to access it: >>>> http://dev.d-lan.net:8083 >>>> >>>> Anyone has an idea? >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> EditLive Enterprise is the world's most technically advanced content >>>> authoring tool. Experience the power of Track Changes, Inline Image >>>> Editing and ensure content is compliant with Accessibility Checking. >>>> http://p.sf.net/sfu/ephox-dev2dev >>>> _______________________________________________ >>>> Erlyaws-list mailing list >>>> Erl...@li... >>>> https://lists.sourceforge.net/lists/listinfo/erlyaws-list >>>> >>> >>> >>> ------------------------------------------------------------------------------ >>> EditLive Enterprise is the world's most technically advanced content >>> authoring tool. Experience the power of Track Changes, Inline Image >>> Editing and ensure content is compliant with Accessibility Checking. >>> http://p.sf.net/sfu/ephox-dev2dev >>> _______________________________________________ >>> Erlyaws-list mailing list >>> Erl...@li... >>> https://lists.sourceforge.net/lists/listinfo/erlyaws-list >>> >>> >> > |
From: Steve V. <vi...@ie...> - 2011-06-22 21:59:19
|
Just to let the list know, Manuel verified that the reverse proxy fixes work, and he closed issue #60 as a result. Thanks to Manual for his test case and for verifying the fix. --steve On Tue, Jun 14, 2011 at 8:25 AM, Manuel Durán Aguete <ma...@ag...> wrote: > Hello > > > I've opened the same issue in github, but I'm using yaws embedded im my > app. > https://github.com/klacke/yaws/issues/60 > Regards. > 2011/6/14 Greg Burri <gre...@gm...> >> >> Hi, >> >> I upgrade Yaws from 1.88 to 1.90 today, I've got a rails website with a >> reverse proxy access via Yaws. >> >> After the upgrade, Yaws hangs when I try to access the rails website and >> after that no virtual host are available at all, all Yaws is frozen. All >> worked fine with Yaws 1.88. >> >> From a browser view, when I access to the rails website the page is >> indefinitely loaded and nothing is displayed. >> >> Here is my configuration for the virtual host "dev.d-lan.net": >> >> <server dev.d-lan.net> >> port = 8081 >> listen = 0.0.0.0 >> revproxy = / http://localhost:8083 >> partial_post_size = nolimit >> </server> >> >> The rails website is working fine, I opened the port to access it: >> http://dev.d-lan.net:8083 >> >> Anyone has an idea? >> >> >> ------------------------------------------------------------------------------ >> EditLive Enterprise is the world's most technically advanced content >> authoring tool. Experience the power of Track Changes, Inline Image >> Editing and ensure content is compliant with Accessibility Checking. >> http://p.sf.net/sfu/ephox-dev2dev >> _______________________________________________ >> Erlyaws-list mailing list >> Erl...@li... >> https://lists.sourceforge.net/lists/listinfo/erlyaws-list >> > > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Erlyaws-list mailing list > Erl...@li... > https://lists.sourceforge.net/lists/listinfo/erlyaws-list > > |
From: Christopher F. <chr...@ca...> - 2011-06-21 09:22:37
Attachments:
signature.asc
|
Le 21/06/2011 04:39, Steve Vinoski a écrit : > I just pushed a fix for this to github. Please give it a try and let > me know if it fixes the issues you've been seeing. > > --steve > Hi Steve, I have a remark about your fix. In processes accepting connections, exit signals are trapped. It is used to close connections properly when yaws is stopped (by sending the response before closing the connection). You're right when you want to skip some exit signals. In particular, {'EXIT', Pid, normal} messages are received and must be ignored. But exit signals coming from gserv process must be catch. Here is my patch to ignore all exit messages but those coming from the gserv process: git fetch git://github.com/capflam/yaws.git gserv_exit_message -- Christopher Faulet |
From: Steve V. <vi...@ie...> - 2011-06-21 11:47:18
|
On Tue, Jun 21, 2011 at 5:22 AM, Christopher Faulet <chr...@ca...> wrote: > Le 21/06/2011 04:39, Steve Vinoski a écrit : >> I just pushed a fix for this to github. Please give it a try and let >> me know if it fixes the issues you've been seeing. >> >> --steve >> > > Hi Steve, > > I have a remark about your fix. In processes accepting connections, exit > signals are trapped. It is used to close connections properly when yaws > is stopped (by sending the response before closing the connection). > You're right when you want to skip some exit signals. In particular, > {'EXIT', Pid, normal} messages are received and must be ignored. But > exit signals coming from gserv process must be catch. > > Here is my patch to ignore all exit messages but those coming from the > gserv process: > > git fetch git://github.com/capflam/yaws.git gserv_exit_message Hi Christopher, if you look at my commit comment you'll see that I believed the fix was only a temporary one and that more work was needed, but that I wanted to get the reverse proxy fix out there first since people were waiting for it. Thanks for saving me the remaining work. I've pulled your change and pushed it to the yaws repo. thanks, --steve |