hi Dave,
your first log is the geoserver log -- that doesn't concern GeoNetwork, so
much. You second log is geonetwork.log which is relevant.
You don't have a "output.log" ? That's the one where, for me, the message
about "Started SocketListener.. " appears. However I also have in
geonetwork.log the message about "=== System working..", maybe that does
indicate something, after all.
So, indeed I see no errors in your log file.. looks fine, everything. Which
makes me wonder if you have some error in how you're addressing this
machine.
Could you check if you have a file called <this date>.request.log ? If
requests actually do arrive at Jetty, they would be logged there.
Another thing to try might be to use a text browser (lynx) on your target
machine itself, so you could use "localhost" and at least see if you get
some response from the application (although not too many things about it
will function without javascript).
Last tip I can think of now, is to set the logging level to DEBUG -- it will
give you more info in the log file.
But it does seem to me that your GeoNetwork application has started
correctly. I'd start investigating whether your addressing is correct.. try
to get it to work if you point to http://<ip address>:8080/geonetwork ?
regards
Heikki Doeleman
On Sun, Jul 12, 2009 at 7:40 AM, Dave Sampson <samper.d@anonymised.com> wrote:
heikki,
The /jetty/geoserver.log logs, See the full log here: (expires 30 days
from this post) http://pastebin.ca/1492350
I see a lot of geo related stuff but nothing about system upness.
For the /jetty/geonetwork.log see here: http://pastebin.ca/1492353
I could not find what you suggested... where might it be going wrong?
Since I am running headless (read no GUI, No Monitor) I have to log in
through SSH for the command line and when I point my browser to the page
I can't do localhost because that would infact be my local machine, but
the application is sitting on my headless server.
SO. I either need to point my browser to the local IP address or its
name it is known by on the network. For example the computer itself is
called AVALANCHE, so I have to point to http://avalanche.lan:8080
This name is picked up by the DNS and points it to that machine as its
localhost. Does that make sense?
I have many virtual servers running on it (I am learning how to
virtualize) and I want another domain to pick up geoserver for when I
push it out to the internet. for example some.domain.com:8080.
So far I would have to make the recommendation that for a headless
install it would be so much easier to do what most PHP projects do and
point to http://some.domain.com/geonetwork/installer and do the install
over a web interface. I know that it is different with java and tomcat
but a simple PHP page to act as an installer would help greatly IMHO.
Cheers
> hi Dave,
>
> could you look inside the log files to see if any error messages
> appeared ?
>
> Normally there is both output.log, which contains less information,
> and geonetwork.log, which contains more information.
>
> The "system ready" message does not mean that the system is actually
> ready (that would be a spoiler 
You should see some message saying
> something like "Started SocketListener on 0.0.0.0:8080
> <http://0.0.0.0:8080>". Then, it should be accessible on a browser
> pointing at http://localhost:8080/geonetwork.
>
> I'm not quite sure what you mean by " the localhost is actually
> processed through a hostname mapping but it
> should work." You're using Apache in front of it ? Maybe try to get it
> to work on its own first, and when that works, put Apache in play.
>
> Kind regards
> Heikki Doeleman
>
>
>
> On Fri, Jul 10, 2009 at 7:35 PM, Dave Sampson <samper.d@anonymised.com
> <mailto:samper.d@anonymised.com>> wrote:
>
> Alright,
>
> The issues was not with all the logs, but I guess just some logs or
> backup files that did not exist...
>
> When I run the script it goes through all of its startup processes
and
> gets to the ===system ready=== stage, but then I can not access
> the web
> interface.
>
> the localhost is actually processed through a hostname mapping but it
> should work.
>
> Where do I go from here?
>
> Cheers
> > Dave Sampson wrote:
> >> should I not start the script from the bin directory?
> >
> > You _must_ start the scripts from
> > the bin directory.
> >
> > > where are the logs directories?
> >
> > Have a look in the start-geonetwork.sh script.
> > The very first line is "cd ../jetty".
> > And that's where you'll find the logs,
> > namely, in jetty/logs.
> >
>
>
>
------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge
> This is your chance to win up to $100,000 in prizes! For a limited
> time,
> vendors submitting new applications to BlackBerry App World(TM)
> will have
> the opportunity to enter the BlackBerry Developer Challenge. See
> full prize
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> GeoNetwork-users mailing list
> GeoNetwork-users@lists.sourceforge.net
> <mailto:GeoNetwork-users@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/geonetwork-users
> GeoNetwork OpenSource is maintained at
> http://sourceforge.net/projects/geonetwork
>
>
You should see some message saying