After upgrading from 7.3.0 to 8.0.0, Splunk Web server turns out the ERROR message:UnicodeDecodeError: 'ascii' codec can't decode byte 0xe7 in position 0: ordinal not in range(128)

New Member

I upgraded splunk enterprise instance from 7.3.0 to 8.0.0.

All preliminary checks passed when splunk restarting.
But when i accessed to the web interface,it turned out this python error:

alt text
500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last):
File "/app/splunk/lib/python3.7/site-packages/cherrypy/", line 628, in respond
File "/app/splunk/lib/python3.7/site-packages/cherrypy/", line 659, in _do_respond
File "/app/splunk/lib/python3.7/site-packages/cherrypy/", line 749, in get_resource
File "/app/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/", line 405, in __call
request.lang, request.mofile, request.t = get_translation('messages', [locale])
File "/app/splunk/lib/python3.7/site-packages/splunk/appserver/mrsparkle/lib/", line 550, in get_translation
t = translations.setdefault(key, SparkleTranslations(open(mofile, 'rb'))) # was GNUTranslations
File "/app/splunk/lib/python3.7/", line 259, in __init
File "/app/splunk/lib/python3.7/", line 420, in _parse
catalog[str(msg, charset)] = str(tmsg, charset)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe7 in position 0: ordinal not in range(128)

Powered by CherryPy unknown

Tags (1)
0 Karma

Splunk Employee
Splunk Employee

I had a situation where Splunk web refused to start after upgrading to SE 8.0.1, with UnicodeDecodeError. In our situation if was due to the system locale being set to sv_SE. Changing it to en_GB helped.

0 Karma

Ultra Champion

Did you run through the migration checks before upgrading?

Take a look at this post following and see if it addresses your issue.

0 Karma

Ultra Champion

I think I have seen another post on the subject - and after a quick look now, I can't find it!

There was a suggestion that Splunk 8 does not handle dashboards that do not have a label, and can trigger this message.
Sadly the message does not give any indication as to which dashboard is the problem.

The suggested advice was to look through the xml for your dashboards and identify any which do not have a label and manually edit the xml to include one.

If I can find the post I will update my answer to give credit/context.


I have retracted my answer, as I was mistaken. Here is the post I was referring to, but it does not apply to your situation.

0 Karma