Monticello connecting to ftp repo on non-standard port

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

Monticello connecting to ftp repo on non-standard port

Pat Maddox-2
Hi, I set up a monticello repository on one of my FTP servers.  The
FTP server does not run on port 21.  I created a repo connection from
my Pharo 09.06.1 image, it looks like:

MCFtpRepository
        host: 'mysite.com:1234'
        directory: 'mc'
        user: 'smalltalk'
        password: 'supersecret'

When I click on "Open" I get the error:
MessageNotUnderstood: ByteArray>>port:

Any ideas what's going on?  These connection settings work fine on a
Squeak image that I downloaded a few weeks ago.

I would post a more complete stack trace but I can't figure out how.
I can open the debugger, but not copy and paste any stack trace
output.

Pat

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Pat Maddox-2
actually scratch that, Pharo's monticello just isn't working on FTP
for me, even if the server is on port 21

On Mon, Jun 15, 2009 at 6:04 AM, Pat Maddox<[hidden email]> wrote:

> Hi, I set up a monticello repository on one of my FTP servers.  The
> FTP server does not run on port 21.  I created a repo connection from
> my Pharo 09.06.1 image, it looks like:
>
> MCFtpRepository
>        host: 'mysite.com:1234'
>        directory: 'mc'
>        user: 'smalltalk'
>        password: 'supersecret'
>
> When I click on "Open" I get the error:
> MessageNotUnderstood: ByteArray>>port:
>
> Any ideas what's going on?  These connection settings work fine on a
> Squeak image that I downloaded a few weeks ago.
>
> I would post a more complete stack trace but I can't figure out how.
> I can open the debugger, but not copy and paste any stack trace
> output.
>
> Pat
>



--
(415) 297-8028
http://www.patmaddox.com
Twitter: @patmaddox
GitHub: http://github.com/pat-maddox

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Stéphane Ducasse
can you tell us the
exact image number + vm + the log trace?

Stef

On Jun 15, 2009, at 3:10 PM, Pat Maddox wrote:

> actually scratch that, Pharo's monticello just isn't working on FTP
> for me, even if the server is on port 21
>
> On Mon, Jun 15, 2009 at 6:04 AM, Pat Maddox<[hidden email]>  
> wrote:
>> Hi, I set up a monticello repository on one of my FTP servers.  The
>> FTP server does not run on port 21.  I created a repo connection from
>> my Pharo 09.06.1 image, it looks like:
>>
>> MCFtpRepository
>>        host: 'mysite.com:1234'
>>        directory: 'mc'
>>        user: 'smalltalk'
>>        password: 'supersecret'
>>
>> When I click on "Open" I get the error:
>> MessageNotUnderstood: ByteArray>>port:
>>
>> Any ideas what's going on?  These connection settings work fine on a
>> Squeak image that I downloaded a few weeks ago.
>>
>> I would post a more complete stack trace but I can't figure out how.
>> I can open the debugger, but not copy and paste any stack trace
>> output.
>>
>> Pat
>>
>
>
>
> --
> (415) 297-8028
> http://www.patmaddox.com
> Twitter: @patmaddox
> GitHub: http://github.com/pat-maddox
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Pat Maddox-2
Image # is 10324.  vm is squeak 4.11beta2u downloaded from the pharo
site.  I don't know how to copy and paste the log trace.  When I click
Open from MC the error window comes up.  If I try to select text from
there (which works in squeak, afaik) it brings up the debugger.  From
there I can see the trace but can't copy and paste it.  What am I
missing?

Pat

On Mon, Jun 15, 2009 at 6:12 AM, Stéphane
Ducasse<[hidden email]> wrote:

