Thanks Dave,

I've changed two names and it works again. I've also disabled remote connections to the VNC server. At the same time updated the README file with a describing how to connect to the VNC over ssh.

Levente

On Tue, 28 Jun 2016, David T. Lewis wrote:

Thanks Levente,

I will fix it as soon as I am able, but I may not have VNC access until tomorrow.

For information in case anyone needs it - There is a readme file in the home directory for ssdotcom that should explain how to connect to the image. The procedure is to send a SIGUSR2 to the VM process, then connect with VNC within the next 60 seconds. The VNC password should be in the readme file. Once into the image, there should be a workspace showing how I did the fix previously. The fix is to replace the WideString user name with a ByteString in the repository. I usually just hunt down the user's name with google and try to guess at a plausible looking ByteString replacement for the user's real name.

Dave

...

Hi All,

As the subject says, squeaksource.com's web interface has become unusable again. I'm not familiar with the code, but I suppose changing the encoding from iso-8859-1 to utf-8 would fix the problem.

Levente

On Tue, Jun 28, 2016 at 10:46:48PM +0200, Levente Uzonyi wrote:

Thanks Dave,

I've changed two names and it works again. I've also disabled remote connections to the VNC server. At the same time updated the README file with a describing how to connect to the VNC over ssh.

Hi Levente,

Noob problem, please be patient.

I am having trouble figuring out how to connect through ssh. I am not experienced with this so I am probably doing something wrong.

I created new keys with ssh-keygen, and copied the public key to box3 with

$ ssh-copy-id ssdotcom@squeaksource.com

This works fine, and I can ssh to davidlewis@box3.squeak.org without entering a password, so I think that the keys are working.

I then do this to set up the tunneling:

$ ssh -N -L 5901:127.0.0.1:5901 davidlewis@box3.squeak.org

I am using a Vinagre remote desktop viewer, and I connect to 127.0.0.1:1 to make the connection. I see this error in the window where I set up the tunneling:

$ ssh -N -L 5901:127.0.0.1:5901 davidlewis@box3.squeak.org channel 2: open failed: connect failed: Connection refused

So I think that I am doing something wrong here.

I am assuming that I should get a connection to an X11 desktop on box3, although I should mention that the VM for squeaksource.com is running headless, so its Squeak window would not be visible in an X11 desktop.

Can you point me in the right direction? Thanks.

Dave

Thank you Levente, I can connect to the image now. I did not understand that I should start RFBServer exactly as before. It works fine, thank you for explaining.

Dave

On Thu, Jun 30, 2016 at 04:25:06AM +0200, Levente Uzonyi wrote:

Hi Dave,

On Wed, 29 Jun 2016, David T. Lewis wrote:

...

On Tue, Jun 28, 2016 at 10:46:48PM +0200, Levente Uzonyi wrote:

...

Thanks Dave,

I've changed two names and it works again. I've also disabled remote connections to the VNC server. At the same time updated the README file with a describing how to connect to the VNC over ssh.

Hi Levente,

Noob problem, please be patient.

I am having trouble figuring out how to connect through ssh. I am not experienced with this so I am probably doing something wrong.

I created new keys with ssh-keygen, and copied the public key to box3 with

$ ssh-copy-id ssdotcom@squeaksource.com

This works fine, and I can ssh to davidlewis@box3.squeak.org without entering a password, so I think that the keys are working.

I then do this to set up the tunneling:

$ ssh -N -L 5901:127.0.0.1:5901 davidlewis@box3.squeak.org

I am using a Vinagre remote desktop viewer, and I connect to 127.0.0.1:1 to make the connection. I see this error in the window where I set up the tunneling:

$ ssh -N -L 5901:127.0.0.1:5901 davidlewis@box3.squeak.org channel 2: open failed: connect failed: Connection refused

The error message means that the tunnel is working, but there's no socket listening on port 5901 on the server. Did you start RFBServer the way you described it in the README file?

...

So I think that I am doing something wrong here.

