emerion Blog » Technical http://www.emerion.com/blog.com emerion Thu, 24 Jun 2010 11:55:26 +0000 http://wordpress.org/?v=2.9.2 en hourly 1 Update of Perl Modules http://www.emerion.com/blog.com/2009/06/22/update-of-perl-modules/ http://www.emerion.com/blog.com/2009/06/22/update-of-perl-modules/#comments Mon, 22 Jun 2009 10:40:12 +0000 emerion http://www.emerion.com/blog.com/?p=152 During our regular software maintenance we updated the following RPM packages on our web cluster:

Package Old Version New Version
perl-Term-ReadLine-Gnu 1.17a-1.el3.rf 1.19-1.el3.rf
perl-Time-Piece 1.13-1.el3.rf 1.14-1.el3.rf
perl-XML-NamespaceSupport 1.09-1.1.el3.rf 1.10-1.el3.rf
perl-XML-SAX 0.16-1.el3.rf 0.96-1.el3.rf
perl-version 0.74-1.el3.rf 0.76-1.el3.rf

 

]]> http://www.emerion.com/blog.com/2009/06/22/update-of-perl-modules/feed/ 0 Wrong AT&T BGP Routing set emerion net out of service http://www.emerion.com/blog.com/2009/04/13/wrong-att-bgp-routing/ http://www.emerion.com/blog.com/2009/04/13/wrong-att-bgp-routing/#comments Mon, 13 Apr 2009 18:48:25 +0000 emerion http://www.emerion.com/blog.com/?p=32 NetworkOn Easter Monday, 04/13/2009, 4.20 pm suddenly all services served by the ip range 212.69.178 were out of order. The emerion technicians found out, that the international provider AT&T announced our ip range by mistake.

The result of such a failure, which one is not in the control of emerion, is fatal: All requests to the webserver do not resolve, because the routes are wrong and no web site is reachable.

A solution is pretty hard, because the responsible AT&T technicians must be reached in a short time in such a huge company. It’s not that easy to get in contact with the right department.

Together with the upstream provider of emerion we could get the responsible technician at AT&T after calling a couple of hours with AT&T. They deleted the wrong announced routes and all services of emerion were recovered again since 7.05 pm.

]]> http://www.emerion.com/blog.com/2009/04/13/wrong-att-bgp-routing/feed/ 0