Mirror maintenance windows, related communication, order of checks (Was: Re: pl1.php.net Disabled)

[email protected] (Patrick Schaaf)
Newsgroups php.mirrors
Message-ID <CAJ26g5QZuusQ8p3W91vb2pE9uVM98ns9VOEgN8RxfLR6rzzq6Q@mail.gmail.com>
Am 30.04.2015 17:40 schrieb "Hannes Magnusson" <[email protected]>:
>
> Mirrors that are frequently randomly unavailable are very frustrating for
users.
> If our mirror check system observes down time and sends you a
> notification -- imagine the annoyance from a real user not being able
> to reach php.net.

I'm pretty sure that a lot of the mirrors run hosted somewhere, and will be
affected by hosting and network provider maintenance windows, as was the
case on our at2.php.net mirror (and as it happens occasionally they had a
problem and the downtime was a bit extended).

These things usually happen in the middle of the night - I don't think many
Austrian PHP developers noticed it Tuesday between 03:00am and 05:00 am.

> Please make sure the mirror is fully functioning at all times and let
> us know about any planned maintenence so we can temporary disable the
> mirror.

Okay, will start to send mail when I get prenotification of planned
downtime at our providers.

Would you also like to be prenotified when I update PHP or the OS/kernel on
the boxes, which when it happens, sometimes takes 30 seconds for a reboot
or rollback in case of problems? So far during the last few years, I simply
relied on the automation to spot somewhat prolongued (unplanned) episodes,
and for short upgrades including reboots I just did it.

> You are right that the manual alias check is the first one to run, so
> any outage is likely to be caught by that check.

Might be good to first do a general reachability check, so that the
notification mail text is more clear about the cause.

best regards
  Patrick
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.