# Found character that cannot start any token while scanning for the next token at line 86 column 1 -e LANG=en\_US.UTF-8

**URL:** https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795
**Category:** Self-hosting
**Created:** [5 ביולי,‏ 2015,‏ 12:51pm UTC](https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795 "2015-07-05T12:51:00Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![kkershaw](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/kkershaw/32/115025_2.png) [@kkershaw](https://meta.discourse.org/u/kkershaw)
#### Post date: [5 ביולי,‏ 2015,‏ 1:18pm UTC](https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795/2 "2015-07-05T13:18:56Z")

</div>

**ok** As it turns out, our log files were completely filling up the server disk space, our docker instance’s `access.log` ended up taking up a whopping 17gb! I found this thread: [Docker install allows nginx log files to keep growing? - #9 by sam](https://meta.discourse.org/t/docker-install-allows-nginx-log-files-to-keep-growing/26518/9)

Which recommends a git pull and rebuild, which is what I’ve been trying to accomplish anyhow, so any tips would still be greatly appreciated!

---

_[View the full topic](https://meta.discourse.org/t/found-character-that-cannot-start-any-token-while-scanning-for-the-next-token-at-line-86-column-1-e-lang-en-us-utf-8/30795)._