Looks like the script is unable to download mosbuild.properties from Moodeaudio site. Maybe not really a script's error
Maybe Tim is working on the new one \o/
Thanks Koda. I was tearing my hair out - I had a script that worked, but thought I would check for a more current one - I got that (and got rid of my previous one in the process) - when it didn't work I was a bit lost...
Sorry if you thought I was dissing your script - I though I must have gotten an out-of-date one and that there must be a location I could go to find the newest.
Do you have a GitHub page, or similar?
Anyway - same result, but it is a funny message from the log...
The stepfile in ~/mosbuild reads '3A' and the etc/rc.local has the following:
The moosimbu.sh file has disappeared from /home/pi/ but not reappeared in /home/pi/mosbuild - that just has mosbuild.stepfile and rel-stretch
Last edited:
Gave up using the single-card script - a reimage of the stretch base and starting from scratch gave the same result.
Can one of the script builders confirm this is the case and not just me?
I've used the 'factory' script from moodeaudio.org and it's halfway through the second stage flawlessly, so nothing wrong with the source.
On the build scripts:
Can we get the new version of dd which supports the new 'status=progress' option? For newbies it can look like its all stopped and it does take some time to complete.
My build stopped with this and following a roboot added the mosbuild_worker.sh line:
losing the internet is not unheard of in our part of the third world, but where do I go to restart the script? There's no mosbuild.sh in /users/pi or anywhere else on the SD and the reboot seems to have lost mosbuild_worker.sh - in fact, a search doesn't turn up any 'mosbuild' file other than the log.
Nothing amended or edited in the build - used the file as downloaded and nothing fancy in the build options, other than asking to keep the image file for other builds.
Can one of the script builders confirm this is the case and not just me?
I've used the 'factory' script from moodeaudio.org and it's halfway through the second stage flawlessly, so nothing wrong with the source.
On the build scripts:
Can we get the new version of dd which supports the new 'status=progress' option? For newbies it can look like its all stopped and it does take some time to complete.
My build stopped with this and following a roboot added the mosbuild_worker.sh line:
losing the internet is not unheard of in our part of the third world, but where do I go to restart the script? There's no mosbuild.sh in /users/pi or anywhere else on the SD and the reboot seems to have lost mosbuild_worker.sh - in fact, a search doesn't turn up any 'mosbuild' file other than the log.
Nothing amended or edited in the build - used the file as downloaded and nothing fancy in the build options, other than asking to keep the image file for other builds.
Last edited:
Here are the results from the SSH of my mac on Pi3:
pi@raspberrypi:~ $ ping Google
ping: Google Name or service not known
pi@raspberrypi:~ $ wget Google
--2018-01-13 04:08:28-- http://www.google.com/
Resolving www.google.com (www.google.com)... 172.217.26.164, 2404:6800:4007:802::2004
Connecting to www.google.com (www.google.com)|172.217.26.164|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: http://www.google.co.in/?gfe_rd=cr&dcr=0&ei=PIZZWrjHFO3x8Aff0IKIBA [following]
--2018-01-13 04:08:28-- http://www.google.co.in/?gfe_rd=cr&dcr=0&ei=PIZZWrjHFO3x8Aff0IKIBA
Resolving www.google.co.in (www.google.co.in)... 216.58.199.195, 2404:6800:4007:801::2003
Connecting to www.google.co.in (www.google.co.in)|216.58.199.195|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'index.html.1'
index.html.1 [ <=> ] 13.11K --.-KB/s in 0.05s
2018-01-13 04:08:28 (258 KB/s) - 'index.html.1' saved [13420]
Index.html is available, please check below
pi@raspberrypi:~ $ ls
index.html index.html.1 mosbuild.sh
Edit:
Good news, its working now after I did the above
. The download has started and will update you on the progress of the image creation.Thanks all
Last edited:
Can you test these command before launching the moosimbu.sh
Code:
sudo apt-get update
sudo apt-get -y upgradeI'll test moosimbu.sh later this day, but maybe these commands can help and if it work give me a feedback.
Thank you & Good Luck.
Will do. I normally do out of habit, but didn't in this case as I thought I would leave the script to do the heavy lifting.
And, we have third-world internet which can just drop out.
What concerned me was that all the mosbuild files have disappeared... I can understand the build breaking with a file problem, but where have all the files gone?
This is one of the many improvements of Koda for the next release, if I remember the thing you must remove these two lines from the cancelBuild function before launch it the first time (line 48 and 49 of moosimbu.sh)
Code:
rm -rf mosbuild 2> /dev/null
rm -f *.zip 2> /dev/nullIf you want a more recent script, Like Koda & Tim said : just a little patience...
But you can test it, just remove the 2 lines before installing it, and you have this improvement !
For me with my 2 previous command from the previous post entered before the launch, the moosimbu.sh script work :
Code:
// STEP 3A - Install core packages
// STEP 3B - Install core packages
// STEP 4 - Install enhanced networking
** Compile bluez-alsa
// STEP 5 - Install Rotary encoder driver
** Compile WiringPi
** Compile rotary encoder driver
// STEP 6 - Compile and install MPD
// STEP 7 - Create moOde runtime environment
// STEP 8 - Install moOde sources and configs
// STEP 9 - Alsaequal
// STEP 10 - Optionally squash /var/www
// STEP 11 - Optionally, install latest Linux Kernel
// STEP 12 - Launch and configure moOde!
// STEP 13 - Final prep for image
// COMPONENT 1 - MiniDLNA
// COMPONENT 2 - Auto-shuffle
// COMPONENT 3 - MPD Audio Scrobbler
// COMPONENT 4 - Shairport-sync
// COMPONENT 5 - Squeezelite
// COMPONENT 6 - Upmpdcli
** Compile Libupnp jfd5
** Compile Libupnpp
** Compile Upmpdcli
** Compile Upexplorer
// COMPONENT 7 - Optionally install gmusicapi
// COMPONENT 8 - Local UI display
// COMPONENT 9 - Allo Piano 2.1 Firmware
// END
Last edited:
Zootalaws, it’s due to repo or Internet connection.
Unfortunately, this version doesn’t allow you to restart from your last stage.
The new one do this job and was tested for this case.
Hmmm, pm me with your email and I can send you the « last of year » version.
ATM, Tim is working on it for final Moode 4 version.
Thanks, that will fix it.
I found the version I used before on a USB stick, but I will use the new one with HeeBoo's fix and see if it works.
Thankyou to both of you - great work on the script(s)!
After installing on a separate 4GB SD card and inserting that in the Pi3 the moOde started and I got the IP address listed on my router. Using Nymeria or Nymeria or http://moode.<ip address>// did not work. I tried to SSH using root@moode and root@<ip address> worked fine and when I tried to enter either moode or raspberry as passwords I am getting error "Permission denied".
Edit: Here is what it looks when I SSH from my mac
Rajs-MBP:.ssh rmses$ ssh root@moode
The authenticity of host 'moode (192.168.1.112)' can't be established.
ECDSA key fingerprint is SHA256:cAmXLUKED8p3OBWWLcA2nV6YwJHdmLklFi5vQq+ocMs.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'moode,192.168.1.112' (ECDSA) to the list of known hosts.
root@moode's password:
Permission denied, please try again.
root@moode's password: <password tried = moode>
Permission denied, please try again.
root@moode's password: <password tried = raspberry>
root@moode: Permission denied (publickey,password).
Rajs-MBP:.ssh rmses$
I get the same error when I try to login directly on Pi using the keyboard. So unable to login or get it listed on my browser.
Edit: Here is what it looks when I SSH from my mac
Rajs-MBP:.ssh rmses$ ssh root@moode
The authenticity of host 'moode (192.168.1.112)' can't be established.
ECDSA key fingerprint is SHA256:cAmXLUKED8p3OBWWLcA2nV6YwJHdmLklFi5vQq+ocMs.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'moode,192.168.1.112' (ECDSA) to the list of known hosts.
root@moode's password:
Permission denied, please try again.
root@moode's password: <password tried = moode>
Permission denied, please try again.
root@moode's password: <password tried = raspberry>
root@moode: Permission denied (publickey,password).
Rajs-MBP:.ssh rmses$
I get the same error when I try to login directly on Pi using the keyboard. So unable to login or get it listed on my browser.
Last edited:
Thanks guys <@pi@moode.local> with moodeaudio password did the trick. I am now able to login to the Pi using SSH of my MAC. But still unable to launch the application using <http://moode.local> or <http://moode.192.168.1.112> or <http:/moode/> on my Chrome browser of mac machine. Do I need to do something more to launch the application on the browser for further setting up of my NAS and DAC setup.
Last edited:
Try http://192.168.1.112 if that is the IP address.
Or do 'sudo vi /etc/hosts' in Terminal if you know how to handle vi, or use a different editor, to edit the hosts file of your Mac. You could then use Nymeria provided that you put this hostname and IP address in your hosts file.
<http://192.168.1.112> did not work as I had tried it earlier. Regarding editing the host file in my MAC I am not proficient on Linux so for the sake of moOde I do not want to crank open my mac
I do not think so as I saw the success message on my raspbian once it wrote the moode image on my new SD card. I also got a message to take a backup of the same. After that I remove the SD card of raspbian and inserted the moode one and it loaded properly and I am able to login via SSH. So not sure where exactly the issue is with the new beta version as last year I used the older version of direct writing on the SD card and it worked flawlessly on my mac and mobile app as well. But with the new beta version which by the way looks nice I wanted to give it a try again with moode.
After removing the Raspbian SD card and inserting the new one the build begins, and you may need to wait for 45-60 minutes for it to complete.
Hmm no I think I did not wait for so long to SSH the Pi
Now when it boots for the first time after putting in the SD card once I get the login prompt does that means that the setup is done and completed or how do I know that the moOde is now done and I can login or use a browser to check?
Thanks
Edit: To be on safer side I restarted to write the image all over again from the Raspbian system.
Last edited: