Home / user-117249

Plutext's questions

Martin Hope
Plutext
Asked: 2015-09-21 01:28:42 +0800 CST
  • 1

I'm trying to reset the ILOM root password on a SPARC Enterprise T5240.

Neither of the 2 methods described below work for me, so I'm after further suggestions (short of guessing the root password - I've been trying that!).

Method 1 - Jumper J10401

Lost root password and ILOM config is reset using Jumper J10401 (short pins 1-2)

Some web sources suggest you may have to press the front panel Power button to power on the system to complete the reset.

But for whatever reason, nothing happens when I press that button (ie the system doesn't power up. The SER MGT port still works, but only ILOM is powered)

Method 2 - default user plus physical presence

As per ILOM 3.1 docs - Password Recovery for root Account

I suspect the problem here is that this only works for ILOM 3.x, and the server is running 2.x?

Any suggestions gratefully received, including tricks to bypass ILOM completely and just boot Solaris?

sun
Martin Hope
Plutext
Asked: 2015-01-14 16:24:03 +0800 CST
  • 0

I created a new EC2 instance using the official CentOS 7 (x86_64) HVM image.

I ran: 

yum upgrade

At:

Running transaction
Warning: RPMDB altered outside of yum.
  Updating   : 32:bind-license-9.9.4-14.el7_0.1.noarch                                                                       1/80
  Updating   : selinux-policy-3.12.1-153.el7_0.13.noarch                                                                     2/80

I can no longer SSH into the box :-(

I can establish a connection on port 22, but see nothing more after that running ssh client in verbose mode.

I guess mounting the EBS on another instance is my only means of recovery.

If I do that, what's the easiest way to restore ssh access? I'm not sure whether that update set selinux to enforcing, and whether that would even be the issue here?

ssh
Martin Hope
Plutext
Asked: 2013-05-12 20:00:54 +0800 CST
  • 1

I have been trying to restrict access to a port on an EC2 box to a single remote computer (my desktop).

The various "what is my IP" services around on the Internet all consistently report an IP address IP1.

However, when I look in the access logs on the EC2 box, I see my address is actually recorded as IP2.

Not surprisingly, restricting access only works properly (via EC2's security group rules, or iptables) when I use this IP2 address.

Now my question: is it Amazon EC2 which is translating my address as some point, or are all the "what is my IP" services (consistently) wrong? Either way, what is different about EC2?

amazon-ec2
Martin Hope
Plutext
Asked: 2013-05-12 02:59:33 +0800 CST
  • 0

I have a web application, and I'd like to limit file upload size.

I thought I'd try using squid for this, via its directive request_body_size_max.

I have my webserver running on port 8080, and I've installed squid 3.1.19 on the same server (Ubuntu 12.04 LTS). The server is running on Amazon's EC2, if that makes any difference.

squid.conf contains:

http_port 3128 transparent

I added to IPTables:

iptables -t nat -A PREROUTING -p tcp --dport 8080 -j REDIRECT --to-port 3128

When I visit the webserver, the result in squid's logs, is:

Forwarding loop detected.

What do I need to do to prevent this? thanks...

amazon-ec2