Password encountered during installation on MacOS

[cwangv]

@phildunlap
Hi, Phil
Thanks for the reply.
So the syntax will be './ma.sh start'?
By the way, what version of Java SDK i should have? I have installed the latest 8 version.

[cwangv]

Just an update - I. managed to put in the password. But the next error is that the command can not be found.
See below screenshot

Any assistance is appreciated!

On a side note, I have the MangoES software running my windows laptop.

[phildunlap]

That would suggest to me that the ma.sh file is not set to be executable. You'll want to run sudo chmod +x ma.sh from the same directory.

[phildunlap]

Also note that the video here says Java 7 is required, but currently Java 8 or above is required.

https://help.infiniteautomation.com/mac-installation

[cwangv]

Good news! Phil.
After reading your reply, I tried what you suggested with 'sudo chmod +x ma.sh'. I was met with a permission denied error message.
Then I did a bit of web research on the file permission issues and I did a listing of the access rights on the files under 'bin' (I got the idea from a post on Stack Overflow).
below is what I found initially:

I saw the ma-start.sh and ma-stop.sh don't have executable permission but ma.sh does. Since ma-start.sh is called by ma.sh but due to the fact ma-start.sh does not have the executable permission, it errors on 'permission denied'.

To test it out my theory, I added the executable permission to both ma-start.sh and ma-stop.sh. And boom, it works.

Please let me know if my theory is not right.

Thanks again for pointing me at the right direction.

[phildunlap]

Hmm. You are correct that those shells scripts need also be executable. I do think the ma.sh needed it based on the error output I responded to, but that doesn't matter. Glad you got it working! When Mango's scripts perform an upgrade, they chmod +x Mango/bin/*.sh but it should also come packaged that way from the store.

Those scripts should come with the executable flag set to true. It may be that however you unzipped it didn't maintain the file permissions, or perhaps there is an issue there. I'll check it out.

[CraigWeb]

I find I always need to run chmod +x Mango/bin/*.sh on my Mac when unzipping mango.

[cwangv]

Thanks Phil and Craig.
I will remember to do that from now on.

[CraigWeb]

I believe/presume it is a Mac OS safety feature.

[terrypacker]

@CraigWeb @cwangv I also use OSX and have found that if you use the Finder to unzip a Mango core it will not preserve the executable bit for the *.sh files inside the zip and it also adds a quarantine attribute to every file.

You can manually remove these and then set the executable via chmod but I find that just unzipping the file from the command line will retain the executable bit. So I usually execute unzip <core-file>.zip. This still leaves all the files quarantined though. See the @ on the end of the attributes:

-rwxr-xr-x@ 1 mango staff 1089 Jul 8 22:15 ma.sh

xattr -l ma.sh
com.apple.quarantine: 0083;5d26502d;Safari;2F8BDDE1-3098-4B0D-A0B5-316BD592EFBF

You can remove the quarantine attribute for all the files recursively if you execute this in your MA_HOME folder.
sudo xattr -dr com.apple.quarantine . (Note the dot to mean from this directory)

The quarantine attributes don't seem to matter much as they are used by the launcher when you double click a file to execute it, which won't happen since you need to execute ma.sh start at the command line to run Mango.

[cwangv]

@terrypacker
Hi, Terry
thanks for the recommendation.
After reading your post, I re-downloaded the install file and found out that in Safari, at the end of the downloading, the zip file was unzipped by Safari and only the folder was shown and the original zip file was discarded in the recycle bin!!!!
There is got to be a setting somewhere to stop this from happening.

Cheers!

[terrypacker]

Ah yes I forgot about that setting. Using the menu: Safari --> Preferences --> General then uncheck:

Open "safe" files after downloading