Unable to run mycroft-core CLI since last Friday noon

So this turned out to be a virtualenv issue. I removed my virtualenv and re-installed and it all came good. Big thanks to @forslund for his help.

Hello, I am facing the same issue (and I think i am not the only one) … Would it be possible to have a detailed way of fixing it ?

Hi @Louis_cormaille, sorry to hear you’re experiencing this issue too.

First, remove your existing virtualenv:

sudo rm -R ~/.virtualenv/mycroft/

then, run ~/dev_setup.sh again.

This will rebuild your virtualenv.

Please let me know how you go.

@KathyReid I have already uninstall and reinstalled (deleted and pulled and ran ~/dev_setup.sh ) and it is still not working. I’ll try to do it your way though. I’ll keep you updated. Thanks
EDIT : It now seems to work (at least it is running) but Mycroft does not recognize any of what I am saying … And if I try to write the question in input in debug, it is lagging (like, I can’t even write it) …
It is annoying … another thing : If I try to run ./start-mycroft.sh all, i can hear Mycroft running in the background but there is no GUI, is it normal ?

Hi @Louis_cormaille, thanks for working through that process.

  • When you say that Mycroft does not recognize what you are saying, does every Skill return “I’m sorry I didn’t understand your request”?

  • Lagging is not normal for debug mode, unless the host you’re running on is heavily loaded at the same time. What does top or htop show when you run that at the same time? Is it mycroft-core using all the system resources?

  • ./start-mycroft debug and ./start-mycroft cli will provide a GUI, but ./start-mycroft all does not.

Can you attach your mycroft-skills.log so we can see what’s happening with the skills?

Kind regards,
Kathy

@KathyReid
Every Skill returns “I’m sorry I didn’t understand your request”
Here is the mycroft-skills.log file
https://drive.google.com/open?id=1Ua0sTOVi4l4eVjjsR9-GCvUR0TO9Kx6s
And ./start-mycroft debug and ./start-mycroft cli don’t provide a GUI

Thanks so much for providing the log, @Louis_cormaille, very useful.

I can see:

  • The device pairs successfully
  • but when asked about the weather, it doesn’t find the intent.

My colleague @forslund might know more about what’s causing the error here - for instance whether Padatious is not picking up the Intent correctly.

With ./start-mycroft debug and ./start-mycroft cli not providing a GUI, if virtualenv has been reinstalled, I’m not sure what to try next, again @forslund may have some suggestions.

I just tried again today with another intent. “what’s the news”. First, Mycroft says it does not understand my request. It does not lag at this moment (I can write and everything). But as soon as I asked this, it asked me to repair the device (as if I did not already paired it yesterday) and it started to lag ( I could not write anymore …) @forslund help would be very appreciated indeed :slight_smile:
Here are the new logs
https://drive.google.com/open?id=1iHeOeUCHjjsuOpDRyfCCpIyD_kz4kiVx
Thank you !

At the top of the skills log file there are a lot of import errors:

ImportError: No module named mycroft.dialog
Traceback (most recent call last):
  File "/home/louis/mycroft-core/mycroft/skills/main.py", line 24, in <module>

but that’s probably the old errors as the process shouldn’t be able to start at all if that was still true.

The skills in question exist but does not seem to ever be loaded. msm exits with an error (-2) which is bad. But I’m not quite certain what that means, but it seems like it gets terminated before it’s done updating. Could be that the messagebus service goes down for some reason.

The messagebus log looks like it’s being terminated by an external signal about the same time as the msm process has problems.

Looking at the mycroft-voice.log it looks like the pairing is complete since it seems to be getting valid responses.

It can take a minute or so for the skill to get loaded since the skills are checked for updates before it’s started. so you might want to start it, leave it alone for a minute or two and then trying to interact with it.

Can you provide platform and OS?

I am running it on Ubuntu. I tried waiting 2 minutes but then, i can’t write anything anymore in the input as it’s lagging.

can you type top in a terminal and see which process is overloading the cpu. And just to be ceertain it’s on a desktop PC right? @Louis_cormaille

also I see there’s a config file: ~/.mycroft/mycroft.conf if there’s no sensitive information in there could you maybe post that as well?

I am running it on a laptop MSI GS60 ghost.
There is no such file.
Only those :
drwxrwxr-x 2 louis louis 4096 Oct 6 18:27 identity
drwxrwxr-x 2 louis louis 4096 Oct 6 18:22 intent_cache
drwxrwxr-x 29 louis louis 4096 Nov 18 15:15 skills
-rw------- 1 louis louis 3243 Nov 18 16:08 wakeword_rsa
(which have not been modified since a long time apparently)

@forslund Here is a video showing what is happening. Maybe it’s going to be easier for you to see what’s going on
https://drive.google.com/open?id=1iHeOeUCHjjsuOpDRyfCCpIyD_kz4kiVx

From the video I can see that mycroft is still updating

... SKILLS DEBUG {type: "msm.updating" ...}

When this is done (after a minute or so) a similar message ... "msm.updated" ... should scroll by. Followed by a lot of intent registrations.

I’ll look into it more tomorrow morning.

/Åke

Thank you for your help. I’ve uploaded a new video, starting this time, 5 minutes after i started running Mycroft

Hi, it’s veeeery slow there. and that should not be the case for fairly modern computers.

Do you get the mycroft “listening” sound?

Have you modified the wakeword? is it mycroft or the default “hey mycroft”. Looking at the feedback it seems like the stt only registers half the sentence (the last part) and misshears “news” for “use” so no intent is triggered there.

I suggest you try “hey mycroft” pause for a couple of seconds (while the “listening” sound is playing) and then “play news”.

While you do that I’ll keep digging trying to find out what causes the slowdown.

/Åke

It is very slow indeed ! :slight_smile:
I do have Mycroft listening sound but it seems to get activated even when I don t say the wake word.
I did change the wake word to “Mycroft” instead of “hey mycroft”.
I ll try to change back the wake word to its default value and do what you suggested, tonight. I ll record it.
Than you again for your time !
@forslund, uploaded the video, it still seems like Mycroft can’t find any skill

Can you provide an updated mycroft-skills.log file?

Updated the drive folder with the new logs !

1 Like