0
Welcome Guest! Login
0 items Join Now

SOLVED RocketLauncher hangs up at 'installing sample data'

    • DanG's Avatar
    • DanG
    • Preeminent Rocketeer
    • Posts: 36750
    • Thanks: 3229
    • Custom work done

    Re: SOLVED RocketLauncher hangs up at 'installing sample data'

    Posted 10 years 5 months ago
    • Thanks Terp, appreciate it.
    • Terp's Avatar
    • Terp
    • Elite Rocketeer
    • Posts: 1720
    • Thanks: 23

    Re: SOLVED RocketLauncher hangs up at 'installing sample data'

    Posted 10 years 5 months ago
    • DanG wrote:
      Okay Steve and Terp if you could give this a try and report any bugs in the guide I would very much appreciate it.

      The guide was very helpful, Dan, and the install went off without a hitch...more or less. :)

      Here are my notes:




      Right after I double-clicked to run the MAMP install, I received a setup message about UAC (Universal Access Control) and what to do if we use it. Given that I never heard of it, I assumed my system isn't using it and continued. :) So maybe make mention of this and how the overwhelming majority of users can simply click next.

      This image is hidden for guests.
      Please log in or register to see it.




      Immediately following that message, I received a second setup message not in the guide that stated the need for C++, so although I instantly thought “bloatware,” I suspiciously continued and took one for the team and installed it.


      This image is hidden for guests.
      Please log in or register to see it.





      The guide states that "On completion of MAMP for WINDOWS Beta installation you see the Control Panel appear with your Apache and MySQL servers already started." That wasn't the case for me. Not only were the servers not started, but the entire program closed after installation, so I had to re-open it to get my first look at the control panel.

      That's when I got my THIRD pop-up. This time MAMP was warning me about port 80 being in use. Sure enough, I had WAMP running, so I exited WAMP in the event it was conflicting. Still fired the following message even after waiting a good bit after I closed WAMP:


      This image is hidden for guests.
      Please log in or register to see it.


      Maybe in the beginning of the guide mention that the user should ensure no other server/server-like applications are running. It makes sense now that I think about it, but the thought didn't cross my mind when I first tried to install it...only after it fired the 'port 80 in use' error. :)

      Nonetheless, even after closing WAMP, appache never stopped running! I had to pull up the command prompt (cmd) and run a netstat -ao..found an httpd.exe*32 running with a description of Apache HTTP server (though no known instances running since I closed WAMP)....closed it in task manager....boom. Good to go.





      The guide goes on to say "Set the Apache port setting to a value of your choosing. Click OK. Back at the Control Panel, click START Servers and then click the WebStart button." However, once I changed something in the preferences and clicked OK, all servers were restarted automatically, so you don't have to (and can't) click START...just click webstart.




      You then mention AdMiner: "Our next step is creating a DataBase (DB) to use for our first new site. I use ADMINER as my DB Admin console. I gave up on the PhPMyAdmin console ages ago. So launch AdMiner."

      I looked all over the main MAMP page, through the settings, the menu items, everwhere looking for AdMiner. I then figured out we would have to go to their website, download, and install (and probably configure), so I skipped this step... :)




      "Once logged we'll create our DB and set its collation. Collation refers to a set of rules that determine how data are sorted and compared." lol Being an economist, I have to make the 'data are' correction at least a dozen times a day. 'Data' are always plural. :)




      "The Apache server must be stopped so as to make any changes to the configuration or .ini files. This change must be made in the php.ini file which is located here -> C:\MAMP\htdocs\conf\php*.*.*"

      ^^ I found no 'conf' directory in that htdocs directory, just a test.php file and an htdocs text file. The 'conf' directory is in the root of MAMP, so chould probably change to: "This change must be made in the php.ini file which is located here -> C:\MAMP\conf\php*.*.*"

      ...and consider flipping those instructions so that the user checks their php version BEFORE navigating to the folder. Following it as it's currently worded, I navigated to the directory, then saw that I have multiple sub directories for the various php versions, then had to return to the control panel to figure out which version I was running, then must return back to the .../conf/ directory. If we figured out our version first before going to the conf folder, then we wouldn't have to switch back and forth an extra time. :)
      Again, this is just the economist in me always striving for efficiency. :)




      After turning off the output buffering, you write, " Let's refresh the Overview page and we'll see this:"

      I did a crtl+F5 and, of course, took me back to the first installation screen...not sure how you refresh it without that, given the URL doesn't change from installation screen to installation screen. "http://localhost:8080/xxxxxxx/installation/index.php#, so refresh for me back to square 1. I would either mention this, or disclose your trick to refresh it without having to start again!

      Once I got back to the last installation screen after the refresh, I noticed the Joomla warning about output buffering was still on!!! So I returned to the .ini file where I had turned 'output buffering' off and discovered that there was a commented out entry in the ini file that looked like the one to change:
      ; - output_buffering = Off        [Performance]



      While searching the ini file, it came across this line first (~line 87) and I made the change quickly without paying attention, saved, and returned to the installation. After the refresh showed that output buffering was still on, I had to go back into the ini file (and you know how much I hate doing things twice lol) and found the real entry to change. Therefore, consider adding the line number or mention that there is a commented out line and ensure the user changes the right one. :)

      Once I changed the right line (line 150 in the free MAMP version's), restarted the servers, and refreshed the installation screen (back to square 1), I was good to go.



      All in all, it does seem easier to use than some of the others I have used...simplistic, intuitive, right to the point. The price premium, however, would keep me from going pro (though the pro version had some nice features).

      I'll switch back and forth for awhile and see if it really grows on me, but it is as easy as 1-2-3.
    • Last Edit: 10 years 5 months ago by Terp.
    • The following users have thanked you: DanG

    • Terp's Avatar
    • Terp
    • Elite Rocketeer
    • Posts: 1720
    • Thanks: 23

    Re: SOLVED RocketLauncher hangs up at 'installing sample data'

    Posted 10 years 5 months ago
    • One more issue I just discovered (not with the guide, but the actual program itself):

      It doesn't seem to really close when I close it, yet it doesn't have an icon in my system tray (Windows 7). I discovered this when I went to launch it again and I got the port warning again, but this time port 8080 was in use...the same port I set MAMP to use when following your guide.

      Therefore, I had to do the ol' ctrl+alt+del task manager trick and close BOTH instances of httpd.exe, which are open as a result of MAMP.

      This isn't an issue if I stop the servers before closing the control panel/program, but if I just close it...believe it's still running in the background or at least it's not stopping the appache server.

      I'll continue to investigate.
    • The following users have thanked you: DanG

    • DanG's Avatar
    • DanG
    • Preeminent Rocketeer
    • Posts: 36750
    • Thanks: 3229
    • Custom work done

    Re: SOLVED RocketLauncher hangs up at 'installing sample data'

    Posted 10 years 5 months ago
    • Your notes post - thanks so much, in the rush to put it out it has become harder and harder for me to give myself the perspective of a novice user :(

      I laughed at the Microsoft Bloatware line. I'll mention that it represents libraries that MAMP for WINDOWS Beta needs to run and not Spam ware.

      The UAC warnings are shut off here as I'm the only one allowed on my PC but I'll have to mention that in the guide.

      The port 80 issue is interesting as it didn't happen for me but I think it better right off the bat to get the user off of port 80.

      I'll elaborate on the installing of Adminer.

      Your issue about httpd.exe is interesting. Mine doesn't do that but instead when I hit Stop Servers the mysqld.exe won't shut off and I was using Ctrl-Alt-Del. As I began using it though I realized I didn't have to do anything. Fire it up at the start of the day - do my work - then shut down the PC at night and everything goes smoothly.

      I have a ticket created with them about this issue. I'll mention the tray icon as thats a good idea and something I'm used to with WAMP.
      Right now I have an icon on the desktop if I need to restart the Control Panel.

      Last thing about it - it's the only local server software that the user can change caching systems on the fly.

      Again, thanks so much Terp
      This image is hidden for guests.
      Please log in or register to see it.
    • Last Edit: 10 years 5 months ago by DanG.

Time to create page: 0.068 seconds