{"id":3406,"date":"2025-12-26T16:54:03","date_gmt":"2025-12-26T13:54:03","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/vps-disk-kullanimi-ve-logrotate-ayarlariyla-no-space-left-on-device-hatasini-onlemek\/"},"modified":"2025-12-26T16:54:03","modified_gmt":"2025-12-26T13:54:03","slug":"vps-disk-kullanimi-ve-logrotate-ayarlariyla-no-space-left-on-device-hatasini-onlemek","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/vps-disk-kullanimi-ve-logrotate-ayarlariyla-no-space-left-on-device-hatasini-onlemek\/","title":{"rendered":"VPS Disk Kullan\u0131m\u0131 ve logrotate Ayarlar\u0131yla \u201cNo Space Left on Device\u201d Hatas\u0131n\u0131 \u00d6nlemek"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>VPS sunucularda en can s\u0131k\u0131c\u0131 hatalardan biri, uygulaman\u0131z tam da i\u015f ba\u015f\u0131ndayken kar\u015f\u0131n\u0131za \u00e7\u0131kan <strong>\u201cNo space left on device\u201d<\/strong> uyar\u0131s\u0131d\u0131r. \u00c7o\u011fu zaman bu hata ger\u00e7ekten &#8220;b\u00fct\u00fcn diski doldurdum&#8221; anlam\u0131na gelmez; yanl\u0131\u015f log ayarlar\u0131, kontrols\u00fcz yedekler, sistem g\u00fcnl\u00fckleri veya ge\u00e7ici dosyalar y\u00fcz\u00fcnden disk alan\u0131n\u0131z\u0131n kritik bir b\u00f6l\u00fcm\u00fc sessizce t\u00fcketilir. Sonu\u00e7ta veritaban\u0131n\u0131z yazamaz, web sunucunuz log \u00fcretemez, hatta baz\u0131 durumlarda SSH bile stabil \u00e7al\u0131\u015famaz.<\/p>\n<p>DCHost olarak sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ger\u00e7ek vakalar\u0131n b\u00fcy\u00fck k\u0131sm\u0131nda, sorun do\u011frudan disk kapasitesinden ziyade <strong>log y\u00f6netimi ve logrotate yap\u0131land\u0131rmas\u0131<\/strong> ile ilgilidir. Do\u011fru disk planlamas\u0131, d\u00fczenli izleme ve iyi kurgulanm\u0131\u015f logrotate ayarlar\u0131yla bu hatay\u0131 neredeyse tamamen hayat\u0131n\u0131zdan \u00e7\u0131karabilirsiniz. Bu yaz\u0131da, <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> disk kullan\u0131m\u0131n\u0131 nas\u0131l okuyaca\u011f\u0131n\u0131z\u0131, hangi klas\u00f6rlerin diski patlatt\u0131\u011f\u0131n\u0131, <strong>logrotate<\/strong> ile log dosyalar\u0131n\u0131z\u0131 nas\u0131l kontrol alt\u0131na alaca\u011f\u0131n\u0131z\u0131 ve &#8220;No space left on device&#8221; hatas\u0131n\u0131 kal\u0131c\u0131 olarak nas\u0131l \u00f6nleyece\u011finizi ad\u0131m ad\u0131m anlataca\u011f\u0131m.<\/p>\n<div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#VPS_Disk_Kullanimi_Neden_Bir_Anda_Dolar\"><span class=\"toc_number toc_depth_1\">1<\/span> VPS Disk Kullan\u0131m\u0131 Neden Bir Anda Dolar?<\/a><\/li><li><a href=\"#No_Space_Left_on_Device_Hatasini_Tanimak_ve_Hizli_Teshis\"><span class=\"toc_number toc_depth_1\">2<\/span> \u201cNo Space Left on Device\u201d Hatas\u0131n\u0131 Tan\u0131mak ve H\u0131zl\u0131 Te\u015fhis<\/a><\/li><li><a href=\"#VPSte_Loglarin_Diski_Doldurmasini_Onlemek\"><span class=\"toc_number toc_depth_1\">3<\/span> VPS\u2019te Loglar\u0131n Diski Doldurmas\u0131n\u0131 \u00d6nlemek<\/a><ul><li><a href=\"#logrotate_Nedir_Nasil_Calisir\"><span class=\"toc_number toc_depth_2\">3.1<\/span> logrotate Nedir, Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/a><\/li><li><a href=\"#Temel_logrotate_Konfigurasyon_Ornekleri\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Temel logrotate Konfig\u00fcrasyon \u00d6rnekleri<\/a><\/li><li><a href=\"#systemd_journal_Boyutunu_Sinirlandirmak\"><span class=\"toc_number toc_depth_2\">3.3<\/span> systemd journal Boyutunu S\u0131n\u0131rland\u0131rmak<\/a><\/li><\/ul><\/li><li><a href=\"#VPS_Disk_Kullanimini_Adim_Adim_Analiz_Etmek\"><span class=\"toc_number toc_depth_1\">4<\/span> VPS Disk Kullan\u0131m\u0131n\u0131 Ad\u0131m Ad\u0131m Analiz Etmek<\/a><ul><li><a href=\"#Gecici_Dosyalar_ve_tmp_Temizligi\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Ge\u00e7ici Dosyalar ve \/tmp Temizli\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#logrotate_Stratejisi_Zaman_mi_Boyut_mu\"><span class=\"toc_number toc_depth_1\">5<\/span> logrotate Stratejisi: Zaman m\u0131 Boyut mu?<\/a><ul><li><a href=\"#MySQLMariaDB_ve_Diger_Servis_Loglari\"><span class=\"toc_number toc_depth_2\">5.1<\/span> MySQL\/MariaDB ve Di\u011fer Servis Loglar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#VPS_Disk_Kullanimini_Proaktif_Yonetmek\"><span class=\"toc_number toc_depth_1\">6<\/span> VPS Disk Kullan\u0131m\u0131n\u0131 Proaktif Y\u00f6netmek<\/a><ul><li><a href=\"#Otomatik_Temizlik_Yedekleme_ve_Merkezi_Loglama\"><span class=\"toc_number toc_depth_2\">6.1<\/span> Otomatik Temizlik, Yedekleme ve Merkezi Loglama<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Uzerinde_VPS_Kullaniyorsaniz_Nelere_Dikkat_Etmelisiniz\"><span class=\"toc_number toc_depth_1\">7<\/span> DCHost \u00dczerinde VPS Kullan\u0131yorsan\u0131z Nelere Dikkat Etmelisiniz?<\/a><\/li><li><a href=\"#Gercek_Dunya_Senaryolari_Disk_Dolma_Vakalarindan_Cikan_Dersler\"><span class=\"toc_number toc_depth_1\">8<\/span> Ger\u00e7ek D\u00fcnya Senaryolar\u0131: Disk Dolma Vakalar\u0131ndan \u00c7\u0131kan Dersler<\/a><ul><li><a href=\"#Senaryo_1_WordPress_debuglog_Dosyasinin_Diski_Gommesi\"><span class=\"toc_number toc_depth_2\">8.1<\/span> Senaryo 1: WordPress debug.log Dosyas\u0131n\u0131n Diski G\u00f6mmesi<\/a><\/li><li><a href=\"#Senaryo_2_MySQL_Slow_Query_Logunun_Kontrolden_Cikmasi\"><span class=\"toc_number toc_depth_2\">8.2<\/span> Senaryo 2: MySQL Slow Query Log\u2019unun Kontrolden \u00c7\u0131kmas\u0131<\/a><\/li><li><a href=\"#Senaryo_3_systemd_journal_ve_varlogjournal_Sismesi\"><span class=\"toc_number toc_depth_2\">8.3<\/span> Senaryo 3: systemd journal ve \/var\/log\/journal \u015ei\u015fmesi<\/a><\/li><\/ul><\/li><li><a href=\"#Ozet_ve_Yol_Haritasi\"><span class=\"toc_number toc_depth_1\">9<\/span> \u00d6zet ve Yol Haritas\u0131<\/a><\/li><\/ul><\/div>\n<h2><span id=\"VPS_Disk_Kullanimi_Neden_Bir_Anda_Dolar\">VPS Disk Kullan\u0131m\u0131 Neden Bir Anda Dolar?<\/span><\/h2>\n<p>VPS diskinin \u201cbir anda\u201d doluyor gibi g\u00f6r\u00fcnmesinin birka\u00e7 tipik sebebi var. Bunlar\u0131 bilmek, te\u015fhis s\u00fcresini dakikalardan saniyelere indirir:<\/p>\n<ul>\n<li><strong>Log dosyalar\u0131 kontrols\u00fcz b\u00fcy\u00fcr:<\/strong> Nginx\/Apache eri\u015fim ve hata loglar\u0131, PHP hata loglar\u0131, uygulama loglar\u0131, veritaban\u0131 slow query loglar\u0131.<\/li>\n<li><strong>Otomatik yedekler ayn\u0131 diske at\u0131l\u0131r:<\/strong> G\u00fcnl\u00fck veya saatlik full yedekler \/home ya da \/var alt\u0131nda saklan\u0131r, logrotate yoksa h\u0131zla onlarca GB olur.<\/li>\n<li><strong>Ge\u00e7ici dizinler temizlenmez:<\/strong> \/tmp, \/var\/tmp, uygulamalar\u0131n kendi temp klas\u00f6rleri.<\/li>\n<li><strong>systemd journal s\u0131n\u0131rs\u0131z b\u00fcy\u00fcr:<\/strong> \/var\/log\/journal alt\u0131nda GB\u2019larca binary log birikir.<\/li>\n<li><strong>Uygulama cache ve upload klas\u00f6rleri:<\/strong> \u00d6zellikle medya a\u011f\u0131rl\u0131kl\u0131 sitelerde eski cache dosyalar\u0131 ve kullan\u0131lmayan upload\u2019lar.<\/li>\n<li><strong>Docker ve container loglar\u0131:<\/strong> \/var\/lib\/docker alt\u0131nda container loglar\u0131 ve imajlar\u0131 h\u0131zla \u015fi\u015fer.<\/li>\n<\/ul>\n<p>Bu noktada loglar\u0131n nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 anlamak kritik. E\u011fer hen\u00fcz loglar\u0131n neyi ifade etti\u011fini tam oturtmad\u0131ysan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/hosting-sunucu-loglarini-okumayi-ogrenin-apache-ve-nginx-ile-4xx-5xx-hatalarini-teshis-rehberi\/\">Apache ve Nginx loglar\u0131n\u0131 okuyarak 4xx\u20135xx hatalar\u0131n\u0131 te\u015fhis etmeyi anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> mutlaka g\u00f6z at\u0131n. Loglar\u0131 anlamadan logrotate ayar\u0131 yapmak, g\u00f6zleri kapal\u0131 disk y\u00f6netimi yapmak gibidir.<\/p>\n<h2><span id=\"No_Space_Left_on_Device_Hatasini_Tanimak_ve_Hizli_Teshis\">\u201cNo Space Left on Device\u201d Hatas\u0131n\u0131 Tan\u0131mak ve H\u0131zl\u0131 Te\u015fhis<\/span><\/h2>\n<p>Bu hatay\u0131 genelde \u015fu \u00e7\u0131kt\u0131larda g\u00f6r\u00fcrs\u00fcn\u00fcz:<\/p>\n<ul>\n<li>Uygulama loglar\u0131nda veya terminalde: <code>write failed: No space left on device<\/code><\/li>\n<li>MySQL\/PostgreSQL loglar\u0131nda disk yazma hatalar\u0131<\/li>\n<li>Nginx\/Apache error loglar\u0131nda log dosyas\u0131na yaz\u0131lamad\u0131\u011f\u0131na dair kay\u0131tlar<\/li>\n<\/ul>\n<p>\u0130lk i\u015f olarak \u015fu temel komutlarla durumu netle\u015ftirin:<\/p>\n<ul>\n<li><code>df -h<\/code> \u2013 Disk kullan\u0131m\u0131n\u0131 insan okunabilir formatta g\u00f6sterir (GB, MB).<\/li>\n<li><code>df -i<\/code> \u2013 <strong>inode<\/strong> kullan\u0131m\u0131n\u0131 g\u00f6sterir. Bazen alan dolmaz, inode biter ve yine ayn\u0131 hatay\u0131 al\u0131rs\u0131n\u0131z.<\/li>\n<li><code>du -sh \/* 2&gt;\/dev\/null<\/code> \u2013 K\u00f6k dizin alt\u0131ndaki klas\u00f6rlerin kabaca ne kadar yer kaplad\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcrs\u00fcn\u00fcz.<\/li>\n<li><code>du -sh \/var\/* \/home\/* 2&gt;\/dev\/null<\/code> \u2013 \u00d6zellikle log ve kullan\u0131c\u0131 dosyalar\u0131n\u0131n oldu\u011fu yerleri inceleyin.<\/li>\n<\/ul>\n<p>E\u011fer df -h \u00e7\u0131kt\u0131s\u0131nda \u00f6zellikle <strong>\/<\/strong> veya <strong>\/var<\/strong> y\u00fczde 100\u2019e yak\u0131nsa, diski as\u0131l dolduran kayna\u011f\u0131 bulmak i\u00e7in ad\u0131m ad\u0131m derine inmeniz gerekir. \u0130\u015f genellikle \/var\/log, \/var\/lib\/mysql, \/home veya \/var\/www alt\u0131nda biter.<\/p>\n<h2><span id=\"VPSte_Loglarin_Diski_Doldurmasini_Onlemek\">VPS\u2019te Loglar\u0131n Diski Doldurmas\u0131n\u0131 \u00d6nlemek<\/span><\/h2>\n<p>Linux tabanl\u0131 VPS\u2019lerin kalbi \/var\/log dizinidir. Burada:<\/p>\n<ul>\n<li>Web sunucusu loglar\u0131 (Nginx, Apache)<\/li>\n<li>Veritaban\u0131 loglar\u0131 (MySQL\/MariaDB, PostgreSQL)<\/li>\n<li>Mail sunucusu loglar\u0131<\/li>\n<li>SSH, sistem ve kernel loglar\u0131<\/li>\n<li>Uygulama servis loglar\u0131<\/li>\n<\/ul>\n<p>bulunur. Bunlar\u0131n \u00e7o\u011fu metin dosyas\u0131d\u0131r ve g\u00fcnlerce, haftalarca d\u00f6nd\u00fcr\u00fclmeden tutulursa 10 GB ve \u00fczeri boyutlara rahatl\u0131kla ula\u015f\u0131r.<\/p>\n<p>Bir noktadan sonra tek sunucuda logla bo\u011fu\u015fmak yerine merkezi \u00e7\u00f6z\u00fcmlere ge\u00e7mek isteyebilirsiniz. Bu noktada <a href=\"https:\/\/www.dchost.com\/blog\/vps-log-yonetimi-nasil-rayina-oturur-grafana-loki-promtail-ile-merkezi-loglama-tutma-sureleri-ve-alarm-kurallari\/\">VPS log y\u00f6netimini Grafana Loki + Promtail ile merkezi hale getirmeyi anlatt\u0131\u011f\u0131m\u0131z rehberi<\/a> incelemenizi \u00f6neririm. Ancak tek bir VPS\u2019te bile olsan\u0131z, ilk yapman\u0131z gereken \u015fey <strong>logrotate<\/strong>\u2019i do\u011fru kurmak.<\/p>\n<h3><span id=\"logrotate_Nedir_Nasil_Calisir\">logrotate Nedir, Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/span><\/h3>\n<p><strong>logrotate<\/strong>, Linux sistemlerde log dosyalar\u0131n\u0131 otomatik d\u00f6nd\u00fcr\u00fcp (rotate), s\u0131k\u0131\u015ft\u0131r\u0131p (compress) belli bir s\u00fcre sonra silen k\u00fc\u00e7\u00fck ama hayati bir ara\u00e7t\u0131r. Genellikle g\u00fcnl\u00fck olarak cron veya systemd timer ile \u00e7al\u0131\u015f\u0131r ve \u015fu i\u015fleri yapar:<\/p>\n<ul>\n<li>Belli bir boyuta ya da zamana ula\u015fm\u0131\u015f log dosyalar\u0131n\u0131 \u201cd\u00f6nd\u00fcr\u00fcr\u201d.<\/li>\n<li>Eski log dosyalar\u0131n\u0131 s\u0131k\u0131\u015ft\u0131r\u0131r (gzip ile .gz uzant\u0131l\u0131 hale getirir).<\/li>\n<li>Belirli say\u0131da eski kopyay\u0131 saklar (\u00f6rn. son 7 dosya).<\/li>\n<li>\u0130ste\u011fe g\u00f6re d\u00f6nd\u00fcrme \u00f6ncesi\/sonras\u0131 komutlar \u00e7al\u0131\u015ft\u0131r\u0131r (\u00f6rn. servis reload).<\/li>\n<\/ul>\n<p>Konfig\u00fcrasyon mant\u0131\u011f\u0131 iki katmandan olu\u015fur:<\/p>\n<ul>\n<li><code>\/etc\/logrotate.conf<\/code> \u2013 Genel ayarlar ve global varsay\u0131lanlar.<\/li>\n<li><code>\/etc\/logrotate.d\/<\/code> \u2013 Servis bazl\u0131, detayl\u0131 logrotate dosyalar\u0131.<\/li>\n<\/ul>\n<p>Sisteminizde neler tan\u0131ml\u0131 g\u00f6rmek i\u00e7in:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">ls -lah \/etc\/logrotate.d\/\n<\/code><\/pre>\n<p>komutunu \u00e7al\u0131\u015ft\u0131rabilirsiniz.<\/p>\n<h3><span id=\"Temel_logrotate_Konfigurasyon_Ornekleri\">Temel logrotate Konfig\u00fcrasyon \u00d6rnekleri<\/span><\/h3>\n<p>\u00d6rnekleri basit ve pratik tutal\u0131m. Diyelim ki Nginx loglar\u0131n\u0131z \/var\/log\/nginx\/access.log ve \/var\/log\/nginx\/error.log alt\u0131nda.<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/var\/log\/nginx\/*.log {\n    daily\n    missingok\n    rotate 14\n    compress\n    delaycompress\n    notifempty\n    create 0640 www-data adm\n    sharedscripts\n    postrotate\n        [ -s \/run\/nginx.pid ] &amp;&amp; kill -USR1 $(cat \/run\/nginx.pid)\n    endscript\n}\n<\/code><\/pre>\n<p>Bu ayar ne yapar?<\/p>\n<ul>\n<li><strong>daily:<\/strong> Loglar\u0131 g\u00fcnl\u00fck d\u00f6nd\u00fcr\u00fcr.<\/li>\n<li><strong>rotate 14:<\/strong> Son 14 dosyay\u0131 saklar (yakla\u015f\u0131k 2 haftal\u0131k log).<\/li>\n<li><strong>compress\/delaycompress:<\/strong> Eski loglar\u0131 gzip ile s\u0131k\u0131\u015ft\u0131r\u0131r, en g\u00fcncel d\u00f6nd\u00fcr\u00fclm\u00fc\u015f dosyay\u0131 bir sonraki turda s\u0131k\u0131\u015ft\u0131r\u0131r.<\/li>\n<li><strong>notifempty:<\/strong> Bo\u015f dosyalar i\u00e7in d\u00f6nd\u00fcrme yapmaz.<\/li>\n<li><strong>create:<\/strong> Yeni log dosyas\u0131n\u0131 belirtilen izin ve kullan\u0131c\u0131\/grup ile olu\u015fturur.<\/li>\n<li><strong>postrotate:<\/strong> Nginx\u2019e USR1 sinyali g\u00f6nderip, yeni log dosyas\u0131na yazmaya ba\u015flamas\u0131n\u0131 sa\u011flar.<\/li>\n<\/ul>\n<p>Benzer mant\u0131kla Apache, PHP-FPM veya \u00f6zel uygulama loglar\u0131n\u0131z\u0131 da y\u00f6netebilirsiniz. \u00d6rne\u011fin kendi uygulaman\u0131z <code>\/var\/www\/app\/storage\/logs\/app.log<\/code> dosyas\u0131na yaz\u0131yorsa:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/var\/www\/app\/storage\/logs\/app.log {\n    size 100M\n    rotate 10\n    compress\n    missingok\n    notifempty\n    copytruncate\n}\n<\/code><\/pre>\n<p>Burada <strong>size 100M<\/strong> ile dosya boyuta g\u00f6re d\u00f6nd\u00fcr\u00fcl\u00fcr; trafik dalgal\u0131ysa ve g\u00fcnl\u00fck rota yetersiz kal\u0131yorsa bu daha g\u00fcvenli bir yakla\u015f\u0131md\u0131r. <strong>copytruncate<\/strong>, dosyan\u0131n eski halini kopyalayarak yeni dosyay\u0131 s\u0131f\u0131rlar; uygulama log dosyas\u0131n\u0131 a\u00e7\u0131k tutuyorsa bu y\u00f6ntem i\u015f g\u00f6r\u00fcr.<\/p>\n<p>Loglar\u0131n ne kadar s\u00fcre saklanaca\u011f\u0131, sadece disk y\u00f6netimi de\u011fil ayn\u0131 zamanda hukuki ve kurumsal gereksinimlerle de ilgilidir. Bu konuda daha geni\u015f \u00e7er\u00e7eve g\u00f6rmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/hosting-ve-e-posta-altyapisinda-log-saklama-sureleri\/\">hosting ve e\u2011posta altyap\u0131s\u0131nda log saklama s\u00fcrelerini anlatt\u0131\u011f\u0131m\u0131z rehberi<\/a> okuman\u0131z\u0131 \u00f6neririm.<\/p>\n<h3><span id=\"systemd_journal_Boyutunu_Sinirlandirmak\">systemd journal Boyutunu S\u0131n\u0131rland\u0131rmak<\/span><\/h3>\n<p>Bir\u00e7ok modern da\u011f\u0131t\u0131mda syslog yerine <strong>systemd-journald<\/strong> kullan\u0131l\u0131r ve loglar \/var\/log\/journal alt\u0131nda binary formatta tutulur. Varsay\u0131lan ayarlar genellikle agresif de\u011fildir ama uzun s\u00fcre dokunulmad\u0131\u011f\u0131nda birka\u00e7 GB\u2019\u0131 rahatl\u0131kla a\u015fabilir.<\/p>\n<p>\u00d6nce mevcut kullan\u0131m\u0131n\u0131z\u0131 g\u00f6r\u00fcn:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">journalctl --disk-usage\n<\/code><\/pre>\n<p>\u00d6rne\u011fin 8 GB \u00fcst\u00fc bir kullan\u0131m g\u00f6r\u00fcyorsan\u0131z s\u0131n\u0131r koyman\u0131n zaman\u0131 gelmi\u015f demektir. \/etc\/systemd\/journald.conf dosyas\u0131n\u0131 a\u00e7\u0131n:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">[Journal]\nSystemMaxUse=1G\nSystemMaxFileSize=200M\nMaxRetentionSec=1month\n<\/code><\/pre>\n<p>Sonra:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">systemctl restart systemd-journald\n<\/code><\/pre>\n<p>komutuyla servisi yeniden ba\u015flat\u0131n. Acil temizlik gerekti\u011finde:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">journalctl --vacuum-size=500M\n<\/code><\/pre>\n<p>ile loglar\u0131n toplam boyutunu 500 MB\u2019a indirebilirsiniz.<\/p>\n<h2><span id=\"VPS_Disk_Kullanimini_Adim_Adim_Analiz_Etmek\">VPS Disk Kullan\u0131m\u0131n\u0131 Ad\u0131m Ad\u0131m Analiz Etmek<\/span><\/h2>\n<p>Disk doldu\u011funda panik yapmak yerine sistematik ilerlemek i\u015finizi kolayla\u015ft\u0131r\u0131r. Sahada en \u00e7ok kulland\u0131\u011f\u0131m\u0131z ad\u0131mlar\u0131 payla\u015fay\u0131m:<\/p>\n<ol>\n<li><strong>Hangi disk\/partition dolu?<\/strong><br \/><code>df -h<\/code> ile kontrol edin. \u00d6zellikle \/, \/var, \/home gibi b\u00f6l\u00fcmleri inceleyin.<\/li>\n<li><strong>Hangi klas\u00f6r \u015fi\u015fmi\u015f?<\/strong><br \/><code>du -sh \/* 2&gt;\/dev\/null<\/code>, ard\u0131ndan problemli klas\u00f6r i\u00e7in benzer komut: <code>du -sh \/var\/* 2&gt;\/dev\/null<\/code>.<\/li>\n<li><strong>Log klas\u00f6rlerini kontrol edin:<\/strong><br \/><code>du -sh \/var\/log\/* 2&gt;\/dev\/null<\/code> ile hangi loglar\u0131n GB seviyesine \u00e7\u0131kt\u0131\u011f\u0131n\u0131 bulun.<\/li>\n<li><strong>Yedek ve upload dizinlerini inceleyin:<\/strong><br \/>\u00d6rne\u011fin \/home\/backup, \/var\/backups, \/var\/www\/site.com\/storage\/app\/backups gibi klas\u00f6rlere bak\u0131n.<\/li>\n<li><strong>inode kullan\u0131m\u0131n\u0131 kontrol edin:<\/strong><br \/><code>df -i<\/code> ile %100\u2019e yakla\u015fm\u0131\u015f inode olup olmad\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcn. \u00c7ok k\u00fc\u00e7\u00fck dosya say\u0131s\u0131 fazla ise bu ortaya \u00e7\u0131kar.<\/li>\n<\/ol>\n<p>Yeni bir VPS ald\u0131ysan\u0131z ve hen\u00fcz temel bak\u0131mlar\u0131 yapmad\u0131ysan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/yeni-vpste-ilk-24-saat-guncelleme-guvenlik-duvari-ve-kullanici-hesaplari\/\">\u201cYeni VPS\u2019te \u0130lk 24 Saat\u201d kontrol listemiz<\/a> disk ve log taraf\u0131nda da sa\u011flam bir ba\u015flang\u0131\u00e7 yapman\u0131za yard\u0131mc\u0131 olur.<\/p>\n<h3><span id=\"Gecici_Dosyalar_ve_tmp_Temizligi\">Ge\u00e7ici Dosyalar ve \/tmp Temizli\u011fi<\/span><\/h3>\n<p>\/tmp ve \/var\/tmp dizinleri; upload i\u015flemlerinde, s\u0131k\u0131\u015ft\u0131rma\/a\u00e7ma operasyonlar\u0131nda, baz\u0131 uygulamalar\u0131n ge\u00e7ici dosya yaz\u0131mlar\u0131nda yo\u011fun kullan\u0131l\u0131r. Normalde da\u011f\u0131t\u0131m\u0131n\u0131z bunlar\u0131 periyodik olarak temizler; ancak baz\u0131 durumlarda bu temizlik yap\u0131land\u0131r\u0131lmam\u0131\u015f olabilir.<\/p>\n<p>systemd tabanl\u0131 sistemlerde \/etc\/tmpfiles.d alt\u0131nda kurallar tan\u0131mlayarak belirli ya\u015f\u0131n \u00fcst\u00fcndeki dosyalar\u0131n otomatik silinmesini sa\u011flayabilirsiniz. \u00d6rne\u011fin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\"># \/etc\/tmpfiles.d\/custom-tmp.conf\nD \/tmp 1777 root root 7d\n<\/code><\/pre>\n<p>Bu kural, \/tmp i\u00e7indeki 7 g\u00fcnden eski dosyalar\u0131n temizlenmesini sa\u011flar. Fakat kritik uygulamalar\u0131n\u0131z\u0131n tmp kullan\u0131m \u015fekline hakim olmadan agresif s\u00fcreler vermekten ka\u00e7\u0131n\u0131n.<\/p>\n<h2><span id=\"logrotate_Stratejisi_Zaman_mi_Boyut_mu\">logrotate Stratejisi: Zaman m\u0131 Boyut mu?<\/span><\/h2>\n<p>Loglar\u0131 nas\u0131l d\u00f6nd\u00fcrece\u011finize karar verirken iki temel soru var:<\/p>\n<ul>\n<li><strong>Zamana g\u00f6re d\u00f6nd\u00fcrme (daily, weekly, monthly)<\/strong><\/li>\n<li><strong>Boyuta g\u00f6re d\u00f6nd\u00fcrme (size 100M, size 1G)<\/strong><\/li>\n<\/ul>\n<p>Ger\u00e7ek d\u00fcnyada genellikle hibrit bir yakla\u015f\u0131m daha mant\u0131kl\u0131:<\/p>\n<ul>\n<li>D\u00fc\u015f\u00fck trafikli siteler i\u00e7in <strong>weekly + rotate 8<\/strong> (yakla\u015f\u0131k 2 ay log).<\/li>\n<li>Orta trafikli siteler i\u00e7in <strong>daily + rotate 14<\/strong> (2 hafta log).<\/li>\n<li>Y\u00fcksek trafikli projeler i\u00e7in <strong>size 100M + rotate 30<\/strong> gibi boyut bazl\u0131 d\u00f6nd\u00fcrme.<\/li>\n<\/ul>\n<p>E\u2011ticaret veya y\u00fcksek trafik senaryolar\u0131nda, uygulama ve veritaban\u0131 optimizasyonu da log hacmini do\u011frudan etkiler. \u00d6rne\u011fin <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-icin-mysql-innodb-tuning-kontrol-listesi-buffer-pool-indeksleme-ve-slow-query-analizi-nasil-akillica-yapilir\/\">WooCommerce i\u00e7in MySQL\/InnoDB tuning rehberinde<\/a> anlatt\u0131\u011f\u0131m\u0131z \u015fekilde slow query log\u2019unu optimize etmek, hem performans hem disk kullan\u0131m\u0131 a\u00e7\u0131s\u0131ndan \u00e7ift tarafl\u0131 kazan\u00e7 sa\u011flar.<\/p>\n<h3><span id=\"MySQLMariaDB_ve_Diger_Servis_Loglari\">MySQL\/MariaDB ve Di\u011fer Servis Loglar\u0131<\/span><\/h3>\n<p>MySQL\/MariaDB taraf\u0131nda \u00f6zellikle \u00fc\u00e7 log t\u00fcr\u00fc diski doldurur:<\/p>\n<ul>\n<li>Error log<\/li>\n<li>Slow query log<\/li>\n<li>General query log (\u00e7o\u011fu zaman kapal\u0131 olmal\u0131)<\/li>\n<\/ul>\n<p>\u00d6rnek bir logrotate tan\u0131m\u0131:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/var\/log\/mysql\/*.log {\n    daily\n    missingok\n    rotate 10\n    compress\n    notifempty\n    create 0640 mysql adm\n    sharedscripts\n    postrotate\n        test -x \/usr\/bin\/mysqladmin || exit 0\n        \/usr\/bin\/mysqladmin flush-logs\n    endscript\n}\n<\/code><\/pre>\n<p>Benzer mant\u0131\u011f\u0131 mail sunucusu, PHP-FPM ve uygulama loglar\u0131na da uygulayabilirsiniz. \u00d6nemli olan, her b\u00fcy\u00fck log dosyas\u0131n\u0131n <strong>\/etc\/logrotate.d\/<\/strong> alt\u0131nda bir kar\u015f\u0131l\u0131\u011f\u0131 olmas\u0131d\u0131r.<\/p>\n<h2><span id=\"VPS_Disk_Kullanimini_Proaktif_Yonetmek\">VPS Disk Kullan\u0131m\u0131n\u0131 Proaktif Y\u00f6netmek<\/span><\/h2>\n<p>Diskin dolmas\u0131n\u0131 beklemek yerine, diskin dolma h\u0131z\u0131n\u0131 izlemek \u00e7ok daha sa\u011fl\u0131kl\u0131 bir yakla\u015f\u0131md\u0131r. Bunu iki seviyede ele alabilirsiniz:<\/p>\n<ul>\n<li><strong>Elle takip:<\/strong> Periyodik olarak df -h, du komutlar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131rmak.<\/li>\n<li><strong>Otomatik izleme ve alarm:<\/strong> Belirli bir y\u00fczdeye gelince e\u2011posta, Slack vb. uyar\u0131 almak.<\/li>\n<\/ul>\n<p>\u0130kinci yolu tercih ediyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/vps-izleme-ve-alarm-kurulumu-prometheus-grafana-ve-uptime-kuma-ile-baslangic\/\">Prometheus, Grafana ve Uptime Kuma ile VPS izleme ve alarm kurulumuna giri\u015f rehberimizi<\/a> mutlaka inceleyin. Disk kullan\u0131m\u0131 ve inode kullan\u0131m\u0131 i\u00e7in metrikleri toplay\u0131p, \u00f6rne\u011fin %80 \u00fczerine \u00e7\u0131k\u0131nca alarm \u00fcretmek i\u015finizi ciddi anlamda rahatlat\u0131r.<\/p>\n<h3><span id=\"Otomatik_Temizlik_Yedekleme_ve_Merkezi_Loglama\">Otomatik Temizlik, Yedekleme ve Merkezi Loglama<\/span><\/h3>\n<p>Sa\u011fl\u0131kl\u0131 bir VPS disk stratejisi \u00fc\u00e7 bacakl\u0131 olmal\u0131:<\/p>\n<ul>\n<li><strong>Log d\u00f6nd\u00fcrme ve s\u0131k\u0131\u015ft\u0131rma:<\/strong> logrotate + systemd journal limitleri.<\/li>\n<li><strong>Yedeklerin do\u011fru yerde tutulmas\u0131:<\/strong> M\u00fcmk\u00fcnse ayn\u0131 diskte devasa yedekler biriktirmemek; harici depolama veya Object Storage kullanmak.<\/li>\n<li><strong>Merkezi loglama:<\/strong> Uygun oldu\u011funda loglar\u0131 VPS d\u0131\u015f\u0131na ak\u0131tmak.<\/li>\n<\/ul>\n<p>\u00d6zellikle birden fazla VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> y\u00f6netiyorsan\u0131z, loglar\u0131 tek tek disklerde tutmak hem y\u00f6netim hem disk planlamas\u0131 a\u00e7\u0131s\u0131ndan yorucu olur. Bu durumda <a href=\"https:\/\/www.dchost.com\/blog\/birden-fazla-sunucuda-log-yonetimi-elk-ve-loki-stack-ile-merkezi-hosting-loglama\/\">ELK veya Loki stack ile merkezi loglama rehberimiz<\/a> size daha \u00f6l\u00e7eklenebilir bir yol sunar.<\/p>\n<p>Yedek taraf\u0131nda ise, uygulama dosyalar\u0131 ve veritaban\u0131 dump\u2019lar\u0131n\u0131 ayn\u0131 VPS diskinde y\u0131llarca saklamak yerine, S3 uyumlu depolama gibi harici \u00e7\u00f6z\u00fcmlere ta\u015f\u0131mak uzun vadede hem maliyeti hem riski azalt\u0131r. Bu konuda <a href=\"https:\/\/www.dchost.com\/blog\/object-storage-vs-block-storage-vs-file-storage-web-uygulamalari-ve-yedekler-icin-dogru-secim\/\">Object Storage vs Block Storage vs File Storage kar\u015f\u0131la\u015ft\u0131rma yaz\u0131m\u0131z<\/a> strateji belirlerken i\u015finize yarayacakt\u0131r.<\/p>\n<h2><span id=\"DCHost_Uzerinde_VPS_Kullaniyorsaniz_Nelere_Dikkat_Etmelisiniz\">DCHost \u00dczerinde VPS Kullan\u0131yorsan\u0131z Nelere Dikkat Etmelisiniz?<\/span><\/h2>\n<p>DCHost altyap\u0131s\u0131nda VPS kullan\u0131rken disk taraf\u0131nda pratik \u00f6nerilerimiz \u015f\u00f6yle:<\/p>\n<ul>\n<li><strong>Ba\u015flang\u0131\u00e7ta ger\u00e7ek\u00e7i disk boyutu se\u00e7in:<\/strong> WordPress + WooCommerce gibi projeler i\u00e7in sadece dosya boyutuna de\u011fil, log ve yedek b\u00fcy\u00fcmesini de hesaba kat\u0131n.<\/li>\n<li><strong>NVMe disk avantaj\u0131n\u0131 kullan\u0131n:<\/strong> Y\u00fcksek IOPS sayesinde log d\u00f6nd\u00fcrme, s\u0131k\u0131\u015ft\u0131rma ve b\u00fcy\u00fck dosya operasyonlar\u0131 \u00e7ok daha h\u0131zl\u0131 tamamlan\u0131r.<\/li>\n<li><strong>Disk kullan\u0131m\u0131 i\u00e7in alarm kurun:<\/strong> \u0130zleme panelinizde disk ve inode i\u00e7in e\u015fik de\u011ferleri belirleyin (\u00f6rn. %80 uyar\u0131, %90 kritik).<\/li>\n<li><strong>Destek ekibiyle ileti\u015fimde olun:<\/strong> Disk s\u00fcrekli %80 \u00fczerindeyse, daha b\u00fcy\u00fck diske ge\u00e7i\u015f veya ek disk ekleme plan\u0131n\u0131 birlikte de\u011ferlendirebiliriz.<\/li>\n<li><strong>Snapshot ve yedek stratejisini ay\u0131r\u0131n:<\/strong> Anl\u0131k snapshot\u2019lar\u0131 kurtarma senaryolar\u0131, harici yedekleri ise uzun vadeli saklama i\u00e7in kullan\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"Gercek_Dunya_Senaryolari_Disk_Dolma_Vakalarindan_Cikan_Dersler\">Ger\u00e7ek D\u00fcnya Senaryolar\u0131: Disk Dolma Vakalar\u0131ndan \u00c7\u0131kan Dersler<\/span><\/h2>\n<h3><span id=\"Senaryo_1_WordPress_debuglog_Dosyasinin_Diski_Gommesi\">Senaryo 1: WordPress debug.log Dosyas\u0131n\u0131n Diski G\u00f6mmesi<\/span><\/h3>\n<p>Geli\u015ftirme a\u015famas\u0131nda a\u00e7\u0131lan <code>WP_DEBUG_LOG<\/code>, canl\u0131ya ge\u00e7i\u015fte kapat\u0131lmad\u0131\u011f\u0131 i\u00e7in \/wp-content\/debug.log dosyas\u0131 haftalar i\u00e7inde 20\u201330 GB\u2019a ula\u015ft\u0131. Disk %100\u2019e vurdu, site zaman zaman 500 hatalar\u0131 vermeye ba\u015flad\u0131.<\/p>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong><\/p>\n<ul>\n<li>debug.log ge\u00e7ici olarak s\u0131k\u0131\u015ft\u0131r\u0131l\u0131p ta\u015f\u0131nd\u0131.<\/li>\n<li>wp-config.php \u00fczerinden WP_DEBUG_LOG kapat\u0131ld\u0131.<\/li>\n<li>\u0130lgili dizin i\u00e7in boyut bazl\u0131 logrotate kural\u0131 eklendi.<\/li>\n<\/ul>\n<p>Ek olarak, WordPress taraf\u0131ndaki genel bak\u0131m ve optimizasyonlar i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-yedekleme-stratejileri-paylasimli-hosting-ve-vpste-otomatik-yedek-ve-geri-yukleme\/\">WordPress yedekleme stratejileri<\/a> ve <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-icin-sunucu-tarafi-optimizasyon-php-fpm-opcache-redis-ve-mysql-ile-neyi-ne-zaman-nasil-ayarlamalisin\/\">sunucu taraf\u0131 optimizasyon rehberimiz<\/a> de uygulamaya al\u0131nd\u0131.<\/p>\n<h3><span id=\"Senaryo_2_MySQL_Slow_Query_Logunun_Kontrolden_Cikmasi\">Senaryo 2: MySQL Slow Query Log\u2019unun Kontrolden \u00c7\u0131kmas\u0131<\/span><\/h3>\n<p>Yo\u011fun sorgu alan bir e\u2011ticaret sitesinde MySQL slow query log a\u00e7\u0131k b\u0131rak\u0131lm\u0131\u015f, ancak ne d\u00f6nd\u00fcrme ne de s\u0131k\u0131\u015ft\u0131rma yap\u0131lmam\u0131\u015ft\u0131. Birka\u00e7 hafta i\u00e7inde sadece slow query log 15 GB\u2019\u0131 ge\u00e7ti.<\/p>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong><\/p>\n<ul>\n<li>\u00d6nce logrotate ile g\u00fcnl\u00fck d\u00f6nd\u00fcrme + s\u0131k\u0131\u015ft\u0131rma ayarland\u0131.<\/li>\n<li>Ard\u0131ndan sorgu optimizasyonu ve indeksleme \u00e7al\u0131\u015fmalar\u0131 yap\u0131ld\u0131.<\/li>\n<li>Slow query threshold de\u011feri ve log detay seviyesi mant\u0131kl\u0131 bir seviyeye \u00e7ekildi.<\/li>\n<\/ul>\n<p>Burada disk y\u00f6netimi ile performans optimizasyonunun el ele y\u00fcr\u00fcd\u00fc\u011f\u00fcn\u00fc g\u00f6rmek \u00f6nemli. Sorgu taraf\u0131na derinlemesine bakmak isterseniz, az \u00f6nce link verdi\u011fimiz WooCommerce\/MySQL tuning rehberi iyi bir ba\u015flang\u0131\u00e7.<\/p>\n<h3><span id=\"Senaryo_3_systemd_journal_ve_varlogjournal_Sismesi\">Senaryo 3: systemd journal ve \/var\/log\/journal \u015ei\u015fmesi<\/span><\/h3>\n<p>Uygulama loglar\u0131 gayet kontrol alt\u0131nda olmas\u0131na ra\u011fmen, \/var dizini beklenmedik \u015fekilde doluyordu. \u0130nceleme sonucunda \/var\/log\/journal alt\u0131nda 8+ GB boyutunda systemd journal dosyalar\u0131 birikti\u011fi g\u00f6r\u00fcld\u00fc.<\/p>\n<p><strong>\u00c7\u00f6z\u00fcm:<\/strong><\/p>\n<ul>\n<li>journalctl &#8211;vacuum-size ile acil olarak boyut 1 GB\u2019a \u00e7ekildi.<\/li>\n<li>journald.conf i\u00e7inde kal\u0131c\u0131 limitler tan\u0131mland\u0131 (SystemMaxUse=1G vb.).<\/li>\n<li>\u00d6nemli loglar\u0131n metin tabanl\u0131 syslog\u2019a da yaz\u0131lmas\u0131 sa\u011fland\u0131.<\/li>\n<\/ul>\n<h2><span id=\"Ozet_ve_Yol_Haritasi\">\u00d6zet ve Yol Haritas\u0131<\/span><\/h2>\n<p>VPS\u2019te \u201cNo space left on device\u201d hatas\u0131, \u00e7o\u011fu zaman \u015fanss\u0131zl\u0131k de\u011fil <strong>\u00f6ng\u00f6r\u00fclmemi\u015f disk ve log stratejisinin do\u011frudan sonucu<\/strong>. Do\u011fru ad\u0131mlar\u0131 att\u0131\u011f\u0131n\u0131zda bu hatay\u0131 g\u00f6rme ihtimaliniz ciddi oranda d\u00fc\u015fer:<\/p>\n<ul>\n<li>Disk ve inode kullan\u0131m\u0131n\u0131 d\u00fczenli izleyin, %80 \u00fczeri de\u011ferleri ciddiye al\u0131n.<\/li>\n<li>\/var\/log, \/var\/lib, \/home ve uygulama klas\u00f6rlerini periyodik olarak boyut analizi yap\u0131n.<\/li>\n<li>T\u00fcm b\u00fcy\u00fck log dosyalar\u0131 i\u00e7in logrotate kural\u0131 tan\u0131mlay\u0131n; zaman ve boyut bazl\u0131 hibrit politikalar kullan\u0131n.<\/li>\n<li>systemd journal i\u00e7in makul boyut limitleri belirleyin.<\/li>\n<li>Yedekleri ve uzun s\u00fcre saklanacak loglar\u0131 m\u00fcmk\u00fcnse VPS diski d\u0131\u015f\u0131na al\u0131n.<\/li>\n<li>\u0130zleme ve alarm sistemi kurarak, diskin dolmas\u0131n\u0131 beklemeden aksiyon al\u0131n.<\/li>\n<\/ul>\n<p>DCHost olarak, VPS ve dedicated sunucular\u0131n\u0131zda disk y\u00f6netimi, logrotate kurgusu, merkezi loglama ve yedek stratejisi gibi konularda ekibimizle birlikte yan\u0131n\u0131zday\u0131z. Mevcut VPS\u2019inizde diskin neden doldu\u011funu tam anlayam\u0131yorsan\u0131z veya yeni projeye ba\u015flarken en ba\u015ftan temiz bir mimari kurmak istiyorsan\u0131z, altyap\u0131n\u0131z\u0131 birlikte g\u00f6zden ge\u00e7irip size en uygun \u00e7\u00f6z\u00fcm\u00fc netle\u015ftirebiliriz. \u0130yi planlanm\u0131\u015f bir disk ve log stratejisi, uzun vadede kesintisiz ve sorunsuz bir bar\u0131nd\u0131rma deneyiminin en g\u00fc\u00e7l\u00fc garantisidir.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>VPS sunucularda en can s\u0131k\u0131c\u0131 hatalardan biri, uygulaman\u0131z tam da i\u015f ba\u015f\u0131ndayken kar\u015f\u0131n\u0131za \u00e7\u0131kan \u201cNo space left on device\u201d uyar\u0131s\u0131d\u0131r. \u00c7o\u011fu zaman bu hata ger\u00e7ekten &#8220;b\u00fct\u00fcn diski doldurdum&#8221; anlam\u0131na gelmez; yanl\u0131\u015f log ayarlar\u0131, kontrols\u00fcz yedekler, sistem g\u00fcnl\u00fckleri veya ge\u00e7ici dosyalar y\u00fcz\u00fcnden disk alan\u0131n\u0131z\u0131n kritik bir b\u00f6l\u00fcm\u00fc sessizce t\u00fcketilir. Sonu\u00e7ta veritaban\u0131n\u0131z yazamaz, web sunucunuz log \u00fcretemez, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3407,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3406","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3406","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\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3406"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3406\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3407"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3406"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3406"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3406"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}