Mycroft repeats last request when starting up

[trekjunky]

OpenSuSE 15.1
I am running mycroft-core version 19 oh 2, release 12

My problem: I have the skill finished booting up running. Right after Mycroft says he is ready, he repeats the last request I made days ago. If I ask him 5 requests, the next time I start him up, he will repeat my last request. How do I stop this?

[forslund]

That sounds really weird. mycroft-core doesn't retain any information about what is spoken between startups. I checked the finished-booting skill and it doesn't seem to do anything like that either.

Does this happen even if you reboot the machine between starting Mycroft?

[trekjunky]

Yes, I have rebooted several times and Mycroft does it every time I start him up. I paid good money that I donated so that I wouldn't have any problems, but that didn't seem to matter. I wonder what problem I will have when and if this is fixed? This is my 4th problem so far.

[forslund]

Thanks for that piece of information, that rules out cached speech wav-files since they would be flushed at reboot.

Could it be another skill that stores those things? Do you have more third-party skills in addition to the finished-booting skill?

To help us look further into the issue could you perform the following actions:

edit the mycroft.conf to enable debugging logs

nano ~/.mycroft/mycroft.conf

add a line to set the log level to debugging

"log_level": "DEBUG"

this needs to be valid json and can be a bit tricky. If the config hasn't been changed previously it should look like this when done:

{
  "max_allowed_core_version": 19.2,
  "log_level": "DEBUG"
}

Since the issue is happening during startup the config editing is necessary, otherwise the debug CLI could perform the log level change during operation.

Then start up mycroft ./start-mycroft.sh all when it has started ask him to "create a support ticket" and follow the verbal instructions to create a support package. then forward the e-mail that will be sent to your registered e-mail to me ake.forslund[-at-]mycroft.ai

If there are issues with the support skill zip up the /var/log/mycroft/skills.log file and send that.

Thank you.

[trekjunky]

I had to send you an email directly as my second email explains that I never got the email that Mycroft sent.

[forslund]

Thank you for sending the logs, I looked them over and one possibility is the fallback-recommendations skill. It has some code that could be responsible for the repeat after reload...

[krisgesling]

@trekjunky can you try uninstalling that Skill and retesting to see if the problem goes away?
You should be able to just say "uninstall recommendations"

[trekjunky]

I uninstalled it and ran a test run and the problem went away. I reinstalled it and ran another test and the problem didn't come back. Thanks!!!!! But now I have a question that should be simple enough. In my troubleshooting I edited the file ~/.mycroft/mycroft.conf and changed the log level to DEBUG. Now I would like to change it back, BUT I don't remember what the setting was before. Can you help? *Cane Kostovski* www.pc-tamer.com

…

__________________________________________ “Here, where a thousand Captains swore grand conquest. . .Tall Grass their monument.” ― Basho "Too many people are beacons of light with hate for others... If only some of that light would shine on them showing them as they are, NOT as they wish they were!!!!!" ― Cane Kostovski

__________________________________________

On Tue, Jun 11, 2019 at 5:27 PM Kris Gesling ***@***.***> wrote: @trekjunky <https://github.com/trekjunky> can you try uninstalling that Skill and retesting to see if the problem goes away? You should be able to just say "uninstall recommendations" — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2155?email_source=notifications&email_token=AE3WZRLKUC5DRDVACDRSX7DP2AKDZA5CNFSM4HWU7EZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXORVVI#issuecomment-501029589>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE3WZRNRMTPUUCOVL6DBOL3P2AKDZANCNFSM4HWU7EZA> .

[trekjunky]

Kris' advice worked. He said to uninstall recommendations and try it. I did and the problem went away. I reinstalled it and tested again. The problem did NOT come back. Thanks for your help!!!! *Cane Kostovski* www.pc-tamer.com

…

__________________________________________ “Here, where a thousand Captains swore grand conquest. . .Tall Grass their monument.” ― Basho "Too many people are beacons of light with hate for others... If only some of that light would shine on them showing them as they are, NOT as they wish they were!!!!!" ― Cane Kostovski

__________________________________________

On Tue, Jun 11, 2019 at 4:42 PM Åke ***@***.***> wrote: Thank you for sending the logs, I looked them over and one possibility is the fallback-recommendations skill. It has some code that could be responsible for the repeat after reload... — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2155?email_source=notifications&email_token=AE3WZRMEQKPG4ZURRAWKSB3P2AE37A5CNFSM4HWU7EZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXOOC7Y#issuecomment-501014911>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE3WZRMNC2IZU2BK4TAGI2LP2AE37ANCNFSM4HWU7EZA> .

[krisgesling]

Great!

I'll still let the developer of that skill know so they can keep an eye out for it and hopefully prevent it from happening again.

As for switching the log level back, you should be able to just delete that line from your conf file and it will switch back to the default level of 'info'.
Another random tip - in the CLI you can type:
:log level debug
or
:log level info
to quickly switch log levels. However I don't think these are retained after a reboot.

[forslund]

@krisgesling as the issue occured during startup I asked him to set the log level to debug through the config so we'd be guaranteed to catch it.

@trekjunky the default config should look like this:

{
  "max_allowed_core_version": 19.2
}

Glad we could help resolve the issue!

[trekjunky]

Thanks Ake!!!! *Cane Kostovski* www.pc-tamer.com

…

__________________________________________ “Here, where a thousand Captains swore grand conquest. . .Tall Grass their monument.” ― Basho "Too many people are beacons of light with hate for others... If only some of that light would shine on them showing them as they are, NOT as they wish they were!!!!!" ― Cane Kostovski

__________________________________________

On Wed, Jun 12, 2019 at 3:15 AM Åke ***@***.***> wrote: @krisgesling <https://github.com/krisgesling> as the issue occured during startup I asked him to set the log level to debug through the config so we'd be guaranteed to catch it. @trekjunky <https://github.com/trekjunky> the default config should look like this: { "max_allowed_core_version": 19.2 } — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2155?email_source=notifications&email_token=AE3WZRPMTWK6AGL4KXPNYJTP2CPBLA5CNFSM4HWU7EZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXPPHEQ#issuecomment-501150610>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AE3WZRJZRYZZZEEGJ7KZYADP2CPBLANCNFSM4HWU7EZA> .

[LinusSkucas]

hi @trekjunky , I'm the developer of that fallback recommendations skill, and I would like to look into this more as I haven't seen something like this. If you could respond to my questions here:
LinusSkucas/fallback-recommendations-skill#9 (comment)
That would be great, so I can further debug this skill.