Re: Re: Re: Installation Help Needed
Back to the original post:
{tomcat user} = use the name of the tomcat process owner ;)
You could also have run:
lsof -i :8080
I should've suggested that instead.
Doing that I got this:
java19217 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19218 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19219 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19220 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19221 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19222 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19223 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19224 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19225 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19227 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19228 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19229 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19230 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19231 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19232 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19233 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19234 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19235 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19236 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19237 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19238 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19239 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19240 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19241 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19242 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19243 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19244 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19245 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19246 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19247 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19248 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19249 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19250 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19251 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19252 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19253 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19254 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19255 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19256 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19257 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19258 root5u IPv4 811539 TCP *:webcache (LISTEN)
No big deal. The fact that you didn't see anything is the key:
Tomcat didn't successfully start.
So now it's a matter of digging through the logs.
Look for a file catalina.out
What I did here was this:
1. Ran shutdown.sh
2. Deleted catalina.out
3. Did a touch catalina.out (In case it had issues with it not being
there)
4. Re-ran startup.sh
Here is the contents of the file now:
Apr 1, 2004 9:35:13 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Apr 1, 2004 9:35:13 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3097 ms
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardHost
getDeployer
INFO: Create Host deployer for direct deployment ( non-jmx )
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Processing Context configuration file URL
file:/usr/local/jakarta-tomcat-5.0.19/conf/Catalina/localhost/admin.
xml
Apr 1, 2004 9:35:15 AM org.apache.struts.util.
PropertyMessageResources init
INFO: Initializing, config='org.apache.struts.util.LocalStrings',
returnNull=true
Apr 1, 2004 9:35:15 AM org.apache.struts.util.
PropertyMessageResources init
INFO: Initializing, config='org.apache.struts.action.ActionResources',
returnNull=true
Apr 1, 2004 9:35:16 AM org.apache.struts.util.
PropertyMessageResources init
INFO: Initializing, config='org.apache.webapp.admin.
ApplicationResources', returnNull=true
Apr 1, 2004 9:35:19 AM org.apache.catalina.core.StandardHostDeployer
install
INFO: Processing Context configuration file URL
Re: Re: Re: Installation Help Needed
On Thu, Apr 01, 2004 at 11:07:21AM -0500, Stormblade wrote: : java19217 root5u IPv4 811539 TCP *:webcache (LISTEN) OK, so Tomcat is up and listening. (I'll assume that webcache = 8080; that's for you to confirm.) Next step: from the Tomcat host, try to interact with the port. Use Lynx if it's available; otherwise send raw HTTP requests to the port, e.g. telnet localhost 8080 Don't worry about specifying valid webapp paths and such: IIRC tomcat doesn't even send an error page when you connect from the browser, right? If that works -- even a tomcat error page -- try the same technique from your other machine. (telnet tomcat-host 8080 or lynx http://tomcat-host:8080/something) If that fails, then you're pretty much down to a networking problem (fw/router/host file/DNS mixup). Run ifconfig on the tomcat server to confirm the IPs are what you think they are. Issue requests to the IPs, if need be. -QM -- software -- http://www.brandxdev.net tech news -- http://www.RoarNetworX.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Re: Installation Help Needed
I know it's simple but have you tried using the IP as in
http://xxx.xxx.xxx.xxx:8080 ?
Just a thought.
Otherwise you might wish to confirm the port is open.
No offense but sometimes we get burned by the silly little things.
Since you are running from the command line you are starting as root (This
is the same as my TC4 box).
But I get only one line of output and one pid (I think that this may be due
to Linux flavors)
As a last ditch effort try this:
Shut down apache.
Change the port on the connector for Tomcat to 80.
Restart Tomcat.
Then see if you can get to Tomcat on port 80 instead.
Everything seems to point to a firewall/router ACL issue.
Are there any devices between the client and server?
Doug
- Original Message -
From: Stormblade [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 11:07 AM
Subject: Re: Re: Re: Installation Help Needed
Back to the original post:
{tomcat user} = use the name of the tomcat process owner ;)
You could also have run:
lsof -i :8080
I should've suggested that instead.
Doing that I got this:
java19217 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19218 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19219 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19220 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19221 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19222 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19223 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19224 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19225 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19227 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19228 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19229 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19230 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19231 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19232 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19233 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19234 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19235 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19236 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19237 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19238 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19239 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19240 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19241 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19242 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19243 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19244 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19245 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19246 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19247 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19248 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19249 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19250 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19251 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19252 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19253 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19254 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19255 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19256 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19257 root5u IPv4 811539 TCP *:webcache (LISTEN)
java19258 root5u IPv4 811539 TCP *:webcache (LISTEN)
No big deal. The fact that you didn't see anything is the key:
Tomcat didn't successfully start.
So now it's a matter of digging through the logs.
Look for a file catalina.out
What I did here was this:
1. Ran shutdown.sh
2. Deleted catalina.out
3. Did a touch catalina.out (In case it had issues with it not being
there)
4. Re-ran startup.sh
Here is the contents of the file now:
Apr 1, 2004 9:35:13 AM org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Apr 1, 2004 9:35:13 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3097 ms
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.0.19
Apr 1, 2004 9:35:13 AM org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
Apr 1, 2004 9:35:13 AM
Re: Re: Re: Re: Installation Help Needed
No offense but sometimes we get burned by the silly little things. No offense taken. As a programmer I definitely have been bitten by the silly little things often enough that I'll try whatever. Everything seems to point to a firewall/router ACL issue. Are there any devices between the client and server? Doug Yup and it was. After I determined that tomcat was running and that I was able to view the start page with lynx (Man how could I have forgotten about lynx) I knew then it had to be firewall but I also knew it wasn't a blocked port. Everytime my firewall rules block something I log it and there was nothing there so I knew I opened the port up properly. Upon further inspection I realized that it was being redirected. One single line, easy to miss but it was me being lazy a while back. Basically my script closes every single port then I open up specific ones. Well I got tired of that and made a rule that redirected a group to another machine and 8080 (Which I never used before) was in that range. I took it out and voila it worked like a charm. Thanks for your help. I just know I'll have some other issues as I'm still new to tomcat. I have a client right now waiting to see something and I need to put something up there. I believe I have to create a context in server.xml so that he can do www.mydomain. com:8080/something. I've not done this before though. On my development machine I've used Netbeans to test and deploy stuff for me. Ah the learning never ends. :) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =- Stormblade (Shaolin Code Warrior) Software Developer (15+ Years Programming exp.) My System: http://www.anandtech.com/mysystemrig.html?rigid=1683 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -- Composed with Newz Crawler 1.7 http://www.newzcrawler.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
