{"id":32682,"date":"2019-10-31T21:48:22","date_gmt":"2019-10-31T18:48:22","guid":{"rendered":"https:\/\/prohoster.info\/blog\/ishhem-problemu-ne-v-tom-meste\/"},"modified":"2019-10-31T21:48:22","modified_gmt":"2019-10-31T18:48:22","slug":"ishhem-problemu-ne-v-tom-meste","status":"publish","type":"post","link":"https:\/\/prohoster.info\/lv\/blog\/administrirovanie\/ishhem-problemu-ne-v-tom-meste","title":{"rendered":"Mekl\u0113jam probl\u0113mu ne tur, kur vajadz\u0113tu","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\u0160\u012b ir \u012bsa st\u0101sta izst\u0101de no re\u0101l\u0101s prakses, kad neliela probl\u0113ma, labi mask\u0113ta ar notur\u012bbu pret k\u013c\u016bd\u0101m, p\u0101rv\u0113r\u0161as par galvas s\u0101p\u0113m.
\n<\/a><\/noindex><\/p>\n

Neliela ievadv\u0101rdi:<\/h2>\n

\nMazs fili\u0101le ar savu PBX (asterisk + FreePBX) uz galda aparat\u016bras un t\u0101du pa\u0161u viet\u0113jo termin\u0101lo serveri ar 1C, failu kr\u0101tavu un virtu\u0101lo RO dom\u0113na kontrolieri. Internets tiek dal\u012bts caur Mikrotik. Fili\u0101le ir maza, vi\u0146iem t\u0101 ir pietiekami.
\nViss s\u0101k\u0101s ar monitoringu (laika tr\u016bkuma un slinkuma d\u0113\u013c nekontrol\u0113 visu), kas zi\u0146oja par viena serveris<\/a> (ar PBX) fili\u0101l\u0113 notiku\u0161u p\u0101rkar\u0161anu. Kam\u0113r viet\u0113jie risin\u0101ja probl\u0113mu, vecais apar\u0101ts aizmiga un nedaudz saboj\u0101ja MySQL datub\u0101zi.<\/p>\n

Daudz kas liecin\u0101ja par nelaimi, bet ne par \u0161o\u2026<\/h3>\n

\nNav probl\u0113mu, datub\u0101zi izdev\u0101s salabot, viss, \u0161\u0137iet, darbosies. Bet viet\u0113jie s\u016bdzas, zvan\u012b\u0161ana p\u0101rtr\u016bkst. Labi \u2014 probl\u0113mas ar FreePBX m\u0113dz b\u016bt, pa\u0146emu dubl\u0113jumu, atveru, viss OK.
\nBet nelaime ir kl\u0101t, viet\u0113jie joproj\u0101m s\u016bdzas, zvan\u012b\u0161ana nenotiek norm\u0101li. Vi\u0146iem \u0161\u0137iet, ka zvans iet cauri norm\u0101li, bet, kad vi\u0146i pa\u0161i zvana vai zvan\u0101s sav\u0101 starp\u0101, rodas vair\u0101ku sekun\u017eu aizture. S\u0101ku skat\u012bties apjom\u012bgas un neskaidras Asterisk un FreePBX \u017eurn\u0101lus, tajos uzskat\u0101m\u0101 probl\u0113ma nav saskat\u0101ma. Atceros, bija probl\u0113ma ar STUN un ICE, kas rad\u012bja l\u012bdz\u012bgas aiztures. Izsl\u0113dzu visu, un rezult\u0101ts ir nulle.<\/p>\n

Izmisums \u2014 ce\u013c\u0161 uz sliktu l\u0113mumu pie\u0146em\u0161anu:<\/h3>\n

\nIelai\u017eos izmisum\u0101, daudzu stundu rak\u0146\u0101\u0161an\u0101s PBX nesniedz nevienu labu rezult\u0101tu, jau ir dzi\u013ca nakts, bet probl\u0113ma netiek atrisin\u0101ta.
\nAtst\u0101ju probl\u0113mu r\u012btam, cerot uz svaig\u0101m idej\u0101m. No r\u012bta tika pie\u0146emts v\u0113l viens neveiksm\u012bgs l\u0113mums: ja jau sist\u0113ma ir saboj\u0101ta (lai gan aizmigt nevar\u0113ja b\u016bt tik posto\u0161i), m\u0113\u0123inu labot sist\u0113mu, p\u0101rinstal\u0113jot visus paketus. Rezult\u0101ts nedaudz p\u0101rsniedza nulli, aizture samazin\u0101j\u0101s (ne iev\u0113rojami, bet jau pan\u0101kums).
\nPie\u0146emu v\u0113l vienu sliktu l\u0113mumu: ja da\u013c\u0113ja oper\u0113t\u0101jsist\u0113mas (un datub\u0101zes no rezerves kopijas) atjauno\u0161ana bija nedaudz veiksm\u012bga, bet probl\u0113mas sakne v\u0113l joproj\u0101m nav skaidra, un taj\u0101 pa\u0161\u0101 laik\u0101 jau ir pavad\u012bts \u013coti daudz laika c\u0113lo\u0146a mekl\u0113\u0161an\u0101, tad nolemju r\u012bkoties radik\u0101li: uzst\u0101jam oper\u0113t\u0101jsist\u0113mu no jauna (paldies automatiz\u0101cijas procesam, kas to paveic sapr\u0101t\u012bg\u0101 laik\u0101). Uzst\u0101d\u012bju FreePBX konfigur\u0101ciju no dubl\u0113juma. V\u0113l viena neveiksme. Rezult\u0101ts ir nulle!<\/p>\n

Izmisls \u2014 pr\u0101ts ir apm\u0101kts, risin\u0101jumi k\u013c\u016bst v\u0113l slikt\u0101ki<\/h3>\n

\nEs iekr\u012btu izmisum\u0101. S\u0101k ien\u0101kt pavisam d\u012bvainas domas, dom\u0101ju: varb\u016bt konference dubl\u0113jum\u0101 ir nepareiza (man t\u0101 ir noticis p\u0113c virknes atjaunin\u0101jumu, kad p\u0113c tiem viss p\u0101rst\u0101ja darboties, un man neizdev\u0101s atrast iemeslu), nekas cits neatliek: j\u0101uzliek viss no jauna ar rok\u0101m. K\u0101ds kauns! Rezult\u0101ts ir stingri nulle, turkl\u0101t pavad\u012bts liels laiks!<\/p>\n

Pie\u0146em\u0161ana \u2014 ce\u013c\u0161 uz apzin\u0101\u0161anos<\/h3>\n

\nIzmis\u012bg\u0101s p\u016bl\u0113s izprast notieko\u0161o, s\u0101ku uzman\u012bgi p\u0113t\u012bt \u017eurn\u0101lus. Paman\u012bju likumsakar\u012bbu. Papildin\u0101jums tiek izsaukts tie\u0161i p\u0113c 5 sekund\u0113m, bet grup\u0101 no 3 papildu izsaukumiem \u2014 p\u0113c 15! S\u0101ku mekl\u0113t inform\u0101ciju par izsaukuma aizturi, bet jau nor\u0101dot konkr\u0113tu aizturi. Un uzd\u016bros jau atrastajam atbildei, cilv\u0113ki saka, ka probl\u0113ma ir DNS, bet es ta\u010du prec\u012bzi zinu, ka probl\u0113mu nav, visi adreses tiek iz\u0161\u0137irtas!<\/p>\n

Ac\u012bmredzamais \u2014 ne ticamais<\/h3>\n

\nNav ko dar\u012bt, \u0146emu rok\u0101s nslookup un bingo (k\u0101 b\u016btu jau uzreiz to izdar\u012bjis)! Prim\u0101rais DNS nestr\u0101d\u0101 (virtu\u0101l\u0101 ma\u0161\u012bna ar kontrolieri), un es pat nepaman\u012bju! Ja b\u016btu viens DNS, t\u016bl\u012bt tiktu izsniegta k\u013c\u016bda \ud83d\ude09<\/p>\n

Rezult\u0101ts<\/h3>\n

\nElement\u0101ra probl\u0113ma, kuru var\u0113tu redz\u0113t monitorings (kur\u0161 j\u0101nosaka visiem mezgliem), mask\u0113ta DNS labad, noveda pie gandr\u012bz divu darba dienu zuduma mu\u013c\u0137\u012bgas situ\u0101cijas risin\u0101\u0161an\u0101. Slinkums ir visu probl\u0113ma, uzst\u0101d\u012bt monitoringu ir min\u016bte \u2014 mekl\u0113t probl\u0113mu tur, kur t\u0101s nav \u2014 divas dienas.<\/p>\n

Tikai re\u0123istr\u0113tie lietot\u0101ji var piedal\u012bties aptauj\u0101. Pieteikties<\/a><\/noindex>, l\u016bdzu.<\/p>\n

Vai jums ir bijusi l\u012bdz\u012bga pieredze?<\/h2>\n