{"id":5557,"date":"2026-09-21T12:18:59","date_gmt":"2026-09-21T09:18:59","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/?p=5557"},"modified":"2026-09-21T06:25:51","modified_gmt":"2026-09-21T03:25:51","slug":"linux-kernel-panic-cozumu-kok-neden-ve-kurtarma","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/linux-kernel-panic-cozumu-kok-neden-ve-kurtarma\/","title":{"rendered":"Sunucuda Kernel Panic: K\u00f6k Neden ve Kurtarma"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div class=\"aiw-summary\">\n<p class=\"aiw-box-title\">H\u0131zl\u0131 \u00f6zet<\/p>\n<p>Sunucu aniden yeniden ba\u015fl\u0131yor, SSH kapan\u0131yor ve servisler a\u00e7\u0131lm\u0131yorsa sorun yaln\u0131zca i\u015fletim sistemiyle s\u0131n\u0131rl\u0131 olmayabilir. Donan\u0131m, \u00e7ekirdek mod\u00fcl\u00fc, disk, bellek, firmware veya \u00f6ny\u00fckleme katman\u0131 da ayn\u0131 belirtiyi olu\u015fturabilir. Linux kernel panic \u00e7\u00f6z\u00fcm\u00fc i\u00e7in \u00f6nce konsoldan kan\u0131t toplay\u0131n, ard\u0131ndan son \u00e7al\u0131\u015fan \u00e7ekirde\u011fe veya kurtarma ortam\u0131na d\u00f6nerek en dar d\u00fczeltmeyi uygulay\u0131n.<\/p>\n<ul>\n<li>Kernel panic ekran\u0131n\u0131 ve sunucunun yeniden ba\u015flama zaman\u0131n\u0131 kaydedin; kan\u0131t\u0131 silmeden yeniden kurulum yapmay\u0131n.<\/li>\n<li>Sa\u011flay\u0131c\u0131n\u0131n konsolunu, BMC\/iKVM aray\u00fcz\u00fcn\u00fc veya fiziksel ekran\u0131 SSH yerine kullan\u0131n.<\/li>\n<li>\u00d6nceki \u00e7ekirdek s\u00fcr\u00fcm\u00fcn\u00fc denemek, hatal\u0131 mod\u00fcl\u00fc veya son kernel g\u00fcncellemesini izole etmenin d\u00fc\u015f\u00fck riskli yollar\u0131ndand\u0131r.<\/li>\n<li>journal, kdump, pstore, donan\u0131m ve depolama kay\u0131tlar\u0131n\u0131 birlikte inceleyin; tek bir log sat\u0131r\u0131na dayanarak karar vermeyin.<\/li>\n<li>De\u011fi\u015fiklikten \u00f6nce anl\u0131k g\u00f6r\u00fcnt\u00fc veya yedek al\u0131n, i\u015flemden sonra a\u00e7\u0131l\u0131\u015f\u0131 ve kritik servisleri do\u011frulay\u0131n.<\/li>\n<\/ul>\n<\/div>\n<p>VPS ya da fiziksel sunucunuz bir anda yeniden ba\u015flad\u0131ysa ve SSH ba\u011flant\u0131s\u0131 art\u0131k kurulmuyorsa, ilk hedefiniz servisi rastgele yeniden ba\u015flatmak de\u011fil, sistemin hangi a\u015famada durdu\u011funu belirlemektir. Ekranda <code>Kernel panic<\/code>, <code>Unable to mount root fs<\/code>, <code>Out of memory<\/code> veya benzeri bir hata g\u00f6rmeniz, Linux \u00e7ekirde\u011finin normal \u00e7al\u0131\u015fmay\u0131 g\u00fcvenli bulmad\u0131\u011f\u0131 i\u00e7in durdu\u011funu g\u00f6sterebilir.<\/p>\n<p>Kernel panic bir k\u00f6k neden de\u011fil, \u00e7ekirde\u011fin devam edemedi\u011fi kritik bir durumdur. Hatal\u0131 veya uyumsuz bir mod\u00fcl, bozuk dosya sistemi, eri\u015filemeyen k\u00f6k disk, ar\u0131zal\u0131 bellek, firmware sorunu, hatal\u0131 \u00e7ekirdek g\u00fcncellemesi ve baz\u0131 sanalla\u015ft\u0131rma katman\u0131 problemleri ayn\u0131 belirtiyi \u00fcretebilir. Bu nedenle Linux kernel panic \u00e7\u00f6z\u00fcm\u00fc, tek bir komuttan \u00e7ok kontroll\u00fc bir te\u015fhis ak\u0131\u015f\u0131d\u0131r.<\/p>\n<div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Kernel_panic_nasil_anlasilir\"><span class=\"toc_number toc_depth_1\">1.<\/span> Kernel panic nas\u0131l anla\u015f\u0131l\u0131r?<\/a><\/li><li><a href=\"#Ilk_mudahale_erisimi_ve_kaniti_guvenceye_alin\"><span class=\"toc_number toc_depth_1\">2.<\/span> \u0130lk m\u00fcdahale: eri\u015fimi ve kan\u0131t\u0131 g\u00fcvenceye al\u0131n<\/a><ul><li><a href=\"#Konsol_erisimini_kullanin\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> Konsol eri\u015fimini kullan\u0131n<\/a><\/li><li><a href=\"#Olayi_zaman_cizelgesine_yerlestirin\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> Olay\u0131 zaman \u00e7izelgesine yerle\u015ftirin<\/a><\/li><\/ul><\/li><li><a href=\"#Onyukleme_sonrasinda_loglari_inceleyin\"><span class=\"toc_number toc_depth_1\">3.<\/span> \u00d6ny\u00fckleme sonras\u0131nda loglar\u0131 inceleyin<\/a><ul><li><a href=\"#Kernel_disk_ve_bellek_belirtilerini_ayirin\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> Kernel, disk ve bellek belirtilerini ay\u0131r\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#En_dusuk_riskli_kurtarma_yollari\"><span class=\"toc_number toc_depth_1\">4.<\/span> En d\u00fc\u015f\u00fck riskli kurtarma yollar\u0131<\/a><ul><li><a href=\"#Onceki_kernel_ile_acilisi_deneyin\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> \u00d6nceki kernel ile a\u00e7\u0131l\u0131\u015f\u0131 deneyin<\/a><\/li><li><a href=\"#Rescue_veya_live_ortaminda_kok_diski_inceleyin\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> Rescue veya live ortam\u0131nda k\u00f6k diski inceleyin<\/a><\/li><li><a href=\"#Cekirdek_paketini_ve_initramfs8217i_yeniden_olusturun\"><span class=\"toc_number toc_depth_2\">4.3.<\/span> \u00c7ekirdek paketini ve initramfs&#8217;i yeniden olu\u015fturun<\/a><\/li><\/ul><\/li><li><a href=\"#Kok_nedenleri_siniflandirin\"><span class=\"toc_number toc_depth_1\">5.<\/span> K\u00f6k nedenleri s\u0131n\u0131fland\u0131r\u0131n<\/a><ul><li><a href=\"#Kernel_guncellemesi_veya_ucuncu_taraf_modul\"><span class=\"toc_number toc_depth_2\">5.1.<\/span> Kernel g\u00fcncellemesi veya \u00fc\u00e7\u00fcnc\u00fc taraf mod\u00fcl<\/a><\/li><li><a href=\"#Dosya_sistemi_disk_veya_RAID_sorunu\"><span class=\"toc_number toc_depth_2\">5.2.<\/span> Dosya sistemi, disk veya RAID sorunu<\/a><\/li><li><a href=\"#Bellek_CPU_ve_firmware\"><span class=\"toc_number toc_depth_2\">5.3.<\/span> Bellek, CPU ve firmware<\/a><\/li><li><a href=\"#OOM_ile_kernel_panic8217i_karistirmayin\"><span class=\"toc_number toc_depth_2\">5.4.<\/span> OOM ile kernel panic&#8217;i kar\u0131\u015ft\u0131rmay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Kdump_ve_pstore_ile_sonraki_olayi_yakalayin\"><span class=\"toc_number toc_depth_1\">6.<\/span> Kdump ve pstore ile sonraki olay\u0131 yakalay\u0131n<\/a><\/li><li><a href=\"#Degisiklik_sonrasi_dogrulama\"><span class=\"toc_number toc_depth_1\">7.<\/span> De\u011fi\u015fiklik sonras\u0131 do\u011frulama<\/a><\/li><li><a href=\"#Sik_Sorulan_Sorular\"><span class=\"toc_number toc_depth_1\">8.<\/span> S\u0131k Sorulan Sorular<\/a><ul><li><a href=\"#Kernel_panic_sunucudaki_verileri_siler_mi\"><span class=\"toc_number toc_depth_2\">8.1.<\/span> Kernel panic sunucudaki verileri siler mi?<\/a><\/li><li><a href=\"#Sunucu_yeniden_basliyor_ama_ekranda_panic_gorunmuyorsa_ne_yapilmali\"><span class=\"toc_number toc_depth_2\">8.2.<\/span> Sunucu yeniden ba\u015fl\u0131yor ama ekranda panic g\u00f6r\u00fcnm\u00fcyorsa ne yap\u0131lmal\u0131?<\/a><\/li><li><a href=\"#Eski_kernel_ile_acilan_sunucuda_yeni_kernel_silinmeli_mi\"><span class=\"toc_number toc_depth_2\">8.3.<\/span> Eski kernel ile a\u00e7\u0131lan sunucuda yeni kernel silinmeli mi?<\/a><\/li><li><a href=\"#Kernel_panic_ile_uygulamanin_beyaz_ekrani_ayni_sorun_mudur\"><span class=\"toc_number toc_depth_2\">8.4.<\/span> Kernel panic ile uygulaman\u0131n beyaz ekran\u0131 ayn\u0131 sorun mudur?<\/a><\/li><\/ul><\/li><li><a href=\"#Uygulanabilir_kontrol_listesi\"><span class=\"toc_number toc_depth_1\">9.<\/span> Uygulanabilir kontrol listesi<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Kernel_panic_nasil_anlasilir\">Kernel panic nas\u0131l anla\u015f\u0131l\u0131r?<\/span><\/h2>\n<p>Normal bir uygulama hatas\u0131nda bir s\u00fcre\u00e7 kapan\u0131r; sistemin geri kalan\u0131 \u00e7al\u0131\u015fmaya devam eder. Kernel panic durumunda ise \u00e7ekirdek, donan\u0131m veya temel sistem kaynaklar\u0131yla g\u00fcvenli bi\u00e7imde ileti\u015fim kuramad\u0131\u011f\u0131 i\u00e7in sistemi durdurabilir. Yap\u0131land\u0131rmaya ba\u011fl\u0131 olarak sunucu ekranda hata mesaj\u0131 b\u0131rak\u0131r, otomatik yeniden ba\u015flar veya donmu\u015f gibi g\u00f6r\u00fcn\u00fcr.<\/p>\n<p>\u015eu belirtiler ayn\u0131 olay\u0131 farkl\u0131 bi\u00e7imlerde g\u00f6sterebilir:<\/p>\n<ul>\n<li>SSH ve di\u011fer a\u011f servisleri ayn\u0131 anda eri\u015filemez hale gelir.<\/li>\n<li>\u0130zleme sistemi k\u0131sa aral\u0131klarla yeniden ba\u015flama bildirimi g\u00f6nderir.<\/li>\n<li>Sunucu sa\u011flay\u0131c\u0131s\u0131n\u0131n konsolunda kernel panic, stack trace veya <code>not syncing<\/code> ifadesi g\u00f6r\u00fcl\u00fcr.<\/li>\n<li>Yeniden ba\u015flatma sonras\u0131nda k\u00f6k dosya sistemi ba\u011flanamaz veya sunucu acil durum kabu\u011funa d\u00fc\u015fer.<\/li>\n<li>Makine yaln\u0131zca belirli \u00e7ekirdek s\u00fcr\u00fcm\u00fcnde a\u00e7\u0131l\u0131r ya da y\u00fck alt\u0131nda tekrar kapan\u0131r.<\/li>\n<\/ul>\n<p>Tek ba\u015f\u0131na SSH kesintisi kernel panic kan\u0131t\u0131 de\u011fildir. A\u011f yap\u0131land\u0131rmas\u0131, g\u00fcvenlik duvar\u0131, dolu disk, servis kilitlenmesi veya sa\u011flay\u0131c\u0131 taraf\u0131ndaki sanal makine olay\u0131 da benzer bir d\u0131\u015f belirti olu\u015fturabilir. \u00d6nce konsoldan g\u00f6r\u00fcnt\u00fc alman\u0131z ve sa\u011flay\u0131c\u0131 panelindeki yeniden ba\u015flatma zaman\u0131n\u0131 not etmeniz bu ayr\u0131m\u0131 yapman\u0131z\u0131 sa\u011flar.<\/p>\n<h2><span id=\"Ilk_mudahale_erisimi_ve_kaniti_guvenceye_alin\">\u0130lk m\u00fcdahale: eri\u015fimi ve kan\u0131t\u0131 g\u00fcvenceye al\u0131n<\/span><\/h2>\n<h3><span id=\"Konsol_erisimini_kullanin\">Konsol eri\u015fimini kullan\u0131n<\/span><\/h3>\n<p>SSH \u00e7al\u0131\u015fmad\u0131\u011f\u0131nda web konsolu, sanal seri konsol, KVM, iKVM veya fiziksel ekran \u00fczerinden ba\u011flan\u0131n. Bu eri\u015fim yollar\u0131 i\u015fletim sisteminin a\u011f servislerine ba\u011fl\u0131 olmad\u0131\u011f\u0131 i\u00e7in te\u015fhisi s\u00fcrd\u00fcrmenize yard\u0131mc\u0131 olur. VPS kullan\u0131yorsan\u0131z konsolun sa\u011flay\u0131c\u0131 panelinde nas\u0131l etkinle\u015ftirildi\u011fini ve ekran \u00e7\u0131kt\u0131s\u0131n\u0131n nas\u0131l al\u0131naca\u011f\u0131n\u0131 \u00f6nceden do\u011frulay\u0131n.<\/p>\n<p>\u00d6nce ekrandaki panic mesaj\u0131n\u0131n tamam\u0131n\u0131 kaydedin. \u00d6zellikle <code>Call Trace<\/code>, <code>RIP<\/code>, <code>Oops<\/code>, mod\u00fcl ad\u0131, disk ayg\u0131t\u0131, UUID, dosya sistemi ve \u00e7ekirdek s\u00fcr\u00fcm\u00fc gibi b\u00f6l\u00fcmler \u00f6nemlidir. Bir sat\u0131rda ge\u00e7en mod\u00fcl ad\u0131 her zaman hatan\u0131n kesin nedeni de\u011fildir; \u00e7a\u011fr\u0131 zincirinde g\u00f6r\u00fcnen son bile\u015fen olabilir.<\/p>\n<div class=\"aiw-note aiw-note-warning\">\n<p class=\"aiw-box-title\">Dikkat<\/p>\n<p>Kan\u0131t toplamadan sistemi yeniden kurmak, eski \u00e7ekirde\u011fi kald\u0131rmak veya geni\u015f kapsaml\u0131 temizlik komutlar\u0131 \u00e7al\u0131\u015ft\u0131rmak k\u00f6k nedeni g\u00f6r\u00fcnmez hale getirebilir. \u00d6nce ekran g\u00f6r\u00fcnt\u00fcs\u00fc, zaman bilgisi ve mevcut disk durumunu kaydedin.<\/p>\n<\/div>\n<h3><span id=\"Olayi_zaman_cizelgesine_yerlestirin\">Olay\u0131 zaman \u00e7izelgesine yerle\u015ftirin<\/span><\/h3>\n<p>\u015eu bilgileri ayn\u0131 zaman aral\u0131\u011f\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131n:<\/p>\n<ul>\n<li>\u0130lk eri\u015fim kesintisinin UTC veya yerel saat kar\u015f\u0131l\u0131\u011f\u0131.<\/li>\n<li>Sa\u011flay\u0131c\u0131 panelindeki g\u00fc\u00e7 d\u00f6ng\u00fcs\u00fc, ta\u015f\u0131ma, bak\u0131m veya sanal makine olay\u0131.<\/li>\n<li>Son kernel, firmware, s\u00fcr\u00fcc\u00fc, depolama veya g\u00fcvenlik g\u00fcncellemesi.<\/li>\n<li>Trafik, disk kullan\u0131m\u0131, bellek t\u00fcketimi ve s\u0131cakl\u0131kta ola\u011fand\u0131\u015f\u0131 de\u011fi\u015fim.<\/li>\n<li>Planl\u0131 cron i\u015fleri, yedekleme, b\u00fcy\u00fck dosya i\u015flemleri veya yo\u011fun derleme s\u00fcre\u00e7leri.<\/li>\n<\/ul>\n<p>Bu zaman \u00e7izelgesi, \u00f6rne\u011fin \u00e7ekirdek g\u00fcncellemesinden hemen sonra ba\u015flayan bir \u00f6ny\u00fckleme sorununu, haftalard\u0131r y\u00fck alt\u0131nda ortaya \u00e7\u0131kan bellek ar\u0131zas\u0131ndan ay\u0131rman\u0131za yard\u0131m eder. Sistem tekrar a\u00e7\u0131labiliyorsa, de\u011fi\u015fiklik yapmadan \u00f6nce temel kay\u0131tlar\u0131 d\u0131\u015far\u0131 aktar\u0131n.<\/p>\n<h2><span id=\"Onyukleme_sonrasinda_loglari_inceleyin\">\u00d6ny\u00fckleme sonras\u0131nda loglar\u0131 inceleyin<\/span><\/h2>\n<p>Sunucu eski bir \u00e7ekirdekle veya ge\u00e7ici bir kurtarma se\u00e7ene\u011fiyle a\u00e7\u0131ld\u0131ysa, ilk i\u015finiz son ba\u015far\u0131s\u0131z a\u00e7\u0131l\u0131\u015fa ait kay\u0131tlar\u0131 aramakt\u0131r. <code>journalctl<\/code> yaln\u0131zca systemd journal tutuluyorsa i\u015fe yarar. Journal kal\u0131c\u0131 de\u011filse, ani g\u00fc\u00e7 kesintisi veya panic sonras\u0131nda \u00f6nceki a\u00e7\u0131l\u0131\u015fa ait kay\u0131tlar\u0131n bir b\u00f6l\u00fcm\u00fc kaybolabilir.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">journalctl --list-boots\njournalctl -b -1 -k --no-pager\njournalctl -b -1 -p err..alert --no-pager\nuname -a\ncat \/proc\/cmdline<\/code><\/pre>\n<p><code>-b -1<\/code> \u00f6nceki a\u00e7\u0131l\u0131\u015f\u0131, <code>-k<\/code> yaln\u0131zca kernel kay\u0131tlar\u0131n\u0131, <code>-p err..alert<\/code> ise hata ve daha y\u00fcksek \u00f6ncelikli kay\u0131tlar\u0131 se\u00e7er. \u00d6nceki boot g\u00f6r\u00fcnm\u00fcyorsa bunu &#8220;kay\u0131t yok, sorun yok&#8221; \u015feklinde yorumlamay\u0131n. Kal\u0131c\u0131 journal yap\u0131land\u0131r\u0131lmam\u0131\u015f olabilir veya panic kay\u0131tlar\u0131 yaln\u0131zca konsola yaz\u0131lm\u0131\u015f olabilir.<\/p>\n<p>Journal kal\u0131c\u0131l\u0131\u011f\u0131n\u0131 kontrol etmek i\u00e7in mevcut dizine bakabilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">test -d \/var\/log\/journal &amp;&amp; echo &quot;Kal\u0131c\u0131 journal dizini var&quot; || echo &quot;Kal\u0131c\u0131 journal dizini yok&quot;\nfindmnt \/var\nfindmnt \/<\/code><\/pre>\n<p>Bu komutlar yaln\u0131zca durum tespiti yapar. Journal kal\u0131c\u0131l\u0131\u011f\u0131n\u0131 sonradan etkinle\u015ftirmek gelecekteki olaylara yard\u0131mc\u0131 olur, ancak ge\u00e7mi\u015fte kaybolan kay\u0131tlar\u0131 geri getirmez. Yap\u0131land\u0131rmay\u0131 de\u011fi\u015ftirecekseniz da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n systemd s\u00fcr\u00fcm\u00fcn\u00fc ve log saklama politikas\u0131n\u0131 kontrol edin.<\/p>\n<h3><span id=\"Kernel_disk_ve_bellek_belirtilerini_ayirin\">Kernel, disk ve bellek belirtilerini ay\u0131r\u0131n<\/span><\/h3>\n<p>Loglarda <code>BUG:<\/code>, <code>Oops:<\/code>, <code>Call Trace:<\/code> veya belirli bir mod\u00fcl ad\u0131 g\u00f6rmeniz \u00e7ekirdek ya da s\u00fcr\u00fcc\u00fc katman\u0131n\u0131 i\u015faret edebilir. <code>I\/O error<\/code>, <code>ata<\/code>, <code>nvme<\/code>, <code>EXT4-fs error<\/code>, <code>XFS<\/code> veya <code>buffer I\/O<\/code> ifadeleri depolama katman\u0131n\u0131 incelemenizi gerektirir. <code>Out of memory<\/code> ve OOM kay\u0131tlar\u0131 ise genellikle Linux&#8217;un bellek bask\u0131s\u0131 nedeniyle s\u00fcre\u00e7 sonland\u0131rd\u0131\u011f\u0131n\u0131 g\u00f6sterir; bunlar her zaman kernel panic de\u011fildir.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">dmesg -T --level=emerg,alert,crit,err,warn\njournalctl -k -b 0 --no-pager | grep -Ei &#039;panic|oops|call trace|oom|io error|nvme|ata|ext4|xfs|mce|edac&#039;<\/code><\/pre>\n<p><code>dmesg<\/code> \u00e7\u0131kt\u0131s\u0131 \u00e7ekirdek mesajlar\u0131n\u0131 g\u00f6sterir; baz\u0131 sistemlerde yetki k\u0131s\u0131tlamas\u0131 nedeniyle root eri\u015fimi gerekebilir. Komutun \u00e7\u0131kt\u0131s\u0131n\u0131 daraltmak te\u015fhisi h\u0131zland\u0131r\u0131r, fakat grep filtresinde g\u00f6r\u00fcnmeyen sat\u0131rlar\u0131 yok saymay\u0131n. Hata bir donan\u0131m ayg\u0131t\u0131na i\u015faret ediyorsa sa\u011flay\u0131c\u0131n\u0131n disk ve sanalla\u015ft\u0131rma kay\u0131tlar\u0131n\u0131 da isteyin.<\/p>\n<h2><span id=\"En_dusuk_riskli_kurtarma_yollari\">En d\u00fc\u015f\u00fck riskli kurtarma yollar\u0131<\/span><\/h2>\n<h3><span id=\"Onceki_kernel_ile_acilisi_deneyin\">\u00d6nceki kernel ile a\u00e7\u0131l\u0131\u015f\u0131 deneyin<\/span><\/h3>\n<p>Son g\u00fcncellemeden sonra ba\u015flayan bir sorun i\u00e7in GRUB men\u00fcs\u00fcndeki <em>Advanced options<\/em> alt\u0131nda daha eski bir kernel se\u00e7mek iyi bir izolasyon testidir. Sunucu eski kernel ile a\u00e7\u0131l\u0131yorsa k\u00f6k dosya sistemi, a\u011f ve temel servisleri do\u011frulay\u0131n; ard\u0131ndan \u00e7al\u0131\u015fan s\u00fcr\u00fcm\u00fc hemen kald\u0131rmay\u0131n.<\/p>\n<p>Bu test, sorunun \u00e7ekirdek paketinde veya initramfs i\u00e7inde olabilece\u011fini d\u00fc\u015f\u00fcnd\u00fcr\u00fcr, ancak donan\u0131m ar\u0131zas\u0131n\u0131 tamamen d\u0131\u015flamaz. Eski kernel ile de y\u00fck alt\u0131nda panic oluyorsa bellek, depolama, firmware ve sanalla\u015ft\u0131rma katman\u0131n\u0131 ayr\u0131ca inceleyin.<\/p>\n<div class=\"aiw-note aiw-note-example\">\n<p class=\"aiw-box-title\">\u00d6rnek senaryo<\/p>\n<p>Bir VPS&#8217;in yaln\u0131zca yeni kernel ile a\u00e7\u0131lmad\u0131\u011f\u0131n\u0131, \u00f6nceki kernel ile a\u011f ve disk servislerinin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 varsayal\u0131m. Bu, &#8220;kesin olarak kernel paketi bozuktur&#8221; kan\u0131t\u0131 de\u011fildir; fakat yeni s\u00fcr\u00fcm, initramfs veya \u00fc\u00e7\u00fcnc\u00fc taraf mod\u00fcl\u00fc izole etmek i\u00e7in g\u00fcvenli bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r. Kal\u0131c\u0131 de\u011fi\u015fiklikten \u00f6nce iki a\u00e7\u0131l\u0131\u015f\u0131n loglar\u0131n\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<\/div>\n<h3><span id=\"Rescue_veya_live_ortaminda_kok_diski_inceleyin\">Rescue veya live ortam\u0131nda k\u00f6k diski inceleyin<\/span><\/h3>\n<p>Hi\u00e7bir kernel ile a\u00e7\u0131l\u0131\u015f ger\u00e7ekle\u015fmiyorsa sa\u011flay\u0131c\u0131n\u0131n rescue ortam\u0131n\u0131 veya da\u011f\u0131t\u0131m\u0131n live ortam\u0131n\u0131 kullan\u0131n. Buradaki ama\u00e7 sistemi rastgele onarmak de\u011fil, k\u00f6k b\u00f6l\u00fcm\u00fcn g\u00f6r\u00fcld\u00fc\u011f\u00fcn\u00fc, dosya sisteminin tutarl\u0131 oldu\u011funu ve gerekli verilerin kopyalanabildi\u011fini do\u011frulamakt\u0131r.<\/p>\n<p>\u00d6nce ayg\u0131tlar\u0131 ve ba\u011flama noktalar\u0131n\u0131 belirleyin. A\u015fa\u011f\u0131daki \u00f6rnek yaln\u0131zca ke\u015fif i\u00e7indir; kendi disk ad\u0131n\u0131z\u0131 \u00e7\u0131kt\u0131dan do\u011frulamadan onar\u0131m komutu \u00e7al\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">lsblk -f\nblkid\nfindmnt\nsmartctl -a \/dev\/sdX<\/code><\/pre>\n<p><code>smartctl<\/code> fiziksel donan\u0131mda yararl\u0131 bilgiler sa\u011flayabilir, ancak sanal disklerde s\u0131n\u0131rl\u0131 veya anlams\u0131z \u00e7\u0131kt\u0131 verebilir. <code>\/dev\/sdX<\/code> yer tutucusunu ger\u00e7ek ayg\u0131t ad\u0131yla de\u011fi\u015ftirmeden komutu \u00e7al\u0131\u015ft\u0131rmay\u0131n. Sa\u011flay\u0131c\u0131n\u0131n sanal disk altyap\u0131s\u0131 i\u00e7in sundu\u011fu sa\u011fl\u0131k bilgileri varsa bunlar\u0131 da kontrol edin. Dosya sistemi kontrol\u00fc yapmadan \u00f6nce ilgili b\u00f6l\u00fcm\u00fc unmount edin ve m\u00fcmk\u00fcnse sa\u011flay\u0131c\u0131n\u0131n anl\u0131k g\u00f6r\u00fcnt\u00fcs\u00fcn\u00fc veya do\u011frulanm\u0131\u015f yede\u011fi al\u0131n.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">umount \/dev\/mapper\/vg-root\nfsck -f \/dev\/mapper\/vg-root<\/code><\/pre>\n<p>Bu komutlar \u00f6rnektir ve ayg\u0131t adlar\u0131 sisteme g\u00f6re de\u011fi\u015fir. LVM, RAID, \u015fifreli disk veya XFS kullan\u0131yorsan\u0131z \u00f6nce ilgili katmanlar\u0131 do\u011fru s\u0131rada etkinle\u015ftirmeniz gerekir. Yanl\u0131\u015f b\u00f6l\u00fcme <code>fsck<\/code> uygulamak veri kayb\u0131na yol a\u00e7abilir; XFS gibi dosya sistemlerinde uygun yerel ara\u00e7lar\u0131 kullan\u0131n. Onar\u0131m tamamland\u0131\u011f\u0131nda dosya sistemini tekrar ba\u011flay\u0131p temel dosyalar\u0131n okunabildi\u011fini do\u011frulay\u0131n.<\/p>\n<h3><span id=\"Cekirdek_paketini_ve_initramfs8217i_yeniden_olusturun\">\u00c7ekirdek paketini ve initramfs&#8217;i yeniden olu\u015fturun<\/span><\/h3>\n<p>Eski kernel ile \u00e7al\u0131\u015fan bir sistemde paket veritaban\u0131n\u0131, disk bo\u015flu\u011funu ve boot b\u00f6l\u00fcm\u00fcn\u00fc kontrol edin. Boot b\u00f6l\u00fcm\u00fcn\u00fcn dolu olmas\u0131, yeni kernel paketinin kurulmu\u015f g\u00f6r\u00fcnmesine ra\u011fmen initramfs dosyas\u0131n\u0131n tamamlanamamas\u0131na yol a\u00e7abilir.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">df -h\nfindmnt \/boot\nls -lh \/boot<\/code><\/pre>\n<p>Da\u011f\u0131t\u0131m ve paket y\u00f6neticisi bilinmeden tek bir yeniden kurulum komutu vermek do\u011fru de\u011fildir. Debian veya Ubuntu tabanl\u0131 bir sistemde paket bilgilerini do\u011frulay\u0131p ilgili kernel paketini yeniden kurmak i\u00e7in APT; AlmaLinux, Rocky veya RHEL tabanl\u0131 bir sistemde DNF ve ilgili initramfs ara\u00e7lar\u0131 kullan\u0131l\u0131r. \u00d6nce \u00e7al\u0131\u015fan kernel s\u00fcr\u00fcm\u00fcn\u00fc, paket ad\u0131n\u0131 ve da\u011f\u0131t\u0131m s\u00fcr\u00fcm\u00fcn\u00fc kaydedin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">cat \/etc\/os-release\nrpm -q kernel 2&gt;\/dev\/null || dpkg-query -W &#039;linux-image*&#039; 2&gt;\/dev\/null<\/code><\/pre>\n<p>Da\u011f\u0131t\u0131m\u0131n resmi paketleriyle yeniden kurulum yapmadan \u00f6nce yedek veya snapshot al\u0131n. \u00dc\u00e7\u00fcnc\u00fc taraf bir kernel mod\u00fcl\u00fc kullan\u0131yorsan\u0131z, DKMS derleme durumunu ayr\u0131ca inceleyin; mod\u00fcl, yeni \u00e7ekirde\u011fe uyumlu bi\u00e7imde derlenmediyse a\u00e7\u0131l\u0131\u015f sorunu olu\u015fturabilir. Yeniden olu\u015fturma sonras\u0131nda initramfs dosyas\u0131n\u0131n boot b\u00f6l\u00fcm\u00fcnde bulundu\u011funu ve \u00f6ny\u00fckleme men\u00fcs\u00fcn\u00fcn ilgili s\u00fcr\u00fcm\u00fc g\u00f6rd\u00fc\u011f\u00fcn\u00fc kontrol edin.<\/p>\n<h2><span id=\"Kok_nedenleri_siniflandirin\">K\u00f6k nedenleri s\u0131n\u0131fland\u0131r\u0131n<\/span><\/h2>\n<h3><span id=\"Kernel_guncellemesi_veya_ucuncu_taraf_modul\">Kernel g\u00fcncellemesi veya \u00fc\u00e7\u00fcnc\u00fc taraf mod\u00fcl<\/span><\/h3>\n<p>Panic ilk kez kernel g\u00fcncellemesinden sonra ba\u015flad\u0131ysa eski kernel ile a\u00e7\u0131l\u0131\u015f testi, paket ve initramfs do\u011frulamas\u0131, ard\u0131ndan mod\u00fcl kay\u0131tlar\u0131 izlenmelidir. NVIDIA, depolama, g\u00fcvenlik veya sanalla\u015ft\u0131rma s\u00fcr\u00fcc\u00fcleri gibi \u00e7ekirdek mod\u00fclleri s\u00fcr\u00fcm de\u011fi\u015fikliklerinden etkilenebilir. Hata mesaj\u0131nda mod\u00fcl ad\u0131 ge\u00e7mesi, mod\u00fcl\u00fc hemen silmeniz gerekti\u011fi anlam\u0131na gelmez; \u00f6nce ilgili paketin ve DKMS durumunun kayd\u0131n\u0131 al\u0131n.<\/p>\n<p>D\u00fczeltme olarak yaln\u0131zca sorunla ili\u015fkili paketi yeniden olu\u015fturun veya \u00fcreticinin uyumlu s\u00fcr\u00fcm\u00fcne d\u00f6n\u00fcn. \u00c7ekirdek parametrelerini topluca de\u011fi\u015ftirmeyin. Her de\u011fi\u015fiklikten sonra bir kontroll\u00fc a\u00e7\u0131l\u0131\u015f, log kar\u015f\u0131la\u015ft\u0131rmas\u0131 ve uygulama servisi kontrol\u00fc yap\u0131n.<\/p>\n<h3><span id=\"Dosya_sistemi_disk_veya_RAID_sorunu\">Dosya sistemi, disk veya RAID sorunu<\/span><\/h3>\n<p>K\u00f6k b\u00f6l\u00fcm ba\u011flanam\u0131yorsa panic, \u00e7ekirde\u011fin \u00e7al\u0131\u015ft\u0131\u011f\u0131 halde temel dosya sistemine eri\u015femedi\u011fi bir \u00f6ny\u00fckleme ar\u0131zas\u0131 olabilir. UUID de\u011fi\u015fikli\u011fi, bozuk superblock, disk ba\u011flant\u0131s\u0131, RAID degradasyonu ve dosya sistemi tutars\u0131zl\u0131\u011f\u0131 olas\u0131 nedenlerdir. <code>\/etc\/fstab<\/code>, initramfs i\u00e7eri\u011fi ve boot parametrelerini birlikte kontrol edin.<\/p>\n<p>Donan\u0131m hata kay\u0131tlar\u0131 tekrarlan\u0131yorsa yaln\u0131zca dosya sistemi onarmak kal\u0131c\u0131 \u00e7\u00f6z\u00fcm de\u011fildir. Veriyi m\u00fcmk\u00fcn olan en k\u0131sa s\u00fcrede ba\u015fka bir ortama kopyalay\u0131n, RAID durumunu ve disk sa\u011fl\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n, fiziksel sunucuda sa\u011flay\u0131c\u0131 veya donan\u0131m y\u00f6neticisiyle de\u011fi\u015fim planlay\u0131n.<\/p>\n<h3><span id=\"Bellek_CPU_ve_firmware\">Bellek, CPU ve firmware<\/span><\/h3>\n<p><code>MCE<\/code>, <code>EDAC<\/code>, ECC d\u00fczeltme hatalar\u0131, rastgele farkl\u0131 kernel izleri veya y\u00fck alt\u0131nda tekrarlayan kilitlenmeler donan\u0131m ihtimalini y\u00fckseltir. VPS ortam\u0131nda bu belirtiler fiziksel host sorunu, sanalla\u015ft\u0131rma katman\u0131 veya kaynak tahsisi problemiyle ili\u015fkili olabilir. Fiziksel sunucuda \u00fcretici tan\u0131lama ara\u00e7lar\u0131, ECC saya\u00e7lar\u0131, s\u0131cakl\u0131k ve firmware s\u00fcr\u00fcmleri incelenmelidir.<\/p>\n<p>Firmware g\u00fcncellemesi veri ve a\u00e7\u0131l\u0131\u015f riski ta\u015f\u0131d\u0131\u011f\u0131 i\u00e7in \u00f6nce yedek, bak\u0131m penceresi ve geri d\u00f6n\u00fc\u015f plan\u0131 haz\u0131rlay\u0131n. Ayn\u0131 anda kernel, firmware ve s\u00fcr\u00fcc\u00fc de\u011fi\u015ftirmeyin; hangi de\u011fi\u015fikli\u011fin sonucu etkiledi\u011fini ay\u0131rmak zorla\u015f\u0131r.<\/p>\n<h3><span id=\"OOM_ile_kernel_panic8217i_karistirmayin\">OOM ile kernel panic&#8217;i kar\u0131\u015ft\u0131rmay\u0131n<\/span><\/h3>\n<p>Bellek t\u00fckenince Linux OOM killer, baz\u0131 s\u00fcre\u00e7leri sonland\u0131rabilir. Bu olayda web sitesi, veritaban\u0131 veya PHP s\u00fcre\u00e7leri kapanabilir; ancak \u00e7ekirdek mutlaka panic yapmaz. <code>journalctl<\/code> i\u00e7inde <code>Out of memory<\/code>, <code>Killed process<\/code> ve cgroup bilgilerini aray\u0131n. Swap, uygulama limitleri ve s\u00fcre\u00e7 bazl\u0131 bellek kullan\u0131m\u0131 incelendikten sonra kaynak art\u0131r\u0131m\u0131 veya uygulama ayar\u0131 d\u00fc\u015f\u00fcn\u00fclmelidir.<\/p>\n<p>PHP-FPM web i\u015f\u00e7ileri ile CLI \u00fczerinden \u00e7al\u0131\u015fan cron veya kuyruk i\u015f\u00e7ilerini de ay\u0131r\u0131n. HTTP iste\u011fi yapmayan bir CLI i\u015fi PHP-FPM web i\u015f\u00e7isi t\u00fcketmez; buna kar\u015f\u0131l\u0131k ayn\u0131 sunucunun toplam belle\u011fini t\u00fcketerek OOM olay\u0131na katk\u0131 sa\u011flayabilir. Bu ayr\u0131m, yanl\u0131\u015f servisi yeniden yap\u0131land\u0131rman\u0131z\u0131 \u00f6nler.<\/p>\n<h2><span id=\"Kdump_ve_pstore_ile_sonraki_olayi_yakalayin\">Kdump ve pstore ile sonraki olay\u0131 yakalay\u0131n<\/span><\/h2>\n<p>Panic sonras\u0131nda normal disk yaz\u0131m\u0131 tamamlanamayabilir. <code>kdump<\/code>, ayr\u0131lm\u0131\u015f bir crash kernel ba\u015flatarak bellek d\u00f6k\u00fcm\u00fc almaya; <code>pstore<\/code> ise uygun firmware veya donan\u0131m deste\u011fi varsa baz\u0131 kernel mesajlar\u0131n\u0131 yeniden ba\u015flatma sonras\u0131nda saklamaya yard\u0131mc\u0131 olur. Bunlar kurtarma mekanizmas\u0131 de\u011fil, gelecekteki te\u015fhis ara\u00e7lar\u0131d\u0131r.<\/p>\n<p>Kdump etkinle\u015ftirilecekse da\u011f\u0131t\u0131m\u0131n\u0131z\u0131n paketini, ayr\u0131lm\u0131\u015f bellek gereksinimini ve d\u00f6k\u00fcm hedefinin yeterli alan\u0131n\u0131 do\u011frulay\u0131n. D\u00f6k\u00fcm dosyalar\u0131 hassas bellek i\u00e7eri\u011fi bar\u0131nd\u0131rabilece\u011fi i\u00e7in eri\u015fim izinlerini ve saklama politikas\u0131n\u0131 da belirleyin. \u00d6nceki panic i\u00e7in kdump etkin de\u011filse geriye d\u00f6n\u00fck d\u00f6k\u00fcm \u00fcretilemez.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">systemctl status kdump 2&gt;\/dev\/null || true\nls -la \/var\/crash 2&gt;\/dev\/null || true\nmount | grep -E &#039;pstore|ramoops&#039; || true<\/code><\/pre>\n<p>Bu komutlar yaln\u0131zca mevcut durumu g\u00f6sterir. Kdump yap\u0131land\u0131rmas\u0131n\u0131, da\u011f\u0131t\u0131m belgelerindeki \u00e7ekirdek parametreleri ve dump hedefiyle birlikte uygulay\u0131n; \u00fcretim sunucusunda rastgele <code>crashkernel<\/code> de\u011feri eklemeyin. Etkinle\u015ftirme sonras\u0131nda kontroll\u00fc bir panic testi ancak bak\u0131m penceresi, yedek ve hizmet kesintisi kabul\u00fc varsa yap\u0131lmal\u0131d\u0131r.<\/p>\n<h2><span id=\"Degisiklik_sonrasi_dogrulama\">De\u011fi\u015fiklik sonras\u0131 do\u011frulama<\/span><\/h2>\n<p>Sunucu yeniden a\u00e7\u0131ld\u0131\u011f\u0131nda SSH ba\u011flant\u0131s\u0131n\u0131n kurulmas\u0131 tek ba\u015f\u0131na \u00e7\u00f6z\u00fcm kan\u0131t\u0131 de\u011fildir. A\u015fa\u011f\u0131daki s\u0131rayla do\u011frulama yap\u0131n:<\/p>\n<ol>\n<li>\u00c7al\u0131\u015fan kernel ve a\u00e7\u0131l\u0131\u015f zaman\u0131n\u0131 kaydedin: <code>uname -r<\/code> ve <code>uptime -s<\/code>.<\/li>\n<li>Son a\u00e7\u0131l\u0131\u015fta yeni panic, Oops, I\/O veya dosya sistemi hatas\u0131 olup olmad\u0131\u011f\u0131n\u0131 inceleyin.<\/li>\n<li>K\u00f6k ve boot b\u00f6l\u00fcmlerinde bo\u015f alan bulundu\u011funu kontrol edin.<\/li>\n<li>A\u011f aray\u00fcz\u00fcn\u00fc, DNS \u00e7\u00f6z\u00fcmlemesini ve g\u00fcvenlik duvar\u0131n\u0131 test edin.<\/li>\n<li>Veritaban\u0131, web sunucusu, PHP-FPM, kuyruk i\u015f\u00e7ileri ve zamanlanm\u0131\u015f g\u00f6revlerin durumunu ayr\u0131 ayr\u0131 kontrol edin.<\/li>\n<li>Uygulama \u00fczerinden basit bir okuma ve gerekiyorsa kontroll\u00fc yazma testi yap\u0131n.<\/li>\n<li>\u0130zleme sisteminde yeniden ba\u015flama, gecikme, disk ve bellek alarmlar\u0131n\u0131n normale d\u00f6nd\u00fc\u011f\u00fcn\u00fc do\u011frulay\u0131n.<\/li>\n<\/ol>\n<p>Son kernel s\u00fcr\u00fcm\u00fcn\u00fc hemen varsay\u0131lan yapmadan \u00f6nce en az\u0131ndan bir kontroll\u00fc yeniden ba\u015flatma plan\u0131 olu\u015fturun. Eski \u00e7al\u0131\u015fan kernel&#8217;i, geri d\u00f6n\u00fc\u015f i\u00e7in yeterli s\u00fcre boyunca sistemde tutun; paket temizli\u011fi yapacaksan\u0131z hangi s\u00fcr\u00fcm\u00fcn kurtarma se\u00e7ene\u011fi olarak kalaca\u011f\u0131n\u0131 \u00f6nceden belirleyin.<\/p>\n<p>Tekrarlayan ar\u0131zalar i\u00e7in olay sonras\u0131 not haz\u0131rlay\u0131n: belirtiler, saat, son de\u011fi\u015fiklik, kullan\u0131lan kernel, log par\u00e7alar\u0131, yap\u0131lan d\u00fczeltme ve do\u011frulama sonucu. Linux sunucularda yama ak\u0131\u015f\u0131n\u0131 belirlemek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/linux-sunucularda-ve-web-uygulamalarinda-yama-yonetimi-otomatik\/\">yama y\u00f6netimi yakla\u015f\u0131m\u0131n\u0131<\/a> inceleyebilir; \u00fcretim \u00f6ncesi \u00e7ekirdek g\u00fcncellemelerini test ve geri d\u00f6n\u00fc\u015f ad\u0131mlar\u0131yla planlayabilirsiniz.<\/p>\n<p>Birden fazla disk veya host katman\u0131 etkileniyorsa tek sunucudaki d\u00fczeltme yeterli olmayabilir. <a href=\"https:\/\/www.dchost.com\/blog\/hosting-tarafinda-felaket-kurtarma-provasi-cpanel-ve-vps-yedeklerini-test-etme-rehberi\/\">Felaket kurtarma provas\u0131n\u0131<\/a> d\u00fczenli uygulayarak yedeklerin ger\u00e7ekten geri y\u00fcklenebildi\u011fini, konsol eri\u015fiminin haz\u0131r oldu\u011funu ve RTO hedefinizin uygulanabilir oldu\u011funu do\u011frulay\u0131n.<\/p>\n<h2><span id=\"Sik_Sorulan_Sorular\">S\u0131k Sorulan Sorular<\/span><\/h2>\n<h3><span id=\"Kernel_panic_sunucudaki_verileri_siler_mi\">Kernel panic sunucudaki verileri siler mi?<\/span><\/h3>\n<p>Kernel panic tek ba\u015f\u0131na verileri silmez; ancak yazma i\u015flemi yar\u0131da kald\u0131ysa dosya sistemi tutars\u0131zl\u0131\u011f\u0131 veya son i\u015flemlerin kayb\u0131 olu\u015fabilir. Yeniden ba\u015flatma d\u00f6ng\u00fcs\u00fcn\u00fc s\u00fcrd\u00fcrmeden \u00f6nce yedek ve disk durumunu kontrol edin.<\/p>\n<h3><span id=\"Sunucu_yeniden_basliyor_ama_ekranda_panic_gorunmuyorsa_ne_yapilmali\">Sunucu yeniden ba\u015fl\u0131yor ama ekranda panic g\u00f6r\u00fcnm\u00fcyorsa ne yap\u0131lmal\u0131?<\/span><\/h3>\n<p>Sa\u011flay\u0131c\u0131 g\u00fc\u00e7 ve hypervisor kay\u0131tlar\u0131n\u0131, watchdog olaylar\u0131n\u0131 ve fiziksel donan\u0131m alarmlar\u0131n\u0131 inceleyin. Panic ekran\u0131 otomatik yeniden ba\u015flama nedeniyle g\u00f6r\u00fclemeyebilir; kal\u0131c\u0131 console log, kdump veya pstore gelecek olayda kan\u0131t sa\u011flayabilir.<\/p>\n<h3><span id=\"Eski_kernel_ile_acilan_sunucuda_yeni_kernel_silinmeli_mi\">Eski kernel ile a\u00e7\u0131lan sunucuda yeni kernel silinmeli mi?<\/span><\/h3>\n<p>Hemen silmeyin. \u00d6nce yeni kernel paketini, initramfs&#8217;i, \u00fc\u00e7\u00fcnc\u00fc taraf mod\u00fclleri ve boot alan\u0131n\u0131 inceleyin. Geri d\u00f6n\u00fc\u015f yolu korunurken sorunlu s\u00fcr\u00fcm\u00fc d\u00fczeltmek veya uygun bir g\u00fcncellemeyle de\u011fi\u015ftirmek daha g\u00fcvenlidir.<\/p>\n<h3><span id=\"Kernel_panic_ile_uygulamanin_beyaz_ekrani_ayni_sorun_mudur\">Kernel panic ile uygulaman\u0131n beyaz ekran\u0131 ayn\u0131 sorun mudur?<\/span><\/h3>\n<p>Hay\u0131r. Beyaz ekran \u00e7o\u011funlukla uygulama, PHP, tema, eklenti veya web sunucusu katman\u0131nda olu\u015fur; kernel panic ise i\u015fletim sisteminin \u00e7ekirdek katman\u0131nda kritik durmad\u0131r. SSH ve konsol eri\u015fimiyle hangi katman\u0131n etkilendi\u011fini ay\u0131r\u0131n.<\/p>\n<h2><span id=\"Uygulanabilir_kontrol_listesi\">Uygulanabilir kontrol listesi<\/span><\/h2>\n<ul>\n<li>Konsol eri\u015fimini a\u00e7\u0131n ve panic ekran\u0131n\u0131 kaydedin.<\/li>\n<li>Yeniden ba\u015flama saatini, son de\u011fi\u015fiklikleri ve sa\u011flay\u0131c\u0131 olaylar\u0131n\u0131 e\u015fle\u015ftirin.<\/li>\n<li>\u00c7al\u0131\u015fan veya eski kernel ile a\u00e7\u0131l\u0131\u015f\u0131 deneyin; \u00e7al\u0131\u015fan s\u00fcr\u00fcm\u00fc silmeyin.<\/li>\n<li><code>journalctl<\/code>, <code>dmesg<\/code>, disk, dosya sistemi, bellek ve donan\u0131m kay\u0131tlar\u0131n\u0131 birlikte inceleyin.<\/li>\n<li>De\u011fi\u015fiklikten \u00f6nce snapshot veya do\u011frulanm\u0131\u015f yedek ve geri d\u00f6n\u00fc\u015f ad\u0131m\u0131 haz\u0131rlay\u0131n.<\/li>\n<li>Yaln\u0131zca belirlenen katmana dar kapsaml\u0131 d\u00fczeltme uygulay\u0131n.<\/li>\n<li>A\u00e7\u0131l\u0131\u015f\u0131, kritik servisleri, disk durumunu ve izleme alarmlar\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li>Tekrarlayan olaylar i\u00e7in kdump, pstore ve kal\u0131c\u0131 journal se\u00e7eneklerini planlay\u0131n.<\/li>\n<\/ul>\n<p>\u0130lk sonraki ad\u0131m\u0131n\u0131z, sunucuya konsoldan eri\u015fip son panic \u00e7\u0131kt\u0131s\u0131n\u0131 ve <code>journalctl -b -1 -k<\/code> sonucunu g\u00fcvenli bir konuma almakt\u0131r. Bu iki kan\u0131t, yeniden kurulum gibi geri d\u00f6n\u00fc\u015f\u00fc zor bir i\u015flem yapmadan do\u011fru kurtarma yolunu se\u00e7menizi sa\u011flar.<\/p>\n<p>Emre<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>VPS veya fiziksel sunucu kernel panic nedeniyle yeniden ba\u015fl\u0131yor ve SSH eri\u015fimi kesiliyorsa konsol, log, eski kernel ve rescue ortam\u0131yla kontroll\u00fc te\u015fhis ve kurtarma ad\u0131mlar\u0131n\u0131 \u00f6\u011frenin.<\/p>\n","protected":false},"author":4,"featured_media":5553,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[25],"tags":[572,573,60,574,123,95],"class_list":["post-5557","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-sunucu","tag-kernel-panic","tag-kurtarma","tag-linux","tag-sistem-yonetimi","tag-sunucu-yonetimi","tag-vps"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5557","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=5557"}],"version-history":[{"count":1,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5557\/revisions"}],"predecessor-version":[{"id":5559,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5557\/revisions\/5559"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/5553"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=5557"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=5557"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=5557"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}