> can you tell us the
> exact image number + vm + the log trace?
>
> Stef
>
> On Jun 15, 2009, at 3:10 PM, Pat Maddox wrote:
>
>> actually scratch that, Pharo's monticello just isn't working on FTP
>> for me, even if the server is on port 21
>>
>> On Mon, Jun 15, 2009 at 6:04 AM, Pat Maddox<[hidden email]>
>> wrote:
>>> Hi, I set up a monticello repository on one of my FTP servers.  The
>>> FTP server does not run on port 21.  I created a repo connection from
>>> my Pharo 09.06.1 image, it looks like:
>>>
>>> MCFtpRepository
>>>        host: 'mysite.com:1234'
>>>        directory: 'mc'
>>>        user: 'smalltalk'
>>>        password: 'supersecret'
>>>
>>> When I click on "Open" I get the error:
>>> MessageNotUnderstood: ByteArray>>port:
>>>
>>> Any ideas what's going on?  These connection settings work fine on a
>>> Squeak image that I downloaded a few weeks ago.
>>>
>>> I would post a more complete stack trace but I can't figure out how.
>>> I can open the debugger, but not copy and paste any stack trace
>>> output.
>>>
>>> Pat
>>>
>>
>>
>>
>> --
>> (415) 297-8028
>> http://www.patmaddox.com
>> Twitter: @patmaddox
>> GitHub: http://github.com/pat-maddox
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



--
(415) 297-8028
http://www.patmaddox.com
Twitter: @patmaddox
GitHub: http://github.com/pat-maddox

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Damien Cassou
On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<[hidden email]> wrote:
> Image # is 10324.  vm is squeak 4.11beta2u downloaded from the pharo
> site.  I don't know how to copy and paste the log trace.  When I click
> Open from MC the error window comes up.  If I try to select text from
> there (which works in squeak, afaik) it brings up the debugger.  From
> there I can see the trace but can't copy and paste it.  What am I
> missing?

you should check for a debug.log file

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Pat Maddox-2
On Mon, Jun 15, 2009 at 6:25 AM, Damien Cassou<[hidden email]> wrote:
> On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<[hidden email]> wrote:
>> Image # is 10324.  vm is squeak 4.11beta2u downloaded from the pharo
>> site.  I don't know how to copy and paste the log trace.  When I click
>> Open from MC the error window comes up.  If I try to select text from
>> there (which works in squeak, afaik) it brings up the debugger.  From
>> there I can see the trace but can't copy and paste it.  What am I
>> missing?
>
> you should check for a debug.log file

Alright, here's the log for a few frames back.  I think that should be
enough, please let me know if you need more info


MessageNotUnderstood: ByteArray>>port:
15 June 2009 6:29:29 am

