[cs615asa] Issues with NetBSD AMI

[Tejas]

The first thing to do on NetBSD

# pkg_add -v bash

Then it's all downhill from there :)


On 04/07/2012 12:19 PM, Piotr Lupinski wrote:
> This assignment has taught me never to use NetBSD.  One of the biggest 
> lessons I've learned in this class.  25 POINTS PLEASE.
>
> On Sat, Apr 7, 2012 at 12:13 PM, Tejas <tnadkarn at stevens.edu 
> <mailto:tnadkarn at stevens.edu>> wrote:
>
>     I'm just using ami-1f8b5576, it's NetBSD 6.0 beta just like the
>     other one and it works fine - except this one is x86_64 vs
>     i386...just make sure you tweak your pkg_path if you're using
>     native installer.
>
>     Jan,
>
>     Please let me know if you have an issue but I've already started
>     working on this using the new AMI.
>
>
>     On Apr 7, 2012, at 12:11 PM, Drew Michel wrote:
>
>>     I've been having the same problem too.
>>
>>     The strange thing is that when I created that same ami last week
>>     everything was working properly.
>>
>>     Umm
>>
>>     Drew
>>
>>     On Apr 7, 2012, at 11:31 AM, Tejas <tnadkarn at stevens.edu
>>     <mailto:tnadkarn at stevens.edu>> wrote:
>>
>>>     Something is definitely screwed up...I can't ping any instance
>>>     of that AMI while other AMI's ping fine...I have ICMP open in
>>>     the security group.
>>>
>>>     If AWS itself can't reach the instance, I don't think I'm going
>>>     to have much luck. Any chance we can use a different NetBSD AMI?
>>>
>>>     How about AMI *ami-1f8b5576*? It seems similar but newer and I
>>>     was able to spin one up and log in fine.
>>>
>>>
>>>     On 04/07/2012 11:21 AM, Tejas wrote:
>>>>     Starting on the extra credit assignment and for some odd reason
>>>>     the ami-820fddeb we're asked to use is having problems. I've
>>>>     spun up 3 different instances of th same AMI and I can't ssh
>>>>     into it. On AWS dashboard, the status checks remain on
>>>>     Initializing and never complete. Meanwhile other AMIs all seem
>>>>     to work fine, status checks complete and I can login.
>>>>
>>>>     After about 10-15 mins AWS reports that the instance fails the
>>>>     reachability test...weird thing is this is right after spinning
>>>>     it up and not changing anything.
>>>>
>>>>     Anybody else seen this?
>>>>
>>>>     -Tejas
>>>>
>>>>     _______________________________________________
>>>>     cs615asa mailing list
>>>>     cs615asa at lists.stevens.edu <mailto:cs615asa at lists.stevens.edu>
>>>>     https://lists.stevens.edu/cgi-bin/mailman/listinfo/cs615asa
>>>     _______________________________________________
>>>     cs615asa mailing list
>>>     cs615asa at lists.stevens.edu <mailto:cs615asa at lists.stevens.edu>
>>>     https://lists.stevens.edu/cgi-bin/mailman/listinfo/cs615asa
>>     _______________________________________________
>>     cs615asa mailing list
>>     cs615asa at lists.stevens.edu <mailto:cs615asa at lists.stevens.edu>
>>     https://lists.stevens.edu/cgi-bin/mailman/listinfo/cs615asa
>
>
>     _______________________________________________
>     cs615asa mailing list
>     cs615asa at lists.stevens.edu <mailto:cs615asa at lists.stevens.edu>
>     https://lists.stevens.edu/cgi-bin/mailman/listinfo/cs615asa
>
>
>
>
> _______________________________________________
> cs615asa mailing list
> cs615asa at lists.stevens.edu
> https://lists.stevens.edu/cgi-bin/mailman/listinfo/cs615asa

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.stevens.edu/cgi-bin/mailman/private/cs615asa/attachments/20120407/c7c282b4/attachment-0001.html>