# 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:** [7월 5, 2015, 12:51오후 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:** 7

<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:** [7월 7, 2015, 6:17오후 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/7 "2015-07-07T18:17:53Z")

</div>

Ah right you are, it’s so strange because the console was reporting the  
offending `LANG: en_US.UTF-8` (which was on line 36), yet accurately the  
incorrect tabspacing on line 86.

Worked perfectly and this freed 22gb of space on our server!

---

_[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)._