Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 332674

Summary:	8.0.0M2 fails to start on Amazon EC2 with regular user
Product:	[RT] Jetty	Reporter:	yvsong
Component:	server	Assignee:	Greg Wilkins <gregw>
Status:	CLOSED INVALID	QA Contact:
Severity:	minor
Priority:	P3	CC:	janb, jetty-inbox
Version:	8.0.0
Target Milestone:	7.1.x
Hardware:	Other
OS:	Linux
Whiteboard:

Description yvsong

2010-12-15 14:29:49 EST

Build Identifier: 8.0.0M2

On Ubuntu10.10 64 bit on an Amazon EC2 micro instance, with following ports open: SSH 22, HTTP 80, HTTP 443, after installation, Jetty runs successfully with a regular user (standard user name: ubuntu) on port 8080. I can access the server locally but not remotely. In order to see if I can access it remotely, I tried to open HTTP 8080 port on my Amazon instance by revising my security group, and "jetty.sh start" fails to start. I closed port 8080 on Amazon, now only the initial 3 ports are open, but I still cannot start Jetty on port 8080 as a regular user. However, I can start it as root using sudo, on either port 80 or 8080.

Reproducible: Always

Comment 1 yvsong

2010-12-15 23:35:53 EST

Following http://wiki.eclipse.org/Jetty/Howto/Port80 , I configured xinetd to redirect port 80 to 8080, and started Jetty successfully as a regular (non-root) user.

Comment 2 Jan Bartel

2010-12-16 03:00:09 EST

Only the root user can open low numbered ports like 80. You have taken the right action in following the instructions on http://wiki.eclipse.org/Jetty/Howto/Port80

Comment 3 yvsong

2010-12-16 09:18:40 EST

I was not clear enough in the original description. The problem is that after some tweaking of my security group on Amazon EC2, I could not start Jetty on port 8080 as a regular user with "jetty.sh start" -- This should not happen. "java -jar start.jar" worked. The problem went away magically after I configured xinetd.

Comment 4 Greg Wilkins

2011-01-10 10:44:24 EST

Sorry but I can't see anything to fix here?

If you have any exceptions or errors or more detail, please reopen issue.

cheers