You should do everything the same way you did before, except for setting up the ssh tunnel and connecting to 127.0.0.1:5901 instead of to the box in your VNC client.

...

I am assuming that I should get a connection to an X11 desktop on box3, although I should mention that the VM for squeaksource.com is running headless, so its Squeak window would not be visible in an X11 desktop.

Your VNC client should show the Squeak desktop. There's no X11 server involved there.

Levente

...

Can you point me in the right direction? Thanks.

Dave

Clearly that was the wrong thing to do, as squeaksource.com went dead immediately after I killed 15483.

I then killed 5940, because I did not want to take a chance that the "wrong" image would save itself on the hourly image save.

Supervise restarted the image as expected, and the site appears normal again, with no extra squeakvm process.

I am concerned that we may have had a period of time during which two instances of the squeaksource.com image were both running, with both saving themselves to disk with the same image name. If the last image to have done so was not the "real" squeaksource.com image, then we may have lost data.

As far as I can tell, everything is OK now. I will watch for problems.

Dave

On Thu, Jun 30, 2016 at 07:43:36PM -0400, David T. Lewis wrote:

Levente,

Just FYI, for reasons that I cannot explain we seem to have two squeaksource images running:

ssdotcom 5940 5939 9 Jun30 ? 01:55:09 /usr/local/lib/squeak/4.15.3-3634/squeakvm -vm-display-null /home/ssdotcom/SqueakSource/squeaksource.4.image ssdotcom 15483 1 10 Jun14 ? 1-19:56:10 /usr/local/lib/squeak/4.15.3-3634/squeakvm -vm-display-null /home/ssdotcom/SqueakSource/squeaksource.4.image

Process 5940 is the one that I can connect to with VNC, and that is running under the control of supervise. Process 15483 is reparented to root.

I will kill 15483. This note is just to let you know what I am doing in case I break something.

Dave

On Thu, Jun 30, 2016 at 12:17:51AM -0400, David T. Lewis wrote:

...

Thank you Levente, I can connect to the image now. I did not understand that I should start RFBServer exactly as before. It works fine, thank you for explaining.

Dave

On Thu, Jun 30, 2016 at 04:25:06AM +0200, Levente Uzonyi wrote:

...

Hi Dave,

On Wed, 29 Jun 2016, David T. Lewis wrote:

...

On Tue, Jun 28, 2016 at 10:46:48PM +0200, Levente Uzonyi wrote:

...

Thanks Dave,

I've changed two names and it works again. I've also disabled remote connections to the VNC server. At the same time updated the README file with a describing how to connect to the VNC over ssh.

Hi Levente,

Noob problem, please be patient.

I am having trouble figuring out how to connect through ssh. I am not experienced with this so I am probably doing something wrong.

I created new keys with ssh-keygen, and copied the public key to box3 with

$ ssh-copy-id ssdotcom@squeaksource.com

This works fine, and I can ssh to davidlewis@box3.squeak.org without entering a password, so I think that the keys are working.

I then do this to set up the tunneling:

$ ssh -N -L 5901:127.0.0.1:5901 davidlewis@box3.squeak.org

I am using a Vinagre remote desktop viewer, and I connect to 127.0.0.1:1 to make the connection. I see this error in the window where I set up the tunneling:

$ ssh -N -L 5901:127.0.0.1:5901 davidlewis@box3.squeak.org channel 2: open failed: connect failed: Connection refused

The error message means that the tunnel is working, but there's no socket listening on port 5901 on the server. Did you start RFBServer the way you described it in the README file?

...

So I think that I am doing something wrong here.

You should do everything the same way you did before, except for setting up the ssh tunnel and connecting to 127.0.0.1:5901 instead of to the box in your VNC client.

...

I am assuming that I should get a connection to an X11 desktop on box3, although I should mention that the VM for squeaksource.com is running headless, so its Squeak window would not be visible in an X11 desktop.

Your VNC client should show the Squeak desktop. There's no X11 server involved there.

Levente

...

Can you point me in the right direction? Thanks.

Dave