WebGoat application not available

[GoogleCodeExporter]

What steps will reproduce the problem?
1. start the VM
2. navigate to the main page
3. click the WebGoat link
4. receive gttp error code 503 - Service Temporarily Unavailable

What is the expected output? What do you see instead?
I expected the application to be opened

What version of the product are you using? On what operating system?
1.1 in VirtualBox on a linux host

Please provide any additional information below.
There are other applications that give the same error message 
(ESAPI-Java-SwingSet-Interactive, bodgeit, yazd, wavsep, zapwave, 
AppSensorDemo). I'm guessing these applications need to be started?

Original issue reported on code.google.com by SWier...@gmail.com on 19 Aug 2013 at 6:54

[GoogleCodeExporter]

Same here with bwa on a linux box under VirtualBox

Original comment by paolo.ar...@gmail.com on 13 Sep 2013 at 12:01

[GoogleCodeExporter]

Thanks for reporting this and sorry that I have been slow to respond.  This 
appears to be an issue with the Tomcat Java Application Server.  It servers 
WebGoat and any other applications that are written in Java and/or JSP.  

The way the VM works is that Tomcat runs on 8080 and serves those applications. 
 Apache on port 80 / 443 then provides access to them using modproxy.  So, it 
could be that modproxy is having issues.

Can you get to WebGoat at this URL: http://owaspbwa:8080/WebGoat/attack

In looking into this issue, I found that there is a problem with Tomcat on the 
VM now that it is running as root (see 
https://bugs.launchpad.net/ubuntu/+source/tomcat6/+bug/632554 and 
http://serverfault.com/questions/157010/fix-a-tomcat6-error-message-bin-bash-alr
eady-running-when-starting-tomcat).  That bug prevents Tomcat from starting if 
anyone is logged on as the user Tomcat runs as (root in this case).  

Under VMware Workstation, Tomcat will start normally on boot up (though it 
sometimes takes a bit longer than some of the other components).  Unfortunately 
I don't have a VirtualBox system to test on, but one thing to ensure is that 
you are giving Tomcat a little extra time to come up.

If you replace /etc/init.d./tomcat6 with the attached file (and ensure that the 
permissions stay at -rwxr-xr-x and the owner/group stays at root/root), it 
corrects that issue and may fix this issue with Tomcat on VirtualBox.  If so, 
I'll push out a 1.1.1 VM to address this since it is a fairly significant issue.

If this doesn't work, please post the output of running the following command:
/etc/init.d./tomcat6 restart

Thanks.

Original comment by chuck.f....@gmail.com on 14 Sep 2013 at 7:30

• Added labels: Priority-High
• Removed labels: Priority-Medium

Attachments:

• tomcat6

[GoogleCodeExporter]

Chuck,

New file works.

cp --no-preserve=all tomcat6 /etc/init.d/tomcat6
/etc/init.d./tomcat6 stop
/etc/init.d./tomcat6 start

Original comment by jester...@gmail.com on 18 Sep 2013 at 3:34

[GoogleCodeExporter]

Thanks - just dropped this into a new download of 1.1 under VMWare Workstation 
& it fixed the same problem.

Original comment by ahar...@gmail.com on 19 Sep 2013 at 9:45

[GoogleCodeExporter]

Fixed in new 1.1.1 release.  Thanks much for reporting and verifying the fix on 
this issue.

Original comment by chuck.f....@gmail.com on 28 Sep 2013 at 7:24

• Changed state: Verified