Smalltalk › Pharo › Pharo Smalltalk Users

Voyage Timeout

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

HilaireFernandes

Voyage Timeout

Hi,

When I configure a production image with command st handler as following:

pharo myImage st --save --quit configureMyImage.st

I notice at image start up, a Socket timeout error.

In the configureMyImage.st script, among other things, I open a
singleton Voyage repository. I added a 5s delay at the end of this
script, just wondering if image was shutdown before Voyage establishes
connection with the Mongo DB, but no.

Any incompatibility issues to be aware of between st command handler
(particularly the --save part) and Voyage repository?

Thanks,
Hilaire

--
Dr. Geo
http://drgeo.eu

PharoDebug.log (9K) Download Attachment

http://drgeo.eu

HilaireFernandes

Re: Voyage Timeout

If I open manualy this image execute the configureMyImage.st code from a
playground, then save the image, I don't have a Voyage time error at
start up.

Are there non friendly interaction between voyage/socket and st command
handler?

Hilaire

Le 22/03/2017 à 20:35, Hilaire a écrit :

> Hi,
>
> When I configure a production image with command st handler as following:
>
> pharo myImage st --save --quit configureMyImage.st
>
> I notice at image start up, a Socket timeout error.
>
> In the configureMyImage.st script, among other things, I open a
> singleton Voyage repository. I added a 5s delay at the end of this
> script, just wondering if image was shutdown before Voyage establishes
> connection with the Mongo DB, but no.
>
> Any incompatibility issues to be aware of between st command handler
> (particularly the --save part) and Voyage repository?
>
> Thanks,
> Hilaire

--
Dr. Geo
http://drgeo.eu

http://drgeo.eu

Sabine Manaa

Re: Voyage Timeout

Hi Hilaire,

I also use a command line handler for start in a new image with voyage . I start it like this on windows:

.\...\Pharo5.0.image --no-default-preferences eval --save " MCRepositoryGroup default addRepository: (MCHttpRepository location: 'http://smalltalkhub.com/mc/Sabine/RKA24/main' user: 'Sabine' password: 'xxx').Metacello new smalltalkhubUser: 'Sabine' project: 'RKA24'; configuration: 'RKA24'; version: #development; load".

Are you sure that the code in the file is executed? I had similar problems and asked in slack. Unfortunately the discussion is gone. It came out that some combinations of file configuration and command line commands do not work. I currently don't remember which (save?) but perhaps this brings you to an idea.

Regards

Sabine

2017-03-24 20:51 GMT+01:00 HilaireFernandes [via Smalltalk] <[hidden email]>:

If I open manualy this image execute the configureMyImage.st code from a
playground, then save the image, I don't have a Voyage time error at
start up.

Are there non friendly interaction between voyage/socket and st command
handler?

Hilaire

Le 22/03/2017 à 20:35, Hilaire a écrit :

> Hi,
>
> When I configure a production image with command st handler as following:
>
> pharo myImage st --save --quit configureMyImage.st
>
> I notice at image start up, a Socket timeout error.
>
> In the configureMyImage.st script, among other things, I open a
> singleton Voyage repository. I added a 5s delay at the end of this
> script, just wondering if image was shutdown before Voyage establishes
> connection with the Mongo DB, but no.
>
> Any incompatibility issues to be aware of between st command handler
> (particularly the --save part) and Voyage repository?
>
> Thanks,
> Hilaire
--
Dr. Geo
http://drgeo.eu

http://drgeo.eu

If you reply to this email, your message will be added to the discussion below:
http://forum.world.st/Voyage-Timeout-tp4939672p4939873.html

To start a new topic under Pharo Smalltalk Users, email [hidden email]
To unsubscribe from Pharo Smalltalk Users, click here.
NAML

HilaireFernandes

Re: Voyage Timeout

Hi Sabine,

Thanks to share your experience.

My process is in 3 folds:

1. I build from bash and smalltalk scripts an application archive for
deployment, as I do for Dr.Geo (with configured image, VM, bootstart
data and bash scripts)

2. On the target host, the archive is deployed (unarchived), then bash
script launches the image for application installation (Mongo repo build
up and filled with data). The image is not saved.

3. The image is launched again with a configured smalltalk script, then
saved at the end. It should result in image to run the application,
hopefully for multiple running instance with load balancing (not there yet).

The 3. does not get well. As you suggested from your response, I will
try to use the 'eval' command handler instead of the 'st' command
handler and see how it goes.

Thanks

Hilaire

Le 25/03/2017 à 07:55, Sabine Manaa a écrit :

> Hi Hilaire,
>
> I also use a command line handler for start in a new image with voyage .
> I start it like this on windows:
>
> .\...\Pharo5.0.image --no-default-preferences eval --save "
> MCRepositoryGroup default addRepository: (MCHttpRepository location:
> 'http://smalltalkhub.com/mc/Sabine/RKA24/main' user: 'Sabine'
> password: 'xxx').Metacello new smalltalkhubUser: 'Sabine' project:
> 'RKA24'; configuration: 'RKA24'; version: #development; load".
>
> Are you sure that the code in the file is executed? I had similar
> problems and asked in slack. Unfortunately the discussion is gone. It
> came out that some combinations of file configuration and command line
> commands do not work. I currently don't remember which (save?) but
> perhaps this brings you to an idea.
>
> Regards
> Sabine

--
Dr. Geo
http://drgeo.eu

http://drgeo.eu

Stephane Ducasse-3

Re: Voyage Timeout

Hilaire

you should think to move to Pharo 50. We closed around 1500 issues between

pharo 40 and pharo 50 and the same amount between pharo 50 and pharo 60.

Pharo 50 is really stable and working well

Stef

On Sat, Mar 25, 2017 at 8:58 AM, Hilaire <[hidden email]> wrote:

Hi Sabine,

Thanks to share your experience.

My process is in 3 folds:

1. I build from bash and smalltalk scripts an application archive for
deployment, as I do for Dr.Geo (with configured image, VM, bootstart
data and bash scripts)

2. On the target host, the archive is deployed (unarchived), then bash
script launches the image for application installation (Mongo repo build
up and filled with data). The image is not saved.

3. The image is launched again with a configured smalltalk script, then
saved at the end. It should result in image to run the application,
hopefully for multiple running instance with load balancing (not there yet).

The 3. does not get well. As you suggested from your response, I will
try to use the 'eval' command handler instead of the 'st' command
handler and see how it goes.

Thanks

Hilaire

Le 25/03/2017 à 07:55, Sabine Manaa a écrit :
> Hi Hilaire,
>
> I also use a command line handler for start in a new image with voyage .
> I start it like this on windows:
>
> .\...\Pharo5.0.image --no-default-preferences eval --save "
> MCRepositoryGroup default addRepository: (MCHttpRepository location:
> 'http://smalltalkhub.com/mc/Sabine/RKA24/main' user: 'Sabine'
> password: 'xxx').Metacello new smalltalkhubUser: 'Sabine' project:
> 'RKA24'; configuration: 'RKA24'; version: #development; load".
>
> Are you sure that the code in the file is executed? I had similar
> problems and asked in slack. Unfortunately the discussion is gone. It
> came out that some combinations of file configuration and command line
> commands do not work. I currently don't remember which (save?) but
> perhaps this brings you to an idea.
>
> Regards
> Sabine

--
Dr. Geo
http://drgeo.eu

HilaireFernandes

Re: Voyage Timeout

Indeed. It was just I was in the middle of something.

Le 25/03/2017 à 19:10, Stephane Ducasse a écrit :
> you should think to move to Pharo 50. We closed around 1500 issues between
> pharo 40 and pharo 50 and the same amount between pharo 50 and pharo 60.
> Pharo 50 is really stable and working well

--
Dr. Geo
http://drgeo.eu

http://drgeo.eu