[Geoserver-users] Log level

Aitor_Calero_Garcia · August 27, 2007, 12:59pm

I am trying to change Log level messages to other value, but when I choose other tan ALL, Geosever always put ALL as log level, no matter what I choose.

Also log file does not ever get created, no matter what I put in Server Configuration. I am using GeoServer 1.5.2.

I’m sorry being so insistent with this problem, but I really need to have a log file configured.

<br>-- <br>                                                                                     Aitor Calero García<br>                                                                             [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                            [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                              Atos Research & Innovation<br>                                                                                       Atos Origin Spain<br>                                                               C/ Albarracín, 25 - 28037 Madrid (Spain)                                               <br>                                                                                Tel.  (+34)  91 214 8805 <br>                                                                                 Fax. (+34)  91 754 3252<br>                                                                              [http://www.atosresearch.eu](http://www.atosresearch.eu)<br>                                            Before printing this e-mail, think if it is really necessary<br><br>

Andrea_Aime3 · August 27, 2007, 1:26pm

Aitor Calero García ha scritto:

I am trying to change Log level messages to other value, but when I choose other tan ALL, Geosever always put ALL as log level, no matter what I choose.

Also log file does not ever get created, no matter what I put in Server Configuration. I am using GeoServer 1.5.2.

I'm sorry being so insistent with this problem, but I really need to have a log file configured.

I don't understand what's going on in your case... things seem to be
working fine for me. When you are setting the log level and log to file,
are you doing the usual "submit, apply, save" cycle?
Have you tried restarting GeoServer after saving the changes (should not
needed, but just to make sure).
Is there any chance the process is not allowed to create the log file
where it wants because of security restrictions on the file system?

Cheers
Andrea

Aitor_Calero_Garcia · August 28, 2007, 6:35am

El lun, 27-08-2007 a las 15:26 +0200, Andrea Aime escribió:

I don't understand what's going on in your case... things seem to be
working fine for me. When you are setting the log level and log to file,
are you doing the usual "submit, apply, save" cycle?

Of course

Have you tried restarting GeoServer after saving the changes (should not
needed, but just to make sure).

Yes I have restarted geoserver always.

Is there any chance the process is not allowed to create the log file
where it wants because of security restrictions on the file system?

I will check this out, but I have installed geoserver in my home directory, so I think that is not the case.


Cheers
Andrea

<br>-- <br>                                                                                     Aitor Calero García<br>                                                                             [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                            [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                              Atos Research & Innovation<br>                                                                                       Atos Origin Spain<br>                                                               C/ Albarracín, 25 - 28037 Madrid (Spain)                                               <br>                                                                                Tel.  (+34)  91 214 8805 <br>                                                                                 Fax. (+34)  91 754 3252<br>                                                                              [http://www.atosresearch.eu](http://www.atosresearch.eu)<br>                                            Before printing this e-mail, think if it is really necessary<br><br>

Andrea_Aime3 · August 28, 2007, 6:38am

Aitor Calero García ha scritto:

El lun, 27-08-2007 a las 15:26 +0200, Andrea Aime escribió:

I don't understand what's going on in your case... things seem to be
working fine for me. When you are setting the log level and log to file,
are you doing the usual "submit, apply, save" cycle?

Of course

Have you tried restarting GeoServer after saving the changes (should not
needed, but just to make sure).

Yes I have restarted geoserver always.

Is there any chance the process is not allowed to create the log file
where it wants because of security restrictions on the file system?

I will check this out, but I have installed geoserver in my home directory, so I think that is not the case.

Home directory on windows? We had code choke in the past because of
spaces in the path... can you check by moving GeoServer on a path
that does not have spaces inside?

Cheers
Andrea

Aitor_Calero_Garcia · August 28, 2007, 7:08am

Home directory on windows? We had code choke in the past because of
spaces in the path... can you check by moving GeoServer on a path
that does not have spaces inside?

No, I am using Ubuntu/Linux, and there are no spaces in the path. But now, surprisingly, Geoserver fail to start and shows the following error. Things seems to get more complicated now!!!

3649 [FINA] org.vfny.geoserver.global.GeoServer - Creating GeoServer

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] Oops: 0000 [#2]

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] SMP

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] CPU: 0

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] EIP: 0060:[find_get_page+38/96] Tainted: P VLI

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] EFLAGS: 00210002 (2.6.20-16-generic #2)

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] EIP is at find_get_page+0x26/0x60

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] eax: 008b2a64 ebx: 0000007e ecx: 008b2a64 edx: 00000000

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] esi: de7b6178 edi: de7b6178 ebp: dc8e1180 esp: ddd95ec4

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] ds: 007b es: 007b ss: 0068

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] Process java (pid: 22707, ti=ddd94000 task=c217d030 task.ti=ddd94000)

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] Stack: 00000117 00000000 c0159a13 c017f2b7 00200246 ddd95f60 f31a4668 dc8e11c8

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] de7b60d4 0000007e 00000000 00000002 c03a9b08 00000001 8b7ff000 c0429e80

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] c016445a f559ef40 c01022c5 dfe401e0 00000001 00000005 00000001 00000000

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] Call Trace:

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] [filemap_nopage+339/928] filemap_nopage+0x153/0x3a0

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] [getname+167/208] getname+0xa7/0xd0

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] [__handle_mm_fault+330/2624] __handle_mm_fault+0x14a/0xa40

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] [__switch_to+341/496] __switch_to+0x155/0x1f0

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] [do_page_fault+296/1520] do_page_fault+0x128/0x5f0

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] [do_page_fault+0/1520] do_page_fault+0x0/0x5f0

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] [error_code+124/144] error_code+0x7c/0x90

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] =======================

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] Code: bf 00 00 00 00 83 ec 08 89 74 24 04 89 c6 8d 40 10 89 1c 24 89 d3 e8 7a 79 19 00 8d 46 04 89 da e8 c0 7c 09 00 85 c0 89 c1 74 0d <8b> 00 89 ca f6 c4 40 75 1f f0 ff 42 04 f0 ff 46 10 fb 90 8d b4

