Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ppgac.org/current/public/wp-settings.php on line 232

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ppgac.org/current/public/wp-settings.php on line 234

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ppgac.org/current/public/wp-settings.php on line 235

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ppgac.org/current/public/wp-settings.php on line 252

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ppgac.org/current/public/wp-includes/cache.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ppgac.org/current/public/wp-includes/query.php on line 15

Deprecated: Assigning the return value of new by reference is deprecated in /var/www/ppgac.org/current/public/wp-includes/theme.php on line 505

Deprecated: Function eregi() is deprecated in /var/www/ppgac.org/current/public/wp-content/plugins/wordspew/wordspew.php on line 75

Deprecated: Function eregi() is deprecated in /var/www/ppgac.org/current/public/wp-content/plugins/ppgac-urss/ppgac-urss.php on line 190
ppgac
une tranche de slip en guise de salamie

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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/wp-includes/functions.php on line 25

Les serveur sur lequel se trouve ppgac (et plein d’autres trucs d’ailleurs) s’appelle Helios, c’est pas un nom super originale mais ça fait bien longtemps qu’ils s’appelle comme ça et en pensant à tous les fichiers de configuration que je devrais changer si je voulais le renommer, et bien disons que je me sens plus que prêt à garder le nom Helios.

Bon, je vous décris la scène, je suis en train de regarder un épisode de Dexter, le fichier se trouve sur un des disques de Helios (pas encore transféré vers Deadalus, mon serveur de fichiers, depuis le répertoire de récéption de Helios), et tout d’un coup Dexter se bloque. Je me dis que ça doit juste être quelques frames perdus, quelques ko du fichier qui ont été corrompus.

En faite Helios avait arrêté de répondre complètement.

Un petit coup de KVM (un boîtier permetant de brancher plusieurs ordis sur un écran/souris/clavier) et hop, un écran noir pour Helios. Je rédémarres. Rien. Là je commences à avoir peur, je me dis que finalement une pièce a grillé alors j’ouvres le boîter de Helios pour voir s’il y a des traces noires ou des étincelles en allumant la machine. Rien.

Helios tourne sous Debian linux et est la machine avec la configuration logicielle la plus avancée de mes serveurs, une des choses que j’ai pris le temps de configurer c’est lm_sensors, la méthode de lecture des sondes de température placés dans la machine. Chaque 5min ces sondes sont examinés et les résultats sont écrits dans un fichier qui lui est exporté vers un logiciel qui s’appelle Splunk qui se trouve sur Deadalus. Ceci me permet d’examiner les derniers instants de Helios même si je n’arrives pas à l’allumer, il me suffit de vérifier le contenu dans Splunk sur Deadalus.

La température ne variait pas tant que ça et n’était pas trop élévée, pas assez pour endommager la machine en tout cas. Bon.

Vu que la machine ne lançait même pas le BIOS, ça ne pouvait pas être un problème logiciel (Bootloader, table des partitions ou autre) ni un problème avec la mémoire, les disques durs ou la carte graphique car justement, le BIOS vérifie tout ça lors du POST (Power On Self Test). ça devait donc être un problème matérielle, j’ai pensé à une microcoupure, mais j’ai des parasurtensioneurs pour éviter ça, peut être carrément une coupure? Les lumières n’ont même pas clignotés alors non, c’était pas ça.

En faite, le câble de la carte graphique était un tout petit peu tendu et ça avait légérement déplacé la carte graphique créant un court circuit sur la carte mère. Il m’a suffit de le remettre à sa place et tadaa, nous revoilà.

Petite anécdote de résolution de problème tout bête mais auquel on ne pense pas immédiatement, il m’arrivait tout le temps ce genre de merde quand je travaillais à l’hôpital d’ailleurs.

2 réponses

commenter |
Warning: strtotime() [function.strtotime]: 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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/wp-includes/link-template.php on line 53

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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/wp-includes/link-template.php on line 65
souscrire
  • tartifwarrior a dit:

    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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/wp-includes/functions.php on line 25
    March 1st, 2007 |

    heureusement que tu n’a pas fait comme moi pour reparé mon casque-micro, je le balance tres fort par terre et après il remarche.

  • vinz a dit:

    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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/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 'UTC' for 'GMT/0.0/no DST' instead in /var/www/ppgac.org/current/public/wp-includes/functions.php on line 25
    March 1st, 2007 |

    comme quoi t’es système marchent bien, quand t’as un problème, c’est juste un cable qui se débranche…moi quand j’ai un problème, c’est le disque dur qui grille ou le ventirad mort :D

laisser une réponse

/dev/geek aaaaaaaaaaaah acturis ajax alcool amies amis amour anniversaire année appart art au debut beaufs berlin biere blague boire bonheur bouffe boulot cest ce qui est trop bien justement. chinois chiottes cigarettes cinema claire clip colère crime Cuisine culture culture geek curieux debian deguisement dementification dessin dns douche drogue drole dépassé déprime ebay education egocentrisme email epita et puis merde à la fin facebook Faille Spatio Temporelle famille film frankfurt fucking drugs fumeurs futur fête garden party gens gens bêtes global warming gné Gueule de bois guinness haine helios histoire vraie humeur humour icart idiot idée Imperial College inquiétant insa internet javascript la classe la merde qui nous arrive La vie le bonheur le sarcasme et le reste.. LHominoïde linux london Lyon manky mankyblahblah meh musique nimporte quoi Néant et Grand Enervement oshannon paris peinture perpignan Petit personnage grotesque avec croix petite histoire photo php poissons politiqixsme politique potossssssssses pour tous ppgac reiser4 retour rien rigolades rss réseau rêves San francisco sculpture sexe ski soirée Sorede sorties spam strasbourg sultanat du götistan surprises tartifisme tartifwarrior the life travaux manuel la truelle troupilon troupilonnement truc fou ultrakiff underground vacances Very deep inside vide video vie vinz voyage voyages wordpress Yet another victim of my pointless rage! youtube zombies émilie étude étudiant