Missing mycroft.conf

[TongShanHui]

I've just installed mycroft on Ubuntu 17.04, but have no mycroft.conf file, so nothing is working except cli. Please help.

[LearnedVector]

@TongShanHui can you give us more information on what you've tried? have you ran the ./dev-setup.sh script?

[TongShanHui]

I have run dev-setup.sh twice, and still nothing. Have removed cloned repository, re-cloned, re-run install and dev setup. I'm constantly asked to rebuild Mimic, which I have agreed on one occasion, refused on the other.

[el-tocino]

Assuming dev_setup completes without issue, have you started mycroft up yet?

[TongShanHui]

I have started using ./start.sh service, ./mycroft.sh start, on separate occasions and have tried starting each individual task on separate terminal screens.

[TongShanHui]

Quick question that could solve alot, do Mycroft HAVE to run in a virtualenv?

[el-tocino]

No it does not. Mk1/picroft don't, you can run without the venv if you have all the requirements installed to the system, and adjust the scripts accordingly.

[TongShanHui]

Okay, that's good. I have it on a 1Tb partition with ubuntu 17.04 which is designed to act as mycroft master, for when I begin to run a picroft system around the flat.

[el-tocino]

When you started it, were you able to pair it [from cli]?

[TongShanHui]

I have no idea, mycroft has no vocab or dialog, which I assume if paired correctly, would be added.

[el-tocino]

Try running "msm default" (should be in msm/ directory off mycroft core) from a shell, see if that installs default skills? The logs for a git install normally show up under scripts/logs/ with various breakdown from there you'll see. Check those for errors as well.

[TongShanHui]

Right, it also seems that mimic wasn't added either, so going to re-run through the tools, and then reboot.

[TongShanHui]

have run msm default, it's installed them, and lost them, neither does the vocab or dialog. Still no vocab or dialog files.

[el-tocino]

Not clear about what you're referring to? What was lost? Vocab and dialog are usually hanging out in the skill subdirectories.

[TongShanHui]

it downloaded the skills, then lost them. IE the skills directory is full of empty folders, all folders are named with the different skills.

AlarmSkill PairingSkill WeatherSkill TimeSkill StopStill

but all are just empty

[el-tocino]

That's unusual. What was the parent directory for the empty skill folders?

[forslund]

What @el-tocino said. The skills should be installed to /opt/mycroft/skills and the default skill folders are named skill-* or fallback-*

[TongShanHui]

yes, the skills are there in /opt/mycroft/skills but when mycroft loads the CLI declares that they are not found. have removed everything and starting again, maybe I have missed something.

[TongShanHui]

Have reinstalled mycroft, run dev_setup.sh, rebooted, and run start-mycroft.sh all, after pairing, it makes an apology for not being able to download default skills, when I run msm default I get error 111.

Now installing 16.04 as it's the only thing that I can think of, that would now cause a problem.

[el-tocino]

That's not likely the issue. hold on.

[el-tocino]

MSM is saying it can't pull the skills list from github.

[TongShanHui]

which is even more confusing as it pulled them just fine last night.

[forslund]

Hmm, strange. Can you provide the exact error message you're seeing in the CLI?

[TongShanHui]

error 111 that is all it gives me.

[forslund]

Hmm, wonder if github has some request limit? (since it's from raw.githubusercontent...)

[TongShanHui]

[forslund]

I believe you. for me it's working however so there might be some sort of limit. I've seen similar things using nltk (has a package list on raw.githubusercontent as well). You might have to leave it for an hour or two and try again later.

Are your skill folders in /opt/mycroft/skills still empty?

[TongShanHui]

No, the folders are populated. Including vocab and dialog files.

[forslund]

Ok then you should be fine using the skills. If you're running master branch try

./mycroft.sh start
./start.sh cli

or if on dev

./start-mycroft.sh all
./start-mycroft.sh cli

(wait 10 sec to let all skills load)

Then when you get the mycroft CLI type in what time is it and hit enter. See if any obvious error message is displayed.

[TongShanHui]

it seems to be okay, although it tells me an error occurred while installing default skills.

[forslund]

Understandable as an error actually occurs.

If you haven't paired Mycroft should prompt you to do so as soon as you try to speak "Hey mycroft... anything"

If there's no chime after "hey mycroft" there may be some issue with the mic.

There is an audiotest to test the mic.

./start-mycroft.sh audiotest or ./start.sh audiotest depending on if you're on dev or master.

Then as soon as you see messages about ALSA start making some noise. The script will then play back whatever noise the mic caught.

[TongShanHui]

Mycroft is paired (it hasn't reacted to being paired, so I assume all went well), it has audio input and output working, have set and turned off an alarm with Mycroft using voice commands and background noise, so I can only assume all is well, so far. Can sort out skills through manual download from git.

[forslund]

Ok, sounds good. So the only issue is the msm error right now? Or is there anything else not working?

[absentdream]

hi. i did a test on vanila fresh install of 17.04 and latest git

20:34:25.506 - requests.packages.urllib3.connectionpool - DEBUG - https://api.mycroft.ai:443 "GET /v1/auth/token HTTP/1.1" 401 38 20:34:25.510 - mycroft.client.speech.listener:transcribe:154 - WARNING - Access Denied at mycroft.ai

device wont speek download etc.. a hunch is is ssl comincation error aka ssl2/3 ?

[forslund]

@absentdream that might just be that you haven't paired yet. The skills takes a while to download. Leave it on for a while and then ask "hey mycroft, pair device" or run ./msm/msm default to download all default skills manually.

[absentdream]

ooops and doh... :) @forslund god catch... :) will run ./msm/msm default and try again...

[absentdream]

@forslund i found a dif in the way cd command works in 17.04 and 16.04 thus the script install-pygtk.sh fails to install see https://github.com/MycroftAI/mycroft-core/issues/1131

[arjenlentz]

@TongShanHui For reference, OS error code 111 is "Connection refused", indicating that there is nothing listening on the destination port to answer the TCP connection request. So it's NOT a) a server application actively refusing to serve a request due to authentication or other issues, or b) a firewall issue (that would cause a different error).

My first guess would be that it was most likely a transient error caused by the server end. Does it still occur now?

[TongShanHui]

@arjenlentz okay have left mycroft powered down for a couple of days, whilst preparing Raspi for picroft, begun ./start-mycroft.sh debug and all working well, so I exit the debug cli, and run ./msm default and it connected and updated without error. So I can only say that, in the downtime something corrected itself. It is still looking for mycroft.conf in multiple locations, but only finding one instance, does it need multiple instances or just one?

@Mn0491 @el-tocino @forslund @absentdream @arjenlentz Thank you all for your help, spoke more with @absentdream last night and he managed to locate possible difference between 16.04 and 17.04 which I shall be looking into today. Once again, thanks for all your help and assistance. :)

[penrods]

Can we close this now, @TongShanHui ?

[TongShanHui]

Yes, have mycroft running on different OS. Sorry have kept open just in case of similar problem, instead of raising another issue. :)

[penrods]

No problem! I'll close this for now.