Re: darcs hub is back up

Thank you so much for all your hard work Simon. It's awesome to have
hub.darcs.net back online!  :o)

Den man. 25. jun. 2018 kl. 20.01 skrev Simon Michael <[email protected]>:

> Darcs hub ssh access, and the whole site should now be working normally
> again. (Thanks to gpiero for the hint to add darcs to $PATH for ssh users.)
>
> *Updating your known hosts file*
>
> When you next attempt a darcs operation using ssh, you will likely see a
> big warning like "WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!",
> because the new server has a new ssh key. I think this was needed to
> prevent warnings about the IP address change. And I think this means every
> user will have to update their $HOME/.ssh/known_hosts file (or windows
> equivalent) to silence the warning. (If you know otherwise, let me know).
>
> The error message should tell you where the known_hosts file is, and the
> problem line. You can open the file in an editor remove this line, and any
> others it complains about. But this is easier, if it works on your system:
>
> $ ssh-keygen -R hub.darcs.net       # remove hub.darcs.net entry from
> known_hosts
> $ ssh-keygen -R 173.255.254.122  # remove entry for the old IP address
> $ ssh-keygen -R 173.255.254.113  # remove any out-of-date entry for the
> new IP address
> $ ssh hub.darcs.net
> The authenticity of host 'hub.darcs.net (173.255.254.113)' can't be
> established.
> RSA key fingerprint is SHA256:3eBJH9dB8ez4tJuxmnEP7dNHRRTk2BAKPuUmcGaoAAM.
> Are you sure you want to continue connecting (yes/no)? yes
>
> Warning: Permanently added 'hub.darcs.net,173.255.254.113' (RSA) to the
> list of known hosts.
> PTY allocation request failed on channel 0
> shell request failed on channel 0
>
> Now "ssh hub.darcs.net" and "darcs push", "darcs pull" etc. should work
> as before, without warnings.
>
> *Sum-up*
>
> I'll keep this brief. I'm sorry for the length of this outage (by far the
> longest in darcs hub's history.) I have no particular plans or budget for
> darcs hub at the moment, and I have been relying on it to just keep
> running. As a result of this incident it now has its own VPS, separate from
> my other projects, which is an old goal. And the file layout and ops
> processes have been improved and documented. When couchdb arrives for
> ubuntu, I will try again to upgrade to latest ubuntu LTS (and couchdb 2.x),
> more carefully.  Hopefully the ops improvements will continue and lead to
> better insight into current darcs hub activity.
>
> Best,
> -Simon
>
>
>
> On Jun 25, 2018, at 2:03 PM, Simon Michael <[email protected]> wrote:
>
> Another update.
>
> I have moved hub.darcs.net to a new VPS of its own. Note the IP address
> has changed to 173.255.219.113.
>
> The web UI is up again and should be working normally. I have added status
> info to the front page.
>
> The ssh server is not yet operational, I am still working out a few
> problems with it. For now, you can get or pull repos using their http url
> (eg darcs get http://hub.darcs.net/simon/ssh).
>
> Thanks for your patience, and please watch the #darcs IRC channel,
> darcs-users list or http://hub.darcs.net front page for more news.
>
> Best
> -Simon
>
>
>
>
> On Jun 17, 2018, at 3:17 PM, Simon Michael <[email protected]> wrote:
>
> Hi all. Here's an update on the current outage at http://hub.darcs.net .
>
> - All data is safe and service will be restored asap.
> - This is the fourth day of the incident. Though this is a best-effort
> free service provided in my "spare" time, I do care about reliability. This
> is the longest outage we've had. I'm very sorry about it.
>
> - Unfortunately due to press of life events just now I'm not able to drop
> everything and work on it; I have windows of time. This is contributing to
> the delay.
>
> - This is an upgrade that went wrong. In short, I upgraded the VPS on
> which darcs hub runs, without realising that couchdb was not available for
> the newer OS. (See below).
>
> - Rolling back the VPS upgrade was not practical, as I run other things
> there as well.
>
> - I guessed wrongly that the new couchdb packages would appear within
> hours. It now looks like that could take a week, or more. (
> https://github.com/apache/couchdb/issues/1314)
>
> - In parallel I started building a new VPS, but last night it got
> compromised. So I must start over with this.
> - Hopefully, you all are working productively from your local repo copies.
> But if you are urgently blocked, there may be something helpful I could do;
> let me know.
>
> I'll update you when things change. Thanks for your patience.
>
> Best,
>
> -Simon
> sm on #darcs IRC channel
>
>
> On Jun 14, 2018, at 2:57 PM, Simon Michael <[email protected]> wrote:
>
> Hi all,
>
> I apologise for the darcs hub outage in progress at the moment. I began a
> systems upgrade to ubuntu bionic, and too late discovered this is a problem
> for couchdb:
>
> - ubuntu's couchdb packages are gone
> - couchdb's ubuntu packages are not yet ready
> - building couchdb from source is too costly
> - https://launchpad.net/~couchdb/+archive/ubuntu/master can't be added to
> my system for some reason
>
> If you know a quick solution, please contact me here or on #darcs.
> Otherwise, I'm afraid we will be waiting until
> https://github.com/apache/couchdb/issues/1314 is complete. I think and
> hope this will be quite soon. Sorry for the inconvenience.
>
> Best,
> -Simon
>
>
>
>
> _______________________________________________
> darcs-users mailing list
> [email protected]
> https://lists.osuosl.org/mailman/listinfo/darcs-users
>

_______________________________________________
darcs-users mailing list
[email protected]
https://lists.osuosl.org/mailman/listinfo/darcs-users