Deprecated: Assigning the return value of new by reference is deprecated in /home/boomerdragon/www/boomer/blog/wp-settings.php on line 232

Deprecated: Assigning the return value of new by reference is deprecated in /home/boomerdragon/www/boomer/blog/wp-settings.php on line 234

Deprecated: Assigning the return value of new by reference is deprecated in /home/boomerdragon/www/boomer/blog/wp-settings.php on line 235

Deprecated: Assigning the return value of new by reference is deprecated in /home/boomerdragon/www/boomer/blog/wp-settings.php on line 252

Deprecated: Assigning the return value of new by reference is deprecated in /home/boomerdragon/www/boomer/blog/wp-includes/cache.php on line 35

Deprecated: Assigning the return value of new by reference is deprecated in /home/boomerdragon/www/boomer/blog/wp-includes/query.php on line 15

Deprecated: Assigning the return value of new by reference is deprecated in /home/boomerdragon/www/boomer/blog/wp-includes/theme.php on line 505
La Guarida de Boomer » IIS

Archive for the 'IIS' Category


Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 11

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 20

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 22

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 25

Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 11

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 20

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 22

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 25

Otra semana interesante…


Warning: mktime() [function.mktime]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 11

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 20

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 22

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 24

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /home/boomerdragon/www/boomer/blog/wp-includes/functions.php on line 25
Sábado, Julio 11th, 2009

Resulta que desde el sábado pasado nos han sucedido cosas muuuuuy curiosas en los servicios.

  1. El IIS de repente se “manda” con las conexiones, pasando de 50-60 a más de 3000 en unos momentos, deteniendo prácticamente el servicio y mandando el error 500.13 (IIS no puede satisfacer la petición).
  2. La base de datos estaba en modo “failover”, lo cual rebotaba conexiones en el cluster entre los diferentes miembros del mismo.
  3. Habiendo matado sesiones tanto en base de datos como en IIS, al reiniciar, de 5 sesiones brincó a cerca de 1000 nuevamente.

Todo esto sucedió el sábado.

El siguiente lunes volvió a hacer lo mismo, aunque tardamos menos en recuperar el control.

El viernes, ¡otra vez el IIS!, aunque al parecer encontré una solución con IIS 6.0, que consiste en dar de alta los diferentes sitios en Application Pools y reciclar las conexiones, ya sea por tiempo, por cantidad de conexiones o manualmente. En este caso, en lugar de 2 horas, se recuperó en un par de minutos (después de haber detectado el caso, claro).

Espero que no vuelva a suceder, pero si a alguien le es útil esto, por favor háganmelo saber.