I know spacewalk doesn't have it's own tomcat, the install pulls
everything it needs it, so I started with a base stripped down CentOS,
followed their instructions and this is where I got from using the
standard installer. There is also a yum repo for the packages so it's
at the latest version. I'm thinking what might work best is just to
wipe the VM with a fresh OS install and try the install again and see
what happens. I got no errors during the install, so it all appeared
to be working until I went to login :)
I'll probably poke at this a little more, because despite the
potentially broken/outdated package that won't change if I re-install,
it seems like something might be missing from the config that if I
could get that it'd be working.
RHN is the management console that on the commercial side Red Hat uses
to manage the Red Hat Enterprise licenses and clients, this is just
the opensource version of that.
Dan
On Oct 1, 2009, at 3:11 AM, André Warnier wrote:
To agree and augment on everything Peter wrote, the whole thing
stinks of a very broken installation and configuration package, or
packages.
Not for lack of desire to help, but I believe you should really go
back to the spacewalker (or CentOS) help forum, and enquire there
about working packages for your specific platform.
We have no idea what is needed by this application. It seems that
you have indeed some kind of Tomcat installed now, with some /rhn
webapp half-installed in it. On the other hand, some other bits and
pieces needed by that /rhn webapp appear to be missing, and some
standard parts of Tomcat also (like the version.sh script).
Even the standard Tomcat 8005 shutdown port doesn't seem to be
there, which as Peter wrote is very strange.
I am starting to wonder if this CentOS spacewalker package is not
installing its own embedded Tomcat, which conflicts with another one
already installed.
Alternatively, you could try to de-install what you have installed
so far, then install *only* the latest CentOS pure-Tomcat package
you can find, and test if that one, on its own, works.
Test it by simply calling the URL http://your-hostname:8080 in your
browser. You should then get some Tomcat page, with an easily
recognisable cat on it.
Most standard Tomcat packages I have seen so far, have Tomcat
configured so that it will, by default, listen on 3 ports :
- port 8005 : that's Tomcat's "shutdown port"; you see it in the
server.xml file as an attribute to the <Server> tag.
- port 8080 : that's Tomcat's standard HTTP connector, which allows
you to use it as a standard webserver (that one, you will find in a
<Connector ... protocol="HTTP"> tag in server.xml
- port 8009 : that is Tomcat's standard listening port for the AJP
connector, another <Connector> tag in server.xml. This one may or
may not be activated, depending on how the CentOS packagers
structured their stuff. It may only get installed/activated if you
install another complementary package containing mod_jk or
mod_proxy_ajp, and this complementary package may in turn depend on
the Apache httpd package being installed.
And so on...
Variations are endless, and depend on the whims and competence of
whoever creates these packages for each platform.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
