<p>Serial logging has to be enabled. <strong>Warning: This will impact the performance of OctoPrint.</strong> Enabling this feature can be done under Settings -&gt; Serial Connection -&gt; Serial Logging and checking the box for &quot;Log communication to serial.log.
<a href="https://i.sstatic.net/Hp3y4.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Hp3y4.png" alt="OctoPrint Settings" /></a></p>
<p>One can download the log under Settings -&gt; Logging and finding serial.log in the list of log files.</p>
<p>The file can also be found in the following directories (according to <a href="https://discourse.octoprint.org/t/where-can-i-find-octoprints-and-octopis-log-files/299" rel="nofollow noreferrer">this FAQ</a>)</p>
<blockquote>
<p>All log files that OctoPrint writes can be found in the logs sub folder in its configuration directory:</p>
<ul>
<li>on Linux: ~/.octoprint/logs</li>
<li>on Windows: %APPDATA%\OctoPrint\logs</li>
<li>on MacOSX: ~/Library/Application Support/OctoPrint/logs</li>
</ul>
</blockquote>

CC BY-SA 4.0
2019-01-23T14:50:30.793Z
While I was editing the answer to include the serial logging to later see that you also found the answer yourself, very good that you also posted an answer, we need multiple answers if possible! Hope this helps you out debugging your problem, good luck! +1
0scar
CC BY-SA 4.0
2019-01-23T14:52:24.660Z
@0scar your answer sparked something and I was finally able to google the right phrase. I have it enabled now so time will tell...
Lux Claridge
CC BY-SA 4.0
2019-01-23T14:26:46.530Z
2019-01-23T14:26:46.530Z
2020-06-18T08:29:41.667Z
Lux Claridge
<p><strong>Yes</strong>, you can show more than 300 lines in the terminal; just <a href="https://github.com/foosel/OctoPrint/commit/e9623fdc36c658a5b8abe7769b1b308edfc3f424" rel="nofollow noreferrer">disable auto scrolling</a> (<a href="https://github.com/foosel/OctoPrint/issues/286#issuecomment-99215149" rel="nofollow noreferrer">reference</a>).</p>