Message from syslogd@anonymised.com at Tue Aug 28 09:05:07 2007 …
localhost kernel: [510031.932000] EIP: [find_get_page+38/96] find_get_page+0x26/0x60 SS:ESP 0068:ddd95ec4


Cheers
Andrea

<br>-- <br>                                                                                     Aitor Calero García<br>                                                                             [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                            [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                              Atos Research & Innovation<br>                                                                                       Atos Origin Spain<br>                                                               C/ Albarracín, 25 - 28037 Madrid (Spain)                                               <br>                                                                                Tel.  (+34)  91 214 8805 <br>                                                                                 Fax. (+34)  91 754 3252<br>                                                                              [http://www.atosresearch.eu](http://www.atosresearch.eu)<br>                                            Before printing this e-mail, think if it is really necessary<br><br>

Andrea_Aime3 · August 28, 2007, 7:12am

Aitor Calero García ha scritto:

Home directory on windows? We had code choke in the past because of
spaces in the path... can you check by moving GeoServer on a path
that does not have spaces inside?

No, I am using Ubuntu/Linux, and there are no spaces in the path. But now, surprisingly, Geoserver fail to start and shows the following error. Things seems to get more complicated now!!!

Well, this error seems to occurr in the Linux kernel paging code...
any recent kernel upgrades?

Cheers
Andrea

Aitor_Calero_Garcia · August 28, 2007, 7:29am

El mar, 28-08-2007 a las 09:12 +0200, Andrea Aime escribió:

Well, this error seems to occurr in the Linux kernel paging code...
any recent kernel upgrades?

No, only updates from Ubuntu repositories, anyway I’ve restarted Ubuntu, and now Geoserver works again, but the only log file that is created is this one (2007_08_28.request.log). Need to mention that I am using stand alone Geoserver version, not the war version.


Cheers
Andrea

<br>-- <br>                                                                                     Aitor Calero García<br>                                                                             [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                            [aitor.calero@anonymised.com](mailto:aitor.calero@anonymised.com)<br>                                                                              Atos Research & Innovation<br>                                                                                       Atos Origin Spain<br>                                                               C/ Albarracín, 25 - 28037 Madrid (Spain)                                               <br>                                                                                Tel.  (+34)  91 214 8805 <br>                                                                                 Fax. (+34)  91 754 3252<br>                                                                              [http://www.atosresearch.eu](http://www.atosresearch.eu)<br>                                            Before printing this e-mail, think if it is really necessary<br><br>

Andrea_Aime3 · August 28, 2007, 8:02am

Aitor Calero García ha scritto:

El mar, 28-08-2007 a las 09:12 +0200, Andrea Aime escribió:

Well, this error seems to occurr in the Linux kernel paging code...
any recent kernel upgrades?

No, only updates from Ubuntu repositories, anyway I've restarted Ubuntu, and now Geoserver works again, but the only log file that is created is this one (2007_08_28.request.log). Need to mention that I am using stand alone Geoserver version, not the war version.

The GeoServer log files should be created in $geoserverInstallDir/data_dir/logs/. The one you're looking at is the container log file, we don't have any control on that one.

You don't have any files in that dir either?
Cheers
Andrea

GIS · September 7, 2007, 8:31am

Aitor Calero García wrote:

I am trying to change Log level messages to other value, but when I choose other tan ALL, Geosever always put ALL as log level, no matter what I choose.

Also log file does not ever get created, no matter what I put in Server Configuration. I am using GeoServer 1.5.2.

I'm sorry being so insistent with this problem, but I really need to have a log file configured.

Are you running under Tomcat? I had a similar problem configuring GeoServer logs until I realised that the GeoServer logs were not being written to the location I had specified, but to the standard Tomcat logs instead.