Komanche ?
Locked
 
|
Something really strange happened to me more than once now.
In a simple dev image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some point, Komanche stops answering anything at all, althought the port keeps listening (as listed on a terminal).
No errors are displayed anywere but the port becomes unusable from that point on. If I wish to continue using the same image I have to add another adaptor in the Seaside Control Panel and start again.
The "dead" ports never become usable again, not even stopping and removing the adaptor and adding a new one. I am not even sure that this is a Komanche issue, as I said no error of anykind is visible.
Has anyone come across this before?
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
I've also had this problem for quite a while now and have not found any way to fix the problem either.
RS Ramiro Diaz Trepat <[hidden email]> wrote: >Something really strange happened to me more than once now.In a simple dev >image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some >point, Komanche stops answering anything at all, althought the port keeps >listening (as listed on a terminal). >No errors are displayed anywere but the port becomes unusable from that >point on. >If I wish to continue using the same image I have to add another adaptor in >the Seaside Control Panel and start again. >The "dead" ports never become usable again, not even stopping and removing >the adaptor and adding a new one. >I am not even sure that this is a Komanche issue, as I said no error of >anykind is visible. >Has anyone come across this before? >_______________________________________________ >seaside mailing list >[hidden email] >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
I've never seen this problem before.
What version of Pharo? Kom? Seaside? Lukas 2009/10/11 Robert Sirois <[hidden email]>: > I've also had this problem for quite a while now and have not found any way to fix the problem either. > > RS > > Ramiro Diaz Trepat <[hidden email]> wrote: > >>Something really strange happened to me more than once now.In a simple dev >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some >>point, Komanche stops answering anything at all, althought the port keeps >>listening (as listed on a terminal). >>No errors are displayed anywere but the port becomes unusable from that >>point on. >>If I wish to continue using the same image I have to add another adaptor in >>the Seaside Control Panel and start again. >>The "dead" ports never become usable again, not even stopping and removing >>the adaptor and adding a new one. >>I am not even sure that this is a Komanche issue, as I said no error of >>anykind is visible. >>Has anyone come across this before? >>_______________________________________________ >>seaside mailing list >>[hidden email] >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
I'm using Pharo 1.0.10419, but I'm not sure how to check the other two. I think I'm still running 2.9 in the image I checked.
RS > Date: Sun, 11 Oct 2009 12:30:37 +0200 > Subject: Re: [Seaside] Komanche ? > From: [hidden email] > To: [hidden email] > > I've never seen this problem before. > > What version of Pharo? Kom? Seaside? > > Lukas > > 2009/10/11 Robert Sirois <[hidden email]>: > > I've also had this problem for quite a while now and have not found any way to fix the problem either. > > > > RS > > > > Ramiro Diaz Trepat <[hidden email]> wrote: > > > >>Something really strange happened to me more than once now.In a simple dev > >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image at some > >>point, Komanche stops answering anything at all, althought the port keeps > >>listening (as listed on a terminal). > >>No errors are displayed anywere but the port becomes unusable from that > >>point on. > >>If I wish to continue using the same image I have to add another adaptor in > >>the Seaside Control Panel and start again. > >>The "dead" ports never become usable again, not even stopping and removing > >>the adaptor and adding a new one. > >>I am not even sure that this is a Komanche issue, as I said no error of > >>anykind is visible. > >>Has anyone come across this before? > >>_______________________________________________ > >>seaside mailing list > >>[hidden email] > >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > _______________________________________________ > > seaside mailing list > > [hidden email] > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up now. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Hi Lukas,
I am using the latest Pharo, and I have loaded Seaside with ScriptLoader loadSeaside30. I am using it on a Mac with Leopard. I have managed to reuse that port, with random tests and I do not believe there may be causality here, but I will tell you anyway what I did.
When this happens, I removed the problematic adaptor from the Seaside Control Panel and created a new one (on the same port), then I tried closing the image and restarting and it did not fix the problem. Although when I closed another non Seaside image I was running and then restarted the problematic image it worked.
I wonder now if it is not a mac vm issue or socket issue. Robert, are you also running on a mac? In spite I got the image working again, it is quite worring because we don't know the cause when an image stops answering requests (although the image itself was not hanged at all and kept working fine), and, most weird of all, there is no exception or trace of a fault happening. This is really what is making me wonder if it is not a low level socket issue that never gets to the image for it to throw an exception or anything at all.
Cheers r ps: I'm cross posting to Pharo because I believe this is not a Seaside issue. On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <[hidden email]> wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Correlation does not mean causality, I know. But in my case this happened right after saving my image, although I had saved it many times before without issues.
Cheers
On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat <[hidden email]> wrote: Hi Lukas, _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
I use the same configuration with the 4.1.1beta2U VM.
Lukas 2009/10/11 Ramiro Diaz Trepat <[hidden email]>: > Correlation does not mean causality, I know. But in my case this happened > right after saving my image, although I had saved it many times before > without issues. > Cheers > > > On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat <[hidden email]> > wrote: >> >> Hi Lukas, >> I am using the latest Pharo, and I have loaded Seaside with ScriptLoader >> loadSeaside30. I am using it on a Mac with Leopard. >> I have managed to reuse that port, with random tests and I do not believe >> there may be causality here, but I will tell you anyway what I did. >> When this happens, I removed the problematic adaptor from the Seaside >> Control Panel and created a new one (on the same port), then I tried closing >> the image and restarting and it did not fix the problem. Although when I >> closed another non Seaside image I was running and then restarted the >> problematic image it worked. >> I wonder now if it is not a mac vm issue or socket issue. Robert, are you >> also running on a mac? >> In spite I got the image working again, it is quite worring because we >> don't know the cause when an image stops answering requests (although the >> image itself was not hanged at all and kept working fine), and, most weird >> of all, there is no exception or trace of a fault happening. This is really >> what is making me wonder if it is not a low level socket issue that never >> gets to the image for it to throw an exception or anything at all. >> Cheers >> >> r >> >> ps: I'm cross posting to Pharo because I believe this is not a Seaside >> issue. >> >> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <[hidden email]> >> wrote: >>> >>> I'm using Pharo 1.0.10419, but I'm not sure how to check the other two. I >>> think I'm still running 2.9 in the image I checked. >>> >>> RS >>> >>> > Date: Sun, 11 Oct 2009 12:30:37 +0200 >>> > Subject: Re: [Seaside] Komanche ? >>> > From: [hidden email] >>> > To: [hidden email] >>> > >>> > I've never seen this problem before. >>> > >>> > What version of Pharo? Kom? Seaside? >>> > >>> > Lukas >>> > >>> > 2009/10/11 Robert Sirois <[hidden email]>: >>> > > I've also had this problem for quite a while now and have not found >>> > > any way to fix the problem either. >>> > > >>> > > RS >>> > > >>> > > Ramiro Diaz Trepat <[hidden email]> wrote: >>> > > >>> > >>Something really strange happened to me more than once now.In a >>> > >> simple dev >>> > >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image at >>> > >> some >>> > >>point, Komanche stops answering anything at all, althought the port >>> > >> keeps >>> > >>listening (as listed on a terminal). >>> > >>No errors are displayed anywere but the port becomes unusable from >>> > >> that >>> > >>point on. >>> > >>If I wish to continue using the same image I have to add another >>> > >> adaptor in >>> > >>the Seaside Control Panel and start again. >>> > >>The "dead" ports never become usable again, not even stopping and >>> > >> removing >>> > >>the adaptor and adding a new one. >>> > >>I am not even sure that this is a Komanche issue, as I said no error >>> > >> of >>> > >>anykind is visible. >>> > >>Has anyone come across this before? >>> > >>_______________________________________________ >>> > >>seaside mailing list >>> > >>[hidden email] >>> > >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> > > >>> > > _______________________________________________ >>> > > seaside mailing list >>> > > [hidden email] >>> > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> > > >>> > > >>> > >>> > >>> > >>> > -- >>> > Lukas Renggli >>> > http://www.lukas-renggli.ch >>> > _______________________________________________ >>> > seaside mailing list >>> > [hidden email] >>> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> ________________________________ >>> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up >>> now. >>> _______________________________________________ >>> seaside mailing list >>> [hidden email] >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >> > > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
I'm running the latest mac vm as well. I believe I attempted the same things to no avail.
RS > Date: Sun, 11 Oct 2009 16:39:37 +0200 > Subject: Re: [Seaside] Komanche ? > From: renggli@gmail.com > To: seaside@lists.squeakfoundation.org > > I use the same configuration with the 4.1.1beta2U VM. > > Lukas > > 2009/10/11 Ramiro Diaz Trepat <ramiro@diaztrepat.name>: > > Correlation does not mean causality, I know. But in my case this happened > > right after saving my image, although I had saved it many times before > > without issues. > > Cheers > > > > > > On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat <ramiro@diaztrepat.name> > > wrote: > >> > >> Hi Lukas, > >> I am using the latest Pharo, and I have loaded Seaside with ScriptLoader > >> loadSeaside30. I am using it on a Mac with Leopard. > >> I have managed to reuse that port, with random tests and I do not believe > >> there may be causality here, but I will tell you anyway what I did. > >> When this happens, I removed the problematic adaptor from the Seaside > >> Control Panel and created a new one (on the same port), then I tried closing > >> the image and restarting and it did not fix the problem. Although when I > >> closed another non Seaside image I was running and then restarted the > >> problematic image it worked. > >> I wonder now if it is not a mac vm issue or socket issue. Robert, are you > >> also running on a mac? > >> In spite I got the image working again, it is quite worring because we > >> don't know the cause when an image stops answering requests (although the > >> image itself was not hanged at all and kept working fine), and, most weird > >> of all, there is no exception or trace of a fault happening. This is really > >> what is making me wonder if it is not a low level socket issue that never > >> gets to the image for it to throw an exception or anything at all. > >> Cheers > >> > >> r > >> > >> ps: I'm cross posting to Pharo because I believe this is not a Seaside > >> issue. > >> > >> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois <watchlala@hotmail.com> > >> wrote: > >>> > >>> I'm using Pharo 1.0.10419, but I'm not sure how to check the other two. I > >>> think I'm still running 2.9 in the image I checked. > >>> > >>> RS > >>> > >>> > Date: Sun, 11 Oct 2009 12:30:37 +0200 > >>> > Subject: Re: [Seaside] Komanche ? > >>> > From: renggli@gmail.com > >>> > To: seaside@lists.squeakfoundation.org > >>> > > >>> > I've never seen this problem before. > >>> > > >>> > What version of Pharo? Kom? Seaside? > >>> > > >>> > Lukas > >>> > > >>> > 2009/10/11 Robert Sirois <watchlala@hotmail.com>: > >>> > > I've also had this problem for quite a while now and have not found > >>> > > any way to fix the problem either. > >>> > > > >>> > > RS > >>> > > > >>> > > Ramiro Diaz Trepat <ramiro@diaztrepat.name> wrote: > >>> > > > >>> > >>Something really strange happened to me more than once now.In a > >>> > >> simple dev > >>> > >>image (Pharo + Seaside3 + Kom on a Mac) after saving the image at > >>> > >> some > >>> > >>point, Komanche stops answering anything at all, althought the port > >>> > >> keeps > >>> > >>listening (as listed on a terminal). > >>> > >>No errors are displayed anywere but the port becomes unusable from > >>> > >> that > >>> > >>point on. > >>> > >>If I wish to continue using the same image I have to add another > >>> > >> adaptor in > >>> > >>the Seaside Control Panel and start again. > >>> > >>The "dead" ports never become usable again, not even stopping and > >>> > >> removing > >>> > >>the adaptor and adding a new one. > >>> > >>I am not even sure that this is a Komanche issue, as I said no error > >>> > >> of > >>> > >>anykind is visible. > >>> > >>Has anyone come across this before? > >>> > >>_______________________________________________ > >>> > >>seaside mailing list > >>> > >>seaside@lists.squeakfoundation.org > >>> > >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >>> > > > >>> > > _______________________________________________ > >>> > > seaside mailing list > >>> > > seaside@lists.squeakfoundation.org > >>> > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >>> > > > >>> > > > >>> > > >>> > > >>> > > >>> > -- > >>> > Lukas Renggli > >>> > http://www.lukas-renggli.ch > >>> > _______________________________________________ > >>> > seaside mailing list > >>> > seaside@lists.squeakfoundation.org > >>> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >>> > >>> ________________________________ > >>> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. Sign up > >>> now. > >>> _______________________________________________ > >>> seaside mailing list > >>> seaside@lists.squeakfoundation.org > >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >>> > >> > > > > > > _______________________________________________ > > seaside mailing list > > seaside@lists.squeakfoundation.org > > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > > > > > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > _______________________________________________ > seaside mailing list > seaside@lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside Hotmail: Trusted email with Microsoft’s powerful SPAM protection. Sign up now. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Lukas Renggli
I know it is an impossible to debug thing for anyone not seeing it. I just wanted to give a heads up and I thought that someone could tell me if there was a vm log somewhere to see or if there was a some switch for socket debugging I could turn on in my image so I could help catching it if happened again.
I will just try to pay more attention at what I am doing in case it happens again I guess. On Sun, Oct 11, 2009 at 3:39 PM, Lukas Renggli <[hidden email]> wrote: I use the same configuration with the 4.1.1beta2U VM. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Robert Sirois
Ah, if Robert still has an image with the issue and if he does not mind giving it away for autopsy, maybe someone could look at it :)
May be John Macintosh can help us.
On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois <[hidden email]> wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Robert, can you see your port still listening with this command ?
sudo lsof -i -P | grep -i listen On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat <[hidden email]> wrote: Ah, if Robert still has an image with the issue and if he does not mind giving it away for autopsy, maybe someone could look at it :) _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
I'm hardly what you would call knowledgeable in UNIX lol. Umm.. I just types that statement in and it went to a blank prompt.
I've actually had this problem over the last eight months or so... ever since I started learning Smalltalk and Seaside and friends. What I've noticed is that I'll try requesting something from the server on a given port and it simply won't respond. Uh, I'll let the mailing list know next time it happens, but the last time it's happened to me was a week or two ago and my computer had been on standby for a while if that matters. This is not to say it exclusively occurs after being on standby, only the most recent circumstance I can recall. I even have a whole list of adapters that I've used in the past. All I do is stop the previous one and start a new one lol. RS Let me know if you need any logs or whatever and how to get them - I'm a noob :) Date: Sun, 11 Oct 2009 16:18:55 +0100 Subject: Re: [Seaside] Komanche ? From: [hidden email] To: [hidden email]; [hidden email] Robert, can you see your port still listening with this command ? sudo lsof -i -P | grep -i listen On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat <[hidden email]> wrote: Ah, if Robert still has an image with the issue and if he does not mind giving it away for autopsy, maybe someone could look at it :) Hotmail: Trusted email with powerful SPAM protection. Sign up now. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by Ramiro Diaz Trepat-2
Did you open another image with the same VM? There is a wired behavior
of the Mac VM that makes the second image listen on the same ports as the already running image. This may (or may not) be related. See http://lists.squeakfoundation.org/pipermail/vm-dev/2009-June/002726.html Adrian On Oct 11, 2009, at 17:18 , Ramiro Diaz Trepat wrote: > Robert, can you see your port still listening with this command ? > > sudo lsof -i -P | grep -i listen > > > > > On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat > <[hidden email]>wrote: > >> Ah, if Robert still has an image with the issue and if he does not >> mind >> giving it away for autopsy, maybe someone could look at it :)May be >> John >> Macintosh can help us. >> >> >> >> On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois >> <[hidden email]>wrote: >> >>> I'm running the latest mac vm as well. I believe I attempted the >>> same >>> things to no avail. >>> >>> RS >>> >>>> Date: Sun, 11 Oct 2009 16:39:37 +0200 >>> >>>> Subject: Re: [Seaside] Komanche ? >>>> From: [hidden email] >>>> To: [hidden email] >>>> >>>> I use the same configuration with the 4.1.1beta2U VM. >>>> >>>> Lukas >>>> >>>> 2009/10/11 Ramiro Diaz Trepat <[hidden email]>: >>>>> Correlation does not mean causality, I know. But in my case this >>> happened >>>>> right after saving my image, although I had saved it many times >>>>> before >>>>> without issues. >>>>> Cheers >>>>> >>>>> >>>>> On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat < >>> [hidden email]> >>>>> wrote: >>>>>> >>>>>> Hi Lukas, >>>>>> I am using the latest Pharo, and I have loaded Seaside with >>> ScriptLoader >>>>>> loadSeaside30. I am using it on a Mac with Leopard. >>>>>> I have managed to reuse that port, with random tests and I do not >>> believe >>>>>> there may be causality here, but I will tell you anyway what I >>>>>> did. >>>>>> When this happens, I removed the problematic adaptor from the >>>>>> Seaside >>>>>> Control Panel and created a new one (on the same port), then I >>>>>> tried >>> closing >>>>>> the image and restarting and it did not fix the problem. >>>>>> Although >>> when I >>>>>> closed another non Seaside image I was running and then >>>>>> restarted the >>>>>> problematic image it worked. >>>>>> I wonder now if it is not a mac vm issue or socket issue. >>>>>> Robert, >>> are you >>>>>> also running on a mac? >>>>>> In spite I got the image working again, it is quite worring >>>>>> because >>> we >>>>>> don't know the cause when an image stops answering requests >>>>>> (although >>> the >>>>>> image itself was not hanged at all and kept working fine), and, >>>>>> most >>> weird >>>>>> of all, there is no exception or trace of a fault happening. >>>>>> This is >>> really >>>>>> what is making me wonder if it is not a low level socket issue >>>>>> that >>> never >>>>>> gets to the image for it to throw an exception or anything at >>>>>> all. >>>>>> Cheers >>>>>> >>>>>> r >>>>>> >>>>>> ps: I'm cross posting to Pharo because I believe this is not a >>> Seaside >>>>>> issue. >>>>>> >>>>>> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois < >>> [hidden email]> >>>>>> wrote: >>>>>>> >>>>>>> I'm using Pharo 1.0.10419, but I'm not sure how to check the >>>>>>> other >>> two. I >>>>>>> think I'm still running 2.9 in the image I checked. >>>>>>> >>>>>>> RS >>>>>>> >>>>>>>> Date: Sun, 11 Oct 2009 12:30:37 +0200 >>>>>>>> Subject: Re: [Seaside] Komanche ? >>>>>>>> From: [hidden email] >>>>>>>> To: [hidden email] >>>>>>>> >>>>>>>> I've never seen this problem before. >>>>>>>> >>>>>>>> What version of Pharo? Kom? Seaside? >>>>>>>> >>>>>>>> Lukas >>>>>>>> >>>>>>>> 2009/10/11 Robert Sirois <[hidden email]>: >>>>>>>>> I've also had this problem for quite a while now and have not >>> found >>>>>>>>> any way to fix the problem either. >>>>>>>>> >>>>>>>>> RS >>>>>>>>> >>>>>>>>> Ramiro Diaz Trepat <[hidden email]> wrote: >>>>>>>>> >>>>>>>>>> Something really strange happened to me more than once >>>>>>>>>> now.In a >>>>>>>>>> simple dev >>>>>>>>>> image (Pharo + Seaside3 + Kom on a Mac) after saving the >>>>>>>>>> image >>> at >>>>>>>>>> some >>>>>>>>>> point, Komanche stops answering anything at all, althought >>>>>>>>>> the >>> port >>>>>>>>>> keeps >>>>>>>>>> listening (as listed on a terminal). >>>>>>>>>> No errors are displayed anywere but the port becomes unusable >>> from >>>>>>>>>> that >>>>>>>>>> point on. >>>>>>>>>> If I wish to continue using the same image I have to add >>>>>>>>>> another >>>>>>>>>> adaptor in >>>>>>>>>> the Seaside Control Panel and start again. >>>>>>>>>> The "dead" ports never become usable again, not even stopping >>> and >>>>>>>>>> removing >>>>>>>>>> the adaptor and adding a new one. >>>>>>>>>> I am not even sure that this is a Komanche issue, as I said >>>>>>>>>> no >>> error >>>>>>>>>> of >>>>>>>>>> anykind is visible. >>>>>>>>>> Has anyone come across this before? >>>>>>>>>> _______________________________________________ >>>>>>>>>> seaside mailing list >>>>>>>>>> [hidden email] >>>>>>>>>> >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> seaside mailing list >>>>>>>>> [hidden email] >>>>>>>>> >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Lukas Renggli >>>>>>>> http://www.lukas-renggli.ch >>>>>>>> _______________________________________________ >>>>>>>> seaside mailing list >>>>>>>> [hidden email] >>>>>>>> >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>> >>>>>>> ________________________________ >>>>>>> Your E-mail and More On-the-Go. Get Windows Live Hotmail Free. >>>>>>> Sign >>> up >>>>>>> now. >>>>>>> _______________________________________________ >>>>>>> seaside mailing list >>>>>>> [hidden email] >>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>> >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> seaside mailing list >>>>> [hidden email] >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Lukas Renggli >>>> http://www.lukas-renggli.ch >>>> _______________________________________________ >>>> seaside mailing list >>>> [hidden email] >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> ------------------------------ >>> Hotmail: Trusted email with Microsoft’s powerful SPAM protection. >>> Sign up >>> now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/> >>> >>> _______________________________________________ >>> seaside mailing list >>> [hidden email] >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> >> > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Hi Adrian,
I did open both images with the same VM. I am sure this must be the problem then. As I said in one of the mails, the problem in my case went away when I bounced all the images. It only happens in the Mac VM then? Do we need to report this bug somewhere or is it already reported? Cheers r On Sun, Oct 11, 2009 at 8:56 PM, Adrian Lienhard <[hidden email]> wrote: Did you open another image with the same VM? There is a wired behavior of the Mac VM that makes the second image listen on the same ports as the already running image. This may (or may not) be related. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Hi Ramiro,
Yes, this is an issue of the Mac VM only. It was reported in the sense that I sent a mail with instructions to reproduce the problem to the Squeak-vm mailing list and John acknowledged the problem. I don't know whether John intends to fix this, though. Adrian On Oct 11, 2009, at 22:06 , Ramiro Diaz Trepat wrote: > Hi Adrian, > I did open both images with the same VM. I am sure this must be the > problem then. As I said in one of the mails, the problem in my case > went > away when I bounced all the images. > It only happens in the Mac VM then? > Do we need to report this bug somewhere or is it already reported? > Cheers > > r > > > On Sun, Oct 11, 2009 at 8:56 PM, Adrian Lienhard <[hidden email]> > wrote: > >> Did you open another image with the same VM? There is a wired >> behavior of >> the Mac VM that makes the second image listen on the same ports as >> the >> already running image. This may (or may not) be related. >> >> See >> http://lists.squeakfoundation.org/pipermail/vm-dev/2009-June/002726.html >> >> Adrian >> >> >> On Oct 11, 2009, at 17:18 , Ramiro Diaz Trepat wrote: >> >> Robert, can you see your port still listening with this command ? >>> >>> sudo lsof -i -P | grep -i listen >>> >>> >>> >>> >>> On Sun, Oct 11, 2009 at 3:53 PM, Ramiro Diaz Trepat >>> <[hidden email]>wrote: >>> >>> Ah, if Robert still has an image with the issue and if he does not >>> mind >>>> giving it away for autopsy, maybe someone could look at it :)May >>>> be John >>>> Macintosh can help us. >>>> >>>> >>>> >>>> On Sun, Oct 11, 2009 at 3:49 PM, Robert Sirois <[hidden email] >>>>> wrote: >>>> >>>> I'm running the latest mac vm as well. I believe I attempted the >>>> same >>>>> things to no avail. >>>>> >>>>> RS >>>>> >>>>> Date: Sun, 11 Oct 2009 16:39:37 +0200 >>>>>> >>>>> >>>>> Subject: Re: [Seaside] Komanche ? >>>>>> From: [hidden email] >>>>>> To: [hidden email] >>>>>> >>>>>> I use the same configuration with the 4.1.1beta2U VM. >>>>>> >>>>>> Lukas >>>>>> >>>>>> 2009/10/11 Ramiro Diaz Trepat <[hidden email]>: >>>>>> >>>>>>> Correlation does not mean causality, I know. But in my case >>>>>>> this >>>>>>> >>>>>> happened >>>>> >>>>>> right after saving my image, although I had saved it many times >>>>>> before >>>>>>> without issues. >>>>>>> Cheers >>>>>>> >>>>>>> >>>>>>> On Sun, Oct 11, 2009 at 3:01 PM, Ramiro Diaz Trepat < >>>>>>> >>>>>> [hidden email]> >>>>> >>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi Lukas, >>>>>>>> I am using the latest Pharo, and I have loaded Seaside with >>>>>>>> >>>>>>> ScriptLoader >>>>> >>>>>> loadSeaside30. I am using it on a Mac with Leopard. >>>>>>>> I have managed to reuse that port, with random tests and I do >>>>>>>> not >>>>>>>> >>>>>>> believe >>>>> >>>>>> there may be causality here, but I will tell you anyway what I >>>>>> did. >>>>>>>> When this happens, I removed the problematic adaptor from the >>>>>>>> Seaside >>>>>>>> Control Panel and created a new one (on the same port), then >>>>>>>> I tried >>>>>>>> >>>>>>> closing >>>>> >>>>>> the image and restarting and it did not fix the problem. >>>>>> Although >>>>>>>> >>>>>>> when I >>>>> >>>>>> closed another non Seaside image I was running and then >>>>>> restarted the >>>>>>>> problematic image it worked. >>>>>>>> I wonder now if it is not a mac vm issue or socket issue. >>>>>>>> Robert, >>>>>>>> >>>>>>> are you >>>>> >>>>>> also running on a mac? >>>>>>>> In spite I got the image working again, it is quite worring >>>>>>>> because >>>>>>>> >>>>>>> we >>>>> >>>>>> don't know the cause when an image stops answering requests >>>>>> (although >>>>>>>> >>>>>>> the >>>>> >>>>>> image itself was not hanged at all and kept working fine), and, >>>>>> most >>>>>>>> >>>>>>> weird >>>>> >>>>>> of all, there is no exception or trace of a fault happening. >>>>>> This is >>>>>>>> >>>>>>> really >>>>> >>>>>> what is making me wonder if it is not a low level socket issue >>>>>> that >>>>>>>> >>>>>>> never >>>>> >>>>>> gets to the image for it to throw an exception or anything at >>>>>> all. >>>>>>>> Cheers >>>>>>>> >>>>>>>> r >>>>>>>> >>>>>>>> ps: I'm cross posting to Pharo because I believe this is not a >>>>>>>> >>>>>>> Seaside >>>>> >>>>>> issue. >>>>>>>> >>>>>>>> On Sun, Oct 11, 2009 at 12:13 PM, Robert Sirois < >>>>>>>> >>>>>>> [hidden email]> >>>>> >>>>>> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> I'm using Pharo 1.0.10419, but I'm not sure how to check the >>>>>>>>> other >>>>>>>>> >>>>>>>> two. I >>>>> >>>>>> think I'm still running 2.9 in the image I checked. >>>>>>>>> >>>>>>>>> RS >>>>>>>>> >>>>>>>>> Date: Sun, 11 Oct 2009 12:30:37 +0200 >>>>>>>>>> Subject: Re: [Seaside] Komanche ? >>>>>>>>>> From: [hidden email] >>>>>>>>>> To: [hidden email] >>>>>>>>>> >>>>>>>>>> I've never seen this problem before. >>>>>>>>>> >>>>>>>>>> What version of Pharo? Kom? Seaside? >>>>>>>>>> >>>>>>>>>> Lukas >>>>>>>>>> >>>>>>>>>> 2009/10/11 Robert Sirois <[hidden email]>: >>>>>>>>>> >>>>>>>>>>> I've also had this problem for quite a while now and have >>>>>>>>>>> not >>>>>>>>>>> >>>>>>>>>> found >>>>> >>>>>> any way to fix the problem either. >>>>>>>>>>> >>>>>>>>>>> RS >>>>>>>>>>> >>>>>>>>>>> Ramiro Diaz Trepat <[hidden email]> wrote: >>>>>>>>>>> >>>>>>>>>>> Something really strange happened to me more than once >>>>>>>>>>> now.In a >>>>>>>>>>>> simple dev >>>>>>>>>>>> image (Pharo + Seaside3 + Kom on a Mac) after saving the >>>>>>>>>>>> image >>>>>>>>>>>> >>>>>>>>>>> at >>>>> >>>>>> some >>>>>>>>>>>> point, Komanche stops answering anything at all, >>>>>>>>>>>> althought the >>>>>>>>>>>> >>>>>>>>>>> port >>>>> >>>>>> keeps >>>>>>>>>>>> listening (as listed on a terminal). >>>>>>>>>>>> No errors are displayed anywere but the port becomes >>>>>>>>>>>> unusable >>>>>>>>>>>> >>>>>>>>>>> from >>>>> >>>>>> that >>>>>>>>>>>> point on. >>>>>>>>>>>> If I wish to continue using the same image I have to add >>>>>>>>>>>> another >>>>>>>>>>>> adaptor in >>>>>>>>>>>> the Seaside Control Panel and start again. >>>>>>>>>>>> The "dead" ports never become usable again, not even >>>>>>>>>>>> stopping >>>>>>>>>>>> >>>>>>>>>>> and >>>>> >>>>>> removing >>>>>>>>>>>> the adaptor and adding a new one. >>>>>>>>>>>> I am not even sure that this is a Komanche issue, as I >>>>>>>>>>>> said no >>>>>>>>>>>> >>>>>>>>>>> error >>>>> >>>>>> of >>>>>>>>>>>> anykind is visible. >>>>>>>>>>>> Has anyone come across this before? >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> seaside mailing list >>>>>>>>>>>> [hidden email] >>>>>>>>>>>> >>>>>>>>>>>> >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> seaside mailing list >>>>>>>>>>> [hidden email] >>>>>>>>>>> >>>>>>>>>>> >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Lukas Renggli >>>>>>>>>> http://www.lukas-renggli.ch >>>>>>>>>> _______________________________________________ >>>>>>>>>> seaside mailing list >>>>>>>>>> [hidden email] >>>>>>>>>> >>>>>>>>>> >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>>> >>>>>>>>> ________________________________ >>>>>>>>> Your E-mail and More On-the-Go. Get Windows Live Hotmail >>>>>>>>> Free. Sign >>>>>>>>> >>>>>>>> up >>>>> >>>>>> now. >>>>>>>>> _______________________________________________ >>>>>>>>> seaside mailing list >>>>>>>>> [hidden email] >>>>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> seaside mailing list >>>>>>> [hidden email] >>>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Lukas Renggli >>>>>> http://www.lukas-renggli.ch >>>>>> _______________________________________________ >>>>>> seaside mailing list >>>>>> [hidden email] >>>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/ >>>>>> seaside >>>>>> >>>>> >>>>> ------------------------------ >>>>> Hotmail: Trusted email with Microsoft’s powerful SPAM >>>>> protection. Sign >>>>> up >>>>> now. <http://clk.atdmt.com/GBL/go/177141664/direct/01/> >>>>> >>>>> _______________________________________________ >>>>> seaside mailing list >>>>> [hidden email] >>>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>>> >>>>> >>>>> >>>> _______________________________________________ >>> seaside mailing list >>> [hidden email] >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >> >> _______________________________________________ >> seaside mailing list >> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
Ok.
(a) the first problem is how the 2nd VM is launched. We actually use Apple Script to re-launch the binary with the supplied image when we receive the open document apple event. The behavior of this is different between 10.3, 10.4, 10.5 and I assume the 10.6 is the same as 10.5 because we had reported an issue with the 10.4 behavior they fixed in 10.5 Indications are is that the apple script code executes a execv (but we are not sure) this then retains the open file descriptors so it retains the knowledge about open sockets. (b) I'm not sure what the behavor would be if you launch VM "A" then listen on socket 8080. Then launch VM "B" then again listen on socket 8080 will both virtual machines "A" and "B" attempt to service socket 8080, or will VM "B" get told it cannot listen on 8080 because it does not own it? Pending is work on a pure objective-c based squeak VM based on the the iPhone work, which would alter the behaviour. But if someone can answer (b) then maybe we can see about an interim fix to deal with (a) On 2009-10-12, at 1:56 AM, Adrian Lienhard wrote: > Hi Ramiro, > > Yes, this is an issue of the Mac VM only. > > It was reported in the sense that I sent a mail with instructions to > reproduce the problem to the Squeak-vm mailing list and John > acknowledged the problem. I don't know whether John intends to fix > this, though. > > Adrian > -- = = = ======================================================================== John M. McIntosh <[hidden email]> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ======================================================================== _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: [Pharo-project] Komanche ?
|
|
Small clarification. In my case the different VMs did not use the same port numbers, they had different ports, indeed one of them did not even have Seaside installed.
f On Mon, Oct 12, 2009 at 9:26 PM, John M McIntosh <[hidden email]> wrote: Ok. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: [Pharo-project] Komanche ?
|
|
On Oct 12, 2009, at 23:10 , Ramiro Diaz Trepat wrote:
> Small clarification. In my case the different VMs did not use the > same port > numbers, they had different ports, indeed one of them did not even > have > Seaside installed. It does not matter what ports the second image opens during startup... the second VM proces would still listen on the same ports like the first one. Adrian > > f > > > On Mon, Oct 12, 2009 at 9:26 PM, John M McIntosh < > [hidden email]> wrote: > >> Ok. >> (a) the first problem is how the 2nd VM is launched. We actually >> use Apple >> Script to re-launch the binary with the supplied image when >> we receive the open document apple event. The behavior of this is >> different between 10.3, 10.4, 10.5 and I assume the 10.6 is the same >> as 10.5 because we had reported an issue with the 10.4 behavior >> they fixed >> in 10.5 >> >> Indications are is that the apple script code executes a execv (but >> we are >> not sure) >> this then retains the open file descriptors so it retains the >> knowledge >> about open sockets. >> >> >> (b) I'm not sure what the behavor would be if you launch VM "A" >> then listen >> on socket 8080. Then launch VM "B" then again listen on socket 8080 >> will both virtual machines "A" and "B" attempt to service socket >> 8080, or >> will VM "B" get told it cannot listen on 8080 because it does not >> own it? >> >> >> Pending is work on a pure objective-c based squeak VM based on the >> the >> iPhone work, which would alter the behaviour. >> But if someone can answer (b) then maybe we can see about an >> interim fix to >> deal with (a) >> >> >> On 2009-10-12, at 1:56 AM, Adrian Lienhard wrote: >> >> Hi Ramiro, >>> >>> Yes, this is an issue of the Mac VM only. >>> >>> It was reported in the sense that I sent a mail with instructions to >>> reproduce the problem to the Squeak-vm mailing list and John >>> acknowledged the problem. I don't know whether John intends to fix >>> this, though. >>> >>> Adrian >>> >>> >> -- >> = >> = >> = >> = >> = >> = >> ===================================================================== >> John M. McIntosh <[hidden email]> Twitter: >> squeaker68882 >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >> = >> = >> = >> = >> = >> = >> ===================================================================== >> >> >> >> >> >> _______________________________________________ >> seaside mailing list >> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by johnmci
On 2009-10-12, at 1:26 PM, John M McIntosh <[hidden email] > wrote: > (b) I'm not sure what the behavor would be if you launch VM "A" then > listen on socket 8080. Then launch VM "B" then again listen on > socket 8080 > will both virtual machines "A" and "B" attempt to service socket > 8080, or will VM "B" get told it cannot listen on 8080 because it > does not own it? VM B will fail in its attempt to listen on the socket. I've run into this a few times by accident. Colin _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |