{"id":84108,"date":"2020-06-05T07:42:44","date_gmt":"2020-06-05T05:42:44","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/tushit-li-servera-esli-zagorelsya-smouk-test-dataczentra"},"modified":"2020-06-05T07:42:44","modified_gmt":"2020-06-05T05:42:44","slug":"tushit-li-servera-esli-zagorelsya-smouk-test-dataczentra","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/tushit-li-servera-esli-zagorelsya-smouk-test-dataczentra","title":{"rendered":"A duhet t\u00eb \u201endaloni\u201c serverat n\u00ebse testi i tymit t\u00eb data qendr\u00ebs d\u00ebshtoi?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\u00c7far\u00eb do t\u00eb ndiheshit n\u00ebse n\u00eb nj\u00eb dit\u00eb t\u00eb bukur vere data-qendra me pajisjet tuaja do t\u00eb dukej k\u00ebshtu?<\/p>\n

\"A
\n
\nP\u00ebrsh\u00ebndetje t\u00eb gjith\u00ebve! Un\u00eb quhem Dmitri Samsonov, dhe punoj si administrator kryesor i sistemeve n\u00eb \u201cOdnoklassniki<\/a><\/noindex>\u201d. N\u00eb fotografi \u00ebsht\u00eb nj\u00eb nga kat\u00ebr data-qendrat ku jan\u00eb vendosur pajisjet q\u00eb mb\u00ebshtesin projektin ton\u00eb. Pas k\u00ebtyre mureve ndodhen rreth 4,000 nj\u00ebsi pajisjeje: server\u00eb, sistem dep\u00ebrtimi t\u00eb t\u00eb dh\u00ebnave, pajisje rrjeti etj. - pothuajse \u2153 e gjith\u00eb pajisjeve tona.
\nShumica e server\u00ebve jan\u00eb me Linux. Ka gjithashtu disa dhjet\u00ebra server\u00eb me Windows (MS SQL) - trash\u00ebgimia jon\u00eb, nga e cila po heqim dor\u00eb gradualisht p\u00ebr vite me radh\u00eb.
\nK\u00ebshtu, m\u00eb 5 Qershor 2019, n\u00eb 14:35 inxhinier\u00ebt e nj\u00eb prej data-qendrave tona raportuan nj\u00eb alarm zjarri.
\n<\/a><\/noindex><\/p>\n

Mohim<\/h4>\n

\n14:45. Incidentet e vogla t\u00eb tymit n\u00eb data-qendra ndodhin m\u00eb shpesh se sa duket. T\u00eb dh\u00ebnat brenda sallave ishin n\u00eb normalitet, k\u00ebshtu q\u00eb reagimi yn\u00eb i par\u00eb ishte relativisht i qet\u00eb: vendos\u00ebm nj\u00eb ndalim p\u00ebr punime n\u00eb prodhim, dometh\u00ebn\u00eb p\u00ebr \u00e7do ndryshim konfiguracioni, p\u00ebr nxjerrjen e versioneve t\u00eb reja etj., p\u00ebrve\u00e7 pun\u00ebve q\u00eb lidhen me rregullimin e ndonj\u00eb gj\u00ebje.<\/p>\n

Ngash\u00ebrim<\/h4>\n

\nA keni provuar ndonj\u00ebher\u00eb t\u00eb pyesni zjarrfik\u00ebsit se n\u00eb cilin vend konkret n\u00eb \u00e7ati ndodhi zjarri, ose t\u00eb shkoni vet\u00eb n\u00eb \u00e7atin e zjarrit p\u00ebr t\u00eb vler\u00ebsuar situat\u00ebn? Sa do t\u00eb ishte shkalla e besimit n\u00eb informacionin e marr\u00eb p\u00ebrmes pes\u00eb personave?<\/p>\n

14:50. P\u00ebrfituam informacion se zjarri po shum\u00ebzohej me sistemin e ftohjes<\/b>. Por, a do t\u00eb arrij\u00eb? Administrator i sistemit n\u00eb turn po heq trafikun e jasht\u00ebm nga frontet e k\u00ebsaj data-qendre.<\/p>\n

N\u00eb k\u00ebt\u00eb moment, frontet e t\u00eb gjith\u00eb sh\u00ebrbimeve tona jan\u00eb t\u00eb kopjuara n\u00eb tri data-qendra, p\u00ebrdoret balancimi n\u00eb nivel DNS, i cili lejon q\u00eb t\u00eb hiqen adresat e nj\u00eb data-qendre nga DNS, duke mbrojtur k\u00ebshtu p\u00ebrdoruesit nga probleme t\u00eb mundshme me qasjen n\u00eb sh\u00ebrbime. N\u00eb rast se ndodhin probleme n\u00eb data-qend\u00ebr, ajo del automatikisht nga rotacioni. P\u00ebr m\u00eb shum\u00eb informacion, mund t\u00eb lexoni k\u00ebtu: Balancimi i ngarkes\u00ebs dhe q\u00ebndrueshm\u00ebria n\u00eb \u201cOdnoklassniki\u201d.<\/a><\/noindex><\/p><\/blockquote>\n

\nZjarri deri tani nuk na ka ndikuar - as p\u00ebrdoruesit, as pajisjet nuk jan\u00eb d\u00ebmtuar. A \u00ebsht\u00eb kjo nj\u00eb aksident? Seksioni i par\u00eb i dokumentit \"Plani i veprimit n\u00eb rast aksidentesh\" jep p\u00ebrcaktimin e konceptit \"Aksident\", dhe seksioni p\u00ebrfundon k\u00ebshtu:
\n\u00abN\u00ebse ka dyshime, a \u00ebsht\u00eb aksident apo jo, at\u00ebher\u00eb \u00ebsht\u00eb aksident!<\/u>\u00bb<\/b><\/p>\n

14:53. Em\u00ebrohet koordinatori i aksidentit.<\/p>\n

Koordinatori \u00ebsht\u00eb personi q\u00eb kontrollon komunikimin midis t\u00eb gjith\u00eb pjes\u00ebmarr\u00ebsve, vler\u00ebson shkall\u00ebn e aksidentit, p\u00ebrdor \"Planin e veprimit n\u00eb rast aksidentesh\", angazhon personelin e nevojsh\u00ebm, kontrollon p\u00ebrfundimin e riparimeve, m\u00eb e r\u00ebnd\u00ebsishmja - delegon \u00e7do detyr\u00eb. Me fjal\u00eb t\u00eb tjera, ky \u00ebsht\u00eb personi q\u00eb menaxhon t\u00eb gjith\u00eb procesin e eliminimit t\u00eb aksidentit.<\/p><\/blockquote>\n

<\/p>\n

Tregti<\/h4>\n

\n15:01. Fillojm\u00eb t\u00eb fikim server\u00ebt q\u00eb nuk jan\u00eb t\u00eb lidhur me prodhimin.
\n15:03. Korrektisht fikim t\u00eb gjitha sh\u00ebrbimet rezerv\u00eb.
\nK\u00ebtu p\u00ebrfshihen jo vet\u00ebm frontet (n\u00eb t\u00eb cilat n\u00eb k\u00ebt\u00eb moment p\u00ebrdoruesit nuk po hyjn\u00eb m\u00eb) dhe sh\u00ebrbimet ndihm\u00ebse t\u00eb tyre (logjika e biznesit, cache-et etj.), por edhe bazat e ndryshme t\u00eb t\u00eb dh\u00ebnave me faktor replikimi 2 dhe m\u00eb shum\u00eb (Cassandra<\/a><\/noindex>, depozit\u00eb t\u00eb t\u00eb dh\u00ebnave t\u00eb binar\u00ebve<\/a><\/noindex>, depozit\u00eb t\u00eb ftoht\u00eb<\/a><\/noindex>, NewSQL<\/a><\/noindex> etj.).
\n15:06. U njoftua se zjarri po k\u00ebrc\u00ebnon nj\u00eb nga sallat e data-qendr\u00ebs.<\/b> N\u00eb k\u00ebt\u00eb sall\u00eb nuk kemi pajisje, por fakti q\u00eb zjarri mund t\u00eb kaloj\u00eb nga \u00e7atia n\u00eb sallat, ndryshon ndjesh\u00ebm situat\u00ebn e ngjarjeve.
\n(M\u00eb von\u00eb doli se nuk kishte k\u00ebrc\u00ebnim fizik p\u00ebr sall\u00ebn sepse ajo ishte hermetikisht e izoluara nga \u00e7atia. K\u00ebrc\u00ebnimi ishte vet\u00ebm p\u00ebr sistemin e ftohjes s\u00eb k\u00ebsaj salle.)
\n15:07. Lejojm\u00eb ekzekutimin e komandave n\u00eb server\u00eb n\u00eb nj\u00eb rit\u00ebm t\u00eb p\u00ebrshpejtuar pa kontrollime t\u00eb m\u00ebtejshme (pa kalkulatorin ton\u00eb t\u00eb dashur<\/a><\/noindex>).
\n15:08. Temperatura n\u00eb sallat \u00ebsht\u00eb brenda norm\u00ebs.
\n15:12. Nj\u00eb rritje e temperatur\u00ebs \u00ebsht\u00eb fikur n\u00eb sallat.<\/b>
\n15:13. M\u00eb shum\u00eb se gjysma e server\u00ebve n\u00eb data-qend\u00ebr jan\u00eb fikur. Po vazhdojm\u00eb.
\n15:16. \u00cbsht\u00eb marr\u00eb vendim p\u00ebr fikjen e gjith\u00eb pajisjeve.
\n15:21. Fillojm\u00eb t\u00eb fikim energjin\u00eb n\u00eb server\u00ebt pa shtes\u00eb t\u00eb sakt\u00eb t\u00eb aplikacionit dhe sistemit operativ.
\n15:23. Caktohet nj\u00eb grup p\u00ebrgjegj\u00ebs p\u00ebr MS SQL (jan\u00eb t\u00eb pak\u00ebt, var\u00ebsia e sh\u00ebrbimeve nga ta nuk \u00ebsht\u00eb e madhe, por procedura e rikthimit n\u00eb funksionalitet merr m\u00eb shum\u00eb koh\u00eb dhe \u00ebsht\u00eb m\u00eb e komplikuar se, p\u00ebr shembull, p\u00ebr Cassandra).<\/p>\n

Depresion<\/h4>\n

\n15:25. U njoftua se energjia \u00ebsht\u00eb fikur n\u00eb kat\u00ebr sallat nga 16 (Nr. 6, 7, 8, 9).<\/b> N\u00eb sallat 7 dhe 8 ndodhet pajisja jon\u00eb. Nuk kemi informacion p\u00ebr dy sallat tona (Nr. 1 dhe 3).
\nZakonisht gjat\u00eb zjarreve energjia elektrik fiket menj\u00ebher\u00eb, por n\u00eb k\u00ebt\u00eb rast, fal\u00eb pun\u00ebs t\u00eb koordinuar t\u00eb zjarrfik\u00ebsve dhe personelit teknik t\u00eb data-qendr\u00ebs, ajo nuk u fik n\u00eb t\u00eb gjitha sallat menj\u00ebher\u00eb, por sipas nevoj\u00ebs.
\n(M\u00eb von\u00eb doli se energjia n\u00eb sallat 8 dhe 9 nuk u fik.)
\n15:28. Fillojm\u00eb bazat MS SQL nga kopjet rezerv\u00eb n\u00eb qendrat e tjera t\u00eb t\u00eb dh\u00ebnave.
\nSa koh\u00eb do t\u00eb k\u00ebrkohet p\u00ebr k\u00ebt\u00eb? A do t\u00eb mjaftoj\u00eb kapaciteti i rrjetit gjat\u00eb t\u00ebr\u00eb rrug\u00ebs?
\n15:37. \u00cbsht\u00eb regjistruar nd\u00ebrprerja e disa segmenteve t\u00eb rrjetit.<\/b>
\nMenaxhimi dhe rrjeti i prodhimit jan\u00eb fizikisht t\u00eb ndara nga nj\u00ebra-tjetra. N\u00ebse rrjeti i prodhimit \u00ebsht\u00eb i aksesuesh\u00ebm, mund t\u00eb hyni n\u00eb server, t\u00eb ndaloni aplikacionin dhe t\u00eb fikni OS-n\u00eb. N\u00ebse nuk \u00ebsht\u00eb i aksesuesh\u00ebm, mund t\u00eb hyni p\u00ebrmes IPMI, t\u00eb ndaloni aplikacionin dhe t\u00eb fikni OS-n\u00eb. N\u00ebse asnj\u00eb nga rrjetet nuk \u00ebsht\u00eb e aksesueshme, nuk mund t\u00eb b\u00ebni asgj\u00eb. \"Faleminderit, kapiten!\" do mendoni.
\n\"Dhe gjithashtu, duket se ka shum\u00eb zhurm\u00eb\", mund t\u00eb mendoni gjithashtu.
\nE gjith\u00eb \u00e7\u00ebshtja \u00ebsht\u00eb se edhe pa zjarr, server\u00ebt gjenerojn\u00eb nj\u00eb sasi t\u00eb madhe marr\u00ebzit k\u00ebtu. M\u00eb sakt\u00eb, kur ka ftohje, ata gjenerojn\u00eb nxeht\u00ebsi, dhe kur nuk ka, ata krijojn\u00eb nj\u00eb sk\u00ebnderb p\u00ebr t\u00eb cilin, n\u00eb rastin m\u00eb t\u00eb mir\u00eb, do t\u00eb shkrijn\u00eb nj\u00eb pjes\u00eb t\u00eb pajisjeve dhe do t\u00eb fiknin nj\u00eb pjes\u00eb tjet\u00ebr, e n\u00eb rastin m\u00eb t\u00eb keq\u2026 do t\u00eb shkaktojn\u00eb nj\u00eb zjarr brenda sall\u00ebs, q\u00eb garanton shkat\u00ebrrimin e gjith\u00e7kaje.<\/p>\n

\"A
\n
\n15:39. Regjistrimi i problemeve me baz\u00ebn conf.<\/p>\n

Baza conf \u00ebsht\u00eb backend p\u00ebr sh\u00ebrbimin e t\u00eb nj\u00ebjtit em\u00ebr, i cili p\u00ebrdoret nga aplikacionet e prodhimit p\u00ebr t\u00eb ndryshuar me shpejt\u00ebsi konfigurimet. Pa k\u00ebt\u00eb baz\u00eb nuk mund t\u00eb menaxhojm\u00eb funksionimin e portalit, por portali mund t\u00eb funksionoj\u00eb gjithsesi.<\/p><\/blockquote>\n

\n15:41. Sensor\u00ebt e temperatur\u00ebs n\u00eb pajisjet e rrjetit Core regjistrojn\u00eb lexime af\u00ebr kufijve t\u00eb lejuar. Kjo \u00ebsht\u00eb nj\u00eb kut q\u00eb z\u00eb nj\u00eb raft dhe siguron funksionimin e t\u00eb gjitha rrjeteve brenda qendres s\u00eb t\u00eb dh\u00ebnave.<\/p>\n

\"A
\n
\n15:42. Issue tracker dhe wiki t\u00eb paarritshme, kalojm\u00eb n\u00eb standby.
\nKjo nuk \u00ebsht\u00eb prodhim, por n\u00eb rast emergjence, disponueshm\u00ebria e \u00e7do baze njohurie mund t\u00eb jet\u00eb kritike.
\n15:50. Nj\u00eb nga sistemet e monitorimit u fik.
\nKa disa prej tyre, dhe ata p\u00ebrgjigjen p\u00ebr aspekte t\u00eb ndryshme t\u00eb funksionimit t\u00eb sh\u00ebrbimeve. Disa prej tyre jan\u00eb t\u00eb konfigurara p\u00ebr t\u00eb punuar autonomisht brenda \u00e7do qendre t\u00eb t\u00eb dh\u00ebnave (dmth., ato monitorojn\u00eb vet\u00ebm qendr\u00ebn e tyre t\u00eb t\u00eb dh\u00ebnave), t\u00eb tjerat p\u00ebrb\u00ebhen nga komponent\u00eb t\u00eb shp\u00ebrndar\u00eb, t\u00eb cil\u00ebt e p\u00ebrballojn\u00eb humbjen e \u00e7do qendre t\u00eb t\u00eb dh\u00ebnave.
\nN\u00eb k\u00ebt\u00eb rast, ka ndaluar funksionimi i sistem\u00ebs s\u00eb zbulimit t\u00eb anomalive t\u00eb logjik\u00ebs s\u00eb biznesit<\/a><\/noindex>, e cila funksionon n\u00eb m\u00ebnyr\u00eb master-standby. Kalojm\u00eb n\u00eb standby.<\/p>\n

Pranimi<\/h4>\n

\n15:51. N\u00ebp\u00ebrmjet IPMI, fik\u00ebm t\u00eb gjith\u00eb server\u00ebt pa mbyllje t\u00eb sakt\u00eb, p\u00ebrve\u00e7 MS SQL.
\nJeni t\u00eb gatsh\u00ebm p\u00ebr menaxhimin masiv t\u00eb server\u00ebve p\u00ebrmes IPMI n\u00eb rast nevoje?<\/p>\n

Ky \u00ebsht\u00eb momenti kur shp\u00ebtimi i pajisjeve n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave n\u00eb k\u00ebt\u00eb faz\u00eb \u00ebsht\u00eb p\u00ebrfunduar. Gjith\u00e7ka q\u00eb mund t\u00eb b\u00ebhej, \u00ebsht\u00eb b\u00ebr\u00eb. Disa koleg\u00eb mund t\u00eb pushojn\u00eb.<\/i>
\n16:13. Kemi marr\u00eb informacion se tubat e freonit n\u00eb \u00e7ati plasarit\u00ebn nga klimatik\u00ebt \u2014 kjo do t\u00eb vonoj\u00eb nisjen e qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave pas eliminimit t\u00eb zjarrit.<\/b>
\n16:19. Sipas t\u00eb dh\u00ebnave t\u00eb marra nga stafi teknik i qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave, ka ndaluar rritja e temperatur\u00ebs n\u00eb sallat.
\n17:10. Rind\u00ebrtuam funksionimin e baz\u00ebs conf. Tani mund t\u00eb ndryshojm\u00eb konfigurimet e aplikacioneve.
\nPse \u00ebsht\u00eb kaq e r\u00ebnd\u00ebsishme, n\u00ebse gjith\u00e7ka \u00ebsht\u00eb e q\u00ebndrueshme dhe funksionon edhe pa nj\u00eb qend\u00ebr t\u00eb dh\u00ebnash?
\nS\u00eb pari, jo gjith\u00e7ka \u00ebsht\u00eb e q\u00ebndrueshme. Ka sh\u00ebrbime t\u00eb ndryshme dyt\u00ebsore, t\u00eb cilat p\u00ebr momentin nuk e p\u00ebrballojn\u00eb mjaftuesh\u00ebm munges\u00ebn e nj\u00eb qendre t\u00eb t\u00eb dh\u00ebnave, dhe ka baza n\u00eb modalitetin master-standby. Mund\u00ebsia p\u00ebr t\u00eb menaxhuar konfigurimet lejon t\u00eb b\u00ebhen t\u00eb gjitha t\u00eb nevojshmet p\u00ebr t\u00eb minimizuar ndikimin e pasojave t\u00eb emergjenc\u00ebs mbi p\u00ebrdoruesit, edhe n\u00eb kushtet m\u00eb t\u00eb v\u00ebshtira.
\nS\u00eb dyti, b\u00ebhet e qart\u00eb se brenda disa or\u00ebsh, funksionimi i qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave nuk do t\u00eb rifilloj\u00eb plot\u00ebsisht, prandaj ishte e nevojshme t\u00eb merreshin masa p\u00ebr t\u00eb parandaluar q\u00eb mungesa e gjat\u00eb e replika t\u00eb sillte nd\u00ebrlikime t\u00eb tjera si mbingarkesa e disqeve n\u00eb qendrat e tjera t\u00eb t\u00eb dh\u00ebnave.
\n17:29. Koha p\u00ebr pic\u00eb! Ne kemi njer\u00ebz q\u00eb punojn\u00eb, jo robot\u00eb.<\/p>\n

\"A
\n<\/p>\n

Rehabilitimi<\/h4>\n

\n18:02. N\u00eb sallat \u2116\u21168 (tona), 9, 10 dhe 11 temperatura u stabilizua. N\u00eb nj\u00ebr\u00ebn nga ato q\u00eb mbeten t\u00eb fikura (\u21167), ndodhet pajisja jon\u00eb dhe temperatura aty vazhdon t\u00eb rritet.
\n18:31. U dha miratimi p\u00ebr fillimin e pajisjeve n\u00eb sallat \u2116\u21161 dhe 3 \u2014 k\u00ebto salla nuk u prek\u00ebn nga zjarri.<\/p>\n

P\u00ebr momentin po fillohet nisja e server\u00ebve n\u00eb sallat \u2116\u21161, 3, 8, duke filluar nga ato m\u00eb kritike. Po kontrollohet sakt\u00ebsia e funksionimit t\u00eb t\u00eb gjith\u00eb sh\u00ebrbimeve t\u00eb hapura. Ka ende probleme me sall\u00ebn \u21167.<\/i><\/p>\n

18:44. Stafi teknik i qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave zbuloi se n\u00eb sall\u00ebn \u21167 (ku ndodhet vet\u00ebm pajisja jon\u00eb) shum\u00eb servera nuk jan\u00eb fikur. Sipas t\u00eb dh\u00ebnave tona, aty mbeten t\u00eb fikura 26 server\u00eb. Pas nj\u00eb kontrolli t\u00eb dyt\u00eb gjejm\u00eb 58 servera.
\n20:18. Stafi teknik i qendr\u00ebs s\u00eb t\u00eb dh\u00ebnave po ajros ajrin n\u00eb sall\u00ebn pa klimatik\u00eb p\u00ebrmes kanaleve mobile t\u00eb ajrosjes, t\u00eb cilat jan\u00eb vendosur p\u00ebrmes korridoreve.
\n23:08. Ekipi ka l\u00ebshuar administrat\u00ebn e par\u00eb p\u00ebr n\u00eb sht\u00ebpi. Disa prej nesh duhet t\u00eb flen\u00eb nat\u00ebn p\u00ebr t\u00eb vazhduar pun\u00ebn nes\u00ebr. P\u00ebr m\u00eb tep\u00ebr, l\u00ebshojm\u00eb edhe disa administrat\u00eb dhe zhvillues.
\n02:56. Aktivizuam gjith\u00e7ka q\u00eb mund t\u00eb aktivizohej. Po b\u00ebjm\u00eb nj\u00eb kontroll t\u00eb gjer\u00eb t\u00eb t\u00eb gjitha sh\u00ebrbimeve me teste automatike.<\/p>\n

\"A
\n
\n03:02. Klimatizimi n\u00eb sall\u00ebn e fundit, sall\u00ebn 7, \u00ebsht\u00eb rikuperuar.
\n03:36. Aktivizuam frontet n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave n\u00eb rotacionin e DNS. Nga ky moment, ka filluar t\u00eb vij\u00eb trafiku i p\u00ebrdoruesve.
\nPo l\u00ebshojm\u00eb shumic\u00ebn e ekipit t\u00eb administrator\u00ebve p\u00ebr n\u00eb sht\u00ebpi. Por disa njer\u00ebz mbeten.<\/p>\n

Nj\u00eb pyetje e vog\u00ebl:
\nP: \u00c7far\u00eb ndodhi nga ora 18:31 deri n\u00eb 02:56?
\nP: Sipas \"Planit t\u00eb Veprimit n\u00eb Rast t\u00eb Fatkeq\u00ebsive\", ne aktivizojm\u00eb t\u00eb gjitha sh\u00ebrbimet, duke filluar nga ato m\u00eb t\u00eb r\u00ebnd\u00ebsishmet. N\u00eb k\u00ebt\u00eb koh\u00eb, koordinatori n\u00eb chat jep sh\u00ebrbimin nj\u00eb administratori t\u00eb lir\u00eb, i cili kontrollon n\u00ebse OS dhe aplikacioni jan\u00eb aktivizuar, n\u00ebse ka ndonj\u00eb gabim, dhe n\u00ebse treguesit jan\u00eb n\u00eb normalitet. Pas p\u00ebrfundimit t\u00eb aktivizimit, ai njofton n\u00eb chat se \u00ebsht\u00eb i lir\u00eb dhe merr nga koordinatori nj\u00eb sh\u00ebrbim t\u00eb ri.
\nProcesi ngadal\u00ebsohet gjithashtu nga hardueri i prishur. Edhe n\u00ebse ndalimi i OS dhe fikja e server\u00ebve jan\u00eb realizuar si\u00e7 duhet, disa server\u00eb nuk rikuperohen p\u00ebr shkak t\u00eb disqeve, memories, ose shasis\u00eb q\u00eb papritur kan\u00eb d\u00ebshtuar. N\u00eb rastin e humbjes s\u00eb furnizimit me energji, p\u00ebrqindja e d\u00ebshtimeve rritet.
\nP: Pse nuk mund ta aktivizoni gjith\u00e7ka nj\u00ebher\u00ebsh dhe pastaj t\u00eb riparoni at\u00eb q\u00eb del n\u00eb monitorim?
\nP: Nd\u00ebrsa k\u00ebrkesa \u00ebsht\u00eb: Gjith\u00e7ka duhet b\u00ebr\u00eb gradualisht, sepse ka var\u00ebsi mes sh\u00ebrbimeve. P\u00ebr m\u00eb tep\u00ebr, gjith\u00e7ka duhet kontrolluar menj\u00ebher\u00eb, pa pritur monitorimin \u2014 sepse \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb merren me problemet menj\u00ebher\u00eb, sesa t\u00eb pritet p\u00ebr t\u2019u agravuar.<\/p><\/blockquote>\n

\n7:40. Administratori i fundit (koordinatori) ka shkuar p\u00ebr t\u00eb fjetur. Pun\u00ebt e dit\u00ebs s\u00eb par\u00eb jan\u00eb p\u00ebrfunduar.
\n8:09. Zhvilluesit e par\u00eb, inxhinier\u00ebt n\u00eb qendrat e t\u00eb dh\u00ebnave dhe administrator\u00ebt (p\u00ebrfshir\u00eb koordinatori t\u00eb ri) kan\u00eb filluar pun\u00ebn e rikuperimit.
\n09:37. Filluam t\u00eb hapim sall\u00ebn num\u00ebr 7 (t\u00eb fundit).
\nN\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb, vazhdojm\u00eb t\u00eb rikuperojm\u00eb at\u00eb q\u00eb nuk e p\u00ebrfunduam n\u00eb sallat e tjera: z\u00ebvend\u00ebsimi i disqeve\/memories\/server\u00ebve, riparimi i gjith\u00e7kaje q\u00eb \u201cdigjet\u201d n\u00eb monitorim, rikthimi i roleve n\u00eb skemat master-standby dhe gj\u00ebra t\u00eb tjera, t\u00eb cilat megjithat\u00eb jan\u00eb mjaft t\u00eb shumta.
\n17:08. Lejojm\u00eb t\u00eb gjitha pun\u00ebt standarde me prodhimin.
\n21:45. Pun\u00ebt e dit\u00ebs s\u00eb dyt\u00eb jan\u00eb p\u00ebrfunduar.
\n09:45. Sot \u00ebsht\u00eb e premte. N\u00eb monitorim ende ka shum\u00eb probleme t\u00eb vogla. Fundjav\u00ebn po vjen, t\u00eb gjith\u00ebve u p\u00eblqen t\u00eb pushojn\u00eb. Po vazhdojm\u00eb t\u00eb riparojm\u00eb masivisht gjith\u00e7ka q\u00eb mundet. Detyrat standarde t\u00eb administrator\u00ebve q\u00eb mund t\u00eb ishin shtyr\u00eb, jan\u00eb shtyr\u00eb. Koordinatori \u00ebsht\u00eb i ri.
\n15:40. Papritur, gjysma e stack-ut t\u00eb pajisjeve rrjetike ka rikonfiguruar n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave TJET\u00cbR. E hoq\u00ebm nga rotacioni frontet p\u00ebr t\u00eb minimizuar rreziqet. Efekti p\u00ebr p\u00ebrdoruesit nuk ka qen\u00eb prezent. M\u00eb von\u00eb doli se kjo ishte nj\u00eb shasi e prishur. Koordinatori punon me riparimin e dy fatkeq\u00ebsive nj\u00ebkoh\u00ebsisht.
\n17:17. Rrjeti n\u00eb qendr\u00ebn e t\u00eb dh\u00ebnave TJET\u00cbR \u00ebsht\u00eb rikuperuar, gjith\u00e7ka \u00ebsht\u00eb kontrolluar. Qendra e t\u00eb dh\u00ebnave \u00ebsht\u00eb kthyer n\u00eb rotacion.
\n18:29. Pun\u00ebt e dit\u00ebs s\u00eb tret\u00eb dhe n\u00eb p\u00ebrgjith\u00ebsi rikuperimi pas fatkeq\u00ebsis\u00eb jan\u00eb p\u00ebrfunduar.<\/p>\n

Pasth\u00ebnie<\/h4>\n

\n04.04.2013, n\u00eb dit\u00ebn e gabimit 404,<\/a><\/noindex>\"Odnoklassniki\" ka p\u00ebrjetuar nj\u00eb fatkeq\u00ebsi t\u00eb madhe.<\/a><\/noindex> \u2014 gjat\u00eb tre dit\u00ebve portali ishte plot\u00ebsisht ose pjes\u00ebrisht i paaksesuesh\u00ebm. Gjat\u00eb gjith\u00eb k\u00ebtij koh\u00eb, m\u00eb shum\u00eb se 100 njer\u00ebz nga qytete t\u00eb ndryshme, nga kompani t\u00eb ndryshme (faleminderit edhe nj\u00ebher\u00eb shum\u00eb!), kan\u00eb riparuar mij\u00ebra server\u00eb n\u00eb distanc\u00eb dhe drejtp\u00ebrdrejt n\u00eb qendrat e t\u00eb dh\u00ebnave, manualisht dhe automatikisht.
\nNe kemi nxjerr\u00eb p\u00ebrfundime. P\u00ebr t\u00eb mos lejuar q\u00eb kjo t\u00eb p\u00ebrs\u00ebritet, ne kemi zhvilluar dhe vazhdojm\u00eb t\u00eb kryejm\u00eb pun\u00eb t\u00eb shumta.<\/p>\n

Cilat jan\u00eb dallimet kryesore t\u00eb fatkeq\u00ebsis\u00eb aktuale nga ajo 404?<\/p>\n