Smalltalk › Pharo › Pharo Smalltalk Developers

Re: stfx.eu down

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

2 messages Options

Stephane Ducasse-3

Re: stfx.eu down

Thanks Sven!!!

On Sat, Dec 22, 2018 at 8:13 PM Sven Van Caekenberghe <[hidden email]> wrote:

>
>
>
> > On 11 Dec 2018, at 21:23, Sven Van Caekenberghe <[hidden email]> wrote:
> >
> >> On 10 Dec 2018, at 22:10, Sven Van Caekenberghe <[hidden email]> wrote:
> >>
> >> Hi,
> >>
> >> This evening I somehow broke my stfx.eu server while doing an ubuntu dist upgrade (an old AWS EC2 machine).
> >>
> >> This means several websites / web services hosted by that machine are down, most notably mc.stfx.eu (hosting several of my packages) and ws.stfx.eu (used for shared smalltalk workspaces). A couple of Zinc tests will also fail.
> >
> > I recovered parts of the functionality: ws.stfx.eu (shared smalltalk workspaces) and zn.stfx.eu are back, so that normal Zinc unit tests should pass everywhere.
> >
> > At least all this is now running on Ubuntu 18.04.1 LTS on Pharo 7 64-bit, as it should.
> >
> > Next up is http://mc.stfx.eu for my Monticello repository, but that might take more time.
>
> At last, http://mc.stfx.eu is back up.
>
> I still recommend everyone to use the http://github.com/svenvc versions of my projects, as this is the better option going forward. I also intend to use these as primary repositories.
>
> >> For source code access, all my public repos exist both in an up to date form on GitHub (http://github.com/svenvc) as well in the original form in SmalltalkHub (http://smalltalkhub.com/#!/~SvenVanCaekenberghe) or SS3.
> >>
> >> The main problem there is that the distributed ConfigurationsOf and Catalog entries will still point to the original. This is not a problem with git's BaselineOf definitions.
> >>
> >> Although the machine will no longer boot, I managed to mount the original volume on another instance so I can still access the whole filesystem. This will make it possible to eventually recover most services. But this will take time as these things never happen when it is convenient. It will give me an opportunity to modernise the setup though, which is good.
> >>
> >> Sorry for the inconvenience.
> >>
> >> Sven
> >>
> >
>
>

philippeback

Re: stfx.eu down

Yes, very welcome!!

Phil

On Sun, Dec 23, 2018, 09:59 Stephane Ducasse <[hidden email] wrote:

Thanks Sven!!!

On Sat, Dec 22, 2018 at 8:13 PM Sven Van Caekenberghe <[hidden email]> wrote:
>
>
>
> > On 11 Dec 2018, at 21:23, Sven Van Caekenberghe <[hidden email]> wrote:
> >
> >> On 10 Dec 2018, at 22:10, Sven Van Caekenberghe <[hidden email]> wrote:
> >>
> >> Hi,
> >>
> >> This evening I somehow broke my stfx.eu server while doing an ubuntu dist upgrade (an old AWS EC2 machine).
> >>
> >> This means several websites / web services hosted by that machine are down, most notably mc.stfx.eu (hosting several of my packages) and ws.stfx.eu (used for shared smalltalk workspaces). A couple of Zinc tests will also fail.
> >
> > I recovered parts of the functionality: ws.stfx.eu (shared smalltalk workspaces) and zn.stfx.eu are back, so that normal Zinc unit tests should pass everywhere.
> >
> > At least all this is now running on Ubuntu 18.04.1 LTS on Pharo 7 64-bit, as it should.
> >
> > Next up is http://mc.stfx.eu for my Monticello repository, but that might take more time.
>
> At last, http://mc.stfx.eu is back up.
>
> I still recommend everyone to use the http://github.com/svenvc versions of my projects, as this is the better option going forward. I also intend to use these as primary repositories.
>
> >> For source code access, all my public repos exist both in an up to date form on GitHub (http://github.com/svenvc) as well in the original form in SmalltalkHub (http://smalltalkhub.com/#!/~SvenVanCaekenberghe) or SS3.
> >>
> >> The main problem there is that the distributed ConfigurationsOf and Catalog entries will still point to the original. This is not a problem with git's BaselineOf definitions.
> >>
> >> Although the machine will no longer boot, I managed to mount the original volume on another instance so I can still access the whole filesystem. This will make it possible to eventually recover most services. But this will take time as these things never happen when it is convenient. It will give me an opportunity to modernise the setup though, which is good.
> >>
> >> Sorry for the inconvenience.
> >>
> >> Sven
> >>
> >
>
>