FYI, I am currently consuming a large amount of disk space on build.squeak.org for testing squeaksource migration. Let me know if this causes any problems.

Over the weekend I was able to bring up a full copy of squeaksource.com on my home PC. I worked around a couple of problems and got the in-image repository updated (so it won't spam the mailing lists after a SqueakSource restart), and I disabled mail delivery. I then copied the entire thing to my user directory on build.squeak.org.

This is just a temporary test and is not yet properly installed, but anyone interested can connect to it on http://build.squeak.org:8888. VNC is running on display 1, please ask if you would like the password (this list is archived so I won't mention the password here).

I do need some help to identify the right location for the real installation. Will this be on box4? If so, can I please get an account?

Thanks, Dave

On Sat, Aug 24, 2013 at 01:12:22PM -0400, David T. Lewis wrote:

On Fri, Aug 23, 2013 at 09:50:08PM -0400, David T. Lewis wrote:

...

We now have access to a complete snapshot copy of SqueakSource. I am in the process of retrieving the files to my personal PC (not yet complete, I'm still trying to get a clean copy of one large 15GB file), and I will now need a place to put them on squeak.org.

I need some help to proceed. We need a server with 20 to 30 GB of file space available for the SqueakSource files, and with memory and CPU resources similar to whatever we are currently doing for source.squeak.org.

Can someone help, either by giving me access to an existing server, or by letting me know what is available? I will need a user account (lewis) similar to my current account on build.squeak.org, and I will need sudo privilege to set up an account for squeaksource and to set up the runtime environment.

In addition it would be helpful if I could get enough access to the source.squeak.org server so that I can look at it and figure out how that server is configured. Even better would be if the source.squeak.org server has enough capacity (mainly disk space) to also host squeaksource, in which case we can put both of them on the same server.

I would like to do this as soon as possible (tomorrow perhaps?) so any assistance and pointers will be gratefully received.

I now (finally) have a complete copy of the SqueakSource files sitting on my hard drive here in Ann Arbor, Michigan. Here is what we have:

-rw-r--r-- 1 lewis users 16341844652 2013-08-24 04:21 Squeaksource-projects-22-8-2013.tar -rw-r--r-- 1 lewis users 5558656 2013-08-23 08:20 Squeak-3.9-8-SqueakSource.app.tar -rw-r--r-- 1 lewis users 167474616 2013-08-23 08:19 squeaksource.image -rw-r--r-- 1 lewis users 15721301 2013-08-23 08:18 squeaksource.changes -rw-r--r-- 1 lewis users 718 2013-08-23 08:18 squeaksource.com -rw-r--r-- 1 lewis users 1686 2013-08-23 08:17 Workspace.text -rw-r--r-- 1 lewis users 14542313 2013-08-23 08:17 SqueakV3.sources

After unpacking the files (these are compressed tars), the total disk usage is a bit over 16 GB:

lewis@linux-jh8m:~/squeak/SS/TransitionToSqueakDotOrg/WORK> du -s * 21564 Squeak-3.9-8-SqueakSource.app 15356 squeaksource.changes 4 squeaksource.com 163552 squeaksource.image 14204 SqueakV3.sources 16401280 ss 4 Workspace.text

So a server with 20GB working space is sufficient, and 30GB would provide comfortable headroom.

Dave

It's still Ken, no-one has stepped up to take over yet. Thankfully, Ken still keeps it up ...

Chris M. just got access to box3 and box4, I assume with sudo rights, so he should be able to set you up.

- Bert -

On 2013-08-28, at 17:56, "David T. Lewis" lewis@mail.msen.com wrote:

Who is the gatekeeper for server and account access? I know Ken has been trying to hand off responsibility for this for quite some time, but I don't recall who picked up the task.

I know we are in the middle of vacation season, but if someone can give me a pointer I'd appreciate it.

Thanks, Dave

On Mon, Aug 26, 2013 at 08:38:01AM -0400, David T. Lewis wrote:

...

FYI, I am currently consuming a large amount of disk space on build.squeak.org for testing squeaksource migration. Let me know if this causes any problems.

Over the weekend I was able to bring up a full copy of squeaksource.com on my home PC. I worked around a couple of problems and got the in-image repository updated (so it won't spam the mailing lists after a SqueakSource restart), and I disabled mail delivery. I then copied the entire thing to my user directory on build.squeak.org.

This is just a temporary test and is not yet properly installed, but anyone interested can connect to it on http://build.squeak.org:8888. VNC is running on display 1, please ask if you would like the password (this list is archived so I won't mention the password here).

I do need some help to identify the right location for the real installation. Will this be on box4? If so, can I please get an account?

Thanks, Dave

On Sat, Aug 24, 2013 at 01:12:22PM -0400, David T. Lewis wrote:

...

On Fri, Aug 23, 2013 at 09:50:08PM -0400, David T. Lewis wrote:

...

We now have access to a complete snapshot copy of SqueakSource. I am in the process of retrieving the files to my personal PC (not yet complete, I'm still trying to get a clean copy of one large 15GB file), and I will now need a place to put them on squeak.org.

I need some help to proceed. We need a server with 20 to 30 GB of file space available for the SqueakSource files, and with memory and CPU resources similar to whatever we are currently doing for source.squeak.org.

Can someone help, either by giving me access to an existing server, or by letting me know what is available? I will need a user account (lewis) similar to my current account on build.squeak.org, and I will need sudo privilege to set up an account for squeaksource and to set up the runtime environment.

In addition it would be helpful if I could get enough access to the source.squeak.org server so that I can look at it and figure out how that server is configured. Even better would be if the source.squeak.org server has enough capacity (mainly disk space) to also host squeaksource, in which case we can put both of them on the same server.

I would like to do this as soon as possible (tomorrow perhaps?) so any assistance and pointers will be gratefully received.

I now (finally) have a complete copy of the SqueakSource files sitting on my hard drive here in Ann Arbor, Michigan. Here is what we have:

-rw-r--r-- 1 lewis users 16341844652 2013-08-24 04:21 Squeaksource-projects-22-8-2013.tar -rw-r--r-- 1 lewis users 5558656 2013-08-23 08:20 Squeak-3.9-8-SqueakSource.app.tar -rw-r--r-- 1 lewis users 167474616 2013-08-23 08:19 squeaksource.image -rw-r--r-- 1 lewis users 15721301 2013-08-23 08:18 squeaksource.changes -rw-r--r-- 1 lewis users 718 2013-08-23 08:18 squeaksource.com -rw-r--r-- 1 lewis users 1686 2013-08-23 08:17 Workspace.text -rw-r--r-- 1 lewis users 14542313 2013-08-23 08:17 SqueakV3.sources

After unpacking the files (these are compressed tars), the total disk usage is a bit over 16 GB:

lewis@linux-jh8m:~/squeak/SS/TransitionToSqueakDotOrg/WORK> du -s * 21564 Squeak-3.9-8-SqueakSource.app 15356 squeaksource.changes 4 squeaksource.com 163552 squeaksource.image 14204 SqueakV3.sources 16401280 ss 4 Workspace.text

So a server with 20GB working space is sufficient, and 30GB would provide comfortable headroom.

Dave

<bump>

Chris? Ken? Anyone?

I am quite anxious to make progress on the squeaksource.com move to squeak.org, but I am somewhat stuck if I cannot get access to one of our servers.

An account for lewis on box4 would be a huge help if anyone with root access can make that happen.

Thanks, Dave

On Thu, Aug 29, 2013 at 04:57:12PM -0400, David T. Lewis wrote:

Hi Chris,

Do you have root (or sudo) access to add me as a user on box4? If so, can you please add me with an account similar to what I currently have on box3:

lewis@box3-squeak:~$ id uid=1003(lewis) gid=1003(lewis) groups=1003(lewis),27(sudo) lewis@box3-squeak:~$ grep lewis /etc/passwd lewis:x:1003:1003:David Lewis lewis@mail.msen.com,,,:/home/lewis:/bin/bash lewis@box3-squeak:~$ grep lewis /etc/group sudo:x:27:kencausey,chriscunnington,lewis,leventeuzonyi,bertfreudenberg,frankshearar,chrismuller lewis:x:1003: lewis@box3-squeak:~$

Thanks a lot!

Dave

On Thu, Aug 29, 2013 at 05:52:11PM +0200, Bert Freudenberg wrote:

...

It's still Ken, no-one has stepped up to take over yet. Thankfully, Ken still keeps it up ...

Chris M. just got access to box3 and box4, I assume with sudo rights, so he should be able to set you up.

• Bert -

On 2013-08-28, at 17:56, "David T. Lewis" lewis@mail.msen.com wrote:

...

Who is the gatekeeper for server and account access? I know Ken has been trying to hand off responsibility for this for quite some time, but I don't recall who picked up the task.

I know we are in the middle of vacation season, but if someone can give me a pointer I'd appreciate it.

Thanks, Dave

On Mon, Aug 26, 2013 at 08:38:01AM -0400, David T. Lewis wrote:

...

FYI, I am currently consuming a large amount of disk space on build.squeak.org for testing squeaksource migration. Let me know if this causes any problems.

Over the weekend I was able to bring up a full copy of squeaksource.com on my home PC. I worked around a couple of problems and got the in-image repository updated (so it won't spam the mailing lists after a SqueakSource restart), and I disabled mail delivery. I then copied the entire thing to my user directory on build.squeak.org.

This is just a temporary test and is not yet properly installed, but anyone interested can connect to it on http://build.squeak.org:8888. VNC is running on display 1, please ask if you would like the password (this list is archived so I won't mention the password here).

I do need some help to identify the right location for the real installation. Will this be on box4? If so, can I please get an account?

Thanks, Dave

On Sat, Aug 24, 2013 at 01:12:22PM -0400, David T. Lewis wrote:

...

On Fri, Aug 23, 2013 at 09:50:08PM -0400, David T. Lewis wrote:

...

We now have access to a complete snapshot copy of SqueakSource. I am in the process of retrieving the files to my personal PC (not yet complete, I'm still trying to get a clean copy of one large 15GB file), and I will now need a place to put them on squeak.org.

I need some help to proceed. We need a server with 20 to 30 GB of file space available for the SqueakSource files, and with memory and CPU resources similar to whatever we are currently doing for source.squeak.org.

Can someone help, either by giving me access to an existing server, or by letting me know what is available? I will need a user account (lewis) similar to my current account on build.squeak.org, and I will need sudo privilege to set up an account for squeaksource and to set up the runtime environment.

In addition it would be helpful if I could get enough access to the source.squeak.org server so that I can look at it and figure out how that server is configured. Even better would be if the source.squeak.org server has enough capacity (mainly disk space) to also host squeaksource, in which case we can put both of them on the same server.

I would like to do this as soon as possible (tomorrow perhaps?) so any assistance and pointers will be gratefully received.

I now (finally) have a complete copy of the SqueakSource files sitting on my hard drive here in Ann Arbor, Michigan. Here is what we have:

-rw-r--r-- 1 lewis users 16341844652 2013-08-24 04:21 Squeaksource-projects-22-8-2013.tar -rw-r--r-- 1 lewis users 5558656 2013-08-23 08:20 Squeak-3.9-8-SqueakSource.app.tar -rw-r--r-- 1 lewis users 167474616 2013-08-23 08:19 squeaksource.image -rw-r--r-- 1 lewis users 15721301 2013-08-23 08:18 squeaksource.changes -rw-r--r-- 1 lewis users 718 2013-08-23 08:18 squeaksource.com -rw-r--r-- 1 lewis users 1686 2013-08-23 08:17 Workspace.text -rw-r--r-- 1 lewis users 14542313 2013-08-23 08:17 SqueakV3.sources

After unpacking the files (these are compressed tars), the total disk usage is a bit over 16 GB:

lewis@linux-jh8m:~/squeak/SS/TransitionToSqueakDotOrg/WORK> du -s * 21564 Squeak-3.9-8-SqueakSource.app 15356 squeaksource.changes 4 squeaksource.com 163552 squeaksource.image 14204 SqueakV3.sources 16401280 ss 4 Workspace.text

So a server with 20GB working space is sufficient, and 30GB would provide comfortable headroom.

Dave

Our copy of squeaksource.com is now running in its own ssdotcom account on box3.squeak.org on port 8888, with a supervisory script that restarts the image in the event of failure. I fixed a problem with reloading the repository on image restart (the one that caused email spam storms on restart), and I have the hourly automatic image process working again (it needed to do the image save from the UI thread).

Everything seems to be working at this point, so I now need to figure out how to bring this up under Apache behind port 80. I will have limited free time over the next week, so this may not happen for a few more days. Meanwhile, if anyone wants to put some load on http://box3.squeak.org:8888, please do so. Extra credit to anyone who can break it :-)

Dave

On Sun, Sep 15, 2013 at 06:05:19PM -0400, David T. Lewis wrote:

An update on the SqueakSource move:

I have moved our copy of squeaksource.com from my personal user account on box3.squeak.org to a newly created account ssdotcom on the same server. All files are now owned by ssdotcom, and the server image is running from a supervisory script ~ssdtocom/SqueakSource/runimage.sh that will restart the image in the event of failure (although that it is not yet wired in to the system start scripts).

Our copy of squeaksource.com has been running without problems on http://box3.squeak.org:8888 (albeit with no load) for about three weeks, so I have moved it to the dedicated ssdotcom account, and I will continue to keep it active there until we can finalize the move.

The most important thing I need to do next is get it running behind Apache on port 80. Unfortunately I have no real experience setting up Apache, so there is a chance that I may screw things up build.squeak.org (which runs on box3 also), so apologies in advance if that happens.

I am keeping some notes in our admin log on box3 /root/admin-log.txt, so if anything looks broken please look there to see how I broke it.

Dave

On Mon, Aug 26, 2013 at 08:38:01AM -0400, David T. Lewis wrote:

...

FYI, I am currently consuming a large amount of disk space on build.squeak.org for testing squeaksource migration. Let me know if this causes any problems.

Over the weekend I was able to bring up a full copy of squeaksource.com on my home PC. I worked around a couple of problems and got the in-image repository updated (so it won't spam the mailing lists after a SqueakSource restart), and I disabled mail delivery. I then copied the entire thing to my user directory on build.squeak.org.

This is just a temporary test and is not yet properly installed, but anyone interested can connect to it on http://build.squeak.org:8888. VNC is running on display 1, please ask if you would like the password (this list is archived so I won't mention the password here).

I do need some help to identify the right location for the real installation. Will this be on box4? If so, can I please get an account?

Thanks, Dave

On Sat, Aug 24, 2013 at 01:12:22PM -0400, David T. Lewis wrote:

...

On Fri, Aug 23, 2013 at 09:50:08PM -0400, David T. Lewis wrote:

...

We now have access to a complete snapshot copy of SqueakSource. I am in the process of retrieving the files to my personal PC (not yet complete, I'm still trying to get a clean copy of one large 15GB file), and I will now need a place to put them on squeak.org.

I need some help to proceed. We need a server with 20 to 30 GB of file space available for the SqueakSource files, and with memory and CPU resources similar to whatever we are currently doing for source.squeak.org.

Can someone help, either by giving me access to an existing server, or by letting me know what is available? I will need a user account (lewis) similar to my current account on build.squeak.org, and I will need sudo privilege to set up an account for squeaksource and to set up the runtime environment.

In addition it would be helpful if I could get enough access to the source.squeak.org server so that I can look at it and figure out how that server is configured. Even better would be if the source.squeak.org server has enough capacity (mainly disk space) to also host squeaksource, in which case we can put both of them on the same server.

I would like to do this as soon as possible (tomorrow perhaps?) so any assistance and pointers will be gratefully received.

I now (finally) have a complete copy of the SqueakSource files sitting on my hard drive here in Ann Arbor, Michigan. Here is what we have:

-rw-r--r-- 1 lewis users 16341844652 2013-08-24 04:21 Squeaksource-projects-22-8-2013.tar -rw-r--r-- 1 lewis users 5558656 2013-08-23 08:20 Squeak-3.9-8-SqueakSource.app.tar -rw-r--r-- 1 lewis users 167474616 2013-08-23 08:19 squeaksource.image -rw-r--r-- 1 lewis users 15721301 2013-08-23 08:18 squeaksource.changes -rw-r--r-- 1 lewis users 718 2013-08-23 08:18 squeaksource.com -rw-r--r-- 1 lewis users 1686 2013-08-23 08:17 Workspace.text -rw-r--r-- 1 lewis users 14542313 2013-08-23 08:17 SqueakV3.sources

After unpacking the files (these are compressed tars), the total disk usage is a bit over 16 GB:

lewis@linux-jh8m:~/squeak/SS/TransitionToSqueakDotOrg/WORK> du -s * 21564 Squeak-3.9-8-SqueakSource.app 15356 squeaksource.changes 4 squeaksource.com 163552 squeaksource.image 14204 SqueakV3.sources 16401280 ss 4 Workspace.text

So a server with 20GB working space is sufficient, and 30GB would provide comfortable headroom.

Dave

On 16.10.2013, at 01:25, David T. Lewis lewis@mail.msen.com wrote:

How is our source.squeak.org image is being started at system boot time on box2? I gather from previous messages that it is (and should be) done with daemontools. I have no experience with daemontools, but I want to do the same thing for squeaksource.com on box3 if possible.

I have written a how to for dameontools+gemstone[1], so I probably can help you there? Daemontools has its quirks, it expects certain directory structures and certain handling of input and output, but in a nutshell

0. On debian, use the packages daemontools The daemontools daemontools-run Helper script to automatically start daemontools svtools (optional but very useful) 1. the service directory. you should execute all commands from the service directory. For default daemontools installation, this typically is `/service`, for debian, it is `/etc/service` The `svdir` command from the svtools package also prints that directory. 1b. the template directory. Debian loves symlinks. Therefore, it has templates for its services in `/etc/sv`. The idea is: 1. create your service as directory in `/etc/sv` 2. link it into `/etc/service` n. if you use daemontools-run or daemontools are already started, it should pick up the directory and start your service 2. main commando: `svc` 0. just executing `svc` does nothing…, so does `svc --help` (not `svc -h`, but it does not print a help page either) 0b. man svc :) 1. start a service (and keep it Up): `svc -u servicedirectoryname` 2. start a service but just Once: `svc -o servicedirectoryname` 3. Terminate a service (will restart): `svc -t servicedirectoryname` 4. stop a service and keep it Down: `svc -d servicedirectoryname`

3. Make sure that your scripts `exec` the actual executable, daemontools expects that. Also, `servicedirectoryname` has to have an executable file named `run` that runs your service. `svsetup` from the svtools package can help here.

4. Make sure, that the executable (squeak in that case) understands unix signals, at least TERM and KILL, correctly; STOP, CONT, and HUP would be nice.

5. optional: logging create a `log` directory in `servicedirectoryname` and use `multilog` in it like #! /bin/sh exec multilog t ./main and from then, it will log to `servicedirectoryname/log/main`. the file `current` is the current log, all other files are named with TAI[2] timestamp. 0. you can inspect the log files in `servicedirectoryname/log/main` manually, or 1. use `mlcat servicedirectoryname` to print the latest log. 2. likewise, `mltac` (cats reverse) `mltail`, `mlhead`. all four are from the `svtools` package

6. optional: init.d script `svinitd` and `svinitd-create` help to create /etc/init.d/scripts for your service. NOTE: the scripts created `svinitd-create` are not yet ready for dependency-based boot[3] but changing that is near trivial. Moreover, if you create init.d script, DO NOT use them to start your service at boot, daemontools already take care of that.

7. other stuff: `svstat`: print info about service `svinfo`: equivalent from svtools, more versatile `svok`: checks whether a service is properly supervised; no output. *`setuidgid`: runs program as specified user and group *`softlimit`: runs program with specified resource limits *`envdir`: runs program with environment variables specified in a directory of files. *`envuidgid`: runs program as user specified by an environment variable/ * can be used in `run` script

HTH

Best -Tobias

[1] https://code.google.com/p/glassdb/wiki/GLASSDaemonTools [2] https://en.wikipedia.org/wiki/International_Atomic_Time, with tai64n(8) [3] https://wiki.debian.org/LSBInitScripts/DependencyBasedBoot

On Sun, 10 Nov 2013, David T. Lewis wrote:

For information - no action required:

Our squeaksource.com service is running with no apparent problems, but there is a possibility of problems arising in the next day, so I am sending this for information.

I checked our squeaksource.com image on box3 via VNC about an hour ago, and noticed an error notifier related to startup processing following an image save. The error was related to port 8888 already in use. I closed the notifier, then found that http://squeaksource.com was no longer active. I made a backup copy of the most recently saved disk image (in a BACKUPS subdirectory), then saved the image and restarted it.

Squeaksource.com is running normally, but VNC access is no longer working. This means that something failed in the startup processing, and this may lead to problems later on. It also means that it is hard to debug, because I no longer have VNC access.

I cannot do anything further tonight, but will follow up tomorrow to correct the problem.

It would be worth installing xpra[1][2], and starting the image with it. IIRC the box has debian installed on it, so the following steps should work:

On the server:

Installation: $ sudo apt-get install xpra

Start xpra on display #100: $ xpra start :100

Start the VM (this might have to be different on the server): $ DISPLAY=:100 squeak -vm-sound-null squeaksource.image

On your machine:

Once you have xpra installed, you can attach to squeak running on the server via ssh:

$ xpra attach --encoding=jpeg --auto-refresh-delay=0.1 ssh:box3:100

Here box3 is the label defined in the ssh config file, which can usually be found in $HOME/.ssh/config If you don't have such entry or file yet, then the following will do the trick:

Host box3 hostname box3.squeak.org user <your_username> compression yes port 22

You might want to use a different value for the --auto-refresh-delay parameter.

To detach from the image - but keep it running on the server - simply stop the xpra on your machine with Ctrl-C.

Levente

[1] http://xpra.org/ [2] https://help.ubuntu.com/community/Xpra

Dave

On Mon, 11 Nov 2013, Frank Shearar wrote:

So xpra is like screen, only for an X session?

Yes. Older versions (like the one which is available on box3 as a prebuilt package) don't support shared sessions, but that's not a problem for us.

Levente

frank

On 11 Nov 2013, at 7:59, Levente Uzonyi leves@elte.hu wrote:

...

On Sun, 10 Nov 2013, David T. Lewis wrote:

...

For information - no action required:

Our squeaksource.com service is running with no apparent problems, but there is a possibility of problems arising in the next day, so I am sending this for information.

I checked our squeaksource.com image on box3 via VNC about an hour ago, and noticed an error notifier related to startup processing following an image save. The error was related to port 8888 already in use. I closed the notifier, then found that http://squeaksource.com was no longer active. I made a backup copy of the most recently saved disk image (in a BACKUPS subdirectory), then saved the image and restarted it.

Squeaksource.com is running normally, but VNC access is no longer working. This means that something failed in the startup processing, and this may lead to problems later on. It also means that it is hard to debug, because I no longer have VNC access.

I cannot do anything further tonight, but will follow up tomorrow to correct the problem.

It would be worth installing xpra[1][2], and starting the image with it. IIRC the box has debian installed on it, so the following steps should work:

On the server:

Installation: $ sudo apt-get install xpra

Start xpra on display #100: $ xpra start :100

Start the VM (this might have to be different on the server): $ DISPLAY=:100 squeak -vm-sound-null squeaksource.image

On your machine:

Once you have xpra installed, you can attach to squeak running on the server via ssh:

$ xpra attach --encoding=jpeg --auto-refresh-delay=0.1 ssh:box3:100

Here box3 is the label defined in the ssh config file, which can usually be found in $HOME/.ssh/config If you don't have such entry or file yet, then the following will do the trick:

Host box3 hostname box3.squeak.org user <your_username> compression yes port 22

You might want to use a different value for the --auto-refresh-delay parameter.

To detach from the image - but keep it running on the server - simply stop the xpra on your machine with Ctrl-C.

Levente

[1] http://xpra.org/ [2] https://help.ubuntu.com/community/Xpra

...

Dave

I have repaired the broken squeaksource.com image and reloaded it on box3. As far as I can tell, no data was lost and nothing bad happened aside from a couple of very brief outages as I was discovering and then fixing the problem.

Good news: We now have a snapshot of an image that captures the problem and that can be used for debugging. I am looking at it now, and anyone else who might be interested can download it from box3.squeak.org. The backup is in /home/ssdotcom/SqueakSource/BACKUPS/ss-image-save-20131111.tgz.

This problem has definitely happened before, both on the old squeaksource.com image from SCG, and also on the new image that is based on source.squeak.org. I think it is quite likely that source.squeak.com was in this condition at the time of our recent failure, and that is my working assumption at this point.

I also corrected the problem in which VNC access was not available when an error occurred in startUp processing.

Here is what I did to repair the image:

- First, open a process browser and note the runaway session handlers. ProcessBrowser open.

- Then kill runaway processes:

Process allInstances do: [ :each | each priority = 30 ifTrue: [ each terminate ] ].

Get a clean image restart by temporarily commenting out the line "SSKom startOn: self port" in the SSRepository class>>startUp: method.

Then close all the debug notifiers, save the image, and restart it.

Restore SSRepository class>>startUp: to its previous version.

Move the RFBServer up in the system startup list so that it will be activated prior to starting Seaside and SqueakSource. This will make it more likely that VNC access will be maintained the next time a problem like this happens.

Smalltalk addToStartUpList: RFBServer after: ModDoc.

Dave

On Sun, Nov 10, 2013 at 11:23:27PM -0500, David T. Lewis wrote:

For information - no action required:

Our squeaksource.com service is running with no apparent problems, but there is a possibility of problems arising in the next day, so I am sending this for information.

I checked our squeaksource.com image on box3 via VNC about an hour ago, and noticed an error notifier related to startup processing following an image save. The error was related to port 8888 already in use. I closed the notifier, then found that http://squeaksource.com was no longer active. I made a backup copy of the most recently saved disk image (in a BACKUPS subdirectory), then saved the image and restarted it.

Squeaksource.com is running normally, but VNC access is no longer working. This means that something failed in the startup processing, and this may lead to problems later on. It also means that it is hard to debug, because I no longer have VNC access.

I cannot do anything further tonight, but will follow up tomorrow to correct the problem.

Dave

On Mon, Nov 11, 2013 at 09:50:03PM +0100, Tobias Pape wrote:

Hi,

On 11.11.2013, at 20:00, David T. Lewis lewis@mail.msen.com wrote:

...

Process allInstances do: [ :each | each priority = 30 ifTrue: [ each terminate ] ].

IIRC, this used to be a doIt in a workspace in the original SCG-Image (if not even a background-task that would run once a day)

Yes, that's right. I preserved the original workspace from the old image in the new image, and I borrowed this doIt from the original. Whatever the cause of this condition, it has been an intermittent problem for a long time, and it is still with us today.

Shall we install such an ?autokill? feature? (I would advise against, tho)

I agree, we should not do an autokill. But if we can solve the underlying problem, that would be a very good thing :-)

Dave

Just a note to to follow up - the squeaksource.com image has been running for 10 days since I sent the note below. Earlier today, the image noticed that it had accumulated too many open file descriptors, so it shut itself down to await a restart by supervise. This worked as expected with no manual intervention.

I think we can generally expect that the image will restart itself a couple of times per month in order to clean up excess file descriptors. From the point of view of squeaksource users this is unlikely to have any noticable impact, and no special monitoring or intervention is required from the box-admins,

Given that the image is running under the control of supervise, I expect that it will start normally following any reboot of box3. However, this has not been tested.

Dave

On Thu, Nov 14, 2013 at 12:55:38PM -0500, David T. Lewis wrote:

I have put the squeaksource.com image under the control of supervise(8) on box3.squeak.org. The service name is "ssdotcom" and it should now be controlled by svc(8) run by root in the /etc/service directory.

This replaces the the homebrew runimage.sh supervisory script that that I had written initially in order to bring squeaksource.com on line. That script will now issue a message informing the user of the change.

Everything seems to be working properly now. I will keep a close eye on it for the next few days to make sure it stays that way.

Assuming that no new problems arise, this completes the transition of squeaksource.com from its original home at SCG to its new home at squeak.org.

Dave