{"id":65,"title":"Linux systemd-journald Yap\u0131land\u0131rma","content":"<p>Linux d&uuml;nyas\u0131nda sistem g&uuml;nl&uuml;klerini do\u011fru y&ouml;netmek, hem g&uuml;venlik hem de performans a&ccedil;\u0131s\u0131ndan b&uuml;y&uuml;k &ouml;nem ta\u015f\u0131r.<br>Ubuntu gibi modern da\u011f\u0131t\u0131mlar, bu i\u015fi art\u0131k <strong>systemd-journald<\/strong> isimli g&uuml;&ccedil;l&uuml; bir servisle yap\u0131yor.<br>Bu yaz\u0131da, systemd-journald&rsquo;nin ne i\u015fe yarad\u0131\u011f\u0131n\u0131, nas\u0131l yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131n\u0131 ve g&uuml;nl&uuml;kleri daha verimli y&ouml;netmek i&ccedil;in neler yapabilece\u011finizi ad\u0131m ad\u0131m anlat\u0131yoruz.<\/p>\r\n<hr>\r\n<h2>Systemd-journald Nedir?<\/h2>\r\n<p>Systemd-journald, systemd altyap\u0131s\u0131n\u0131n bir par&ccedil;as\u0131d\u0131r. G&ouml;revi, sistemdeki t&uuml;m servislerden gelen g&uuml;nl&uuml;k (log) mesajlar\u0131n\u0131 toplamak ve d&uuml;zenli \u015fekilde saklamakt\u0131r.<br>Geleneksel syslog servislerine alternatif olarak geli\u015ftirilmi\u015ftir ve bir&ccedil;ok avantaja sahiptir:<\/p>\r\n<ul>\r\n<li>\r\n<p>Daha verimli bir <strong>ikili (binary) format<\/strong> kullan\u0131r.<\/p>\r\n<\/li>\r\n<li>\r\n<p><strong>Yap\u0131land\u0131r\u0131lm\u0131\u015f g&uuml;nl&uuml;k mesajlar\u0131<\/strong> sayesinde arama ve analiz kolayla\u015f\u0131r.<\/p>\r\n<\/li>\r\n<li>\r\n<p><strong>Kal\u0131c\u0131 ya da ge&ccedil;ici depolama<\/strong> se&ccedil;enekleri sunar.<\/p>\r\n<\/li>\r\n<li>\r\n<p>G&uuml;nl&uuml;klerde <strong>meta veri<\/strong> (&ouml;rne\u011fin hangi kullan\u0131c\u0131 hangi i\u015flemi ba\u015flatt\u0131) bilgilerini de saklar.<\/p>\r\n<\/li>\r\n<\/ul>\r\n<p>K\u0131sacas\u0131 systemd-journald, modern bir log y&ouml;netim sistemidir.<\/p>\r\n<hr>\r\n<h2>Temel Yap\u0131land\u0131rma Dosyas\u0131<\/h2>\r\n<p>Servisin yap\u0131land\u0131rma dosyas\u0131 <code>\/etc\/systemd\/journald.conf<\/code> konumundad\u0131r.<br>Bu dosyada g&uuml;nl&uuml;klerin nerede saklanaca\u011f\u0131, ne kadar yer kaplayabilece\u011fi ve ne kadar s&uuml;reyle tutulaca\u011f\u0131 gibi ayarlar\u0131 de\u011fi\u015ftirebilirsiniz.<\/p>\r\n<p>Dosyay\u0131 d&uuml;zenlemek i&ccedil;in:<\/p>\r\n<pre><code>sudo nano \/etc\/systemd\/journald.conf\r\n<\/code><\/pre>\r\n<hr>\r\n<h2>&Ouml;nemli Yap\u0131land\u0131rma Parametreleri<\/h2>\r\n<h3>G&uuml;nl&uuml;klerin Nerede Saklanaca\u011f\u0131<\/h3>\r\n<p><code>Storage=<\/code> parametresiyle g&uuml;nl&uuml;klerin depolanaca\u011f\u0131 yeri belirleyebilirsiniz:<\/p>\r\n<ul>\r\n<li>\r\n<p><strong>auto<\/strong> &rarr; Varsay\u0131lan ayar (genellikle \/var\/log\/journal dizini)<\/p>\r\n<\/li>\r\n<li>\r\n<p><strong>persistent<\/strong> &rarr; Kal\u0131c\u0131 depolama (sistem yeniden ba\u015flasa bile loglar korunur)<\/p>\r\n<\/li>\r\n<li>\r\n<p><strong>volatile<\/strong> &rarr; Sadece RAM&rsquo;de saklar (yeniden ba\u015flat\u0131ld\u0131\u011f\u0131nda silinir)<\/p>\r\n<\/li>\r\n<li>\r\n<p><strong>none<\/strong> &rarr; G&uuml;nl&uuml;k kayd\u0131n\u0131 tamamen devre d\u0131\u015f\u0131 b\u0131rak\u0131r<\/p>\r\n<\/li>\r\n<\/ul>\r\n<p>Genellikle &ouml;nerilen ayar:<\/p>\r\n<pre><code>Storage=persistent\r\n<\/code><\/pre>\r\n<h3>G&uuml;nl&uuml;k Boyutu S\u0131n\u0131rlamalar\u0131<\/h3>\r\n<p>Disk kullan\u0131m\u0131n\u0131 kontrol alt\u0131nda tutmak i&ccedil;in:<\/p>\r\n<pre><code>SystemMaxUse=1G\r\nRuntimeMaxUse=200M\r\nSystemMaxFileSize=100M\r\n<\/code><\/pre>\r\n<h3>G&uuml;nl&uuml;klerin S\u0131k\u0131\u015ft\u0131r\u0131lmas\u0131<\/h3>\r\n<p>Disk alan\u0131 tasarrufu i&ccedil;in:<\/p>\r\n<pre><code>Compress=yes\r\n<\/code><\/pre>\r\n<h3>Saklama S&uuml;resi<\/h3>\r\n<p>G&uuml;nl&uuml;klerin ne kadar s&uuml;re tutulaca\u011f\u0131n\u0131 ayarlayabilirsiniz:<\/p>\r\n<pre><code>MaxRetentionSec=30days\r\n<\/code><\/pre>\r\n<hr>\r\n<h2>Yayg\u0131n Kullan\u0131m Senaryolar\u0131<\/h2>\r\n<h3>Kal\u0131c\u0131 G&uuml;nl&uuml;kleri Etkinle\u015ftirme<\/h3>\r\n<p>Baz\u0131 Ubuntu sistemlerinde g&uuml;nl&uuml;kler varsay\u0131lan olarak yaln\u0131zca RAM&rsquo;de tutulur.<br>Kal\u0131c\u0131 hale getirmek i&ccedil;in \u015fu ad\u0131mlar\u0131 izleyin:<\/p>\r\n<pre><code>sudo mkdir -p \/var\/log\/journal\r\nsudo systemd-tmpfiles --create --prefix \/var\/log\/journal\r\nsudo nano \/etc\/systemd\/journald.conf\r\nStorage=persistent\r\nsudo systemctl restart systemd-journald\r\n<\/code><\/pre>\r\n<h3>G&uuml;nl&uuml;k Rotasyonu<\/h3>\r\n<p>Log dosyalar\u0131n\u0131n a\u015f\u0131r\u0131 b&uuml;y&uuml;mesini &ouml;nlemek i&ccedil;in:<\/p>\r\n<pre><code>SystemMaxUse=2G\r\nSystemMaxFileSize=100M\r\nMaxRetentionSec=1month\r\n<\/code><\/pre>\r\n<h3>Uzaktan G&uuml;nl&uuml;k Kayd\u0131<\/h3>\r\n<p>Journald loglar\u0131 ba\u015fka bir sisteme g&ouml;nderebilir:<\/p>\r\n<pre><code>ForwardToSyslog=yes\r\n<\/code><\/pre>\r\n<p>Ard\u0131ndan rsyslog yap\u0131land\u0131rmas\u0131na \u015fu mod&uuml;l&uuml; ekleyin:<\/p>\r\n<pre><code>module(load=\"imjournal\")\r\n<\/code><\/pre>\r\n<hr>\r\n<h2>G&uuml;nl&uuml;kleri G&ouml;r&uuml;nt&uuml;leme<\/h2>\r\n<p>Systemd-journald loglar\u0131n\u0131 g&ouml;r&uuml;nt&uuml;lemek i&ccedil;in <code>journalctl<\/code> komutu kullan\u0131l\u0131r.<br>Birka&ccedil; &ouml;rnek:<\/p>\r\n<ul>\r\n<li>\r\n<p>T&uuml;m g&uuml;nl&uuml;kleri listele:<\/p>\r\n<pre><code>journalctl\r\n<\/code><\/pre>\r\n<\/li>\r\n<li>\r\n<p>Belirli bir servisin loglar\u0131n\u0131 g&ouml;ster:<\/p>\r\n<pre><code>journalctl -u nginx.service\r\n<\/code><\/pre>\r\n<\/li>\r\n<li>\r\n<p>Bug&uuml;nk&uuml; loglar\u0131 g&ouml;ster:<\/p>\r\n<pre><code>journalctl --since today\r\n<\/code><\/pre>\r\n<\/li>\r\n<li>\r\n<p>Hata ve kritik mesajlar\u0131 g&ouml;ster:<\/p>\r\n<pre><code>journalctl -p err..crit\r\n<\/code><\/pre>\r\n<\/li>\r\n<li>\r\n<p>Ger&ccedil;ek zamanl\u0131 takip:<\/p>\r\n<pre><code>journalctl -f\r\n<\/code><\/pre>\r\n<\/li>\r\n<\/ul>\r\n<hr>\r\n<h2>G&uuml;nl&uuml;kleri Temizleme<\/h2>\r\n<p>Zamanla log dosyalar\u0131 &ccedil;ok yer kaplayabilir.<br>A\u015fa\u011f\u0131daki komutlarla temizlik yapabilirsiniz:<\/p>\r\n<ul>\r\n<li>\r\n<p>Boyut s\u0131n\u0131r\u0131na g&ouml;re temizleme:<\/p>\r\n<pre><code>sudo journalctl --vacuum-size=500M\r\n<\/code><\/pre>\r\n<\/li>\r\n<li>\r\n<p>Tarihe g&ouml;re temizleme (&ouml;rne\u011fin 2 haftadan eski):<\/p>\r\n<pre><code>sudo journalctl --vacuum-time=2weeks\r\n<\/code><\/pre>\r\n<\/li>\r\n<\/ul>\r\n<hr>\r\n<h2>Sorun Giderme<\/h2>\r\n<h3>Loglar &Ccedil;ok Yer Kapl\u0131yorsa<\/h3>\r\n<ol>\r\n<li>\r\n<p>Mevcut kullan\u0131m miktar\u0131n\u0131 &ouml;\u011frenin:<\/p>\r\n<pre><code>journalctl --disk-usage\r\n<\/code><\/pre>\r\n<\/li>\r\n<li>\r\n<p>Gerekirse journald.conf i&ccedil;inde boyut limitlerini azalt\u0131n.<\/p>\r\n<\/li>\r\n<li>\r\n<p>Temizlik komutlar\u0131n\u0131 &ccedil;al\u0131\u015ft\u0131r\u0131n.<\/p>\r\n<\/li>\r\n<\/ol>\r\n<h3>Loglar G&ouml;r&uuml;nt&uuml;lenmiyorsa<\/h3>\r\n<ol>\r\n<li>\r\n<p>Servisin &ccedil;al\u0131\u015ft\u0131\u011f\u0131n\u0131 kontrol edin:<\/p>\r\n<pre><code>systemctl status systemd-journald\r\n<\/code><\/pre>\r\n<\/li>\r\n<li>\r\n<p>Kal\u0131c\u0131 depolama aktif mi kontrol edin.<\/p>\r\n<\/li>\r\n<li>\r\n<p>Kullan\u0131c\u0131n\u0131z\u0131n gerekli izinleri oldu\u011fundan emin olun:<\/p>\r\n<pre><code>sudo usermod -aG systemd-journal $USER\r\n<\/code><\/pre>\r\n<\/li>\r\n<\/ol>\r\n<hr>\r\n<h2>G&uuml;venlik &Ouml;nlemleri<\/h2>\r\n<p>Log dosyalar\u0131n\u0131n sadece yetkili kullan\u0131c\u0131lar taraf\u0131ndan eri\u015filebilir olmas\u0131 &ouml;nemlidir.<\/p>\r\n<pre><code>sudo chown -R root:systemd-journal \/var\/log\/journal\r\nsudo chmod -R 2750 \/var\/log\/journal\r\n<\/code><\/pre>\r\n<p>Ek olarak <code>journald.conf<\/code> dosyas\u0131na \u015fu sat\u0131r\u0131 eklemek, g&uuml;nl&uuml;klerin b&uuml;t&uuml;nl&uuml;\u011f&uuml;n&uuml; korur:<\/p>\r\n<pre><code>Seal=yes\r\n<\/code><\/pre>\r\n<hr>\r\n<p>Systemd-journald, Ubuntu sistemlerinde log y&ouml;netimini daha g&uuml;&ccedil;l&uuml;, d&uuml;zenli ve g&uuml;venli hale getirir.<br>Do\u011fru yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda hem sistem performans\u0131n\u0131 art\u0131r\u0131r hem de olas\u0131 hatalar\u0131 &ccedil;ok daha h\u0131zl\u0131 tespit etmenizi sa\u011flar.<\/p>\r\n<p>Unutmay\u0131n: ayarlar\u0131 de\u011fi\u015ftirdikten sonra servisi yeniden ba\u015flatmay\u0131 ihmal etmeyin.<\/p>\r\n<pre><code>sudo systemctl restart systemd-journald\r\n<\/code><\/pre>\r\n<p>Bu rehberin, Ubuntu &uuml;zerinde log y&ouml;netimini optimize etmenize yard\u0131mc\u0131 olmas\u0131n\u0131 diliyoruz.<br>Daha temiz, daha g&uuml;venli ve daha izlenebilir bir sistem i&ccedil;in systemd-journald, elinizdeki en g&uuml;&ccedil;l&uuml; ara&ccedil;lardan biridir. \ud83c\udf3f<\/p>\r\n<hr>\r\n<p>\u0130stersen yaz\u0131ya giri\u015f k\u0131sm\u0131na <strong>hikayele\u015ftirilmi\u015f<\/strong> (&ouml;rne\u011fin &ldquo;bir sistem y&ouml;neticisinin ya\u015fad\u0131\u011f\u0131 log sorunu&rdquo; tarz\u0131nda) bir ba\u015flang\u0131&ccedil; ekleyebilirim.<br>\u0130ster misin &ouml;yle bir versiyon haz\u0131rlayay\u0131m?<\/p>","excerpt":"Systemd-journald, modern Linux da\u011f\u0131t\u0131mlar\u0131nda (Ubuntu dahil) sistem g\u00fcnl\u00fcklerini toplamak ve y\u00f6netmek i\u00e7in kullan\u0131lan g\u00fc\u00e7l\u00fc bir...","created_at":"2025-05-18 20:06:47","updated_at":"2026-09-08 04:19:47","category_id":10,"view_count":724,"reading_time":5,"status":"published","editor_choice":0,"is_editor_choice":0,"published_at":"2025-05-18 20:06:00","featured_image":"api_unsplash_1762014342_69063486255f1.jpg","slug":"linux-systemd-journald-yapilandirma","category_name":"nix Linux Unix","category_slug":"nix-linux-unix"}