Build an open future with us.

Invest in Mycroft and become a community partner.

Mark I troubleshoot? Not starting?


#1

Hi,

My Mark I has been quite unstable…

Sometime it has worked perfectly, but sometimes I dint get the confirmation “ping” when the display turns “listen mode” and Mark I also do not execute my request. (Usally turn on / off lights by the HUE skill).

I have tried booth with cable and using Wifi without any noticeable change…

Since it’s still a “early prototype” I have bought the flaws and just rebooted the device which normally works.

But sadly after the last reboot Mark I do not start anymore… The eyes go to yellow but newer blue… I get into the menu when long pressing the button, but it seams like nothing happens when selecting anything… Rotating the button change sound but again the “brain” seams dead…

What should be my next step? Tried even reset from the menu but again nothing happen…

Can I reinstall the OS image on the memory-card ? How do I do that?

Br,

Lars


#2

Hi @Lars_Modig,
First of all a big welcome and sorry to hear that your Mark 1 has been unstable.

There are many possible causes for the “Yellow Eyes”, and we have several fixes available, depending on what the problem is.

  • One of the common causes of Yellow Eyes is that Mark 1 did not complete a software update successfully. Do you know what version of software Mark 1 was running? The latest version is 18.8.4b. If you ask Hey Mycroft, what version are you running, does he respond?

  • Are you comfortable using ssh to connect to the Mark 1 and perform command line operations? If so there are some commands I can share with you that can be used to help recover from Yellow Eyes.

  • Sometimes, Yellow Eyes can be caused by Mycroft getting “stuck” updating a Skill. Were any Skills recently installed?

We’re here to get your Mark 1 back to being happy :wink:


#3

So, now got some time to connec… And yes I can ssh into MYCROFT. Sadly I cant find any command that shows version…
when write help I just get…

GNU bash, version 4.3.30(1)-release (arm-unknown-linux-gnueabihf) …

So what do I do now…

Worked a bit more and, wiped it reconnected it to the Mycroft Home, installed HUE skill again (worked) then answer yes on the question on a major update request.

After that yellow eyes again…

Asking -:“Hey MYROFT, whats the time?” I get the answer…

“Please wait a moment until I finished booting up”…

The problem is that that moment has lasted more then 4 hours (and counting) now…

(but maybe I found the issue with the unstable system earlier…, My router channel setting was set to auto, and due to that it sometimes goes up in channel if theres less traffic… and since Rasberry PI cant handle that it could be, at least, one reason for the unstability. Now I set to a fixed lower channel, but as mention still stuclk on yellow…)

Br,

Lars


#4

@KathyReid so any ideas?


#5

Hi @Lars_Modig, sorry I missed this one, the forum has been really busy the last few days.

Firstly, let’s see what version of mycroft packages you have installed:

sudo apt list --installed | grep mycroft

This will tell us which versions are installed. If you are are at a version less than 18.8.5 then we need to get Mycroft on to the latest version.

Try;

sudo apt-get update && sudo apt-get upgrade

You should see Yellow Eyes while this is happening, then Mycroft should reboot.


#6

pi@mark_1:~ $ sudo apt list --installed | grep mycroft

WARNING: apt does not have a stable CLI interface yet. Use with caution in scripts.

mycroft-core/unknown,now 18.8.5 armhf [installed]
mycroft-mark-1/unknown,now 18.8.5 armhf [installed]
mycroft-wifi-setup/unknown,now 0.2.5 armhf [installed]
pi@mark_1:~ $

Calculating upgrade… The following packages were automatically installed and are no longer required:
libpython-dev libpython2.7-dev python-dev python2.7-dev
Use ‘apt-get autoremove’ to remove them.
Done
The following packages have been kept back:
raspberrypi-kernel
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
pi@mark_1:~ $

Still yellow eyes and the same comment at any question

"Please wait a moment until I finished booting up”
@KathyReid


#7

I dont know if this can help…

