davidc
Level 1 (15 points)

Q: application won't start, probable privilege problem

I have several PromiseR6 RAID arrays that I recently moved from a Mac Mini to the new Mac Pro.  There is a Promise utility to configure the arrays and do various maintenance. The Promise utility won't start...the application icon bounces in the dock for a few seconds and then exits.

 

Key information:

The utility will run if I sign on as root.

I created a test ID with admin privileges, signed on with it, and it will run.

My regular ID has admin privileges.

I've deleted and installed the most recent version of the app multiple times, same results.

My current, regular ID was created as new on the Mac Pro, but the Home directory was moved from an older Mac Pro to the new Mac Pro, and this home directory exists on the RAID array.

All system files are on the Mac Pro internal SSD boot drive.

 

Clearly there's something different about my ID.  What could it be and how can I resolve it?

 

Thanks!

Mac Pro, OS X Mavericks (10.9.4)

Posted on Jul 17, 2014 1:36 AM

Close
davidc

Q: application won't start, probable privilege problem

  • All replies
  • Helpful answers

Previous Page 2

  • by davidc,

    davidc davidc Jul 17, 2014 10:05 PM in response to davidc
    Level 1 (15 points)
    Jul 17, 2014 10:05 PM in response to davidc

    oops, type...I meant NOTE the response from the previous command

  • by davidc,

    davidc davidc Jul 17, 2014 10:13 PM in response to davidc
    Level 1 (15 points)
    Jul 17, 2014 10:13 PM in response to davidc

    added escape to handle space

     

     

    total 624

    drwxrwxrwx  3 0  0  -    102 Jul 17 01:18 .

    drwxrwxrwx  8 0  0  -    272 Jul 17 01:18 ..

    -rwxrwxrwx  1 0  0  - 317888 Apr 21 03:20 Promise Utility

  • by Linc Davis,

    Linc Davis Linc Davis Jul 17, 2014 10:13 PM in response to davidc
    Level 10 (208,000 points)
    Applications
    Jul 17, 2014 10:13 PM in response to davidc 
    ls -@Oaen /A*/Promise*.app/*/MacOS | pbcopy

  • by davidc,

    davidc davidc Jul 17, 2014 10:18 PM in response to Linc Davis
    Level 1 (15 points)
    Jul 17, 2014 10:18 PM in response to Linc Davis

    I should've paid more attention to the error.  Again, same output:

    total 624

    drwxrwxrwx  3 0  0  -    102 Jul 17 01:18 .

    drwxrwxrwx  8 0  0  -    272 Jul 17 01:18 ..

    -rwxrwxrwx  1 0  0  - 317888 Apr 21 03:20 Promise Utility

  • by Linc Davis,

    Linc Davis Linc Davis Jul 17, 2014 10:29 PM in response to davidc
    Level 10 (208,000 points)
    Applications
    Jul 17, 2014 10:29 PM in response to davidc

    Those are wide-open permissions, and if they were set by an installer, it was botched. But the permissions wouldn't prevent the app from launching in any account. The problem lies elsewhere. Maybe some required support file has wrong permissions.

     

    Since I know nothing about the software, I don't know that I can do any more to help. Try reinstalling it. Probably there will be no change. In that case, refer to the developer for support.

  • by davidc,

    davidc davidc Jul 17, 2014 10:38 PM in response to Linc Davis
    Level 1 (15 points)
    Jul 17, 2014 10:38 PM in response to Linc Davis

    Thanks for your help.  So far the support at Promise is junior level and is terrible.  All of this effort is to get their utility running so the real problem can be solved which is the constant unmounting of one of the arrays.  This is a big headache.

  • by macnicol,

    macnicol macnicol Jul 18, 2014 8:55 AM in response to davidc
    Level 1 (0 points)
    Jul 18, 2014 8:55 AM in response to davidc

    Had a similar problem after installing Mavericks. Some apps would not run or would start to run and stop with an error message. After a week of trying to reset permissions and reinstalling affected apps to no avail, I remembered something that is not in the Mavericks install instructions.

     

    Beware!  When you initialize your boot disk to install Mavericks, be sure that you specify "Journaled" and NOT "Case-sensitive, Journaled". Previous OSX installers would check this and give an error message. Mavericks does NOT! If you install using "Case-sensitive" many apps will not work.

  • by mmarionsd1,

    mmarionsd1 mmarionsd1 Aug 28, 2014 12:02 PM in response to davidc
    Level 1 (9 points)
    Aug 28, 2014 12:02 PM in response to davidc

    I just had a very similar issue and figured it out after a bunch of trial and error.  I was going to try to dtruss the application to see if it was failing on something obvious, but that failed, so I ran it manually via the terminal and finally got helpful info:

    MigiMac (OSX) [~ (master)↓⚡]$ /Applications/Promise\ Utility.app/Contents/MacOS/Promise\ Utility

    2014-08-28 11:51:54.680 Promise Utility[13319:507] Stsrt find product

    httpd: Could not reliably determine the server's fully qualified domain name, using MigiMac.local for ServerName

    (48)Address already in use: make_sock: could not bind to address 127.0.0.1:8080

    no listening sockets available, shutting down

     

    I finally realized that the apache server the utility tries to start up in the background was clashing with an ssh process I was running that forwarded port 8080.  I stopped that ssh and now the utility starts up ok.

  • by T-Ray,

    T-Ray T-Ray Sep 22, 2014 4:18 AM in response to mmarionsd1
    Level 2 (225 points)
    Sep 22, 2014 4:18 AM in response to mmarionsd1

    I've had the drive for several months and couldn't get the utility to launch, even after a dozen emails and failed Promise support suggestions. I finally gave up since I had too much else on my plate.

     

    But this morning, for the heck of it, I tried again and a search turned up this discussion. Based on some of the comments here I created a new admin account and signed in. The utility started right up in the new account. However, that doesn't really fix my problem since I need it to run in my "real" admin account.

     

    Unfortunately, I'm not that savvy in the terminal and was wondering if there's some simple instruction someone could provide that would help me resolve the issue that mmarionsd1 describes above. How do I go about identifying the "ssh process I was running that forwarded port 8080"? And once identified, how do I stop it?

     

    Thanks a ton in advance.

    T-Ray

  • by Gav B,

    Gav B Gav B May 27, 2015 6:13 PM in response to T-Ray
    Level 1 (0 points)
    May 27, 2015 6:13 PM in response to T-Ray

    This port 8080 solution that mmarion revealed helped me to solve the issue for good as our server also runs services on 8080.

     

    If you can switch off the other service using port 8080, then the Promise Utility should run and it allows you to change its port number in the Preferences. Then you can switch on the other service again.

     

    If you can't switch off the other service or don't know how, you can manually change the port number that Promise Utility uses. This in the httpd.conf file buried inside the Promise Utility.app folder.

     

    The path to this file is:

    /Applications/Promise Utility.app/Contents/Resources/apache2/conf/httpd.conf

     

    You can get to the folder easily in Finder by using Go -> Go to Folder… and pasting the above path into the dialog box.

     

    Using TextEdit or some other text editor, open up the httpd.conf file and look for where is says:

    Listen 127.0.0.1:8080

     

    Change the 8080 to something else above 1000 that you know is available, save the config file and then reopen Promise Utility. If all goes well, it should now open as it doesn't conflict with the other service running on port 8080.

     

    Hope this helps someone.

  • by rgilbert,

    rgilbert rgilbert Oct 14, 2015 8:11 AM in response to Gav B
    Level 1 (85 points)
    Oct 14, 2015 8:11 AM in response to Gav B

    This thread solved my problem also.  I tried 127.0.0.1:8080 in Safari and received an error message referring to my "Cardo Updater" which is an app running in the background that I had forgotten about.  It is for updating a Scala G9 headset for motorcycle helmets.  I took Gav Bs' suggestion and edited the Promise Utility http.conf file to port 8888 and now everyone is happy again. Thank you Gav B and mmarionsd1.

Previous Page 2