{"id":1580,"date":"2020-06-07T22:15:36","date_gmt":"2020-06-07T14:15:36","guid":{"rendered":"https:\/\/www.wesbytes.com\/guide\/?post_type=kb&#038;p=1580"},"modified":"2026-01-12T13:57:03","modified_gmt":"2026-01-12T05:57:03","slug":"how-to-increase-logging-for-railgun","status":"publish","type":"kb","link":"https:\/\/www.servergigabit.com\/guide\/kb\/how-to-increase-logging-for-railgun","title":{"rendered":"How to Increase Logging for Railgun"},"content":{"rendered":"<h5><strong>How to Increase Logging for Railgun?<\/strong><\/h5>\n<p>When troubleshooting or testing the Railgun Listener, it may be necessary to raise the level of verbosity to capture more log data for debugging.<\/p>\n<p>In order to increase logging, the\u00a0<code>log.level<\/code>\u00a0within\u00a0<code>railgun.conf<\/code>\u00a0should be set to\u00a0<strong>5<\/strong>\u00a0in order for all events within the Listener instance to be captured during troubleshooting.<\/p>\n<p>*The Railgun service running on the server will also need to be restarted for changes to take affect:<br \/>\n<code>\u00a0 service railgun restart<\/code><\/p>\n<p>The log files for Railgun can be found in the following locations for each supported operating system:<\/p>\n<p><strong><a href=\"https:\/\/www.servergigabit.com\/\">Debian\/Ubuntu<\/a> Default Location: <\/strong><code><strong>\/var\/log\/syslog<\/strong><\/code><\/p>\n<p>*Note: When the\u00a0<code>log.level<\/code>\u00a0set to\u00a0<strong>5<\/strong>\u00a0in\u00a0<code>railgun.conf<\/code>, no further action is needed to have very verbose logs appear in <a href=\"https:\/\/www.solarwinds.com\/resources\/it-glossary\/syslog\" rel=\"nofollow noopener\" target=\"_blank\">syslog<\/a>.<\/p>\n<p><strong><a href=\"https:\/\/www.servergigabit.com\/\">CentOS<\/a>\/RHEL Default Location: <\/strong><code><strong>\/var\/log\/messages<\/strong><\/code>Default Location:\u00a0<code>\/var\/log\/messages<\/code><\/p>\n<p>By default, CentOS and RHEL omit many logs from \/messages. A few extra steps are need to achieve the same level of verbosity as Debian\/Ubuntu:<\/p>\n<p>1. \u00a0 \u00a0Editing \/etc\/rsyslog.conf so that the line that reads:<\/p>\n<div data-hasbody=\"true\" data-macro-name=\"noformat\">\n<pre>*.info;mail.none;authpriv.none;cron.none \/var\/log\/messages<\/pre>\n<\/div>\n<p>is update to be:<\/p>\n<div data-hasbody=\"true\" data-macro-name=\"noformat\">\n<pre>*.* \/var\/log\/messages<\/pre>\n<\/div>\n<p>*Note: This can be done by commenting out the default line and adding this on a new line below it. Or this can be a new log file if you choose.<\/p>\n<p>2. \u00a0 \u00a0Restarting rsyslog and Railgun services. This may need to be done with sudo or as root:<\/p>\n<div data-hasbody=\"true\" data-macro-name=\"noformat\">\n<pre>service rsyslog restart \r\nservice railgun restart<\/pre>\n<\/div>\n<p>*If Railgun or memcached fails over\/crashes, logs can be found under\u00a0<code>\/var\/log\/railgun\/panic.log<\/code><\/p>\n","protected":false},"excerpt":{"rendered":"<p>How to Increase Logging for Railgun? When troubleshooting or testing the Railgun Listener, it may be necessary to raise the level of verbosity to capture more log data for debugging. In order to increase logging, the\u00a0log.level\u00a0within\u00a0railgun.conf\u00a0should be set to\u00a05\u00a0in order for all events within the Listener instance to be captured during troubleshooting. *The Railgun service running on the server will&hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"kbtopic":[43],"kbtag":[1422,1419],"class_list":["post-1580","kb","type-kb","status-publish","hentry","kbtopic-cloudflare","kbtag-logging","kbtag-railgun"],"_links":{"self":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/1580","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb"}],"about":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/types\/kb"}],"author":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/comments?post=1580"}],"version-history":[{"count":4,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/1580\/revisions"}],"predecessor-version":[{"id":6023,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kb\/1580\/revisions\/6023"}],"wp:attachment":[{"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/media?parent=1580"}],"wp:term":[{"taxonomy":"kbtopic","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtopic?post=1580"},{"taxonomy":"kbtag","embeddable":true,"href":"https:\/\/www.servergigabit.com\/guide\/wp-json\/wp\/v2\/kbtag?post=1580"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}