VM: Mac OS - intel - 1057 - Squeak3.8.1 of '28 Aug 2006' [latest
update: #6747] Squeak VM 4.1.1b2
Image: Pharo0.1 [Latest update: #10324]

SecurityManager state:
Restricted: false
FileAccess: true
SocketAccess: true
Working Dir /Users/padillac/code/dogadopt
Trusted Dir /foobar/tooBar/forSqueak/bogus
Untrusted Dir /Users/padillac/Library/Preferences/Squeak/Internet/My Squeak

ByteArray(Object)>>doesNotUnderstand: #port:
        Receiver: #[173 45 239 88]
        Arguments and temporary variables:
                aMessage: port: 47682
                exception: MessageNotUnderstood: ByteArray>>port:
                resumeValue: nil
        Receiver's instance variables:
#[173 45 239 88]

Socket>>connectTo:port:
        Receiver: a Socket[unconnected]
        Arguments and temporary variables:
                hostAddress: #[173 45 239 88]
                port: 47682
        Receiver's instance variables:
                semaphore: a Semaphore()
                socketHandle: #[254 248 53 74 0 0 0 0 144 91 48 22]
                readSemaphore: a Semaphore()
                writeSemaphore: a Semaphore()
                primitiveOnlySupportsOneSemaphore: false

FTPClient>>openDataSocket:port:
        Receiver: a FTPClient
        Arguments and temporary variables:
                remoteHostAddress: #[173 45 239 88]
                dataPort: 47682
        Receiver's instance variables:
                stream: SocketStream[inbuf:4kb/outbuf:4kb]
                connectInfo: a
Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-metan...etc...
                lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
                pendingResponses: nil
                progressObservers: nil
                responseCode: 227
                dataSocket: a Socket[unconnected]

FTPClient>>openPassiveDataConnection
        Receiver: a FTPClient
        Arguments and temporary variables:
                portInfo: '173,45,239,88,186,66'
                list: an OrderedCollection('173' '45' '239' '88' '186' '66')
                dataPort: 47682
                remoteHostAddress: #[173 45 239 88]
        Receiver's instance variables:
                stream: SocketStream[inbuf:4kb/outbuf:4kb]
                connectInfo: a
Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-metan...etc...
                lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
                pendingResponses: nil
                progressObservers: nil
                responseCode: 227
                dataSocket: a Socket[unconnected]

FTPClient>>getDirectory
        Receiver: a FTPClient
        Arguments and temporary variables:
                dirList: nil
        Receiver's instance variables:
                stream: SocketStream[inbuf:4kb/outbuf:4kb]
                connectInfo: a
Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-metan...etc...
                lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
                pendingResponses: nil
                progressObservers: nil
                responseCode: 227
                dataSocket: a Socket[unconnected]

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Cameron Sanders-3
This defect and its fix has been documented -- see the comments I  
added to the bug-log. I am using Monticello on a Mac with FTP. (I do  
not specify the port.) Do a search of the defects and you'll see my  
comments.

You need to add a message... but... to be honest, I've had 3 hours of  
sleep, no water in many hours, and I'm leaving for the hospital for  
surgery in two minutes... so i can't look it up.

above (in the caller/message-sender) where #port: is sent, insert a  
asSocketAddress  (or something like that)

Also, at least a few weeks back, I was still needing to return "true"  
in net-name-resolver method #useOldSockets (? or Address?)

again, my apologies for not being more clear.

-Cam
On Jun 15, 2009, at 9:35 AM, Pat Maddox wrote:

> On Mon, Jun 15, 2009 at 6:25 AM, Damien  
> Cassou<[hidden email]> wrote:
>> On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<[hidden email]>  
>> wrote:
>>> Image # is 10324.  vm is squeak 4.11beta2u downloaded from the pharo
>>> site.  I don't know how to copy and paste the log trace.  When I  
>>> click
>>> Open from MC the error window comes up.  If I try to select text  
>>> from
>>> there (which works in squeak, afaik) it brings up the debugger.  
>>> From
>>> there I can see the trace but can't copy and paste it.  What am I
>>> missing?
>>
>> you should check for a debug.log file
>
> Alright, here's the log for a few frames back.  I think that should be
> enough, please let me know if you need more info
>
>
> MessageNotUnderstood: ByteArray>>port:
> 15 June 2009 6:29:29 am
>
> VM: Mac OS - intel - 1057 - Squeak3.8.1 of '28 Aug 2006' [latest
> update: #6747] Squeak VM 4.1.1b2
> Image: Pharo0.1 [Latest update: #10324]
>
> SecurityManager state:
> Restricted: false
> FileAccess: true
> SocketAccess: true
> Working Dir /Users/padillac/code/dogadopt
> Trusted Dir /foobar/tooBar/forSqueak/bogus
> Untrusted Dir /Users/padillac/Library/Preferences/Squeak/Internet/My  
> Squeak
>
> ByteArray(Object)>>doesNotUnderstand: #port:
> Receiver: #[173 45 239 88]
> Arguments and temporary variables:
> aMessage: port: 47682
> exception: MessageNotUnderstood: ByteArray>>port:
> resumeValue: nil
> Receiver's instance variables:
> #[173 45 239 88]
>
> Socket>>connectTo:port:
> Receiver: a Socket[unconnected]
> Arguments and temporary variables:
> hostAddress: #[173 45 239 88]
> port: 47682
> Receiver's instance variables:
> semaphore: a Semaphore()
> socketHandle: #[254 248 53 74 0 0 0 0 144 91 48 22]
> readSemaphore: a Semaphore()
> writeSemaphore: a Semaphore()
> primitiveOnlySupportsOneSemaphore: false
>
> FTPClient>>openDataSocket:port:
> Receiver: a FTPClient
> Arguments and temporary variables:
> remoteHostAddress: #[173 45 239 88]
> dataPort: 47682
> Receiver's instance variables:
> stream: SocketStream[inbuf:4kb/outbuf:4kb]
> connectInfo: a
> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
> metan...etc...
> lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
> pendingResponses: nil
> progressObservers: nil
> responseCode: 227
> dataSocket: a Socket[unconnected]
>
> FTPClient>>openPassiveDataConnection
> Receiver: a FTPClient
> Arguments and temporary variables:
> portInfo: '173,45,239,88,186,66'
> list: an OrderedCollection('173' '45' '239' '88' '186' '66')
> dataPort: 47682
> remoteHostAddress: #[173 45 239 88]
> Receiver's instance variables:
> stream: SocketStream[inbuf:4kb/outbuf:4kb]
> connectInfo: a
> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
> metan...etc...
> lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
> pendingResponses: nil
> progressObservers: nil
> responseCode: 227
> dataSocket: a Socket[unconnected]
>
> FTPClient>>getDirectory
> Receiver: a FTPClient
> Arguments and temporary variables:
> dirList: nil
> Receiver's instance variables:
> stream: SocketStream[inbuf:4kb/outbuf:4kb]
> connectInfo: a
> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
> metan...etc...
> lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
> pendingResponses: nil
> progressObservers: nil
> responseCode: 227
> dataSocket: a Socket[unconnected]
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Pat Maddox-2
Okay per http://www.mail-archive.com/pharo-project@.../msg08133.html
all I had to do was change NetNameResolver class >> useOldNetwork to
return true.  Thanks for the pointer.  I hope your surgery and
recovery go well...

Pat

On Mon, Jun 15, 2009 at 8:03 AM, Cameron
Sanders<[hidden email]> wrote:

> This defect and its fix has been documented -- see the comments I
> added to the bug-log. I am using Monticello on a Mac with FTP. (I do
> not specify the port.) Do a search of the defects and you'll see my
> comments.
>
> You need to add a message... but... to be honest, I've had 3 hours of
> sleep, no water in many hours, and I'm leaving for the hospital for
> surgery in two minutes... so i can't look it up.
>
> above (in the caller/message-sender) where #port: is sent, insert a
> asSocketAddress  (or something like that)
>
> Also, at least a few weeks back, I was still needing to return "true"
> in net-name-resolver method #useOldSockets (? or Address?)
>
> again, my apologies for not being more clear.
>
> -Cam
> On Jun 15, 2009, at 9:35 AM, Pat Maddox wrote:
>
>> On Mon, Jun 15, 2009 at 6:25 AM, Damien
>> Cassou<[hidden email]> wrote:
>>> On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<[hidden email]>
>>> wrote:
>>>> Image # is 10324.  vm is squeak 4.11beta2u downloaded from the pharo
>>>> site.  I don't know how to copy and paste the log trace.  When I
>>>> click
>>>> Open from MC the error window comes up.  If I try to select text
>>>> from
>>>> there (which works in squeak, afaik) it brings up the debugger.
>>>> From
>>>> there I can see the trace but can't copy and paste it.  What am I
>>>> missing?
>>>
>>> you should check for a debug.log file
>>
>> Alright, here's the log for a few frames back.  I think that should be
>> enough, please let me know if you need more info
>>
>>
>> MessageNotUnderstood: ByteArray>>port:
>> 15 June 2009 6:29:29 am
>>
>> VM: Mac OS - intel - 1057 - Squeak3.8.1 of '28 Aug 2006' [latest
>> update: #6747] Squeak VM 4.1.1b2
>> Image: Pharo0.1 [Latest update: #10324]
>>
>> SecurityManager state:
>> Restricted: false
>> FileAccess: true
>> SocketAccess: true
>> Working Dir /Users/padillac/code/dogadopt
>> Trusted Dir /foobar/tooBar/forSqueak/bogus
>> Untrusted Dir /Users/padillac/Library/Preferences/Squeak/Internet/My
>> Squeak
>>
>> ByteArray(Object)>>doesNotUnderstand: #port:
>>       Receiver: #[173 45 239 88]
>>       Arguments and temporary variables:
>>               aMessage:       port: 47682
>>               exception:      MessageNotUnderstood: ByteArray>>port:
>>               resumeValue:    nil
>>       Receiver's instance variables:
>> #[173 45 239 88]
>>
>> Socket>>connectTo:port:
>>       Receiver: a Socket[unconnected]
>>       Arguments and temporary variables:
>>               hostAddress:    #[173 45 239 88]
>>               port:   47682
>>       Receiver's instance variables:
>>               semaphore:      a Semaphore()
>>               socketHandle:   #[254 248 53 74 0 0 0 0 144 91 48 22]
>>               readSemaphore:  a Semaphore()
>>               writeSemaphore:         a Semaphore()
>>               primitiveOnlySupportsOneSemaphore:      false
>>
>> FTPClient>>openDataSocket:port:
>>       Receiver: a FTPClient
>>       Arguments and temporary variables:
>>               remoteHostAddress:      #[173 45 239 88]
>>               dataPort:       47682
>>       Receiver's instance variables:
>>               stream:         SocketStream[inbuf:4kb/outbuf:4kb]
>>               connectInfo:    a
>> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
>> metan...etc...
>>               lastResponse:   '227 Entering Passive Mode (173,45,239,88,186,66).'
>>               pendingResponses:       nil
>>               progressObservers:      nil
>>               responseCode:   227
>>               dataSocket:     a Socket[unconnected]
>>
>> FTPClient>>openPassiveDataConnection
>>       Receiver: a FTPClient
>>       Arguments and temporary variables:
>>               portInfo:       '173,45,239,88,186,66'
>>               list:   an OrderedCollection('173' '45' '239' '88' '186' '66')
>>               dataPort:       47682
>>               remoteHostAddress:      #[173 45 239 88]
>>       Receiver's instance variables:
>>               stream:         SocketStream[inbuf:4kb/outbuf:4kb]
>>               connectInfo:    a
>> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
>> metan...etc...
>>               lastResponse:   '227 Entering Passive Mode (173,45,239,88,186,66).'
>>               pendingResponses:       nil
>>               progressObservers:      nil
>>               responseCode:   227
>>               dataSocket:     a Socket[unconnected]
>>
>> FTPClient>>getDirectory
>>       Receiver: a FTPClient
>>       Arguments and temporary variables:
>>               dirList:        nil
>>       Receiver's instance variables:
>>               stream:         SocketStream[inbuf:4kb/outbuf:4kb]
>>               connectInfo:    a
>> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
>> metan...etc...
>>               lastResponse:   '227 Entering Passive Mode (173,45,239,88,186,66).'
>>               pendingResponses:       nil
>>               progressObservers:      nil
>>               responseCode:   227
>>               dataSocket:     a Socket[unconnected]
>>
>> _______________________________________________
>> Pharo-project mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



--
(415) 297-8028
http://www.patmaddox.com
Twitter: @patmaddox
GitHub: http://github.com/pat-maddox

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Michael Rueger-6
Pat Maddox wrote:
> Okay per http://www.mail-archive.com/pharo-project@.../msg08133.html
> all I had to do was change NetNameResolver class >> useOldNetwork to
>

A real fix is attached here:
http://code.google.com/p/pharo/issues/detail?id=892

>> above (in the caller/message-sender) where #port: is sent, insert a
>> asSocketAddress  (or something like that)

This actually doesn't work as I found out.

>> Also, at least a few weeks back, I was still needing to return "true"
>> in net-name-resolver method #useOldSockets (? or Address?)

That is causing it to work as it circumvents the problematic code
altogether.

Michael


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Adrian Lienhard
Thanks, Mike,

is http://code.google.com/p/pharo/issues/detail?id=794 a duplicate?

Adrian

On Jun 16, 2009, at 11:40 , Michael Rueger wrote:

> Pat Maddox wrote:
>> Okay per http://www.mail-archive.com/pharo-project@.../msg08133.html
>> all I had to do was change NetNameResolver class >> useOldNetwork to
>>
>
> A real fix is attached here:
> http://code.google.com/p/pharo/issues/detail?id=892
>
>>> above (in the caller/message-sender) where #port: is sent, insert a
>>> asSocketAddress  (or something like that)
>
> This actually doesn't work as I found out.
>
>>> Also, at least a few weeks back, I was still needing to return  
>>> "true"
>>> in net-name-resolver method #useOldSockets (? or Address?)
>
> That is causing it to work as it circumvents the problematic code
> altogether.
>
> Michael
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Michael Rueger-6
Adrian Lienhard wrote:
> Thanks, Mike,
>
> is http://code.google.com/p/pharo/issues/detail?id=794 a duplicate?

no, that's a different issue. Need to fire up my virtualbox Ubuntu now :-)

Michael

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Stéphane Ducasse
In reply to this post by Pat Maddox-2
can you try with the latest update and let us know if this is working  
out of the box :)

Stef

On Jun 15, 2009, at 3:35 PM, Pat Maddox wrote:

> On Mon, Jun 15, 2009 at 6:25 AM, Damien  
> Cassou<[hidden email]> wrote:
>> On Mon, Jun 15, 2009 at 3:22 PM, Pat Maddox<[hidden email]>  
>> wrote:
>>> Image # is 10324.  vm is squeak 4.11beta2u downloaded from the pharo
>>> site.  I don't know how to copy and paste the log trace.  When I  
>>> click
>>> Open from MC the error window comes up.  If I try to select text  
>>> from
>>> there (which works in squeak, afaik) it brings up the debugger.  
>>> From
>>> there I can see the trace but can't copy and paste it.  What am I
>>> missing?
>>
>> you should check for a debug.log file
>
> Alright, here's the log for a few frames back.  I think that should be
> enough, please let me know if you need more info
>
>
> MessageNotUnderstood: ByteArray>>port:
> 15 June 2009 6:29:29 am
>
> VM: Mac OS - intel - 1057 - Squeak3.8.1 of '28 Aug 2006' [latest
> update: #6747] Squeak VM 4.1.1b2
> Image: Pharo0.1 [Latest update: #10324]
>
> SecurityManager state:
> Restricted: false
> FileAccess: true
> SocketAccess: true
> Working Dir /Users/padillac/code/dogadopt
> Trusted Dir /foobar/tooBar/forSqueak/bogus
> Untrusted Dir /Users/padillac/Library/Preferences/Squeak/Internet/My  
> Squeak
>
> ByteArray(Object)>>doesNotUnderstand: #port:
> Receiver: #[173 45 239 88]
> Arguments and temporary variables:
> aMessage: port: 47682
> exception: MessageNotUnderstood: ByteArray>>port:
> resumeValue: nil
> Receiver's instance variables:
> #[173 45 239 88]
>
> Socket>>connectTo:port:
> Receiver: a Socket[unconnected]
> Arguments and temporary variables:
> hostAddress: #[173 45 239 88]
> port: 47682
> Receiver's instance variables:
> semaphore: a Semaphore()
> socketHandle: #[254 248 53 74 0 0 0 0 144 91 48 22]
> readSemaphore: a Semaphore()
> writeSemaphore: a Semaphore()
> primitiveOnlySupportsOneSemaphore: false
>
> FTPClient>>openDataSocket:port:
> Receiver: a FTPClient
> Arguments and temporary variables:
> remoteHostAddress: #[173 45 239 88]
> dataPort: 47682
> Receiver's instance variables:
> stream: SocketStream[inbuf:4kb/outbuf:4kb]
> connectInfo: a
> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
> metan...etc...
> lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
> pendingResponses: nil
> progressObservers: nil
> responseCode: 227
> dataSocket: a Socket[unconnected]
>
> FTPClient>>openPassiveDataConnection
> Receiver: a FTPClient
> Arguments and temporary variables:
> portInfo: '173,45,239,88,186,66'
> list: an OrderedCollection('173' '45' '239' '88' '186' '66')
> dataPort: 47682
> remoteHostAddress: #[173 45 239 88]
> Receiver's instance variables:
> stream: SocketStream[inbuf:4kb/outbuf:4kb]
> connectInfo: a
> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
> metan...etc...
> lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
> pendingResponses: nil
> progressObservers: nil
> responseCode: 227
> dataSocket: a Socket[unconnected]
>
> FTPClient>>getDirectory
> Receiver: a FTPClient
> Arguments and temporary variables:
> dirList: nil
> Receiver's instance variables:
> stream: SocketStream[inbuf:4kb/outbuf:4kb]
> connectInfo: a
> Dictionary(#host->173.45.239.88(173-45-239-88),2112(idonix-
> metan...etc...
> lastResponse: '227 Entering Passive Mode (173,45,239,88,186,66).'
> pendingResponses: nil
> progressObservers: nil
> responseCode: 227
> dataSocket: a Socket[unconnected]
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Michael Rueger-6
In reply to this post by Adrian Lienhard
Adrian Lienhard wrote:
> Thanks, Mike,
>
> is http://code.google.com/p/pharo/issues/detail?id=794 a duplicate?

I just tested on Virtualbox Ubuntu 8.04 and it worked.
So I guess I have to set up a 9.x environment...

Michael

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Damien Cassou
In reply to this post by Stéphane Ducasse
On Tue, Jun 16, 2009 at 2:04 PM, Stéphane
Ducasse<[hidden email]> wrote:
> can you try with the latest update and let us know if this is working
> out of the box :)

Latest Pharo has this fix included: http://pharo-project.org/download

--
Damien Cassou
http://damiencassou.seasidehosting.st

"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Alain Plantec-4
In reply to this post by Michael Rueger-6
Michael Rueger a écrit :

> Adrian Lienhard wrote:
>  
>> Thanks, Mike,
>>
>> is http://code.google.com/p/pharo/issues/detail?id=794 a duplicate?
>>    
>
> I just tested on Virtualbox Ubuntu 8.04 and it worked.
> So I guess I have to set up a 9.x environment...
>  
yes.
It worked well with 8.04, the problem is with 9.04.
Alain
> Michael
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
>  


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Michael Rueger-6
Alain Plantec wrote:

> It worked well with 8.04, the problem is with 9.04.

well, works for me here.
Fresh 9.04 install on Virtualbox 2.2.4., Linux VM downloaded from the
pharo site.

Michael

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Alain Plantec-4
Michael Rueger a écrit :
> Alain Plantec wrote:
>
>> It worked well with 8.04, the problem is with 9.04.
>
> well, works for me here.
> Fresh 9.04 install on Virtualbox 2.2.4., Linux VM downloaded from the
> pharo site.

strange, I will do exactly the same and give you feedbacks.
is the 32 or the 64 bits version that you have installed ?
(I don't remember well, but maybe it has worked for a while and then
stopped to work....)
alain
>
> Michael
>
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Michael Rueger-6
Alain Plantec wrote:

> Michael Rueger a écrit :
>> Alain Plantec wrote:
>>
>>> It worked well with 8.04, the problem is with 9.04.
>>
>> well, works for me here.
>> Fresh 9.04 install on Virtualbox 2.2.4., Linux VM downloaded from the
>> pharo site.
>
> strange, I will do exactly the same and give you feedbacks.

thanks!

> is the 32 or the 64 bits version that you have installed ?

32-bit version

Michael

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Cameron Sanders-3
In reply to this post by Pat Maddox-2
Excellent, I am glad that did it for you. [Although... that other  
point I made about #port was indeed a defect ... in some version --  
perhaps somebody fixed that and I missed it.]

And thanks the surgery did go well. I had a torn meniscus -- left  
knee. A big tear, but the surgeon I went to handles the US ski team.  
It felt "pinched" last night post-surgery, but I didn't need any pain  
meds; and today if feels better than it did for most of the last 3  
months! We live in a very lucky era.

That latter point applies to computing as well. I first started  
working with-computers full-time in 1981. But even today, I don't take  
this all for granted. These "toys" and systems we have  built over the  
years are totally impressive. Do not forget to stop and appreciate it  
once in a while... it wasn't always like this!

Ciao,
Cam

On Jun 15, 2009, at 6:19 PM, Pat Maddox wrote:

> Okay per http://www.mail-archive.com/pharo-project@.../msg08133.html
> all I had to do was change NetNameResolver class >> useOldNetwork to
> return true.  Thanks for the pointer.  I hope your surgery and
> recovery go well...


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Monticello connecting to ftp repo on non-standard port

Alain Plantec-4
In reply to this post by Michael Rueger-6
I've installed ubuntu 32 and 64-bit with virtualbox.
ubuntu 32 bit (virtualbox) : ok, no network problem - host is broken
ubuntu 64 bit :)
ubuntu 64 bit (virtualbox) : broken as my host is

Alain

Michael Rueger a écrit :

> Alain Plantec wrote:
>> Michael Rueger a écrit :
>>> Alain Plantec wrote:
>>>
>>>> It worked well with 8.04, the problem is with 9.04.
>>>
>>> well, works for me here.
>>> Fresh 9.04 install on Virtualbox 2.2.4., Linux VM downloaded from
>>> the pharo site.
>>
>> strange, I will do exactly the same and give you feedbacks.
>
> thanks!
>
>> is the 32 or the 64 bits version that you have installed ?
>
> 32-bit version
>
> Michael
>
>


_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project