Re: Re: Re: Re: Installation Help Needed

2004-04-01 Thread Stormblade
> 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]



Re: Re: Re: Installation Help Needed

2004-04-01 Thread Parsons Technical Services
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 s

Re: Re: Re: Installation Help Needed

2004-04-01 Thread QM
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

2004-04-01 Thread Stormblade
> 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 

INFO: Initializing, config='org.apache.struts.util.LocalStrings', 
returnNull=true

Apr 1, 2004 9:35:15 AM org.apache.struts.util.
PropertyMessageResources 

INFO: Initializing, config='org.apache.struts.action.ActionResources',
 returnNull=true

Apr 1, 2004 9:35:16 AM org.apache.struts.util.
PropertyMessageResources 

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 
file:/usr/local/jakarta-tom

Re: Re: Installation Help Needed

2004-04-01 Thread QM
On Thu, Apr 01, 2004 at 10:14:52AM -0500, Stormblade wrote:
: Forgive me but I'm unfamiliar with that command. I typed it exactly 
: as you had it above. Copy and paste even.

For the archives:

lsof is a tool to LiSt Open Files.  It lets admins match a port to a
process, among other things.  Invaluable for troubleshooting.

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.


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"


: I did do a lsof -i -a and got a listing. I didn't see tomcat user or 
: anything that said tomcat even. Was I supposed to create a tomcat 
: user? I installed tomcat from the rpm.

I believe the RPM creates a user and group "tomcat" for you.  


-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: Installation Help Needed

2004-04-01 Thread Stormblade
> On Thu, Apr 01, 2004 at 12:16:49AM -0500, Stormblade wrote:

> : Then I tried to access my box from another machine and there

> : is no answer. www.mymachinedomain:8080 doesn't even give me the 
default

> : page.

> 

> 

> What's the result of

> 

>  lsof -i -a -u {tomcat user}

> 

> ?

> 

> -or better still,

> 

>  lsof -n -i -a -u {tomcat user}  ## show IP addresses

lsof: can't get UID for {tomcat

lsof 4.63

 latest revision: ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/

 latest FAQ: ftp://vic.cc.purdue.edu/pub/tools/unix/lsof/FAQ

 latest man page: ftp://vic.cc.purdue.
edu/pub/tools/unix/lsof/lsof_man

 usage: [-?abhlnNoOPRstUvV] [-c c] [+|-d s] [+D D] [+|-f]

 [-F [f]] [-g [s]] [-i [i]] [+|-L [l]] [+|-M] [-o [o]] [-p s]

 [+|-r [t]] [-S [t]] [-T [t]] [-u s] [+|-w] [--] [names]

Use the ``-h'' option to get more help information.



Forgive me but I'm unfamiliar with that command. I typed it exactly 
as you had it above. Copy and paste even.

I did do a lsof -i -a and got a listing. I didn't see tomcat user or 
anything that said tomcat even. Was I supposed to create a tomcat 
user? I installed tomcat from the rpm.

> 

> Does that IP address match what your workstation (browser) thinks 
is

> www.mymachinedomain? e.g. do you have some sort of split-domain DNS

> going, or a rogue hosts file?

> 

> -QM

> 

> -- 

> 

> software  -- http://www.brandxdev.net

> tech news -- http://www.RoarNetworX.com

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-

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]



Re: Re: Installation Help Needed

2004-04-01 Thread Stormblade
Woo almost missed this one cuz it wasn't threaded under the others in 
my newsreader. Anyway, thanks for the reply.

I have opened the port. I have done this for several other 
applications over the years. Games too so I know what I'm doing in 
that respect. However, I'm still not sure about Tomcat. I don't know 
if I configured things correctly or anything like that.

What do you mean change the port in the admin console. The only 
changing of ports I saw was to edit the server.xml file directly 
which I didn't do since port 8080 works just fine for my purposes 
here.

> read on linux site about opening port :server port on the firwall  
or change 

> the port in the

> admin console off tomcatl

> 

> 

> 

> [EMAIL PROTECTED]

> administrateur http://entre-nous.qc.tc





-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-

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]



Re: Re: Installation Help Needed

2004-04-01 Thread Stormblade
> This is almost certainly because you're running a firewall. It's 
kind of 

> an involved topic, and not one I'm an expert on anyway, so you 
should 

> check out this:

> 

> http://www.tldp.org/HOWTO/Firewall-HOWTO.html



Thank you for the reply. Yes I am running a firewall but I am 
familiar with it as I have been running it for years. I have opened 
port 8080 as I have other ports when I needed to. 

> > Beware: many distros have customized firewall software. Anyway, 
this 

> isn't a tomcat problem.



I run iptables. I suppose it could be a firewall problem, however, I 
am able to run other servers like Apache just fine but yet Tomcat is 
not. Perhaps there is some configuration that I failed to do with 
Tomcat or should it work right out the box with no modifications 
needed?

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-

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]



Re: Re: Installation Help Needed

2004-04-01 Thread Stormblade
> Back to basics.

> 

> Is it running?

> Look at your processes with something like  >ps -ax



As far as I can tell yes. There is a line which I believe indicates 
it's running but it gets cut off and I don't remember how to make it 
word wrap. Re-directing it to a file is worse.

/usr/java/j2sdk1.4.2_04//bin/java -Djava.endorsed.
dirs=/usr/local/jakarta-tomcat-5.0.19/common/endorsed -classpath

> 

> Do you have a firewall running?



Yes I use iptables and I run my own customized script. I have opened 
port 8080.

> 

> Can you ping the machine?



No because I drop those packets. Part of my firewall script, however, 
this machine is definitely accessible from the outside. Apache is 
running happily there as is a Cold Fusion Application server. I can 
get to my web pages just fine.

> 

> Do a  netstat -an  and see if port 8080 is active.



tcp0  0 0.0.0.0:80800.0.0.0:*   
LISTEN 

If I'm reading this right then yes it's active.

> 

> Doug



-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
=-

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]