Re: [bitfolk] Renumbering: resolver not working? still point…

Top Page

Reply to this message
Author: Max B
Date:  
Subject: Re: [bitfolk] Renumbering: resolver not working? still points to 212.x, instead of 85.y on >=1 machine
oot every node. For some
nodes this would mean a full OS upgrade. This will be done
eventually but over a longer time span, as it will obviously be
necessary in order to support 64-bit guests.

Cheers,
Andy

--=20
http://bitfolk.com/ -- No-nonsense VPS hosting

--jesV4P1FjH8FXPjZ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAk/XV54ACgkQIJm2TL8VSQvBBACg8Ww4gR18Uz444hWnIJbI6wEA
J3EAn14Alsm+vT2aBMAx2JXPIsdlfBxY
=pJMP
-----END PGP SIGNATURE-----

--jesV4P1FjH8FXPjZ--


--===============0061280036==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
announce mailing list
announce@???
https://lists.bitfolk.com/mailman/listinfo/announce

--===============0061280036==--



From announce-bounces+users=lists.bitfolk.com@??? Tue Jun 12 19:25:27 2012
Received: from localhost ([127.0.0.1] helo=bitfolk.com)
    by mail.bitfolk.com with esmtp (Exim 4.72) (envelope-from
    <announce-bounces+users=lists.bitfolk.com@???>)
    id 1SeWiV-0001lr-MC
    for users@???; Tue, 12 Jun 2012 19:25:27 +0000
Received: from andy by mail.bitfolk.com with local (Exim 4.72)
    (envelope-from <andy@???>) id 1SeWhY-0001iO-GS
    for announce@???; Tue, 12 Jun 2012 19:24:49 +0000
Date: Tue, 12 Jun 2012 19:24:28 +0000
From: Andy Smith <andy@???>
To: announce@???
Message-ID: <20120612192428.GA11695@???>
MIME-Version: 1.0
OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
X-URL: http://strugglers.net/wiki/User:Andy
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Tue,
    12 Jun 2012 19:24:28 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    spamd1.lon.bitfolk.com
X-Spam-Level: 
X-Spam-ASN: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no
    autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP
X-BeenThere: announce@???
X-Mailman-Version: 2.1.13
Precedence: list
Content-Type: multipart/mixed; boundary="===============0548683290=="
Sender: announce-bounces+users=lists.bitfolk.com@???
Errors-To: announce-bounces+users=lists.bitfolk.com@???
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Tue,
    12 Jun 2012 19:25:27 +0000
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: announce-bounces+users=lists.bitfolk.com@???
X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false
Subject: [bitfolk] Network issue, starting around 1819Z today
X-BeenThere: users@???
Reply-To: users@???
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
    <mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
    <mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 19:25:27 -0000



--===============0548683290==
Content-Type: multipart/signed; micalg=pgp-ripemd160;
    protocol="application/pgp-signature"; boundary="8+OS07CeIgZ706fH"
Content-Disposition: inline



--8+OS07CeIgZ706fH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

As of aprox 1819Z there have been network problems at our
colo/transit provider, resulting in high packet loss. This is not
specific to Bitfolk; it affects all customers that I am aware of.
I've spoken to provider and they are working on it, is more info as I
have it.

Apologies for the disruption.

Cheers,
Andy

--=20
http://bitfolk.com/ -- No-nonsense VPS hosting


--8+OS07CeIgZ706fH
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAk/Xl2wACgkQIJm2TL8VSQuDzQCfXDoE4031qq0QGNTXPsW6YSPk
guEAoKdQgY0iCAeny9fGmjg2TvidTJg+
=y7p/
-----END PGP SIGNATURE-----

--8+OS07CeIgZ706fH--


--===============0548683290==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
announce mailing list
announce@???
https://lists.bitfolk.com/mailman/listinfo/announce

--===============0548683290==--



