[Chugalug] Amazon EC2 woes

Sean Brewer seabre986 at gmail.com
Thu Aug 22 16:29:26 UTC 2013


Just checking, but you ran: sudo /opt/bitnami/ctlscript.sh restart

Or even: sudo /opt/binami/ctlscript.sh apache restart

After you made those changes right? Anytime you make a change to apache
config settings, you have to restart apache.


On Thu, Aug 22, 2013 at 12:15 PM, Jon Stanford <jbirdvegas at aokp.co> wrote:

> I tried that exactly as it is in the gist but I'm still getting reclusive
> gitlab/... in the urls
>
>  I'm running grep -R "<directory />" against the instance for well over
> two hours without a return yet.  Along with that I've spent the morning
> googling and have yet to find an answer to where I could find that element
> without any luck.  I wouldn't mind giving you the key to the instance and
> allowing you to see the setup via ssh... if you would want to do that.
>  Like I said before nothing is on there yet so its not a huge deal I can
> always just boot a new instance of the AMI is anything messes up.  If it
> gets it fixed I'll definitely be creating an AMI with the correct settings
> to avoid this in the future.
>
> I'll let you guys know if grep returns anything... if it ever finishes haha
>
> If your interested in that please just email me directly @
> jbirdvegas at gmail.com and I'll send the key over. Thanks for the help
> either way
>
> ------------------------------
> *From: *"Sean Brewer" <seabre986 at gmail.com>
> *To: *"Chattanooga Unix Gnu Android Linux Users Group" <
> chugalug at chugalug.org>
> *Sent: *Thursday, August 22, 2013 10:43:50 AM
>
> *Subject: *Re: [Chugalug] Amazon EC2 woes
>
> That "Redirect permanent / http://jbirdvegas.org/gitlab/" shouldn't be
> inside the directory declaration for "/opt/bitnami/apps/gitlab/
> htdocs/public"
>
> Try changing it to something like this:
> https://gist.github.com/anonymous/90498fe6eb1f383c9502
>
> What Line 18-20 does is tell apache to redirect root to gitlab. It that
> change doesn't work, it is possible that "<directory />" is defined
> somewhere else, and you'll have to add "Redirect permanent /
> http://jbirdvegas.org/gitlab/". That's all I can figure without actually
> seeing the setup.
>
>
>
> On Thu, Aug 22, 2013 at 3:34 AM, Jon Stanford <jbirdvegas at aokp.co> wrote:
>
>> well I managed to create a new AMI; dropped the old instance and booted
>> the new instance. After reassociating the elastic IP address with the new
>> instance I was able to ssh into the instance... unfortunately the Redirect
>> statement seems to have no effect, even after I ran:
>>
>> sudo /opt/bitnami/ctlscript.sh restart
>>
>> here is what I have for my config
>> (/opt/bitnami/apps/gitlab/conf/gitlab.conf)
>>
>> bitnami at ip-10-164-73-31:/opt/bitnami$ cat apps/gitlab/conf/gitlab.conf
>> Alias /gitlab /opt/bitnami/apps/gitlab/htdocs/public
>>
>> <Directory "/opt/bitnami/apps/gitlab/htdocs/public">
>> Options -MultiViews
>> allow from all
>>
>> Redirect permanent / http://jbirdvegas.org/gitlab/
>>  PassengerUser git
>> PassengerGroup git
>>
>> </Directory>
>>
>> <Location /gitlab>
>> SetEnv RAILS_RELATIVE_URL_ROOT "/gitlab"
>> SetEnv MAGIC
>> "/opt/bitnami/ruby/lib/ruby/gems/1.9.1/gems/charlock_holmes-0.6.9.1/ext/charlock_holmes/dst/share/misc/magic.mgc"
>> PassengerAppRoot "/opt/bitnami/apps/gitlab/htdocs"
>> </Location>
>>
>> PassengerPreStart http://127.0.0.1:80/gitlab
>>
>> Adding the Redirect causes reclusive gitlabs :(
>>
>> http://jbirdvegas.org/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/gitlab/
>>
>> My first thought was to remove the /gitlab from PassengerPreStart... but
>> then the application becomes 404
>> and after a little googling I see why
>> http://www.modrails.com/documentation/Users%20guide%20Apache.html#PassengerPreStart
>>
>> Am I missing something?
>>
>> ------------------------------
>> *From: *"Jon Stanford" <jbirdvegas at aokp.co>
>>
>> *To: *"Chattanooga Unix Gnu Android Linux Users Group" <
>> chugalug at chugalug.org>
>> *Sent: *Thursday, August 22, 2013 12:48:33 AM
>>
>> *Subject: *Re: [Chugalug] Amazon EC2 woes
>>
>>
>> Ok I'm going to try creating a new AMI
>>
>> about the authorized_keys file ... I'm kinda up the creek on that one as
>> I'd need to ssh into the instance in order to modify the file :(
>>
>> again (and I can't say this enough) thanks guys! I'll let you know how it
>> goes
>> ------------------------------
>> *From: *"Sean Brewer" <seabre986 at gmail.com>
>> *To: *"Chattanooga Unix Gnu Android Linux Users Group" <
>> chugalug at chugalug.org>
>> *Sent: *Thursday, August 22, 2013 12:44:45 AM
>> *Subject: *Re: [Chugalug] Amazon EC2 woes
>>
>> You *can *create an AMI from the running instance, and create a new
>> instance from that AMI with your new key:
>> http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/creating-an-ami.html?r=8284
>>
>>
>> On Thu, Aug 22, 2013 at 12:41 AM, wes <wes at the-wes.com> wrote:
>>
>>>
>>>> jbird at jbird:~$ chmod 400 ~/Downloads/laptop.pem
>>>> jbird at jbird:~$ ssh -i ~/Downloads/laptop.pem
>>>> ubuntu at ec2-54-235-163-94.compute-1.amazonaws.com
>>>> Permission denied (publickey).
>>>> jbird at jbird:~$ ssh -i ~/Downloads/laptop.pem
>>>> JBirdVegas at ec2-54-235-163-94.compute-1.amazonaws.com
>>>> Permission denied (publickey).
>>>> jbird at jbird:~$ ssh -i ~/Downloads/laptop.pem
>>>> root at ec2-54-235-163-94.compute-1.amazonaws.com
>>>> Permission denied (publickey).
>>>>
>>> you also need to enable the public key in the authorized_keys file. the
>>> fact that the filename ends in .pem makes me wonder where you got it.
>>>
>>>  I'm on a different laptop and don't have the original key used to
>>>> generate the instance... am I screwed?  Should I just dump this instance
>>>> and make a new one? (it wouldn't be a huge pain I'd just have to email a
>>>> couple users but nothing important is hosted there yet)
>>>>
>>> Yup, you're screwed. The easiest solution is indeed to nuke it and start
>>> over. There is a way to recover but it's likely more work than it's worth
>>> in your situation.
>>>
>>> -wes
>>>
>>> _______________________________________________
>>> Chugalug mailing list
>>> Chugalug at chugalug.org
>>> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>>
>>>
>>
>> _______________________________________________
>> Chugalug mailing list
>> Chugalug at chugalug.org
>> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>
>>
>>
>> _______________________________________________
>> Chugalug mailing list
>> Chugalug at chugalug.org
>> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>>
>>
>
> _______________________________________________
> Chugalug mailing list
> Chugalug at chugalug.org
> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>
>
> _______________________________________________
> Chugalug mailing list
> Chugalug at chugalug.org
> http://chugalug.org/cgi-bin/mailman/listinfo/chugalug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://chugalug.org/pipermail/chugalug/attachments/20130822/a266794c/attachment-0001.html>


More information about the Chugalug mailing list