Estimated reading time: 6 minutes

This documentation was last modified: Thursday, December 6th, 2018 at 8:23 pm

Troubleshooting and known errors

This section is grouped by Device to help you quickly find the information you need.

Help us to help you

When you contact Mycroft for support, we may ask for some of the following information:

  • What type of Mycroft Device you’re using, such as Mark 1, Picroft, KDE Plasmoid and so on
  • Whether your Device was Paired
  • Your account details
  • Information from your Mycroft logs
  • Information generated from the Support Skill

Using the Support Skill

As of December 2017, we have implemented a Support Skill as a core (default) Skill on all Mycroft Devices. This means that you can generate information about what the Device is doing. This information is then emailed to you, so you can review it for privacy reasons, and then if you choose, forward it to Mycroft for support.

To generate information for a Support Ticket, say any of these phrases:

"Create a support ticket"
"You’re not working!"
"Send me debug info"

Mycroft will then ask:

"Please give me a brief description of the problem"

Tell Mycroft what the problem was, or what you were doing. Mycroft will then compile information and send an email to the address registered to your account. The email will contain a link to, with information about your Device, settings, and Skills. This information can be used for troubleshooting.

Support information generated by Support Skill

About the Mycroft logs

The Mycroft logs each follow a standard format, being:

  • A timestamp
  • The function or action that was called
  • The level of the error, which can be one of:

    • DEBUG – incidental information used for debugging purposes
    • INFO – informational log entries which do not indicate an error
    • WARNING – an error occurred, but it did not stop execution of the Skill or process
    • ERROR – an error occurred, and it stopped execution of a Skill or other process
    • CRITICAL – a significant error occurred, and it halted execution of the Mycroft functionality itself

How to find the Mycroft logs

Mark 1

On a Mark 1 Device, first ssh into the Mark 1.

The logs on a Mark 1 are held at /var/log/

To find the specific Mycroft logs, run the following Linux command:

ls -las | grep -i Mycroft

This command lists all the log files with ‘Mycroft’ in the file name.


  pi@mark_1:/var/log $ ls -las | grep mycroft
     20 -rw-r--r--  1 mycroft root    17136 Oct 16 15:52 mycroft-audio.log
  22808 -rw-r--r--  1 mycroft root 23348347 Oct 17 10:19 mycroft-enclosure-client.log
  38336 -rw-r--r--  1 mycroft root 39249935 Oct 17 10:19 mycroft-messagebus.log
  24564 -rw-r--r--  1 mycroft root 25147196 Oct 17 10:19 mycroft-skills.log
     28 -rw-r--r--  1 mycroft root    23272 Oct 16 15:52 mycroft-speech-client.log
    584 -rw-r--r--  1 root    root   590008 Oct 17 10:00 mycroft-update.log
     84 -rw-r--r--  1 mycroft root    84493 Oct 16 12:50 mycroft-wifi-setup-client.log


On a Raspberry Pi 3 running Picroft, first ssh into the Picroft.

The logs on a Picroft are held at /var/log/ and are named mycroft-LOGFILE.log.

To see all the Picroft logs that are available, use the command ls -las /var/log/ | grep mycroft


On a Linux device running Mycroft for Linux, the logs are held at;

relative to where mycroft-core was installed.

$ ls -las
total 191360
    8 drwxrwxr-x 2 kathyreid kathyreid     4096 Sep  4 14:05 .
    8 drwxrwxr-x 3 kathyreid kathyreid     4096 Sep  4 14:05 ..
  344 -rw-rw-r-- 1 kathyreid kathyreid   341056 Oct 17 00:44 mycroft-audio.log
95552 -rw-rw-r-- 1 kathyreid kathyreid 97836905 Oct 17 00:44 mycroft-cli.log
   36 -rw-rw-r-- 1 kathyreid kathyreid    25499 Oct 17 00:44 mycroft-service.log
94968 -rw-rw-r-- 1 kathyreid kathyreid 97238978 Oct 17 00:44 mycroft-skills.log
  444 -rw-rw-r-- 1 kathyreid kathyreid   442637 Oct 17 00:44 mycroft-voice.log


@TODO Not sure where log files are on Android

Log file descriptions


This log contains information on actions such as:

  • When Mycroft loads audio services
  • When Mycroft speaks
  • When the Text to Speech (TTS) cache is hit
  • When volume is increased or decreased


This log is primarily used on Linux installations of Mycroft and contains information on actions such as:

  • Errors and warnings with Mycroft services
  • When a Fallback cannot handle an Intent


This log contains information on actions such as:

  • Loading of configurations for the Enclosure
  • Altering properties of the Enclosure, such as the Eyes or Mouth on a Mark 1
  • Activities related to the Enclosure Display Manager


This log contains information on actions such as:

  • Messages sent between Mycroft components such as Skills and the Enclosure that Mycroft is running on
  • Data generated through invoking and controlling Skills


