Well, okay, this is odd...
My current site, which is a plain-jane JSP site, runs just fine with
the address set at http://localhost/antoniomalcolm/index.jsp (thanks
to my settings with Apache and mod_jk, however, I found, on a whim,
Magnolia still requires localhost:8080. With that, it still takes me
to an update page, but that page leads to where it's supposed to.
One down, database connectivity to go. And just maybe I'll take a
deeper look at my connector settings. There's nothing wrong with
them, per say, there are no more errors in the logs (maybe a good
reason for this happenstance), but maybe I can tweak them to give my
server setup greater dexterity.
~Antonio
On Jan 16, 2008, at 6:01 PM, David Smith wrote:
And what is in your logs? This works for me repeatedly out of the
box using MySQL. Unlike 3.0 and earlier you don't have to start
tomcat and then wait blindly for several minutes for the bootstrap
to finish. The install/update does all the bootstrapping. About
all that happens on initial tomcat start is the repository is
initialized and left empty until the install/update process.
--David
Antonio Malcolm wrote:
Hey all, I Just installed v3.5 on Tomcat v6.0.13 with Apache
v2.2.6 and mod_jk. I have Apache configured to handle html and php
files.
When first loading after installing, I get "Magnolia install/
update ...Magnolia needs to be updated." instead of the
AdminCentral page. And the update link, of course, does not work.
Also, I've tried getting it to work with the MySQL repository as
per Gregory Joseph's instructions, but that lands me with a 403
Access Forbidden error.
I have the database set up for the site, and correctly entered the
username, password, and database names in the xml file, as well as
followed the rest of the instructions (which I felt left a lot
out, to be honest), so what gives? Am I missing something here? Is
there a means for database connectivity which is more out-of-the
box than the JNDIPooledDatabasePersistenceManager? I noticed Derby
is installed, and that there are some other MySQL related files in
WEB-INF.
Well, first I suppose I should worry about making the generic
install work. I have no idea why it doesn't. Set Tomcat to a
minimum of 512m, drop the WAR package into WEBAPPS, start Tomcat,
give it time to expand and bootstrap, stop Tomcat, remove the WAR,
restart Tomcat.
Seems simple enough, but then again, I think too simple.
Thanks in advance for any advice,
~Antonio
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
