# Storagenode logs to RAM

**URL:** <https://forum.storj.io/t/storagenode-logs-to-ram/19534>\
**Category:** Node Operators\
**Tags:** storagenode\
**Created:** [August 31, 2022, 7:27pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534 "2022-08-31T19:27:00Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![pietjebell](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pietjebell/32/1140_2.png) [@pietjebell](https://forum.storj.io/u/pietjebell)\
**Post date:** [August 31, 2022, 7:27pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/1 "2022-08-31T19:27:00Z")

</div>

Hi guys,

I’m running a storagenode on Unraid. My dockerfile is on a SSD, and I’m trying to reduce the writes from my docker logs to that SSD. I’m planning on placing the storagenode logs to /tmp (on the RAM). Is this advisable?

Thanks!

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [August 31, 2022, 8:23pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/2 "2022-08-31T20:23:52Z")

</div>

You may [redirect your logs to the file on data storage](https://docs.storj.io/node/resources/faq/redirect-logs/) or reduce a log level with `log.level: error` in your `config.yaml`

---

<div class="post-metadata">

**Author:** ![Bivvo](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/bivvo/32/7825_2.png) [@Bivvo](https://forum.storj.io/u/Bivvo)\
**Post date:** [August 31, 2022, 8:49pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/3 "2022-08-31T20:49:25Z")

</div>

> [@Alexey](#):
>
> or reduce a log level with `log.level: error` in your `config.yaml`

I assume you, @pietjebell, won’t be able to run the [success rate script](https://github.com/ReneSmeekes/storj_success_rate) or the [alerting monitoring](https://github.com/bjoerrrn/storj-system-health.sh) then or at least they won’t fully work. If you don’t care, that’s fine. Personally I strongly recommend to monitor your node(s) in order to be able to react quickly, especially with the [new auditing rules implemented recently](https://forum.storj.io/t/new-audit-scoring-is-live/19466/31).

I am storing the logs on an old HDD (non-NAS) and it’s working well.

---

<div class="post-metadata">

**Author:** ![pietjebell](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pietjebell/32/1140_2.png) [@pietjebell](https://forum.storj.io/u/pietjebell)\
**Post date:** [September 2, 2022, 5:36pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/4 "2022-09-02T17:36:50Z")

</div>

Thanks for the answers! I’m not using any monitoring, so that won’t be a problem.

Can I just manually edit the config file when using dockers? Or should I use a docker environment variable?

---

<div class="post-metadata">

**Author:** ![pietjebell](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/pietjebell/32/1140_2.png) [@pietjebell](https://forum.storj.io/u/pietjebell)\
**Post date:** [September 2, 2022, 5:58pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/5 "2022-09-02T17:58:28Z")

</div>

This seems to have answered itself. I have edited the config.yaml, and it remained persistant after a docker update

---

<div class="post-metadata">

**Author:** ![LrrrAc](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/lrrrac/32/8809_2.png) [@LrrrAc](https://forum.storj.io/u/LrrrAc)\
**Post date:** [October 27, 2022, 11:28pm UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/6 "2022-10-27T23:28:58Z")

</div>

Can you direct the logs to both stderr and an output file? I use dozzle and it doesnt show the logs when i output to a file.

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [October 28, 2022, 7:18am UTC](https://forum.storj.io/t/storagenode-logs-to-ram/19534/7 "2022-10-28T07:18:47Z")

</div>

yes, but externally. You do not redirect logs to the file in the storagenode’s configuration and tail logs to the file, i.e.

```auto
while true; do docker logs --tail 20 -f storagenode 2>> /mnt/storj/storagenode/storagenode.log; done

```

however this method is less reliable and requires some scripting.  
You may also use a different log driver, include syslog and journald, see [Configure logging drivers | Docker Documentation](https://docs.docker.com/config/containers/logging/configure/#supported-logging-drivers)
