Hi,
I've scanned the forums on this topic and haven't found a solution to my
problem though I've seen there's been some tweaks and discussion on
GeoServer logging.
Running 1.6 Beta 3, no matter what I do, the geoserver.log file is empty.
I've installed GeoServer from scratch on XP into C:\GeoServer, using
JAVA_HOME set to C:\Program Files\Java\jdk1.5.0_07. Using Config - Server,
I've placed check marks in the Verbose and VerboseExceptions options,
selected VERBOSE_LOGGING.properties for the Logging Profile, and have left
the default Log Location set to logs/geoserver.log. No matter which Logging
Profile I select, the geoserver.log is empty.
In the console, I see the following two lines that caught my eye:
log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
That 'WARN File option' bit suggests to me that there is something not
switched on to write out the file? There is such a thing (I think) in
1.5.3:
I removed 1.6 Beta 3 and installed from scratch 1.5.3. The Config - Server
options I note are slightly different. I select the 'ALL' for the Logging
Level, placed a check mark in front of Write logs to file (an option not
present in 1.6 Beta 3), and left the default log location at
logs/geoserver.log. After saving this, I can see a lot of information
stored in the C:\GeoServer\data_dir\logs\geoserver.log file.
Any help greatly appreciated.
Thanks, Bob
--
View this message in context: http://www.nabble.com/Problem-setting-up-logging---log-files-are-empty-tf4671333.html#a13344893
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
A note to the reader...
I am now getting information into the geoserver.log now that I've converted
from using Jetty to using Tomcat 5.5.
Thanks, Bob
Bob Nutsch wrote:
Hi,
I've scanned the forums on this topic and haven't found a solution to my
problem though I've seen there's been some tweaks and discussion on
GeoServer logging.
Running 1.6 Beta 3, no matter what I do, the geoserver.log file is empty.
I've installed GeoServer from scratch on XP into C:\GeoServer, using
JAVA_HOME set to C:\Program Files\Java\jdk1.5.0_07. Using Config -
Server, I've placed check marks in the Verbose and VerboseExceptions
options, selected VERBOSE_LOGGING.properties for the Logging Profile, and
have left the default Log Location set to logs/geoserver.log. No matter
which Logging Profile I select, the geoserver.log is empty.
In the console, I see the following two lines that caught my eye:
log4j:WARN File option not set for appender [geoserverlogfile].
log4j:WARN Are you using FileAppender instead of ConsoleAppender?
That 'WARN File option' bit suggests to me that there is something not
switched on to write out the file? There is such a thing (I think) in
1.5.3:
I removed 1.6 Beta 3 and installed from scratch 1.5.3. The Config -
Server options I note are slightly different. I select the 'ALL' for the
Logging Level, placed a check mark in front of Write logs to file (an
option not present in 1.6 Beta 3), and left the default log location at
logs/geoserver.log. After saving this, I can see a lot of information
stored in the C:\GeoServer\data_dir\logs\geoserver.log file.
Any help greatly appreciated.
Thanks, Bob
--
View this message in context: http://www.nabble.com/Problem-setting-up-logging---log-files-are-empty-tf4671333.html#a13416283
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
Bob Nutsch ha scritto:
A note to the reader...
I am now getting information into the geoserver.log now that I've converted
from using Jetty to using Tomcat 5.5.
Which version of Jetty were you using?
Cheers
Andrea
Hi,
I was using the default Jetty that installs when using the
'geoserver-1.6-beta3.exe' version of GeoServer. I believe that I saw
6.02 in the console during startup of GeoServer.
Regards, Bob
-----Original Message-----
From: Andrea Aime [mailto:aaime@anonymised.com]
Sent: Friday, October 26, 2007 2:31 AM
To: Nutsch, Bob D.
Cc: geoserver-devel@lists.sourceforge.net
Subject: Re: [Geoserver-devel] Problem setting up logging -
log files are empty
Bob Nutsch ha scritto:
> A note to the reader...
>
> I am now getting information into the geoserver.log now that I've
> converted from using Jetty to using Tomcat 5.5.
Which version of Jetty were you using?
Cheers
Andrea
Nutsch, Bob D. ha scritto:
Hi,
I was using the default Jetty that installs when using the
'geoserver-1.6-beta3.exe' version of GeoServer. I believe that I saw
6.02 in the console during startup of GeoServer.
What you were seeing is probably:
http://jira.codehaus.org/browse/GEOS-1444
Maybe the tomcat install you have is located in a path without any
spaces whilst the exe did have at least one in the path.
Cheers
Andrea
Hi Andrea,
Yes, that is mostly correct. The .exe that I installed did have spaces in
the path initially, but when trying to fix the problem of the logging
options not being editable within Config->Server (they were grayed out), I
switched over to installing the .exe into c:\geoserver. The logging options
were then configurable (but still no output to geoserver.log.
When I first tried to implement GeoServer with Tomcat, I had Tomcat under
'Program Files' (I used the default install path) and in that mode when
trying to deploy, the deploy failed (but I did get a geoserver.log!) and in
the log and in the console, there appeared to be problems with paths to
classpaths and possibly other entities.
I then uninstalled Tomcat and reinstalled to C:\Tomcat55 and I could then
deploy GeoServer and the geoserver.log had content in it.
So, spaces aren't good. 
My Java 1.5.0_13 is however still in a spaced
out directory: C:\Program Files\Java.
Regards, Bob
aaime wrote:
Nutsch, Bob D. ha scritto:
Hi,
I was using the default Jetty that installs when using the
'geoserver-1.6-beta3.exe' version of GeoServer. I believe that I saw
6.02 in the console during startup of GeoServer.
What you were seeing is probably:
http://jira.codehaus.org/browse/GEOS-1444
Maybe the tomcat install you have is located in a path without any
spaces whilst the exe did have at least one in the path.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
View this message in context: http://www.nabble.com/Problem-setting-up-logging---log-files-are-empty-tf4671333.html#a13427821
Sent from the GeoServer - Dev mailing list archive at Nabble.com.
Hi,
I should have noted that part of my "recipe" for getting GeoServer deployed
to Tomcat on XP included putting tomcat under C:\Tomcat55 and installing the
JAI files. Once I did BOTH, the install to C:\Tomcat55 AND installing the
JAI files, THEN I was good to go.
Regards, Bob
Bob Nutsch wrote:
Hi Andrea,
Yes, that is mostly correct. The .exe that I installed did have spaces in
the path initially, but when trying to fix the problem of the logging
options not being editable within Config->Server (they were grayed out), I
switched over to installing the .exe into c:\geoserver. The logging
options were then configurable (but still no output to geoserver.log.
When I first tried to implement GeoServer with Tomcat, I had Tomcat under
'Program Files' (I used the default install path) and in that mode when
trying to deploy, the deploy failed (but I did get a geoserver.log!) and
in the log and in the console, there appeared to be problems with paths to
classpaths and possibly other entities.
I then uninstalled Tomcat and reinstalled to C:\Tomcat55 and I could then
deploy GeoServer and the geoserver.log had content in it.
So, spaces aren't good. My Java 1.5.0_13 is however still in a
spaced out directory: C:\Program Files\Java.
Regards, Bob
aaime wrote:
Nutsch, Bob D. ha scritto:
Hi,
I was using the default Jetty that installs when using the
'geoserver-1.6-beta3.exe' version of GeoServer. I believe that I saw
6.02 in the console during startup of GeoServer.
What you were seeing is probably:
http://jira.codehaus.org/browse/GEOS-1444
Maybe the tomcat install you have is located in a path without any
spaces whilst the exe did have at least one in the path.
Cheers
Andrea
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
View this message in context: http://www.nabble.com/Problem-setting-up-logging---log-files-are-empty-tf4671333.html#a13428209
Sent from the GeoServer - Dev mailing list archive at Nabble.com.