The Patch Failed: ConfigurationManager

That did install, which surprised me because I thought everything was up to date. Unfortunately after a reboot I got the same error message. I dug through the mycroft-skills.log file and was able to pull this information out. Please ignore the time stamp as the time seems to be wrong.

07:03:48.668 - PlatformPatchSkill - INFO - Patch failure
07:03:48.740 - mycroft.skills.core:load_skill:157 - INFO - Loaded skill-platform-patch
07:03:48.745 - mycroft.skills.core:load_skill:139 - INFO - ATTEMPTING TO LOAD SKILL: skill-naptime with ID 609713676
07:03:48.869 - SKILLS - DEBUG - {"type": "speak", "data": {"expect_response": false, "utterance": "The patch failed because of a AttributeError. type object 'ConfigurationManager' has no attribute 'load_local'"}, "context": null}
07:03:48.872 - SKILLS - DEBUG - {"type": "mycroft.skills.loaded", "data": {"id": 1493316045, "name": "PlatformPatchSkill"}, "context": null}
07:03:49.092 - mycroft.skills.core:load_skill:157 - INFO - Loaded skill-naptime
07:03:49.097 - SKILLS - DEBUG - {"type": "register_vocab", "data": {"start": "go to sleep", "end": "SleepCommand"}, "context": null}
07:03:49.102 - mycroft.skills.core:load_skill:139 - INFO - ATTEMPTING TO LOAD SKILL: skill-playback-control with ID 1406552044
07:03:49.111 - skill-playback-control - INFO - Playback Control Inited
07:03:49.112 - SKILLS - DEBUG - {"type": "register_vocab", "data": {"start": "nap time", "end": "SleepCommand"}, "context": null}
07:03:49.116 - SKILLS - DEBUG - {"type": "register_vocab", "data": {"start": "sleepy time tea", "end": "SleepCommand"}, "context": null}
07:03:49.119 - SKILLS - DEBUG - {"type": "register_vocab", "data": {"start": "sleepytime tea", "end": "SleepCommand"}, "context": null}
07:03:49.128 - SKILLS - DEBUG - {"type": "register_intent", "data": {"at_least_one": [], "requires": [["SleepCommand", "SleepCommand"]], "optional": [], "name": "609713676:NapTimeIntent"}, "context": null}
07:03:49.138 - SKILLS - DEBUG - {"type": "mycroft.skills.loaded", "data": {"id": 609713676, "name": "NapTimeSkill"}, "context": null}
07:03:49.141 - skill-playback-control - INFO - initializing Playback Control Skill
07:03:49.146 - SKILLS - DEBUG - {"type": "register_vocab", "data": {"start": "next track", "end": "NextKeyword"}, "context": null}
07:03:49.153 - SKILLS - DEBUG - {"type": "register_vocab", "data": {"start": "skip", "end": "NextKeyword"}, "context": null}
07:03:49.157 - mycroft.skills.core:load_skill:157 - INFO - Loaded skill-playback-control
07:03:49.165 - mycroft.skills.core:load_skill:139 - INFO - ATTEMPTING TO LOAD SKILL: skill-media with ID -474202112

It seems like there’s something amiss with the skill-naptime, as that’s the line that comes right before the verbal error message, and the syntax doesn’t look the same as other skill loads.

Mike

Good thinking. Let’s remove skill-naptime to prove that by removing it. We can then reinstall it.

pi@mark_1:~ $ cd /opt/mycroft/skills/
pi@mark_1:/opt/mycroft/skills $ ls -las | grep naptime
4 drwxr-xr-x  6 mycroft mycroft 4096 Jan 28 07:22 skill-naptime
pi@mark_1:/opt/mycroft/skills $ sudo rm -R skill-naptime

Then, reboot and see whether Mycroft Mark 1 loads OK. I so, then we know it’s skill-naptime and we can reinstall it.