This log contains information on actions such as:

  • The outcome of Mycroft attempting to load Skills, such as whether a Skill was successfully loaded, blacklisted (disabled by Mycroft) or failed to load
  • When an Utterance is spoken, which Skill it was matched with, and the information provided to the Skill
  • Information related to the Mycroft Skill Manager (msm), including an msm-specific error code.


This log contains information on actions such as:

  • Loading of configuration information from the Device
  • Registration of keywords associated with Utterances and Skills
  • Any errors associated with the ‘listener’ functionality


Some Enclosures, like the Mark 1, will automatically try to update their software periodically. This log is the output of this log, and has similar output to what you would see if you manually ran apt-get update.


Some Enclosures, like the Mark 1, will create a WiFi hotspot when they are first set up. This log contains messages related to the creation and tear-down of the WiFi hotspot, as well as errors and information related to clients connecting to the WiFi hotspot.

General troubleshooting (all Devices)

I’ve made changes to my settings on, but these are not reflected on my Device

Have you recently updated your Location or your measurement preferences (ie. kilometers vs miles) in, but these are not reflected on your Device?

All Devices pull down a local copy of configuration settings from You may need to instruct your Device to pull down your configuration again. To do this, Speak

hey Mycroft, configuration update

Mycroft will respond in one of two ways:

  • If your configuration was out of date, and has been pulled down again, Mycroft will respond Your device has been configured.
  • If your configuration was the same on your Device as on, Mycroft will respond Updated configuration.

If you’re comfortable SSHing into your device, SSH in and then run the following commands to see what configuration values are stored locally.

To see the city location value:

jq "" < /var/tmp/mycroft_web_cache.json

To see the latitude and longitude coordinates of your location:

jq ".location.coordinate" < /var/tmp/mycroft_web_cache.json

To see the timezone setting:

jq ".location.timezone" < /var/tmp/mycroft_web_cache.json

To see the listener setting:

jq ".listener" < /var/tmp/mycroft_web_cache.json

To see the Speech to Text (STT) settings:

jq ".stt" < /var/tmp/mycroft_web_cache.json

To see the Text to Speech (TTS) settings:

jq ".tts" < /var/tmp/mycroft_web_cache.json

We also have more information available on mycroft.conf and mycroft_web_cache.json files.

Troubleshooting Mark 1

Not connected to the internet

If your Mark 1 loses internet connectivity

If your Mark 1 has previously been connected to the internet, and loses internet connectivity, it will speak

I have lost connection to the internet

Troubleshooting Picroft

Troubleshooting Linux

Logs state that Python packages are not installed

If your logs have entries like
@TODO example of Python package not being installed

then you may need to reinstall your virtualenv. To do this,

  • sudo rm -R ~/.virtualenv/mycroft
  • From the directory where you have cloned mycroft-core, run ./ This shell script will re-install any virtualenv dependencies that you may be missing.

Troubleshooting Skills development

Skill fails on first run with ERROR - Failed to load skill

If you’re developing a Skill, and run it for the first time, you may encounter an error similar to the below:

12:30:32.158 - mycroft.skills.core:load_skill:142 - INFO - First run of mycroft-skill-cat-facts
12:30:32.164 - mycroft.skills.core:load_skill:156 - ERROR - Failed to load skill: mycroft-skill-cat-facts
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/site-packages/mycroft_core-0.9.7-py2.7.egg/mycroft/skills/", line 144, in load_skill
  File "/usr/local/lib/python2.7/site-packages/mycroft_core-0.9.7-py2.7.egg/mycroft/skills/", line 323, in store
    with open(self._settings_path, 'w') as f:
IOError: [Errno 13] Permission denied: '/opt/mycroft/skills/mycroft-skill-cat-facts/settings.json'

The error here is that the file system permission on the Skill‘s directory are incorrect. The directory should have owner and group permissions of mycroft:mycroft as per the below.

4 drwxr-xr-x  4 mycroft mycroft  4096 Nov 24 14:34 .
4 drwxrwxrwx 38 mycroft mycroft  4096 Nov 27 12:50 ..
4 drwxr-xr-x  3 mycroft mycroft  4096 Nov 23 16:57 dialog
4 drwxr-xr-x  8 mycroft mycroft  4096 Nov 27 12:36 .git
4 -rw-r--r--  1 mycroft mycroft    20 Nov 23 16:57 .gitignore
8 -rw-r--r--  1 mycroft mycroft  6265 Nov 23 16:57
8 -rw-r--r--  1 mycroft mycroft  7509 Nov 24 14:34 init.pyc
12 -rw-r--r--  1 mycroft mycroft 11357 Nov 23 16:57 LICENSE
4 -rw-r--r--  1 mycroft mycroft   695 Nov 24 14:33
4 -rw-r--r--  1 mycroft mycroft    35 Nov 25 19:28 settings.json

If your permissions are different to those shown above, change them by running the following commands:

cd /opt/mycroft/skills/
sudo chown mycroft:mycroft -R your-skill-name

Help us serve you better by rating this documentation