From announce-bounces+users=lists.bitfolk.com@??? Tue Jun 12 20:00:46 2012
Received: from localhost ([127.0.0.1] helo=bitfolk.com)
    by mail.bitfolk.com with esmtp (Exim 4.72) (envelope-from
    <announce-bounces+users=lists.bitfolk.com@???>)
    id 1SeXGg-0003aK-Ge
    for users@???; Tue, 12 Jun 2012 20:00:46 +0000
Received: from andy by mail.bitfolk.com with local (Exim 4.72)
    (envelope-from <andy@???>) id 1SeXGa-0003ZF-Hd
    for announce@???; Tue, 12 Jun 2012 20:00:40 +0000
Date: Tue, 12 Jun 2012 20:00:40 +0000
From: Andy Smith <andy@???>
To: announce@???
Message-ID: <20120612200040.GB11695@???>
References: <20120612192428.GA11695@???>
MIME-Version: 1.0
In-Reply-To: <20120612192428.GA11695@???>
OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
X-URL: http://strugglers.net/wiki/User:Andy
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Tue,
    12 Jun 2012 20:00:40 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    spamd3.lon.bitfolk.com
X-Spam-Level: 
X-Spam-ASN: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no
    autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP
X-BeenThere: announce@???
X-Mailman-Version: 2.1.13
Precedence: list
Content-Type: multipart/mixed; boundary="===============1754472669=="
Sender: announce-bounces+users=lists.bitfolk.com@???
Errors-To: announce-bounces+users=lists.bitfolk.com@???
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Tue,
    12 Jun 2012 20:00:46 +0000
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: announce-bounces+users=lists.bitfolk.com@???
X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false
Subject: Re: [bitfolk] Network issue, starting around 1819Z today
X-BeenThere: users@???
Reply-To: users@???
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
    <mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
    <mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 20:00:46 -0000



--===============1754472669==
Content-Type: multipart/signed; micalg=pgp-ripemd160;
    protocol="application/pgp-signature"; boundary="LtN0I0gXzHUftVCi"
Content-Disposition: inline



--LtN0I0gXzHUftVCi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

On Tue, Jun 12, 2012 at 07:24:28PM +0000, Andy Smith wrote:
> As of aprox 1819Z there have been network problems at our
> colo/transit provider, resulting in high packet loss. This is not
> specific to Bitfolk; it affects all customers that I am aware of.


This was fixed at approximately 1935Z. Initial diagnosis is an
inter-switch link which started spewing errors. That is rather
unusual since you would normally expect it to work or not. When the
link was shutdown, things started to return to normality.

There is no expectation that the problem will return, but there will
be more information to come as to the actual cause.

Thanks for your patience.

Cheers,
Andy

--=20
http://bitfolk.com/ -- No-nonsense VPS hosting

--LtN0I0gXzHUftVCi
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAk/Xn+gACgkQIJm2TL8VSQuzygCgtIo2xd6eTeB01TkqT2baUQ9y
xZIAniwATPtCoYEM2VFNUyDrqPsjgGJe
=1eM3
-----END PGP SIGNATURE-----

--LtN0I0gXzHUftVCi--


--===============1754472669==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
announce mailing list
announce@???
https://lists.bitfolk.com/mailman/listinfo/announce

--===============1754472669==--



From announce-bounces+users=lists.bitfolk.com@??? Wed Jun 13 08:44:18 2012
Received: from localhost ([127.0.0.1] helo=bitfolk.com)
    by mail.bitfolk.com with esmtp (Exim 4.72) (envelope-from
    <announce-bounces+users=lists.bitfolk.com@???>)
    id 1SejBa-0004rU-0d
    for users@???; Wed, 13 Jun 2012 08:44:18 +0000
Received: from andy by mail.bitfolk.com with local (Exim 4.72)
    (envelope-from <andy@???>) id 1SejBT-0004qF-Ui
    for announce@???; Wed, 13 Jun 2012 08:44:12 +0000
Date: Wed, 13 Jun 2012 08:44:11 +0000
From: Andy Smith <andy@???>
To: announce@???
Message-ID: <20120613084411.GG11695@???>
References: <20120612192428.GA11695@???>
    <20120612200040.GB11695@???>