pi@mark_1:/opt/mycroft/skills $ msm install skill-naptime
Searching for for 'skill-naptime'...'skill-naptime' skill was not found
msm: error 202
pi@mark_1:/opt/mycroft/skills $ msm install naptime
Searching for for 'naptime'...installing
Installing from: https://github.com/mycroftai/skill-naptime
07:25:08.721 - root - INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
07:25:08.866 - root - INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt
07:25:09.677 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /usr/local/lib/python2.7/site-packages/mycroft_core-0.9.14-py2.7.egg/mycroft/configuration/mycroft.conf loaded
07:25:09.685 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /usr/local/lib/python2.7/site-packages/mycroft_core-0.9.14-py2.7.egg/mycroft/configuration/mycroft.conf loaded
07:25:09.690 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /etc/mycroft/mycroft.conf loaded
07:25:09.697 - mycroft.configuration.config:load_local:133 - DEBUG - Configuration '/home/pi/.mycroft/mycroft.conf' not found
07:25:09.708 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.mycroft.ai
07:25:11.620 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 "GET /v1/device//setting HTTP/1.1" 401 38
07:25:11.634 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.mycroft.ai
07:25:14.121 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 "GET /v1/auth/token HTTP/1.1" 401 38
07:25:14.133 - mycroft.configuration.config:__init__:175 - ERROR - HTTPError fetching remote configuration: 401
07:25:14.137 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /opt/mycroft/web_config_cache.json loaded
07:25:14.141 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /etc/mycroft/mycroft.conf loaded
07:25:14.144 - mycroft.configuration.config:load_local:133 - DEBUG - Configuration '/home/pi/.mycroft/mycroft.conf' not found
Cloning into 'skill-naptime'...
remote: Counting objects: 79, done.
remote: Total 79 (delta 0), reused 0 (delta 0), pack-reused 78
Unpacking objects: 100% (79/79), done.
Checking connectivity... done.
Installed: skill-naptime
07:25:18.348 - root - INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
07:25:18.490 - root - INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt
07:25:19.302 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /usr/local/lib/python2.7/site-packages/mycroft_core-0.9.14-py2.7.egg/mycroft/configuration/mycroft.conf loaded
07:25:19.309 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /usr/local/lib/python2.7/site-packages/mycroft_core-0.9.14-py2.7.egg/mycroft/configuration/mycroft.conf loaded
07:25:19.314 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /etc/mycroft/mycroft.conf loaded
07:25:19.319 - mycroft.configuration.config:load_local:133 - DEBUG - Configuration '/home/pi/.mycroft/mycroft.conf' not found
07:25:19.328 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.mycroft.ai
07:25:21.101 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 "GET /v1/device//setting HTTP/1.1" 401 38
07:25:21.115 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.mycroft.ai
07:25:22.970 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 "GET /v1/auth/token HTTP/1.1" 401 38
07:25:22.982 - mycroft.configuration.config:__init__:175 - ERROR - HTTPError fetching remote configuration: 401
07:25:22.987 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /opt/mycroft/web_config_cache.json loaded
07:25:22.990 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /etc/mycroft/mycroft.conf loaded
07:25:22.994 - mycroft.configuration.config:load_local:133 - DEBUG - Configuration '/home/pi/.mycroft/mycroft.conf' not found
07:25:23.617 - root - INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/Grammar.txt
07:25:23.761 - root - INFO - Generating grammar tables from /usr/lib/python2.7/lib2to3/PatternGrammar.txt
07:25:24.574 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /usr/local/lib/python2.7/site-packages/mycroft_core-0.9.14-py2.7.egg/mycroft/configuration/mycroft.conf loaded
07:25:24.581 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /usr/local/lib/python2.7/site-packages/mycroft_core-0.9.14-py2.7.egg/mycroft/configuration/mycroft.conf loaded
07:25:24.586 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /etc/mycroft/mycroft.conf loaded
07:25:24.590 - mycroft.configuration.config:load_local:133 - DEBUG - Configuration '/home/pi/.mycroft/mycroft.conf' not found
07:25:24.600 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.mycroft.ai
07:25:26.011 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 "GET /v1/device//setting HTTP/1.1" 401 38
07:25:26.025 - requests.packages.urllib3.connectionpool - DEBUG - Starting new HTTPS connection (1): api.mycroft.ai
07:25:27.966 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 "GET /v1/auth/token HTTP/1.1" 401 38
07:25:27.979 - mycroft.configuration.config:__init__:175 - ERROR - HTTPError fetching remote configuration: 401
07:25:27.983 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /opt/mycroft/web_config_cache.json loaded
07:25:27.987 - mycroft.configuration.config:load_local:128 - DEBUG - Configuration /etc/mycroft/mycroft.conf loaded
07:25:27.990 - mycroft.configuration.config:load_local:133 - DEBUG - Configuration '/home/pi/.mycroft/mycroft.conf' not found