pi@mark_1:/var/log/mycroft $ ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.4 5464 4000 ? Ss Nov13 0:05 /sbin/init
root 2 0.0 0.0 0 0 ? S Nov13 0:00 [kthreadd]
root 3 0.0 0.0 0 0 ? S Nov13 0:00 [ksoftirqd/0]
root 5 0.0 0.0 0 0 ? S< Nov13 0:00 [kworker/0:0H]
root 7 0.2 0.0 0 0 ? S Nov13 3:22 [rcu_sched]
root 8 0.0 0.0 0 0 ? S Nov13 0:00 [rcu_bh]
root 9 0.0 0.0 0 0 ? S Nov13 0:00 [migration/0]
root 10 0.0 0.0 0 0 ? S Nov13 0:00 [migration/1]
root 11 0.0 0.0 0 0 ? S Nov13 0:01 [ksoftirqd/1]
root 13 0.0 0.0 0 0 ? S< Nov13 0:00 [kworker/1:0H]
root 14 0.0 0.0 0 0 ? S Nov13 0:00 [migration/2]
root 15 0.0 0.0 0 0 ? S Nov13 0:00 [ksoftirqd/2]
root 17 0.0 0.0 0 0 ? S< Nov13 0:00 [kworker/2:0H]
root 18 0.0 0.0 0 0 ? S Nov13 0:00 [migration/3]
root 19 0.0 0.0 0 0 ? S Nov13 0:00 [ksoftirqd/3]
root 21 0.0 0.0 0 0 ? S< Nov13 0:00 [kworker/3:0H]
root 22 0.0 0.0 0 0 ? S Nov13 0:00 [kdevtmpfs]
root 23 0.0 0.0 0 0 ? S< Nov13 0:00 [netns]
root 24 0.0 0.0 0 0 ? S< Nov13 0:00 [perf]
root 25 0.0 0.0 0 0 ? S Nov13 0:00 [khungtaskd]
root 26 0.0 0.0 0 0 ? S< Nov13 0:00 [writeback]
root 27 0.0 0.0 0 0 ? S< Nov13 0:00 [crypto]
root 28 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 29 0.0 0.0 0 0 ? S< Nov13 0:00 [kblockd]
root 31 0.0 0.0 0 0 ? S< Nov13 0:00 [rpciod]
root 32 0.0 0.0 0 0 ? S Nov13 0:00 [kswapd0]
root 33 0.0 0.0 0 0 ? S< Nov13 0:00 [vmstat]
root 34 0.0 0.0 0 0 ? S Nov13 0:00 [fsnotify_mark]
root 35 0.0 0.0 0 0 ? S< Nov13 0:00 [nfsiod]
root 44 0.0 0.0 0 0 ? S< Nov13 0:00 [kthrotld]
root 45 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 46 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 47 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 48 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 49 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 50 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 51 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 52 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 53 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 54 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 55 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 56 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 57 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 58 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 59 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 60 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 61 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 62 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 63 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 64 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 65 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 66 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 67 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 68 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 69 0.0 0.0 0 0 ? S< Nov13 0:00 [VCHIQ-0]
root 70 0.0 0.0 0 0 ? S< Nov13 0:00 [VCHIQr-0]
root 71 0.0 0.0 0 0 ? S< Nov13 0:00 [VCHIQs-0]
root 72 0.0 0.0 0 0 ? S< Nov13 0:00 [iscsi_eh]
root 73 0.0 0.0 0 0 ? S< Nov13 0:00 [dwc_otg]
root 75 0.0 0.0 0 0 ? S< Nov13 0:00 [DWC Notificati
root 77 0.0 0.0 0 0 ? S Nov13 0:16 [irq/92-mmc1]
root 78 0.0 0.0 0 0 ? S Nov13 0:00 [VCHIQka-0]
root 79 0.0 0.0 0 0 ? S< Nov13 0:00 [SMIO]
root 80 0.0 0.0 0 0 ? S< Nov13 0:00 [deferwq]
root 82 0.0 0.0 0 0 ? S< Nov13 0:00 [bioset]
root 83 0.0 0.0 0 0 ? S Nov13 0:04 [mmcqd/0]
root 87 0.0 0.0 0 0 ? S Nov13 0:00 [jbd2/mmcblk0p2
root 88 0.0 0.0 0 0 ? S< Nov13 0:00 [ext4-rsv-conve
root 89 0.0 0.0 0 0 ? S< Nov13 0:00 [ipv6_addrconf]
root 107 0.0 0.0 0 0 ? S< Nov13 0:00 [kworker/3:1H]
root 145 0.0 0.2 9944 2604 ? Ss Nov13 0:03 /lib/systemd/sy
root 148 0.0 0.3 11416 2856 ? Ss Nov13 0:00 /lib/systemd/sy
root 188 0.0 0.0 0 0 ? S Nov13 0:00 [spi0]
root 226 0.0 0.0 0 0 ? S< Nov13 0:00 [cfg80211]
root 231 0.0 0.0 0 0 ? S< Nov13 0:00 [brcmf_wq/mmc1:
root 233 0.0 0.0 0 0 ? S Nov13 0:09 [brcmf_wdog/mmc
systemd+ 340 0.0 0.2 12668 2032 ? Ssl Nov13 0:00 /lib/systemd/sy
root 513 0.0 0.2 32144 2804 ? Ssl Nov13 0:01 /usr/sbin/rsysl
avahi 514 0.0 0.2 3876 2476 ? Ss Nov13 0:05 avahi-daemon: r
root 520 0.0 0.2 5072 2428 ? Ss Nov13 0:00 /usr/sbin/cron
root 523 0.0 0.2 3928 2440 ? Ss Nov13 0:00 /lib/systemd/sy
message+ 535 0.0 0.3 5624 3132 ? Ss Nov13 0:00 /usr/bin/dbus-d
root 562 0.0 0.1 2564 1844 ? Ss Nov13 0:02 /sbin/dhcpcd -q
avahi 566 0.0 0.1 3876 1480 ? S Nov13 0:00 avahi-daemon: c
nobody 567 0.0 0.1 2292 1456 ? Ss Nov13 0:00 /usr/sbin/thd -
root 635 0.0 0.3 6700 3276 ? Ss Nov13 0:00 /sbin/wpa_suppl
root 746 0.0 0.2 5668 2720 tty1 Ss Nov13 0:00 /bin/login -f
ntp 767 0.0 0.3 5688 3684 ? Ss Nov13 0:05 /usr/sbin/ntpd
mycroft 790 0.0 0.3 4976 3292 ? Ss Nov13 0:00 /lib/systemd/sy
root 793 0.0 0.4 7860 4320 ? Ss Nov13 0:00 /usr/sbin/sshd
mycroft 798 0.0 0.1 6820 1356 ? S Nov13 0:00 (sd-pam)
root 802 0.0 0.3 4520 2900 ? Ss Nov13 0:00 /lib/systemd/sy
root 807 0.0 0.1 6820 1360 ? S Nov13 0:00 (sd-pam)
mycroft 824 0.3 3.4 208928 32568 ? Sl Nov13 4:03 /opt/venvs/mycr
mycroft 825 0.2 2.9 160864 28408 ? Sl Nov13 3:38 /opt/venvs/mycr
root 826 0.0 0.1 2140 1052 ? S Nov13 0:00 mycroft-admin-s
mycroft 827 2.7 2.5 37988 23992 ? Sl Nov13 36:23 /opt/venvs/mycr
root 845 0.0 1.1 15016 10852 ? S Nov13 0:01 mycroft-admin-s
mycroft 851 2.9 0.8 101828 7968 ? Sl Nov13 38:07 pulseaudio -D
rtkit 852 0.0 0.2 21376 2024 ? SNsl Nov13 0:00 /usr/lib/rtkit/
root 856 0.0 0.5 36508 5640 ? Ssl Nov13 0:00 /usr/lib/policy
mycroft 873 5.5 3.6 288280 34856 ? Sl Nov13 72:04 /opt/venvs/mycr
pi 891 0.0 0.3 4976 3400 ? Ss Nov13 0:00 /lib/systemd/sy
pi 897 0.0 0.1 6820 1368 ? S Nov13 0:00 (sd-pam)
pi 902 0.0 0.4 6352 4316 tty1 S+ Nov13 0:00 -bash
root 1033 0.0 0.0 0 0 ? S< Nov13 0:00 [kworker/2:1H]
mycroft 1058 0.0 0.1 2140 1072 ? S Nov13 0:00 /home/mycroft/.
mycroft 1061 51.0 11.1 300500 105368 ? Sl Nov13 665:37 /home/mycroft/.
root 1134 0.0 0.0 0 0 ? S< Nov13 0:00 [kworker/1:1H]
mycroft 1184 0.4 2.5 300404 24064 ? Sl Nov13 5:35 /opt/venvs/mycr
root 2220 0.0 0.9 43700 9260 ? Ssl Nov13 0:00 /usr/lib/packag
root 4293 0.0 0.0 0 0 ? S< 00:17 0:00 [kworker/0:1H]
root 20952 0.0 0.0 0 0 ? S 15:56 0:00 [kworker/2:1]
root 22729 0.0 0.0 0 0 ? S 17:36 0:00 [kworker/0:2]
root 22892 0.0 0.0 0 0 ? S 17:46 0:00 [kworker/3:1]
root 23218 0.0 0.0 0 0 ? S 18:06 0:01 [kworker/u8:1]
root 23382 0.0 0.0 0 0 ? S 18:16 0:00 [kworker/u8:0]
root 23902 0.0 0.0 0 0 ? S 18:44 0:00 [kworker/1:2]
root 24064 0.0 0.0 0 0 ? S 18:54 0:00 [kworker/2:0]
root 24065 0.0 0.0 0 0 ? S 18:55 0:00 [kworker/0:1]
root 24105 0.0 0.0 0 0 ? S 18:56 0:00 [kworker/u8:2]
root 24106 0.0 0.0 0 0 ? S 18:56 0:00 [kworker/3:2]
root 24107 0.0 0.0 0 0 ? S 18:56 0:00 [kworker/1:0]
root 24153 0.0 0.5 9512 5148 ? Ss 18:59 0:00 sshd: pi [priv]
pi 24160 0.0 0.3 9644 3564 ? S 18:59 0:00 sshd: pi@pts/0
pi 24162 0.1 0.4 6360 4548 pts/0 Ss 18:59 0:00 -bash
root 24178 0.0 0.0 0 0 ? S 19:00 0:00 [kworker/0:0]
root 24230 0.0 0.0 0 0 ? S 19:02 0:00 [kworker/2:2]
root 24270 0.0 0.0 0 0 ? S 19:03 0:00 [kworker/3:0]
pi 24272 0.0 0.2 4744 2108 pts/0 R+ 19:03 0:00 ps aux


#8

Your ps list is cut off. Can you see if there’s anything interesting in the logs? (/var/log/mycroft*)


#9

This sounds like the skill service not starting up correctly.

As @baconator suggests the logs is the next logical place to look.

Check your /var/log/mycroft/skills.log in particular. You should be able to upload it to termbin using

cat /var/log/mycroft/skills.log | nc termbin.com 9999

It should return a short link which you can share here.


#10

Thanks, I had a hard time to understand how I should copy the logs to the forum… :slight_smile:
But here’s the link

http://termbin.com/xpjc

Br,

Lars


#11

Ok, there’s an error message in there which would indicate that some files related to msm has been corrupted.

try running sudo rm -rf /opt/mycroft/.skills-repo and then restarting the device.


#12

Super thanks!

A reboot and a restart later and it answer the clock!

/Lars


#13

A fix handling this issue is on it’s way into core together with some other msm updates. Hope it behaves for a while now.