<p>You can put the following in your <code>rippled.cfg</code> file:</p>

<pre><code>[rpc_startup]
{ "command" : "log_level", "severity" : "error" }
</code></pre>

CC BY-SA 3.0
2014-03-31T22:08:34.323Z
Thanks! I see that the wiki was updated with the correct severities.
lid
CC BY-SA 3.0
2014-03-31T21:48:17.623Z
2014-03-31T21:48:17.623Z
David Schwartz
<p>By default, rippled seems to log at the NFO level, which spits out many megabytes of log files each day. How do I reduce this level? According to the <a href="https://ripple.com/wiki/Rippled_Troubleshooting#Logging_Severity" rel="nofollow">Ripple wiki</a>, we can edit pass arguments to rippled when starting it, or edit the configuration file via [rpc_startup], but neither of these methods had any effect for me (on v0.23.0).</p>

<ripple><ripple-api>
How do I reduce the loglevel on rippled?
lid
# How do I reduce the loglevel on rippled?

(Asked by: username_0 on 2014-03-30)

By default, rippled seems to log at the NFO level, which spits out many megabytes of log files each day. How do I reduce this level? According to the [Ripple wiki](https://ripple.com/wiki/Rippled_Troubleshooting#Logging_Severity), we can edit pass arguments to rippled when starting it, or edit the configuration file via [rpc\_startup], but neither of these methods had any effect for me (on v0.23.0).

**Tags:** ripple, ripple-api


---

## 1 answers

### Answer by username_1 on 2014-03-31. Score: 3 | Accepted answer

You can put the following in your rippled.cfg file:
[rpc_startup]
{ "command" : "log_level", "severity" : "error" }

> **Comments:**
> **username_0**: Thanks! I see that the wiki was updated with the correct severities.  

---

