Hi Jody,
I updated my test server from 2.20 to 2.21-M0 using the Windows installer. Basically logging worked, but I’m seeing less logging entries now for the DEFAULT_LOGGING configuration. For example, I’m missing the
…
2022-04-26 13:46:57,820 INFO [org.geoserver] - Loaded data store ‘***’, enabled
2022-04-26 13:46:59,413 INFO [org.geoserver] - Loaded feature type ‘***’, enabled
2022-04-26 13:46:59,429 INFO [org.geoserver] - Loaded layer ‘***’
…
2022-04-26 13:47:00,070 INFO [org.geoserver] - Read catalog in 3.422 s
2022-04-26 13:47:00,148 INFO [org.geoserver] - Loaded service ‘WMTSInfoImpl–44f35506:159d0de9a1e:-7fff’, disabled
…
entries after restarting the service. Is this intentional behaviour?
Sending the log output to a location outside of the GeoServer installation directory did work as before.
My previous *.properties configuration files have been deleted by the installer, which I had changed to reflect my needs (which maybe I shouldn’t have done??)
Changing the new *.xml configuration files didn’t work because they are reset to default after restarting the service. But this isn’t a problem because I was able to recreate my previous configuration (simple RollingFile appender with TimeBasedTriggeringPolicy) in a new profile xml file.
Switching between profiles works seamlessly without the need to restart the service.
Best regards
Daniel
···
–
Jody Garnett