Hi,
i have a server in a local network where run a GemStone version '3.1.0.1' update at GLASS : * 1.0-beta.9 <development> On the MAC desktop i run a GemTools ( based on Pharo-1.1-11411 Latest update: #11411 ) update to * 1.0-beta.8.7 <release> to port my development package to GLASS. Problem: Now when open the GemTools Monticello and add a new repository based on directory on local desktop /Users/dtr/MonticelloDTR none entry is add to the repository list. Any idea ? My development environment on the MAC is based on Pharo1.4 Latest update: #14445 wtih : ConfigurationOfSeaside30 3.0.7.1 ConfigurationOfMagritte3 3.0 ConfigurationOfPier3 3.0.0 The relative Monticello work fine on the local directory /Users/dtr/MonticelloDTR Thanks, Dario |
Dario,
I would assume that the path that you are using to add the repository is incorrect in some way (the Monticello browser filters out repositories that "don't exist") ... which menu item item are you using to add the repository? directory directory on .... When your stone/gems are on the same machine it doesn't matter (the 'directory on' form provides much better performance. When your stone/gems are on a different machine (which sounds like the case here) then you need to use the 'directory' form, but be aware that this form is much slower ... I would recommend that you always use the "directory on ..." form which means that you'd be creating repositories on the stone/gems machine and the paths provided are based on the directory structure on that machine ... Dale ----- Original Message ----- | From: "Dario Trussardi" <[hidden email]> | To: "beta discussion Gemstone Seaside" <[hidden email]> | Sent: Tuesday, November 27, 2012 8:21:41 AM | Subject: [GS/SS Beta] GLASS monticello don't work with local directory on MAC desktop | | Hi, | | i have a server in a local network where run a GemStone version | '3.1.0.1' update at GLASS : * 1.0-beta.9 <development> | | On the MAC desktop i run a GemTools ( based on Pharo-1.1-11411 | Latest update: #11411 ) update to * 1.0-beta.8.7 <release> | | to port my development package to GLASS. | | | Problem: Now when open the GemTools Monticello and add a new | repository based on directory on local desktop | /Users/dtr/MonticelloDTR | | none entry is add to the repository list. | | | | Any idea ? | | | | My development environment on the MAC is based on Pharo1.4 Latest | update: #14445 | | | wtih : ConfigurationOfSeaside30 3.0.7.1 | | ConfigurationOfMagritte3 3.0 | | ConfigurationOfPier3 3.0.0 | | The relative Monticello work fine on the local directory | /Users/dtr/MonticelloDTR | | | | | Thanks, | | Dario |
Ciao Dale,
> Dario, > > I would assume that the path that you are using to add the repository is incorrect in some way (the Monticello browser filters out repositories that "don't exist") ... which menu item item are you using to add the repository? > > directory I use directory In the same hardware configuration i have a GLASS 2.4.1run on the server and Gemtools update to * 1.0-beta.8.3 on the MAC. With this all work fine. I create a new directory /mnt/test/ with a package on the MAC and add this to the repository items of GemTools update to * 1.0-beta.8.7 <release> with directory menu option When i open the repository from GemTools it don't report any package. With hold Gemtools 1.0-beta.8.3 all work correctly. > directory on .... > > When your stone/gems are on the same machine it doesn't matter (the 'directory on' form provides much better performance. When your stone/gems are on a different machine (which sounds like the case here) then you need to use the 'directory' form, but be aware that this form is much slower ... I would recommend that you always use the "directory on ..." form which means that you'd be creating repositories on the stone/gems machine and the paths provided are based on the directory structure on that machine ... I agree, but in the development environment on the MAC based on Pharo 1.4 the Monticello +repository don't include the directoty on.... options. How i can configured the monticello remote directory on the server where run stone/gems Thank, Dario > > Dale > > ----- Original Message ----- > | From: "Dario Trussardi" <[hidden email]> > | To: "beta discussion Gemstone Seaside" <[hidden email]> > | Sent: Tuesday, November 27, 2012 8:21:41 AM > | Subject: [GS/SS Beta] GLASS monticello don't work with local directory on MAC desktop > | > | Hi, > | > | i have a server in a local network where run a GemStone version > | '3.1.0.1' update at GLASS : * 1.0-beta.9 <development> > | > | On the MAC desktop i run a GemTools ( based on Pharo-1.1-11411 > | Latest update: #11411 ) update to * 1.0-beta.8.7 <release> > | > | to port my development package to GLASS. > | > | > | Problem: Now when open the GemTools Monticello and add a new > | repository based on directory on local desktop > | /Users/dtr/MonticelloDTR > | > | none entry is add to the repository list. > | > | > | > | Any idea ? > | > | > | > | My development environment on the MAC is based on Pharo1.4 Latest > | update: #14445 > | > | > | wtih : ConfigurationOfSeaside30 3.0.7.1 > | > | ConfigurationOfMagritte3 3.0 > | > | ConfigurationOfPier3 3.0.0 > | > | The relative Monticello work fine on the local directory > | /Users/dtr/MonticelloDTR > | > | > | > | > | Thanks, > | > | Dario |
Dario,
Are you using the same stone when comparing your results between GemTools 1.0-beta.8.3 and GemTools 1.0-beta.8.7? I would be surprised if you are seeing differences in MonticelloBrowser behavior between two different GemTools versions (especially these two versions) ... I am assuming that the differences are showing up because you are running against different stones and using different versions of the gci libraries ... So I guess I would like to know more details about how you are running things: the session description used for login for both variants, the version of Pharo you are running on and the version of GLASS that you are running against will be a good starting point... also the versions of the gci libraries that you are using (the gemtools one-click version would be fine if you are using a one-click)... I've got a mac myself and I've been using directory-based repositories with gemstone 3.1.x but I tend to run the stone on my mac, so I don't have much experience with using monticello repositories with a remote stone ... also I left my mac at home, so I can't easily run tests right now ... I'll take your setup for spin tonight when I get home ... I am suspicious that you are hitting a bug in the 3.1.0.1 gci libraries, but I'll have to verify that ... Pharo doesn't have option for "remote directories" so I guess we'll have to figure out what's going wrong ... in the case of a bug, I assume that you could use unix level tools for synchronizing a directory between your mac and the stone/gem machine ... Dale ----- Original Message ----- | From: "Dario Trussardi" <[hidden email]> | To: "GemStone Seaside beta discussion" <[hidden email]> | Sent: Wednesday, November 28, 2012 7:45:09 AM | Subject: Re: [GS/SS Beta] GLASS monticello don't work with local directory on MAC desktop | | Ciao Dale, | | | > Dario, | > | > I would assume that the path that you are using to add the | > repository is incorrect in some way (the Monticello browser | > filters out repositories that "don't exist") ... which menu item | > item are you using to add the repository? | > | > directory | | I use directory | | In the same hardware configuration i have a GLASS 2.4.1run on the | server | | and Gemtools update to * 1.0-beta.8.3 on the MAC. | | With this all work fine. | | | | | I create a new directory /mnt/test/ with a package on the MAC | and add this to the repository items of GemTools update to * | 1.0-beta.8.7 <release> with directory menu option | | When i open the repository from GemTools it don't report any | package. | | | With hold Gemtools 1.0-beta.8.3 all work correctly. | | | | > directory on .... | > | > When your stone/gems are on the same machine it doesn't matter (the | > 'directory on' form provides much better performance. When your | > stone/gems are on a different machine (which sounds like the case | > here) then you need to use the 'directory' form, but be aware that | > this form is much slower ... I would recommend that you always use | > the "directory on ..." form which means that you'd be creating | > repositories on the stone/gems machine and the paths provided are | > based on the directory structure on that machine ... | | I agree, but in the development environment on the MAC based on Pharo | 1.4 the Monticello | | +repository don't include the directoty on.... options. | | How i can configured the monticello remote directory on the server | where run stone/gems | | Thank, | | Dario | | > | > Dale | > | > ----- Original Message ----- | > | From: "Dario Trussardi" <[hidden email]> | > | To: "beta discussion Gemstone Seaside" | > | <[hidden email]> | > | Sent: Tuesday, November 27, 2012 8:21:41 AM | > | Subject: [GS/SS Beta] GLASS monticello don't work with local | > | directory on MAC desktop | > | | > | Hi, | > | | > | i have a server in a local network where run a GemStone version | > | '3.1.0.1' update at GLASS : * 1.0-beta.9 <development> | > | | > | On the MAC desktop i run a GemTools ( based on Pharo-1.1-11411 | > | Latest update: #11411 ) update to * 1.0-beta.8.7 <release> | > | | > | to port my development package to GLASS. | > | | > | | > | Problem: Now when open the GemTools Monticello and add a new | > | repository based on directory on local desktop | > | /Users/dtr/MonticelloDTR | > | | > | none entry is add to the repository list. | > | | > | | > | | > | Any idea ? | > | | > | | > | | > | My development environment on the MAC is based on Pharo1.4 | > | Latest | > | update: #14445 | > | | > | | > | wtih : ConfigurationOfSeaside30 3.0.7.1 | > | | > | ConfigurationOfMagritte3 3.0 | > | | > | ConfigurationOfPier3 3.0.0 | > | | > | The relative Monticello work fine on the local directory | > | /Users/dtr/MonticelloDTR | > | | > | | > | | > | | > | Thanks, | > | | > | Dario | |
In reply to this post by dario trussardi
Dario
Am 28.11.2012 um 16:45 schrieb Dario Trussardi: > > >> directory on .... >> >> When your stone/gems are on the same machine it doesn't matter (the 'directory on' form provides much better performance. When your stone/gems are on a different machine (which sounds like the case here) then you need to use the 'directory' form, but be aware that this form is much slower ... I would recommend that you always use the "directory on ..." form which means that you'd be creating repositories on the stone/gems machine and the paths provided are based on the directory structure on that machine ... > > I agree, but in the development environment on the MAC based on Pharo 1.4 the Monticello > > +repository don't include the directoty on.... options. > > How i can configured the monticello remote directory on the server where run stone/gems > Are you certain that you use the GemStone/GemTools monticello Browser or do you accidentally use the Pharo one? best -Tobias |
In reply to this post by Dale Henrichs
Ciao Dale,
sorry for the delay, but I was sick. > Dario, > > Are you using the same stone when comparing your results between GemTools 1.0-beta.8.3 and GemTools 1.0-beta.8.7? No, the GemTools 1.0-beta.8.3 is relative to a one GLASS 2.4.1 the GemTools 1.0-beta.8.7 is relative to a one GLASS 3.1.0.1 > > I would be surprised if you are seeing differences in MonticelloBrowser behavior between two different GemTools versions (especially these two versions) ... I am assuming that the differences are showing up because you are running against different stones and using different versions of the gci libraries ... > > So I guess I would like to know more details about how you are running things: the session description used for login for both variants, I REPORT SOME DATA: > the version of Pharo you are running on THIS IS RELATIVE TO GemTools 1.0-beta.8.3 OGStandardSessionDescription new name: 'Gofame'; stoneHost: 'monviso'; stoneName: 'gofame'; gemHost: 'monviso'; netLDI: '50377'; userId: 'DataCurator'; password: 'mypassword'; backupDirectory: '/gofametran/'; yourself. Pharo-1.0Latest update: #10517 THIS IS RELATIVE TO GemTools 1.0-beta.8.7 OGCustomSessionDescription new name: 'MonvisoGruppi'; stoneHost: 'Monviso'; stoneName: 'gruppi'; gemHost: 'monviso'; netLDI: '50379'; gemTask: 'gemnetobject'; userId: 'DataCurator'; password: 'mypassword'; osUserId: ''; osPassword: ''; backupDirectory: '/DTRdbBackups/backupGruppi/'; dataDirectory: ''; yourself. Pharo-1.1-11411 Latest update: #11411 > and the version of GLASS that you are running against will be a good starting point. I start the GLASS 3.1.0.1 with the file : startoobgruppi it ' s: source /DTRDataBase/opt3101/gemstone/product/seaside/defSeaside ## export GEMSTONE_LOGDIR=$GEMSTONE/EnvGruppi/log export GEMSTONE_DATADIR=$GEMSTONE/EnvGruppi/data ## export GEMSTONE_NAME=gruppi export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf ## export PATH=$GEMSTONE/EnvGruppi/bin:$PATH ### $GEMSTONE/EnvGruppi/bin/startGemstone $GEMSTONE/EnvGruppi/bin/runSeasideGems30 start WAFastCGIAdaptor "9010 9011 9012" $GEMSTONE/EnvGruppi/bin/startnet The relative startnet it's: #!/bin/bash export GEMSTONE_NRS_ALL='#dir:$GEMSTONE_DATADIR#log:/$GEMSTONE_LOGDIR/%N%P.log' export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf export GEMSTONE_EXE_CONF=$GEMSTONE_DATADIR $GEMSTONE/bin/startnetldi 50379 -p 50380:50380 -g -a $USER -n -l $GEMSTONE_LOGDIR/gs64ldi.log The startoodbgrubbi shell report: Starting stone: gruppi --- 04/12/2012 17:19:31.110 CET --- stopstone[Info]: GemStone version '3.1.0.1' stopstone[Info]: Server 'gruppi' is not running. startstone[Info]: GemStone version '3.1.0.1' startstone[Info]: Starting Stone repository monitor 'gruppi'. startstone[Info]: GEMSTONE is: '/DTRDataBase/opt3101/gemstone/product'. startstone[Info]: GEMSTONE_SYS_CONF=/mnt/ISTDataBase//DTRdbGruppi/data/system.conf GEMSTONE_EXE_CONF=/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/seaside/data/gruppi.conf startstone[Info]: Log file is '/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/EnvGruppi/log/gruppi.log'. startstone[Info]: GemStone server 'gruppi' has been started, process 1259 . Starting Gems.... Starting WAFastCGIAdaptor gem on port 9010 Starting WAFastCGIAdaptor gem on port 9011 Starting WAFastCGIAdaptor gem on port 9012 Starting maintenance gem startnetldi[Info]: GemStone version '3.1.0.1' startnetldi[Info]: Starting GemStone network server '50379'. startnetldi[Info]: GEMSTONE is: '/DTRDataBase/opt3101/gemstone/product'. startnetldi[Info]: GEMSTONE_NRS_ALL is: '#dir:$GEMSTONE_DATADIR#log:/$GEMSTONE_LOGDIR/%N%P.log'. startnetldi[Info]: Log file is '/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/EnvGruppi/log/gs64ldi.log'. startnetldi[Info]: GemStone server '50379' has been started, process 1316 . > .. also the versions of the gci libraries that you are using (the gemtools one-click version would be fine if you are using a one-click)... > Regarding the gci libraries relative to GemTools 1.0-beta.8.7 i report the last relative e-mail with you >> >>> Dario, >>> >>> Regarding: 'The versions of RPC GCI client and Gem server are incompatible.' >>> >>> >>> The gci libraries (embedded in your gemtools one clicks) are different between 3.1.0 and 3.1.0.1 ... it's probably easiest to keep a separate GemTools for each version 2.4.x, 3.1.0 and 3.1.0.1 ... we don't always change RPC compatibility levels (especially with minor version updates), but occasionally it is necessary and that is the case this time around ... >>> >>> Here's a snippet from the one-click build script that should help you decipher which gci files to copy and where they should be copied to: >>> >>> # copy gemstone-specific artifacts >>> cp "$LINUX_GEMSTONE/lib32/libgcirpc-3.1.0-32.so" "$OUTPUT_PATH/Contents/Linux686/gciForLinux.so" >>> cp "$LINUX_GEMSTONE/lib32/libssl-3.1.0-32.so" "$OUTPUT_PATH/Contents/Linux686/" >> >>> cp "$MAC_GEMSTONE/lib32/libgcirpc-3.1.0-32.dylib" "$OUTPUT_PATH/Contents/Resources/gciForMacintosh.so" >>> cp "$MAC_GEMSTONE/lib32/libssl-3.1.0-32.dylib" "$OUTPUT_PATH/Contents/Resources/" >> >> On the MacBook with the relative *3.1.0.1* works fine. >> >> Thanks, >> >> Dario I'm ready for any other data or information you required. Thanks, Dario > I've got a mac myself and I've been using directory-based repositories with gemstone 3.1.x but I tend to run the stone on my mac, so I don't have much experience with using monticello repositories with a remote stone ... also I left my mac at home, so I can't easily run tests right now ... I'll take your setup for spin tonight when I get home ... I am suspicious that you are hitting a bug in the 3.1.0.1 gci libraries, but I'll have to verify that ... > > Pharo doesn't have option for "remote directories" so I guess we'll have to figure out what's going wrong ... in the case of a bug, I assume that you could use unix level tools for synchronizing a directory between your mac and the stone/gem machine ... > > Dale > > ----- Original Message ----- > | From: "Dario Trussardi" <[hidden email]> > | To: "GemStone Seaside beta discussion" <[hidden email]> > | Sent: Wednesday, November 28, 2012 7:45:09 AM > | Subject: Re: [GS/SS Beta] GLASS monticello don't work with local directory on MAC desktop > | > | Ciao Dale, > | > | > | > Dario, > | > > | > I would assume that the path that you are using to add the > | > repository is incorrect in some way (the Monticello browser > | > filters out repositories that "don't exist") ... which menu item > | > item are you using to add the repository? > | > > | > directory > | > | I use directory > | > | In the same hardware configuration i have a GLASS 2.4.1run on the > | server > | > | and Gemtools update to * 1.0-beta.8.3 on the MAC. > | > | With this all work fine. > | > | > | > | > | I create a new directory /mnt/test/ with a package on the MAC > | and add this to the repository items of GemTools update to * > | 1.0-beta.8.7 <release> with directory menu option > | > | When i open the repository from GemTools it don't report any > | package. > | > | > | With hold Gemtools 1.0-beta.8.3 all work correctly. > | > | > | > | > directory on .... > | > > | > When your stone/gems are on the same machine it doesn't matter (the > | > 'directory on' form provides much better performance. When your > | > stone/gems are on a different machine (which sounds like the case > | > here) then you need to use the 'directory' form, but be aware that > | > this form is much slower ... I would recommend that you always use > | > the "directory on ..." form which means that you'd be creating > | > repositories on the stone/gems machine and the paths provided are > | > based on the directory structure on that machine ... > | > | I agree, but in the development environment on the MAC based on Pharo > | 1.4 the Monticello > | > | +repository don't include the directoty on.... options. > | > | How i can configured the monticello remote directory on the server > | where run stone/gems > | > | Thank, > | > | Dario > | > | > > | > Dale > | > > | > ----- Original Message ----- > | > | From: "Dario Trussardi" <[hidden email]> > | > | To: "beta discussion Gemstone Seaside" > | > | <[hidden email]> > | > | Sent: Tuesday, November 27, 2012 8:21:41 AM > | > | Subject: [GS/SS Beta] GLASS monticello don't work with local > | > | directory on MAC desktop > | > | > | > | Hi, > | > | > | > | i have a server in a local network where run a GemStone version > | > | '3.1.0.1' update at GLASS : * 1.0-beta.9 <development> > | > | > | > | On the MAC desktop i run a GemTools ( based on Pharo-1.1-11411 > | > | Latest update: #11411 ) update to * 1.0-beta.8.7 <release> > | > | > | > | to port my development package to GLASS. > | > | > | > | > | > | Problem: Now when open the GemTools Monticello and add a new > | > | repository based on directory on local desktop > | > | /Users/dtr/MonticelloDTR > | > | > | > | none entry is add to the repository list. > | > | > | > | > | > | > | > | Any idea ? > | > | > | > | > | > | > | > | My development environment on the MAC is based on Pharo1.4 > | > | Latest > | > | update: #14445 > | > | > | > | > | > | wtih : ConfigurationOfSeaside30 3.0.7.1 > | > | > | > | ConfigurationOfMagritte3 3.0 > | > | > | > | ConfigurationOfPier3 3.0.0 > | > | > | > | The relative Monticello work fine on the local directory > | > | /Users/dtr/MonticelloDTR > | > | > | > | > | > | > | > | > | > | Thanks, > | > | > | > | Dario > | |
In reply to this post by Tobias Pape
Sorry for the delay, but I was sick.
> Dario > > Am 28.11.2012 um 16:45 schrieb Dario Trussardi: >> >> >>> directory on .... >>> >>> When your stone/gems are on the same machine it doesn't matter (the 'directory on' form provides much better performance. When your stone/gems are on a different machine (which sounds like the case here) then you need to use the 'directory' form, but be aware that this form is much slower ... I would recommend that you always use the "directory on ..." form which means that you'd be creating repositories on the stone/gems machine and the paths provided are based on the directory structure on that machine ... >> >> I agree, but in the development environment on the MAC based on Pharo 1.4 the Monticello >> >> +repository don't include the directoty on.... options. >> >> How i can configured the monticello remote directory on the server where run stone/gems >> > > Are you certain that you use the GemStone/GemTools monticello Browser or > do you accidentally use the Pharo one? Yes i'm certain to use the Gemstone/GemTools 1.0-beta.8.7 monticello browser. Thanks for any indications, idea. Ciao, Dario |
In reply to this post by dario trussardi
Ciao, to understand GLASS monticello don't work with local directory on MAC desktop, has anyone encountered this my problem? For now i configure the GLASS Monticello with a repository directory on the stone/gem machine and sync the package, created with Pharo in directory on MAC, with FTP. This work fine. I have dubt it's my GLASS configurations problem or not ? Thanks for any considerations. Dario >> between your mac and the stone/gem machine ... > Ciao Dale, > > sorry for the delay, but I was sick. > >> Dario, >> >> Are you using the same stone when comparing your results between GemTools 1.0-beta.8.3 and GemTools 1.0-beta.8.7? > > No, the GemTools 1.0-beta.8.3 is relative to a one GLASS 2.4.1 > > the GemTools 1.0-beta.8.7 is relative to a one GLASS 3.1.0.1 >> >> I would be surprised if you are seeing differences in MonticelloBrowser behavior between two different GemTools versions (especially these two versions) ... I am assuming that the differences are showing up because you are running against different stones and using different versions of the gci libraries ... > >> >> So I guess I would like to know more details about how you are running things: the session description used for login for both variants, > > I REPORT SOME DATA: > > >> the version of Pharo you are running on > > > THIS IS RELATIVE TO GemTools 1.0-beta.8.3 > > OGStandardSessionDescription new > name: 'Gofame'; > stoneHost: 'monviso'; > stoneName: 'gofame'; > gemHost: 'monviso'; > netLDI: '50377'; > userId: 'DataCurator'; > password: 'mypassword'; > > backupDirectory: '/gofametran/'; > yourself. > > Pharo-1.0Latest update: #10517 > > > > THIS IS RELATIVE TO GemTools 1.0-beta.8.7 > > OGCustomSessionDescription new > name: 'MonvisoGruppi'; > stoneHost: 'Monviso'; > stoneName: 'gruppi'; > gemHost: 'monviso'; > netLDI: '50379'; > gemTask: 'gemnetobject'; > userId: 'DataCurator'; > password: 'mypassword'; > osUserId: ''; > osPassword: ''; > backupDirectory: '/DTRdbBackups/backupGruppi/'; > dataDirectory: ''; > yourself. > > > Pharo-1.1-11411 > Latest update: #11411 > >> and the version of GLASS that you are running against will be a good starting point. > > > I start the GLASS 3.1.0.1 with the file : startoobgruppi it ' s: > > source /DTRDataBase/opt3101/gemstone/product/seaside/defSeaside > ## > export GEMSTONE_LOGDIR=$GEMSTONE/EnvGruppi/log > export GEMSTONE_DATADIR=$GEMSTONE/EnvGruppi/data > ## > export GEMSTONE_NAME=gruppi > export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf > ## > export PATH=$GEMSTONE/EnvGruppi/bin:$PATH > ### > $GEMSTONE/EnvGruppi/bin/startGemstone > $GEMSTONE/EnvGruppi/bin/runSeasideGems30 start WAFastCGIAdaptor "9010 9011 9012" > $GEMSTONE/EnvGruppi/bin/startnet > > > The relative startnet it's: > > #!/bin/bash > > export GEMSTONE_NRS_ALL='#dir:$GEMSTONE_DATADIR#log:/$GEMSTONE_LOGDIR/%N%P.log' > > export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf > export GEMSTONE_EXE_CONF=$GEMSTONE_DATADIR > > $GEMSTONE/bin/startnetldi 50379 -p 50380:50380 -g -a $USER -n -l $GEMSTONE_LOGDIR/gs64ldi.log > > > > > The startoodbgrubbi shell report: > > Starting stone: gruppi > --- 04/12/2012 17:19:31.110 CET --- > stopstone[Info]: GemStone version '3.1.0.1' > stopstone[Info]: Server 'gruppi' is not running. > startstone[Info]: GemStone version '3.1.0.1' > startstone[Info]: Starting Stone repository monitor 'gruppi'. > startstone[Info]: GEMSTONE is: '/DTRDataBase/opt3101/gemstone/product'. > startstone[Info]: > GEMSTONE_SYS_CONF=/mnt/ISTDataBase//DTRdbGruppi/data/system.conf > GEMSTONE_EXE_CONF=/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/seaside/data/gruppi.conf > startstone[Info]: Log file is '/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/EnvGruppi/log/gruppi.log'. > startstone[Info]: GemStone server 'gruppi' has been started, process 1259 . > Starting Gems.... > Starting WAFastCGIAdaptor gem on port 9010 > Starting WAFastCGIAdaptor gem on port 9011 > Starting WAFastCGIAdaptor gem on port 9012 > Starting maintenance gem > startnetldi[Info]: GemStone version '3.1.0.1' > startnetldi[Info]: Starting GemStone network server '50379'. > startnetldi[Info]: GEMSTONE is: '/DTRDataBase/opt3101/gemstone/product'. > startnetldi[Info]: GEMSTONE_NRS_ALL is: '#dir:$GEMSTONE_DATADIR#log:/$GEMSTONE_LOGDIR/%N%P.log'. > startnetldi[Info]: Log file is '/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/EnvGruppi/log/gs64ldi.log'. > startnetldi[Info]: GemStone server '50379' has been started, process 1316 . > > >> .. also the versions of the gci libraries that you are using (the gemtools one-click version would be fine if you are using a one-click)... >> > > > Regarding the gci libraries relative to GemTools 1.0-beta.8.7 i report the last relative e-mail with you > >>> >>>> Dario, >>>> >>>> Regarding: 'The versions of RPC GCI client and Gem server are incompatible.' >>>> >>>> >>>> The gci libraries (embedded in your gemtools one clicks) are different between 3.1.0 and 3.1.0.1 ... it's probably easiest to keep a separate GemTools for each version 2.4.x, 3.1.0 and 3.1.0.1 ... we don't always change RPC compatibility levels (especially with minor version updates), but occasionally it is necessary and that is the case this time around ... >>>> >>>> Here's a snippet from the one-click build script that should help you decipher which gci files to copy and where they should be copied to: >>>> >>>> # copy gemstone-specific artifacts >>>> cp "$LINUX_GEMSTONE/lib32/libgcirpc-3.1.0-32.so" "$OUTPUT_PATH/Contents/Linux686/gciForLinux.so" >>>> cp "$LINUX_GEMSTONE/lib32/libssl-3.1.0-32.so" "$OUTPUT_PATH/Contents/Linux686/" >>> >>>> cp "$MAC_GEMSTONE/lib32/libgcirpc-3.1.0-32.dylib" "$OUTPUT_PATH/Contents/Resources/gciForMacintosh.so" >>>> cp "$MAC_GEMSTONE/lib32/libssl-3.1.0-32.dylib" "$OUTPUT_PATH/Contents/Resources/" >>> >>> On the MacBook with the relative *3.1.0.1* works fine. >>> >>> Thanks, >>> >>> Dario > > I'm ready for any other data or information you required. > > Thanks, > Dario > >> I've got a mac myself and I've been using directory-based repositories with gemstone 3.1.x but I tend to run the stone on my mac, so I don't have much experience with using monticello repositories with a remote stone ... also I left my mac at home, so I can't easily run tests right now ... I'll take your setup for spin tonight when I get home ... I am suspicious that you are hitting a bug in the 3.1.0.1 gci libraries, but I'll have to verify that ... >> >> Pharo doesn't have option for "remote directories" so I guess we'll have to figure out what's going wrong ... in the case of a bug, I assume that you could use unix level tools for synchronizing a directory between your mac and the stone/gem machine ... >> >> Dale >> >> ----- Original Message ----- >> | From: "Dario Trussardi" <[hidden email]> >> | To: "GemStone Seaside beta discussion" <[hidden email]> >> | Sent: Wednesday, November 28, 2012 7:45:09 AM >> | Subject: Re: [GS/SS Beta] GLASS monticello don't work with local directory on MAC desktop >> | >> | Ciao Dale, >> | >> | >> | > Dario, >> | > >> | > I would assume that the path that you are using to add the >> | > repository is incorrect in some way (the Monticello browser >> | > filters out repositories that "don't exist") ... which menu item >> | > item are you using to add the repository? >> | > >> | > directory >> | >> | I use directory >> | >> | In the same hardware configuration i have a GLASS 2.4.1run on the >> | server >> | >> | and Gemtools update to * 1.0-beta.8.3 on the MAC. >> | >> | With this all work fine. >> | >> | >> | >> | >> | I create a new directory /mnt/test/ with a package on the MAC >> | and add this to the repository items of GemTools update to * >> | 1.0-beta.8.7 <release> with directory menu option >> | >> | When i open the repository from GemTools it don't report any >> | package. >> | >> | >> | With hold Gemtools 1.0-beta.8.3 all work correctly. >> | >> | >> | >> | > directory on .... >> | > >> | > When your stone/gems are on the same machine it doesn't matter (the >> | > 'directory on' form provides much better performance. When your >> | > stone/gems are on a different machine (which sounds like the case >> | > here) then you need to use the 'directory' form, but be aware that >> | > this form is much slower ... I would recommend that you always use >> | > the "directory on ..." form which means that you'd be creating >> | > repositories on the stone/gems machine and the paths provided are >> | > based on the directory structure on that machine ... >> | >> | I agree, but in the development environment on the MAC based on Pharo >> | 1.4 the Monticello >> | >> | +repository don't include the directoty on.... options. >> | >> | How i can configured the monticello remote directory on the server >> | where run stone/gems >> | >> | Thank, >> | >> | Dario >> | >> | > >> | > Dale >> | > >> | > ----- Original Message ----- >> | > | From: "Dario Trussardi" <[hidden email]> >> | > | To: "beta discussion Gemstone Seaside" >> | > | <[hidden email]> >> | > | Sent: Tuesday, November 27, 2012 8:21:41 AM >> | > | Subject: [GS/SS Beta] GLASS monticello don't work with local >> | > | directory on MAC desktop >> | > | >> | > | Hi, >> | > | >> | > | i have a server in a local network where run a GemStone version >> | > | '3.1.0.1' update at GLASS : * 1.0-beta.9 <development> >> | > | >> | > | On the MAC desktop i run a GemTools ( based on Pharo-1.1-11411 >> | > | Latest update: #11411 ) update to * 1.0-beta.8.7 <release> >> | > | >> | > | to port my development package to GLASS. >> | > | >> | > | >> | > | Problem: Now when open the GemTools Monticello and add a new >> | > | repository based on directory on local desktop >> | > | /Users/dtr/MonticelloDTR >> | > | >> | > | none entry is add to the repository list. >> | > | >> | > | >> | > | >> | > | Any idea ? >> | > | >> | > | >> | > | >> | > | My development environment on the MAC is based on Pharo1.4 >> | > | Latest >> | > | update: #14445 >> | > | >> | > | >> | > | wtih : ConfigurationOfSeaside30 3.0.7.1 >> | > | >> | > | ConfigurationOfMagritte3 3.0 >> | > | >> | > | ConfigurationOfPier3 3.0.0 >> | > | >> | > | The relative Monticello work fine on the local directory >> | > | /Users/dtr/MonticelloDTR >> | > | >> | > | >> | > | >> | > | >> | > | Thanks, >> | > | >> | > | Dario >> | > |
Ciao,
yesterday i download and install on my local server the GLASS 3.1.0.2. Today i test if the GLASS Monticello ( GemTools 1.0-beta.8.7 ) work fine on directory placed on MAC book. It work fine. The test is run on GLASS 3.1.0.2 as well as distribute. In the next days i load other package ( Seaside - Pier ....... ) and i will do some test for check. This is all for now. Thanks, Dario > > Ciao, > > to understand > > GLASS monticello don't work with local directory on MAC desktop, > > has anyone encountered this my problem? > > > > For now i configure the GLASS Monticello with a repository directory on the stone/gem machine > > and sync the package, created with Pharo in directory on MAC, with FTP. > > This work fine. > > > I have dubt it's my GLASS configurations problem or not ? > > Thanks for any considerations. > > Dario > > > >>> between your mac and the stone/gem machine ... > >> Ciao Dale, >> >> sorry for the delay, but I was sick. >> >>> Dario, >>> >>> Are you using the same stone when comparing your results between GemTools 1.0-beta.8.3 and GemTools 1.0-beta.8.7? >> >> No, the GemTools 1.0-beta.8.3 is relative to a one GLASS 2.4.1 >> >> the GemTools 1.0-beta.8.7 is relative to a one GLASS 3.1.0.1 >>> >>> I would be surprised if you are seeing differences in MonticelloBrowser behavior between two different GemTools versions (especially these two versions) ... I am assuming that the differences are showing up because you are running against different stones and using different versions of the gci libraries ... >> >>> >>> So I guess I would like to know more details about how you are running things: the session description used for login for both variants, >> >> I REPORT SOME DATA: >> >> >>> the version of Pharo you are running on >> >> >> THIS IS RELATIVE TO GemTools 1.0-beta.8.3 >> >> OGStandardSessionDescription new >> name: 'Gofame'; >> stoneHost: 'monviso'; >> stoneName: 'gofame'; >> gemHost: 'monviso'; >> netLDI: '50377'; >> userId: 'DataCurator'; >> password: 'mypassword'; >> >> backupDirectory: '/gofametran/'; >> yourself. >> >> Pharo-1.0Latest update: #10517 >> >> >> >> THIS IS RELATIVE TO GemTools 1.0-beta.8.7 >> >> OGCustomSessionDescription new >> name: 'MonvisoGruppi'; >> stoneHost: 'Monviso'; >> stoneName: 'gruppi'; >> gemHost: 'monviso'; >> netLDI: '50379'; >> gemTask: 'gemnetobject'; >> userId: 'DataCurator'; >> password: 'mypassword'; >> osUserId: ''; >> osPassword: ''; >> backupDirectory: '/DTRdbBackups/backupGruppi/'; >> dataDirectory: ''; >> yourself. >> >> >> Pharo-1.1-11411 >> Latest update: #11411 >> >>> and the version of GLASS that you are running against will be a good starting point. >> >> >> I start the GLASS 3.1.0.1 with the file : startoobgruppi it ' s: >> >> source /DTRDataBase/opt3101/gemstone/product/seaside/defSeaside >> ## >> export GEMSTONE_LOGDIR=$GEMSTONE/EnvGruppi/log >> export GEMSTONE_DATADIR=$GEMSTONE/EnvGruppi/data >> ## >> export GEMSTONE_NAME=gruppi >> export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf >> ## >> export PATH=$GEMSTONE/EnvGruppi/bin:$PATH >> ### >> $GEMSTONE/EnvGruppi/bin/startGemstone >> $GEMSTONE/EnvGruppi/bin/runSeasideGems30 start WAFastCGIAdaptor "9010 9011 9012" >> $GEMSTONE/EnvGruppi/bin/startnet >> >> >> The relative startnet it's: >> >> #!/bin/bash >> >> export GEMSTONE_NRS_ALL='#dir:$GEMSTONE_DATADIR#log:/$GEMSTONE_LOGDIR/%N%P.log' >> >> export GEMSTONE_SYS_CONF=$GEMSTONE_DATADIR/system.conf >> export GEMSTONE_EXE_CONF=$GEMSTONE_DATADIR >> >> $GEMSTONE/bin/startnetldi 50379 -p 50380:50380 -g -a $USER -n -l $GEMSTONE_LOGDIR/gs64ldi.log >> >> >> >> >> The startoodbgrubbi shell report: >> >> Starting stone: gruppi >> --- 04/12/2012 17:19:31.110 CET --- >> stopstone[Info]: GemStone version '3.1.0.1' >> stopstone[Info]: Server 'gruppi' is not running. >> startstone[Info]: GemStone version '3.1.0.1' >> startstone[Info]: Starting Stone repository monitor 'gruppi'. >> startstone[Info]: GEMSTONE is: '/DTRDataBase/opt3101/gemstone/product'. >> startstone[Info]: >> GEMSTONE_SYS_CONF=/mnt/ISTDataBase//DTRdbGruppi/data/system.conf >> GEMSTONE_EXE_CONF=/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/seaside/data/gruppi.conf >> startstone[Info]: Log file is '/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/EnvGruppi/log/gruppi.log'. >> startstone[Info]: GemStone server 'gruppi' has been started, process 1259 . >> Starting Gems.... >> Starting WAFastCGIAdaptor gem on port 9010 >> Starting WAFastCGIAdaptor gem on port 9011 >> Starting WAFastCGIAdaptor gem on port 9012 >> Starting maintenance gem >> startnetldi[Info]: GemStone version '3.1.0.1' >> startnetldi[Info]: Starting GemStone network server '50379'. >> startnetldi[Info]: GEMSTONE is: '/DTRDataBase/opt3101/gemstone/product'. >> startnetldi[Info]: GEMSTONE_NRS_ALL is: '#dir:$GEMSTONE_DATADIR#log:/$GEMSTONE_LOGDIR/%N%P.log'. >> startnetldi[Info]: Log file is '/mnt/ISTDataBase//opt3101/gemstone//GemStone64Bit3.1.0.1-x86_64.Linux/EnvGruppi/log/gs64ldi.log'. >> startnetldi[Info]: GemStone server '50379' has been started, process 1316 . >> >> >>> .. also the versions of the gci libraries that you are using (the gemtools one-click version would be fine if you are using a one-click)... >>> >> >> >> Regarding the gci libraries relative to GemTools 1.0-beta.8.7 i report the last relative e-mail with you >> >>>> >>>>> Dario, >>>>> >>>>> Regarding: 'The versions of RPC GCI client and Gem server are incompatible.' >>>>> >>>>> >>>>> The gci libraries (embedded in your gemtools one clicks) are different between 3.1.0 and 3.1.0.1 ... it's probably easiest to keep a separate GemTools for each version 2.4.x, 3.1.0 and 3.1.0.1 ... we don't always change RPC compatibility levels (especially with minor version updates), but occasionally it is necessary and that is the case this time around ... >>>>> >>>>> Here's a snippet from the one-click build script that should help you decipher which gci files to copy and where they should be copied to: >>>>> >>>>> # copy gemstone-specific artifacts >>>>> cp "$LINUX_GEMSTONE/lib32/libgcirpc-3.1.0-32.so" "$OUTPUT_PATH/Contents/Linux686/gciForLinux.so" >>>>> cp "$LINUX_GEMSTONE/lib32/libssl-3.1.0-32.so" "$OUTPUT_PATH/Contents/Linux686/" >>>> >>>>> cp "$MAC_GEMSTONE/lib32/libgcirpc-3.1.0-32.dylib" "$OUTPUT_PATH/Contents/Resources/gciForMacintosh.so" >>>>> cp "$MAC_GEMSTONE/lib32/libssl-3.1.0-32.dylib" "$OUTPUT_PATH/Contents/Resources/" >>>> >>>> On the MacBook with the relative *3.1.0.1* works fine. >>>> >>>> Thanks, >>>> >>>> Dario >> >> I'm ready for any other data or information you required. >> >> Thanks, >> Dario >> >>> I've got a mac myself and I've been using directory-based repositories with gemstone 3.1.x but I tend to run the stone on my mac, so I don't have much experience with using monticello repositories with a remote stone ... also I left my mac at home, so I can't easily run tests right now ... I'll take your setup for spin tonight when I get home ... I am suspicious that you are hitting a bug in the 3.1.0.1 gci libraries, but I'll have to verify that ... >>> >>> Pharo doesn't have option for "remote directories" so I guess we'll have to figure out what's going wrong ... in the case of a bug, I assume that you could use unix level tools for synchronizing a directory between your mac and the stone/gem machine ... >>> >>> Dale >>> >>> ----- Original Message ----- >>> | From: "Dario Trussardi" <[hidden email]> >>> | To: "GemStone Seaside beta discussion" <[hidden email]> >>> | Sent: Wednesday, November 28, 2012 7:45:09 AM >>> | Subject: Re: [GS/SS Beta] GLASS monticello don't work with local directory on MAC desktop >>> | >>> | Ciao Dale, >>> | >>> | >>> | > Dario, >>> | > >>> | > I would assume that the path that you are using to add the >>> | > repository is incorrect in some way (the Monticello browser >>> | > filters out repositories that "don't exist") ... which menu item >>> | > item are you using to add the repository? >>> | > >>> | > directory >>> | >>> | I use directory >>> | >>> | In the same hardware configuration i have a GLASS 2.4.1run on the >>> | server >>> | >>> | and Gemtools update to * 1.0-beta.8.3 on the MAC. >>> | >>> | With this all work fine. >>> | >>> | >>> | >>> | >>> | I create a new directory /mnt/test/ with a package on the MAC >>> | and add this to the repository items of GemTools update to * >>> | 1.0-beta.8.7 <release> with directory menu option >>> | >>> | When i open the repository from GemTools it don't report any >>> | package. >>> | >>> | >>> | With hold Gemtools 1.0-beta.8.3 all work correctly. >>> | >>> | >>> | >>> | > directory on .... >>> | > >>> | > When your stone/gems are on the same machine it doesn't matter (the >>> | > 'directory on' form provides much better performance. When your >>> | > stone/gems are on a different machine (which sounds like the case >>> | > here) then you need to use the 'directory' form, but be aware that >>> | > this form is much slower ... I would recommend that you always use >>> | > the "directory on ..." form which means that you'd be creating >>> | > repositories on the stone/gems machine and the paths provided are >>> | > based on the directory structure on that machine ... >>> | >>> | I agree, but in the development environment on the MAC based on Pharo >>> | 1.4 the Monticello >>> | >>> | +repository don't include the directoty on.... options. >>> | >>> | How i can configured the monticello remote directory on the server >>> | where run stone/gems >>> | >>> | Thank, >>> | >>> | Dario >>> | >>> | > >>> | > Dale >>> | > >>> | > ----- Original Message ----- >>> | > | From: "Dario Trussardi" <[hidden email]> >>> | > | To: "beta discussion Gemstone Seaside" >>> | > | <[hidden email]> >>> | > | Sent: Tuesday, November 27, 2012 8:21:41 AM >>> | > | Subject: [GS/SS Beta] GLASS monticello don't work with local >>> | > | directory on MAC desktop >>> | > | >>> | > | Hi, >>> | > | >>> | > | i have a server in a local network where run a GemStone version >>> | > | '3.1.0.1' update at GLASS : * 1.0-beta.9 <development> >>> | > | >>> | > | On the MAC desktop i run a GemTools ( based on Pharo-1.1-11411 >>> | > | Latest update: #11411 ) update to * 1.0-beta.8.7 <release> >>> | > | >>> | > | to port my development package to GLASS. >>> | > | >>> | > | >>> | > | Problem: Now when open the GemTools Monticello and add a new >>> | > | repository based on directory on local desktop >>> | > | /Users/dtr/MonticelloDTR >>> | > | >>> | > | none entry is add to the repository list. >>> | > | >>> | > | >>> | > | >>> | > | Any idea ? >>> | > | >>> | > | >>> | > | >>> | > | My development environment on the MAC is based on Pharo1.4 >>> | > | Latest >>> | > | update: #14445 >>> | > | >>> | > | >>> | > | wtih : ConfigurationOfSeaside30 3.0.7.1 >>> | > | >>> | > | ConfigurationOfMagritte3 3.0 >>> | > | >>> | > | ConfigurationOfPier3 3.0.0 >>> | > | >>> | > | The relative Monticello work fine on the local directory >>> | > | /Users/dtr/MonticelloDTR >>> | > | >>> | > | >>> | > | >>> | > | >>> | > | Thanks, >>> | > | >>> | > | Dario >>> | >> > |
Ciao,
Ciao, Only apparently. I have configured with GLASS Monticello a directory repository /mnt/MonticelloDTR on my MAC. But when i open this repository in reality it open the /mnt/MonticelloDTR on the server where GLASS 3.1.0.2 run Ciao Dario
|
Free forum by Nabble | Edit this page |