Time for some Oz magic... Got this kind of thing as well a couple times. Phil On Fri, Dec 27, 2013 at 7:40 AM, Esteban Lorenzano <estebanlm@gmail.com>wrote:

do you have a PharoDebug.log?

this things are usually related to an open socket not well handled…

On 26 Dec 2013, at 22:04, Hernán Morales Durand <hernan.morales@gmail.com> wrote:

OS VM version Image version ?

2013/12/26 Esteban A. Maringolo <emaringolo@gmail.com>

...

Help please!

I closed my image with "Save & Quit" and now everytime I try to open it it opens the window but closes immediately. No error or anything else.

It is... the image opens, I can see a couple of workspaces. But then quits.

I'm using: /pharo-ui myapp.image

I also tried to start it using my startup script, and the same thing happens.

Any idea?

Regards.

Esteban A. Maringolo

Next time put information about your environment, which OS, which Image, which VM, because people cannot help with such missing important information. People cannot guess what Pharo are you using. So any replies would be wasteful. 2013/12/27 Esteban A. Maringolo <emaringolo@gmail.com>

Esteban Lorenzano wrote:

...

do you have a PharoDebug.log? this things are usually related to an open socket not well handled…

It might be, the last thing I did before saving was to close the Zinc server. But it never failed before.

If there was a PharoDebug.log I didn't see it. (see next)

2013/12/27 phil@highoctane.be <phil@highoctane.be>:

...

Time for some Oz magic...

Got this kind of thing as well a couple times.

Sometimes I rely too much on the image stability. And when it fails, it hurts.

Fortunately I saved all the Monticello packages before saving and closing the image. So I was able to restore it quickly.

I need to implement a private CI ASAP.

Regards!

Hi Esteban, No harsh intended, really :) If this is a new Pharo web based-project worth to comment, let us know about the experience. Cheers, Hernán 2013/12/29 Esteban A. Maringolo <emaringolo@gmail.com>

2013/12/27 Hernán Morales Durand <hernan.morales@gmail.com>:

...

Next time put information about your environment, which OS, which Image, which VM, because people cannot help with such missing important information. People cannot guess what Pharo are you using. So any replies would be wasteful.

No need to be harsh. I know I should give more information, but some errors are common, independently of the VM, OS and Image. Maybe this was the case, as Esteban Lorenzano suggested.

I was a couple of hours away from uploading the server into production. Fortunately I was able to apply the changes on a previously backup version of the image.

Next time I'll provide more details. By now the server has been up since last Friday :)

Regards,

Esteban A. Maringolo