Re: [Pharo-project] Too many semaphores, image blocked

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: [Pharo-project] Too many semaphores, image blocked

Eliot Miranda-2
 


On Fri, Oct 7, 2011 at 2:31 PM, Schwab,Wilhelm K <[hidden email]> wrote:
Eliot,

Is there a way to save the image given that it is non-responsive?  Otherwise (and this could be "how it is") one would have to apply the fix before having the problem.  Just curious.  Should we all periodically take a semaphore head count in our images?

I try to leave a reasonable trail of backups of working images just in case I do something stupid; a little uncertainty can motivate cautious behavior...

Hmm... I think what's needed is a command-line parameter.  Give me a few...


Bill



________________________________________
From: [hidden email] [[hidden email]] On Behalf Of Eliot Miranda [[hidden email]]
Sent: Friday, October 07, 2011 4:22 PM
To: [hidden email]
Subject: Re: [Pharo-project] Too many semaphores, image blocked

Hi Janko,

   you need to /save/ the image having applied Smalltalk vm maxExternalSemaphoresSilently: 3000.  This must be set in the image at start-up, not after the image has loaded.  i.e. the VM inspects the value saved in the image header and applies the value *before* the image starts running.

2011/10/7 Janko Mivšek <[hidden email]<mailto:[hidden email]>>
Hi Henrik,

S, Henrik Sperre Johansen piše:
> On 05.10.2011 01:18, Schwab,Wilhelm K wrote:

>> The log you posted contains the string "Not enough space for external
>> objects, set a larger size at startup!"  Maybe a command-line switch
>> to the vm will give you more memory and a way to get the image going?

> Smalltalk vm maxExternalSemaphoresSilently: aSize  would be the line to
> include.
> If the script passed on a command line is higher in the startuplist than
> the InputEventSensor, it would get it working again.

Ok, I'm back having time to look at this problem and I made a start.st<http://start.st>
script below, start the image with it, but get the same blank screen as
you can see in attached screenshot. Ctrl or Alt . doesn't help.

start.st<http://start.st>
Smalltalk vm maxExternalSemaphoresSilently: 3000


./Contents/Linux/squeak ./Contents/Resources/waste.image start.st<http://start.st>

Any more idea? Otherwise I'll start to recover from changes, but
starting this nonresponsive image would of course be faster solution:)

Best regards
Janko


--
Janko Mivšek
Aida/Web
Smalltalk Web Application Server
http://www.aidaweb.si



--
best,
Eliot





--
best,
Eliot

Reply | Threaded
Open this post in threaded view
|

Re: [squeak-dev] Re: [Pharo-project] Too many semaphores, image blocked

David T. Lewis
 
For an immediate workaround, you can probably just open the image with
an interpreter VM, change the parameter, save and restart on Cog.

Dave


On Fri, Oct 07, 2011 at 02:43:16PM -0700, Eliot Miranda wrote:

> On Fri, Oct 7, 2011 at 2:31 PM, Schwab,Wilhelm K <[hidden email]>wrote:
>
> > Eliot,
> >
> > Is there a way to save the image given that it is non-responsive?
> >  Otherwise (and this could be "how it is") one would have to apply the fix
> > before having the problem.  Just curious.  Should we all periodically take a
> > semaphore head count in our images?
> >
> > I try to leave a reasonable trail of backups of working images just in case
> > I do something stupid; a little uncertainty can motivate cautious
> > behavior...
> >
>
> Hmm... I think what's needed is a command-line parameter.  Give me a few...
>
>
> > Bill
> >
> >
> >
> > ________________________________________
> > From: [hidden email] [
> > [hidden email]] On Behalf Of Eliot Miranda [
> > [hidden email]]
> > Sent: Friday, October 07, 2011 4:22 PM
> > To: [hidden email]
> > Subject: Re: [Pharo-project] Too many semaphores, image blocked
> >
> > Hi Janko,
> >
> >    you need to /save/ the image having applied Smalltalk vm
> > maxExternalSemaphoresSilently: 3000.  This must be set in the image at
> > start-up, not after the image has loaded.  i.e. the VM inspects the value
> > saved in the image header and applies the value *before* the image starts
> > running.
> >
> > 2011/10/7 Janko Miv??ek <[hidden email]<mailto:
> > [hidden email]>>
> > Hi Henrik,
> >
> > S, Henrik Sperre Johansen pi??e:
> > > On 05.10.2011 01:18, Schwab,Wilhelm K wrote:
> >
> > >> The log you posted contains the string "Not enough space for external
> > >> objects, set a larger size at startup!"  Maybe a command-line switch
> > >> to the vm will give you more memory and a way to get the image going?
> >
> > > Smalltalk vm maxExternalSemaphoresSilently: aSize  would be the line to
> > > include.
> > > If the script passed on a command line is higher in the startuplist than
> > > the InputEventSensor, it would get it working again.
> >
> > Ok, I'm back having time to look at this problem and I made a start.st<
> > http://start.st>
> > script below, start the image with it, but get the same blank screen as
> > you can see in attached screenshot. Ctrl or Alt . doesn't help.
> >
> > start.st<http://start.st>
> > Smalltalk vm maxExternalSemaphoresSilently: 3000
> >
> >
> > ./Contents/Linux/squeak ./Contents/Resources/waste.image start.st<
> > http://start.st>
> >
> > Any more idea? Otherwise I'll start to recover from changes, but
> > starting this nonresponsive image would of course be faster solution:)
> >
> > Best regards
> > Janko
> >
> >
> > --
> > Janko Miv??ek
> > Aida/Web
> > Smalltalk Web Application Server
> > http://www.aidaweb.si
> >
> >
> >
> > --
> > best,
> > Eliot
> >
> >
> >
>
>
> --
> best,
> Eliot

>