waxworlds.org
servers which will incur some
downtime to services.
Currently, oak
and ash
run Debian 10 (Buster). They will be upgraded to
Debian 11 (Bullseye), which is an LTS release.
waxworlds.org
servers which will incur some downtime to services.
Currently, oak
and ash
run Debian 10 (Buster). They will be upgraded to
Debian 11 (Bullseye), which is an LTS release.
All waxworlds.org services should be back up and running again now.
]]>oak
to the cloud is being undertaken now.
This includes:
Data to be migrated later (upon request):
ash
has been upgraded from 5.6 to 7.3. PHP 7.3 introduces lots of
breaking changes.
Please check that your websites still function correctly.
]]>oak
and ash
are to upgraded to Debian 10 (Buster) immediately. This is
in order to address security issues with packages that, while supported by
Debian, are no longer maintained.
Notes
oak.waxworlds.org
. An engineer has already
been scheduled to address and resolve the issue but he will not be on-site until
Monday 16th December. Until then, oak
will be down, I'm afraid.
Since oak has been partially migrated in to the cloud, web, DNS and chat services are unaffected. The major service affected by this is email. We shouldn't lose any mail -- SMTP replays hang on to it and retry delivery when it fails -- but I'm also going to look in to whether or not I can migrating mail to the cloud immediately.
(2019-12-15) There seems to be intermittent line sync and some mail is getting through.
(2019-12-16 1:32pm) Fault is fixed. We're back up!
oak
to a new cloud-based server.
This includes:
To that end, I plan to retire the waxworlds XMPP (Jabber) services on 12th June 2018.
We also now host a matrix server for chat. Matrix (and riot) have proved to be a very successful alternative to jabber that also works well on mobile platforms, handles multiple connections better, facilitates posting images/files/links and is generally much more modern in its approach to chat. Essentially, I would propose that he Jabber service is also now redundant and my recommendation, going forwards, would be to use matrix anyway.
If there are any significant reasons why you think I shouldn't EOL the jabber service, or why you think I should attempt to manually migrate the data and revive it, please get in touch before 12th June.
]]>