MIME-Version: 1.0
In-Reply-To: <20120612200040.GB11695@???>
OpenPGP: id=BF15490B; url=http://strugglers.net/~andy/pubkey.asc
X-URL: http://strugglers.net/wiki/User:Andy
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Wed,
    13 Jun 2012 08:44:11 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
    spamd1.lon.bitfolk.com
X-Spam-Level: 
X-Spam-ASN: 
X-Spam-Status: No, score=-0.0 required=5.0 tests=NO_RELAYS shortcircuit=no
    autolearn=disabled version=3.3.1
X-Spam-Report: * -0.0 NO_RELAYS Informational: message was not relayed via SMTP
X-BeenThere: announce@???
X-Mailman-Version: 2.1.13
Precedence: list
Content-Type: multipart/mixed; boundary="===============1915306549=="
Sender: announce-bounces+users=lists.bitfolk.com@???
Errors-To: announce-bounces+users=lists.bitfolk.com@???
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Wed,
    13 Jun 2012 08:44:18 +0000
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: announce-bounces+users=lists.bitfolk.com@???
X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false
Subject: Re: [bitfolk] Network issue, starting around 1819Z today
X-BeenThere: users@???
Reply-To: users@???
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
    <mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/listinfo/users>,
    <mailto:users-request@lists.bitfolk.com?subject=subscribe>
X-List-Received-Date: Wed, 13 Jun 2012 08:44:18 -0000



--===============1915306549==
Content-Type: multipart/signed; micalg=pgp-ripemd160;
    protocol="application/pgp-signature"; boundary="YwTTlJgQ7QoYB9ta"
Content-Disposition: inline



--YwTTlJgQ7QoYB9ta
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jun 12, 2012 at 08:00:40PM +0000, Andy Smith wrote:
> There is no expectation that the problem will return, but there will
> be more information to come as to the actual cause.


More info from Jump:

    I'm afraid we had a period of network instability leading to
    packet loss last night, starting sometime between 19:19 BST and
    19:25 BST, and finishing at 20:34 BST.


    The root cause was a faulty pair on an ethernet cable between
    sw-tfm4-b and sw-tfm8-a, tdr on the cable from each end shows a
    problem towards the sw-tfm8-a end of Pair D:


    Interface Speed Local pair Pair length        Remote pair Pair status
    --------- ----- ---------- ------------------ ----------- -------------=
-------
    Gi0/46    auto  Pair A     N/A                N/A         Normal
                    Pair B     N/A                N/A         Normal
                    Pair C     N/A                N/A         Normal
                    Pair D     11   +/- 2  meters N/A         Impedance Mis=
matched



    Interface Speed Local pair Pair length        Remote pair Pair status
    --------- ----- ---------- ------------------ ----------- -------------=
-------
    Gi0/3     auto  Pair A     96   +/- 4  meters N/A         Normal
                    Pair B     94   +/- 4  meters N/A         Normal
                    Pair C     95   +/- 4  meters N/A         Normal
                    Pair D     81   +/- 4  meters N/A         Short


    The pair fault wasn't enough to bring the link down, just induce
    packet loss, which was sufficient to disrupt normal spanning
    tree operation and cause instability as a result of
    reconvergence.


    Once the link was manually shutdown the network returned to its
    normal state.


    I'll investigate in the morning potential ways to automatically
    error disable links that are suffering from errors like this, as
    clearly if the link had failed completely the outcome would have
    been a lot better.


    Apologies for the delay in fixing this.


Cheers,
Andy

--=20
http://bitfolk.com/ -- No-nonsense VPS hosting

--YwTTlJgQ7QoYB9ta
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEAREDAAYFAk/YUtsACgkQIJm2TL8VSQvNIQCaAjvW1aqSUpERAyvzlYWec6+a
L2cAoJ/tlfcn6Jdmss5IlT2w02syCqKg
=J+Dg
-----END PGP SIGNATURE-----

--YwTTlJgQ7QoYB9ta--


--===============191530654