That was kind of odd. The Mark I loaded up better, but the error is still there. Previously the eyes were yellow and the display wasn’t working. Now I see the time on the front of the device and the eyes are green. I was hopeful we resolved the issue, but it gave me the same error message. It appears that after restarting the unit it reinstalled the naptime skill for me as it was miraculously back in the skills directory when it came back from a reboot. I did remove it and verify that it was gone, so it wasn’t just a bad command or anything like that. So, there goes my theory that it was the naptime skill.

Mike

Thanks @linuxrants for that info.

My gut call here is that this line;
07:03:48.869 - SKILLS - DEBUG - {"type": "speak", "data": {"expect_response": false, "utterance": "The patch failed because of a AttributeError. type object 'ConfigurationManager' has no attribute 'load_local'"}, "context": null}

is the issue.

I’m going to ping my colleagues @forslund an @steve.penrod to see if they have any ideas.

Best, Kathy

Thanks Kathy. I think you’re right. I appreciate your help.

Mike

Anytime, I’m just sorry I couldn’t fix it straight away for you.

1 Like

Hi,

Easiest way to fix this is to remove the platform patch skill. The patch has been installed and some of the changes makes the patch incompatible. See PR here: https://github.com/MycroftAI/skill-platform-patch/pull/4

The PR should fix it as well but as the patch has been applied it’s best to remove it.

Sorry for the inconvenience, this fell between chairs in the pre-christmas rush I think.

/Åke

1 Like

That seems to have resolved the issue that I was having with the patch failed message. Now the eye color on the unit has turned back to yellow and they are unresponsive (for example if I use the nap time command the eyes don’t dim or “close”).

Thank you for your help @forslund.

Mike

Ah, Yellow Eyes. I’ve had this problem too, and we’ve heard a couple of other reports, but we don’t have good data on which to start root cause analysis. I solved Yellow Eyes by

  • Wiping the unit using the factory default setting accessible by the top button, then ‘WIPE’
  • Removing the Device in home.mycroft.ai
  • Rebooting
  • Repairing

Be interested to know if this works for you too, but I understand too that it’s a lot of mucking around.

Best, Kathy

Unfortunately I’ve done all of that over the course of troubleshooting the patch failed error I was getting. Sometimes a reboot will resolve it, but whether it’s still fixed after the next reboot is a flip of a coin. I am noticing this showing up repeatedly in the logs which might have something to do with it. Might not too.

01:29:29.112 - mycroft.skills.settings:_send_settings_meta:195 - ERROR - HTTPSConnectionPool(host='api.mycroft.ai', port=443): Read timed out. (read timeout=15)

I also see this which is interesting but also may or may not be related.

01:28:52.350 - mycroft.client.speech.listener:transcribe:167 - ERROR - Could not request Speech Recognition recognition request failed: Forbidden

What I really need is an image of the default Mark I SDCard so I can just pull it and nuke it with Etcher. I don’t suppose that could be made available (or is available and I’m just illiterate)?

