I must be overlooking something.
A process listing shows this: root 671 665 0 2017 ? 00:00:00 readproctitle service errors: ..............................................................................................................................................................................................................................................................................................................................................svscan: warning: unable to stat squeaksource: file does not exist
And I can see the squeaksource image being endlessly restarted.
What changed: I stopped the service (sudo -d /service/squeaksource), replaced the image, and started it again (sudo -u /service/squeaksource).
I restored the previously working image, and still have the same problem (I put the right image back after that verification).
I can't spot what I am overlooking here. I'll see if I can get it running manually outside of the supervise system.
:-/
Dave
On Wed, May 13, 2020 at 04:42:18PM +0200, Fabio Niephaus wrote:
Thank you, Dave!
On Wed, May 13, 2020 at 4:41 PM David T. Lewis lewis@mail.msen.com wrote:
I restarted source.squeak.org and am not having difficulties getting it restarted. I'll report back as soon as possible.
Dave
On Tue, May 12, 2020 at 09:39:05PM -0400, David T. Lewis wrote:
On Tue, May 12, 2020 at 05:55:53PM -0700, tim Rowledge wrote:
On 2020-05-12, at 5:45 PM, David T. Lewis lewis@mail.msen.com wrote:
Tim,
Indeed, the SqueakSource-tpr.1127 update looks suspicious. It changes #deliverMailFrom:to:text: and the changed method now calls an unimplemented method:
SMTPClient>>deliverMailFrom:to:text:usingServer:userName:password:
Hmm. According to the history I see before me this is in Network-tpr.238 in trunk. It's in my running 19666 level image and MC swears it has not been removed.
Ok, that makes sense. When I updated the source.squeak.org image, I updated the packages that I found in the ss repository. I did not update the other packages in the image (it is based on a Squeak 5.2 release image) and I should not do that.
I cannot follow up tonight, but it sounds like the best thing is for me to revert any non-essential changes, and restart the image with just the essential changes (Chris' patch.st to fix moving packages from inbox to treated or trunk, plus my update for commented MCMs).
Sorry for the mail problem, I will get it straightened out tomorrow.
Dave
OK, it should be back now, and hopefully the mail delivery will be working again.
I don't know the details, but it looks like the startup script is looking for a file called "patch.st" to load. Chris had previously told me to rename that file to "patch.st.old", which I had done. But today I wanted to undo my earlier changes, and I renamed patch.st.old to patch.st. That was entirely my mistake, I should not have done that.
When I manually started the run script, I got an abort error dump with this message at the end:
^^^^^^^^^^^^^^^^^^ Error: patch.st file is older than the image file. Aborting. ^^^^^^^^^^^^^^^^^^
So apparently the startup script saw the patch.st was old relative to the image, and decided that it would be a good idea to abort (as opposed to say just don't load the old patch file). When running under supervise, the error condition was not obvious, and supervise just went into an endless abort/retry loop.
Meanwhile, I still see this in the process listing:
root 671 665 0 2017 ? 00:00:00 readproctitle service errors: ..............................................................................................................................................................................................................................................................................................................................................svscan: warning: unable to stat squeaksource: file does not exist
I cannot figure out where that error is coming from, but apparently it is a red herring and had nothing to do with the restart problem.
Ugh. Sorry for the disruption.
Dave
On Wed, May 13, 2020 at 10:55:11AM -0400, David T. Lewis wrote:
I must be overlooking something.
A process listing shows this: root 671 665 0 2017 ? 00:00:00 readproctitle service errors: ..............................................................................................................................................................................................................................................................................................................................................svscan: warning: unable to stat squeaksource: file does not exist
And I can see the squeaksource image being endlessly restarted.
What changed: I stopped the service (sudo -d /service/squeaksource), replaced the image, and started it again (sudo -u /service/squeaksource).
I restored the previously working image, and still have the same problem (I put the right image back after that verification).
I can't spot what I am overlooking here. I'll see if I can get it running manually outside of the supervise system.
:-/
Dave
On Wed, May 13, 2020 at 04:42:18PM +0200, Fabio Niephaus wrote:
Thank you, Dave!
On Wed, May 13, 2020 at 4:41 PM David T. Lewis lewis@mail.msen.com wrote:
I restarted source.squeak.org and am not having difficulties getting it restarted. I'll report back as soon as possible.
Dave
On Tue, May 12, 2020 at 09:39:05PM -0400, David T. Lewis wrote:
On Tue, May 12, 2020 at 05:55:53PM -0700, tim Rowledge wrote:
On 2020-05-12, at 5:45 PM, David T. Lewis lewis@mail.msen.com wrote:
Tim,
Indeed, the SqueakSource-tpr.1127 update looks suspicious. It changes #deliverMailFrom:to:text: and the changed method now calls an unimplemented method:
SMTPClient>>deliverMailFrom:to:text:usingServer:userName:password:
Hmm. According to the history I see before me this is in Network-tpr.238 in trunk. It's in my running 19666 level image and MC swears it has not been removed.
Ok, that makes sense. When I updated the source.squeak.org image, I updated the packages that I found in the ss repository. I did not update the other packages in the image (it is based on a Squeak 5.2 release image) and I should not do that.
I cannot follow up tonight, but it sounds like the best thing is for me to revert any non-essential changes, and restart the image with just the essential changes (Chris' patch.st to fix moving packages from inbox to treated or trunk, plus my update for commented MCMs).
Sorry for the mail problem, I will get it straightened out tomorrow.
Dave
box-admins@lists.squeakfoundation.org