<blockquote>
  <p>Disabling Autoscroll now completely disables cutting off the lines (so
  you can have way more than 300 lines while that's disabled), filtering
  has been improved too and doesn't cause scrolling anymore.</p>
</blockquote>

<p>Note that with disabled autoscrolling, you will be able to see more lines up to the point that the buffer is full. If you need even more lines to monitor, just enable the logging the data to file <code>serial.log</code>. If you open the options page (OctoPrint Settings), just tick the box for "Log communication to <code>serial.log</code>" under "Serial logging" of the "Serial connection" options.</p>

<p>This serial logging file is typically used for debug purposes, but as can be read from the options, it comes with a warning:</p>

<blockquote>
  <p>While this can negatively impact performance, a <code>serial.log</code> can be
  incredibly useful for debugging any issues observed in the
  communication between OctoPrint and your printer.</p>
</blockquote>

<p>You can either access the log file through the OctoPrint options/setting through the "Logging" options tab, or direct download/copy from the logging directory:</p>

<blockquote>
  <ul>
  <li>on Linux: ~/.octoprint/logs</li>
  <li>on Windows: %APPDATA%\OctoPrint\logs</li>
  <li>on MacOSX: ~/Library/Application Support/OctoPrint/logs</li>
  </ul>
</blockquote>

CC BY-SA 4.0
2019-01-23T14:09:50.700Z
So I would have to disable the auto scrolling at the start of the print and never leave the terminal tab because doing so enables auto scrolling. I also hit the buffer limit at 1500 lines so I don't think this option will be super helpful.
Lux Claridge
CC BY-SA 4.0
2019-01-23T14:31:24.813Z
@LuxClaridge Updated if you even need more lines to monitor.
0scar
CC BY-SA 4.0
2019-01-24T22:16:03.847Z
yep, `serial.log` is your friend more than the terminal.
300D7309EF17
CC BY-SA 4.0
2019-01-23T00:16:23.540Z
2019-01-23T14:45:37.270Z
2019-01-23T14:45:37.270Z
0scar
<p>Is there a way to view more than the last 300 lines in the terminal tab on OctoPrint? Or is there a txt file of a log? Or even a setting/plugin that does either?</p>

<p>I keep finding my prints pausing as if I said to change the filament even though that wasn't set in the slicer, but I catch it long after the 300<sup>th</sup> line in the terminal so I can't see what OctoPrint is trying to do.</p>

<octoprint>
How to log more than 300 lines of the OctoPrint terminal?
Lux Claridge
# How to log more than 300 lines of the OctoPrint terminal?

(Asked by: username_0 on 2019-01-22)

Is there a way to view more than the last 300 lines in the terminal tab on OctoPrint? Or is there a txt file of a log? Or even a setting/plugin that does either?

I keep finding my prints pausing as if I said to change the filament even though that wasn't set in the slicer, but I catch it long after the 300th line in the terminal so I can't see what OctoPrint is trying to do.

**Tags:** octoprint


---

## 2 answers

### Answer by username_0 on 2019-01-23. Score: 2 | Accepted answer

Serial logging has to be enabled. **Warning: This will impact the performance of OctoPrint.** Enabling this feature can be done under Settings -> Serial Connection -> Serial Logging and checking the box for "Log communication to serial.log.
[![OctoPrint Settings](https://i.sstatic.net/Hp3y4.png)](https://i.sstatic.net/Hp3y4.png)

One can download the log under Settings -> Logging and finding serial.log in the list of log files.

The file can also be found in the following directories (according to [this FAQ](https://discourse.octoprint.org/t/where-can-i-find-octoprints-and-octopis-log-files/299))

> All log files that OctoPrint writes can be found in the logs sub folder in its configuration directory:
>
> * on Linux: ~/.octoprint/logs
> * on Windows: %APPDATA%\OctoPrint\logs
> * on MacOSX: ~/Library/Application Support/OctoPrint/logs

> **Comments:**
> **username_1**: While I was editing the answer to include the serial logging to later see that you also found the answer yourself, very good that you also posted an answer, we need multiple answers if possible! Hope this helps you out debugging your problem, good luck! +1  
> **username_0**: @username_1 your answer sparked something and I was finally able to google the right phrase. I have it enabled now so time will tell...  

---

### Answer by username_1 on 2019-01-23. Score: 7

**Yes**, you can show more than 300 lines in the terminal; just [disable auto scrolling](https://github.com/foosel/OctoPrint/commit/e9623fdc36c658a5b8abe7769b1b308edfc3f424) ([reference](https://github.com/foosel/OctoPrint/issues/286#issuecomment-99215149)).

> Disabling Autoscroll now completely disables cutting off the lines (so
> you can have way more than 300 lines while that's disabled), filtering
> has been improved too and doesn't cause scrolling anymore.

Note that with disabled autoscrolling, you will be able to see more lines up to the point that the buffer is full. If you need even more lines to monitor, just enable the logging the data to file `serial.log`. If you open the options page (OctoPrint Settings), just tick the box for "Log communication to `serial.log`" under "Serial logging" of the "Serial connection" options.

This serial logging file is typically used for debug purposes, but as can be read from the options, it comes with a warning:

> While this can negatively impact performance, a `serial.log` can be
> incredibly useful for debugging any issues observed in the
> communication between OctoPrint and your printer.

You can either access the log file through the OctoPrint options/setting through the "Logging" options tab, or direct download/copy from the logging directory:

> * on Linux: ~/.octoprint/logs
> * on Windows: %APPDATA%\OctoPrint\logs
> * on MacOSX: ~/Library/Application Support/OctoPrint/logs

> **Comments:**
> **username_0**: So I would have to disable the auto scrolling at the start of the print and never leave the terminal tab because doing so enables auto scrolling. I also hit the buffer limit at 1500 lines so I don't think this option will be super helpful.  
> **username_1**: @username_0 Updated if you even need more lines to monitor.  
> **username_2**: yep, `serial.log` is your friend more than the terminal.  

---