Thanks for that info @linuxrants, I’m going to ping @forslund to see if he has any other suggestions here.

The default Mark 1 Micro SD card image is available at:

https://mycroft.ai/to/mark-1-image

Hi again,

The first is an issue with the server, which occurs if a the device which first uploaded the skill settings were removed. Our backend team is working on a fix for this, it’s a huge general issue but shouldn’t really be a problem for basic functionality.

The second error message is more worrying because it looks like the server isn’t accepting your pairing. You should be getting a pairing code. or at least a reply for the pairing skill.

Have you at some point deleted your device on home.mycroft.ai?

It hasn’t asked for a pairing code recently. @KathyReid suggested reboots, so I rebooted the device until the eyes came up their configured green. This isn’t a permanent state, because when Mycroft gets restarted it usually comes up with the Yellow Eyes. Sometimes I can hear Mycroft talking (though there’s no display on the front panel), but he almost never gives me a pairing code. I have removed my device from home.mycroft.ai before. Sometimes it seems to randomly lose the registration (only maybe 2 or 3 times since I got the unit) and it will ask me to go through the code bit again. When that happens I go to the site and I remove the “old” device and add a “new” device and everything is happy again. It doesn’t fix the Yellow Eye issue permanently though.

That sounds extremely peculiar. Reflashing the device with the latest release might be the best solution to make sure the state of the device is in a good state.

The image that Kathy pointed to is much improved over the one the device was delivered with so if we missed something in the platform patch it should be resolved in the new image.

OK, I’ll give that a shot. Thank you @KathyReid for that link! I really appreciate it! Also, thank you @forslund for your time and help.

Mike

@linuxrants - did flashing things over work for you?

Unfortunately I’ve had 3 sick kids since my last post, and I just haven’t had a chance to do it yet.

Hope the kiddos are feeling much better soon @linuxrants.

nice -n -20 ./kids-better.sh

1 Like

@J_Montgomery_Mycroft and @KathyReid,

I wanted to make sure I kept a working copy of the Mycroft image in case whole process went sideways, so this weekend I ran down to my local Fry’s Electronics and picked up a new SD Card. I imaged it using the link that Kathy provided (thank you again!), and I’ve had mixed results.

Everything started out pretty normal (other than the fact that Mycroft seems to have started at max volume and it wouldn’t let me reduce that volume until I’d completed the setup). I started it up, connected to the hot spot, and directed Mycroft to my WiFi network. I was instructed to go to https://home.mycroft.ai and register the device (which was pretty much expected), and Mycroft proceeded to run updates. After the updates, it rebooted and then asked me to _re_register the device on the site, despite the fact that I’d done that minutes before. I removed the old registration and added a new device, and it seemed happy with the whole setup. I’ve still seen the yellow eyes, but they seem more rare now. Restarting the device usually gets things back to good, but I’ve only tried it two or three times at this point.

I admit that I’m a little concerned that the yellow eyes are still an issue, even if it’s more rare. If it was a desktop PC or a server in the data center and I’d just reimaged the system and it didn’t solve the issue, I’d be leaning towards hardware. The Pi inside seems to be working fine as I can always ssh into the device and use the cli without issue. I’d lean towards the display or possibly even a network connectivity issue. I’d don’t know. I’m just random throwing stuff out now.

One thing I was surprised about was when Mycroft did finally start up and work completely, it started with the green eyes that I’d configured on the previous image. Does this mean that the settings are global for eye color? If I got another Mark I device, would they share eye color all the time?

Thanks for all of your help! Right now the Mark II is sitting at $196,420, so let me preemptively congratulate you on reaching the $200,000 mark. It looks like people are very excited about the Mark II!

Mike

Thanks @linuxrants, we’re still trying to track down the root cause of Yellow Eyes, so your information is super helpful.

Regarding the eyes, the color is set via the Mark 1 Skill - so if you have two Mark 1s, they will share this value.

Thanks too for your well wishes - we’re so close to $200K!!!

1 Like