Newest picroft running 100% CPU

Archive - Mycroft Project Picroft
1

Please move this to the appropriate catagory.

My Pi3b, 32G SD, picroft 0.8 has been working, listening and answering for a week.
Yesterday it started taking “2-3+ Minutes” to bing that it heard the wakeup (then 15 seconds before telling the time).

ps shows python2.7 /usr/local/bin/mycroft-speech-client running at 100% CPU.
top shows a python2.7 process running at 100.9(??)

none of the logs show any activity for 3 minutes before to 2.5 minutes after the wakeup/command sentence.

Any ideas?

The only odd things I see are: (in messages)
Feb 27 15:20:32 picroft rsyslogd-2007: action ‘action 17’ suspended, next retry is Mon Feb 27 15:21:02 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 27 15:20:41 picroft pulseaudio[1032]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Feb 27 15:20:41 picroft pulseaudio[1032]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Feb 27 15:20:45 picroft pulseaudio[1145]: [pulseaudio] server-lookup.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Feb 27 15:20:45 picroft pulseaudio[1145]: [pulseaudio] main.c: Unable to contact D-Bus: org.freedesktop.DBus.Error.NotSupported: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
Feb 27 15:21:18 picroft rsyslogd-2007: action ‘action 17’ suspended, next retry is Mon Feb 27 15:21:48 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 27 15:27:58 picroft rsyslogd-2007: action ‘action 17’ suspended, next retry is Mon Feb 27 15:28:28 2017 [try http://www.rsyslog.com/e/2007 ]
Feb 27 15:35:27 picroft rsyslogd-2007: action ‘action 17’ suspended, next retry is Mon Feb 27 15:35:57 2017 [try http://www.rsyslog.com/e/2007 ]

Why is this headless pi looking for an X11?

2

Hey Riddle,

Thanks for the post of your logs. We’ve heard about the Pis running slow but haven’t gotten any logs so it’s hard to track down. We’ll look into it.

3

For completeness here is some of the PS output:

mycroft 760 1.1 3.8 181772 36908 ? Sl Feb27 12:27 python2.7 /usr/local/bin/mycroft-skills
root 761 0.3 2.6 145332 25276 ? Sl Feb27 3:25 python2.7 /usr/local/bin/mycroft-wifi-setup-client
mycroft 763 3.5 2.5 28320 24124 ? S Feb27 38:17 python2.7 /usr/local/bin/mycroft-messagebus
root 794 0.0 0.0 0 0 ? S< Feb27 0:00 [kworker/u9:0]
root 795 0.0 0.0 0 0 ? S< Feb27 0:00 [hci0]
root 796 0.0 0.0 0 0 ? S< Feb27 0:00 [hci0]
root 797 0.0 0.0 2068 132 ? S Feb27 0:00 /usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -
root 800 0.0 0.0 0 0 ? S< Feb27 0:00 [kworker/u9:2]
root 802 0.0 0.2 4812 2500 ? Ss Feb27 0:00 /usr/lib/bluetooth/bluetoothd
root 807 0.0 0.0 0 0 ? S Feb27 0:00 [kworker/3:3]
root 975 0.0 0.4 22468 4468 ? Ss Feb27 0:01 /usr/sbin/nmbd -D
pi 983 0.0 0.3 4976 3352 ? Ss Feb27 0:00 /lib/systemd/systemd --user
pi 989 0.0 0.1 7124 1416 ? S Feb27 0:00 (sd-pam)
pi 994 0.0 0.4 6348 4272 tty1 S+ Feb27 0:00 -bash
pi 1032 0.0 0.8 101324 7640 ? S<l Feb27 0:00 /usr/bin/pulseaudio --start --log-target=syslog
rtkit 1033 0.0 0.2 21376 2020 ? SNsl Feb27 0:01 /usr/lib/rtkit/rtkit-daemon
root 1046 0.0 1.3 35636 12668 ? Ss Feb27 0:04 /usr/sbin/smbd -D
root 1056 0.0 0.5 35636 4904 ? S Feb27 0:00 /usr/sbin/smbd -D
mycroft 1145 2.8 0.8 109736 8520 ? Sl Feb27 31:14 /usr/bin/pulseaudio --start --log-target=syslog
mycroft 1408 100 5.9 349136 55956 ? Sl Feb27 1092:35 python2.7 /usr/local/bin/mycroft-speech-client
pi 1485 0.0 0.0 3436 380 tty1 S+ Feb27 0:00 tail -f /var/log/mycroft-speech-client.log

4

Update: Issue found, fixed and not understood.(?)

For testing I went back to your original picroft SD image.

Slowly adding exactly what I did from history until it broke.
mycroft updates to 0.8.5, Raspi updates, upgrades, dist-upgrades, set static address.
MyCroft kept working and running about 62% CPU.
Until I added a mount point to my NAS into /etc/fstab.

All my Raspi(5) have nfs to the common NAS. Upgrading Raspian Jessie has changed how fstab auto mount works with a better(?) way. (Without telling me)
Everybody needs to add:
",noauto,x-systemd.automount"
to their options in fstab. You can read about this in many other forums.

Now, I (and inquiring minds) would like to know “why does an automount, wedge up picroft?”